Hi Pascal,
Thanks for the Primo-suggestions. One thing I should probably have
added besides some confidential information, the collection will also
be only useful for a small number of scholars working with this
specific collection and not something anyone else would probably be
all that interested in. Thus having the collection in something that
combines it with other collections is not a requirement and might even
be considered an impediment. That said, I'll check out your
suggestions.
Thanks,
Edward
On Wed, Mar 16, 2011 at 11:17 AM, Pascal Calarco <[log in to unmask]> wrote:
> Hi Edward --
>
> I am not sure if you're allowed to tweak normalization and pipe rules for the hosted Primo you have, but if the confidential information were in fairly consistent fields, you could either 1) make this a collection that is only searchable for authenticated Primo users or 2) define a regex normalization rule that strips out the confidential information (although you may want to retain that for staff to see), or 3) retain the information in the PNX record, but not add it to the display section with a regex normalization rule (so staff users could still see these with the view PNX option, but general users would not see these fields). Just some ideas from the Primo end of things.
>
> - pascal
>
> ---
> Pascal Calarco
> Head, Library Information Systems
> Hesburgh Libraries, University of Notre Dame /
> Michiana Academic Library Consortium
> Notre Dame, IN
> http://www.library.nd.edu/
> ________________________________________
> From: Code for Libraries [[log in to unmask]] On Behalf Of Edward M. Corrado [[log in to unmask]]
> Sent: Wednesday, March 16, 2011 11:00 AM
> To: [log in to unmask]
> Subject: [CODE4LIB] Simple Web-based Dublin Core search engine?
>
> Hi,
>
> I [will soon] have a small set (< 1000 records) of Dublin Core
> metadata published in OAI_DC format that I want to be searchable via a
> Web browser. Normally we would use Ex Libris's Primo for this, but
> this particular set of data may have some confidential information and
> our repository only has minimal built in search functions. While we
> still may go with Primo for these records, I am looking for at other
> possibilities. The requirements as I see them are:
>
> 1) Can ingest records in OAI_DC format
> 2) Allow remote end-users who are familiar with the collection search
> these ingest records via a Web browser.
> 3)Search should be keyword anywhere or individual fields although it
> does not need to have every whizzbang feature out there. In other
> words, basic search feature are fine.
> 4) Should support the ability to link to the display copy in our
> repository (probably goes without saying)
> 5) Should be simple to install and maintain (Thus, at least in my
> mind, eliminating something like Blacklight)
> 6) Preferably a LAMP application although a Windows server based
> solution is a possibility as well
> 7) Preferably Open Source, or at least no- or low-cost
>
> I haven't been able to find anything searching the Web, but it seems
> like something people may have done before. Before I re-invent the
> wheel or shoe-horn something together, does anyone have any
> suggestions?
>
> Edward
>
|
