[Archon-L] User Defined Fields
Jason Fowler
jfowler at sbts.edu
Fri Feb 23 14:46:08 MST 2007
Thanks, Chris. One of my workers asked. I thought it probably was by design. I am indifferent about it. It's one of those things we can work around.
-jf
-----Original Message-----
From: archon-bounces at archon.org [mailto:archon-bounces at archon.org]On
Behalf Of Chris Prom
Sent: Friday, February 23, 2007 4:42 PM
To: archon at archon.org
Subject: Re: [Archon-L] User Defined Fields
Jason,
Yes, they are specifically excluded by design--It was a decision
I made, so you can blame or thank me for it. My rationale was
partially to keep the search response times robust and partially
since most of the fields would not typically include an access
point that would not appear somewhere else in the descriptive
record, e.g. at a higher level or in the title or scopecontent.
The search does hit against title and scopecontent fields
throughout Archon, so any keywords that need to be access points
should be put in those fields.
Thanks,
Chris
--
Christopher J. Prom
Assistant University Archivist
University of Illinois Archives
19 Library
1408 W. Gregory Dr.
Urbana, IL 61801
phone: 217.333.0798
fax: 217.333.2868
e-mail: prom at uiuc.edu
web: http://web.library.uiuc.edu/ahx
On Fri, 23 Feb 2007, Jason Fowler wrote:
> I noticed that the search function does not seem to be able to search the user defined fields. Is this by design?
>
> Jason Fowler, C.A.
> Archives and Special Collections Librarian
> The Southern Baptist Theological Seminary
> jfowler at sbts.edu
> 502-897-4573
>
>
_______________________________________________
Archon mailing list
Archon at archon.org
http://archon.org/mailman/listinfo/archon_archon.org
More information about the Archon
mailing list