From: Demian K. <dem...@vi...> - 2011-07-27 16:37:44
|
Regarding EAD files, have you seen Eric Lease Morgan's work on the subject? http://www.catholicresearch.net/blog/2010/10/indexing-ead/ It uses Perl scripts and in some ways is tailored to the CRRA portal, but perhaps you can reuse some of it. If you come up with a more generic, PHP-oriented variation, I'd definitely be interested in getting more EAD tools into the trunk. - Demian > -----Original Message----- > From: Alan Rykhus [mailto:ala...@mn...] > Sent: Wednesday, July 27, 2011 12:33 PM > To: vuf...@li... > Subject: Re: [VuFind-Tech] Collections Module outline > > Hello Eoghan, > > Since we do something similar with our MnPALS implementation I'm very > interested in this. I'm also looking at doing something similar for a > library we will be bringing up shortly(mid August) on VuFind 1.1. > > I do have a couple of comments. > > Instead of creating an additional Solr field, couldn't you use some > combination of the building, institution, and collection fields? Since > you will need a record driver, using the current fields would allow > searching everything at once. This is something that the library we are > bringing up would like. It would still allow you to have the other > features you are looking at. Searches could be limited by institution > or > something. We do that with something like this: > http://plus.mnpals.net/catalog/MSU > > The record driver would know how to handle the fields. Adding the > ability to limit searches to an institution(think collection level) and > collection(think head-of-collection) would be great. > > I noticed someone commented about EAD records. This is the type of > records I plan on adding to VuFind. So again, I'm very interested. > > al > > On Wed, 2011-07-27 at 16:30 +0100, Eoghan Ó Carragáin wrote: > > Hi, > > We hope to do some work on a Collections Module over the next few > > weeks & wanted to run our current plans past the list, so hopefully > > our design will be reusable in the trunk. > > > > Requirements: > > 1) A splash page for the collection to include some or all of the > > following > > > > * Collection name and any available collection-level > > metadata/descriptions > > * Facets & facet counts for items in the collection, e.g. > > display all topics, persons, genre etc from Solr (something > > like what the Open Library display for their Work-level > > Records: > > http://openlibrary.org/works/OL8721462W/Great_Expectations) > > * Links to sub-collections where present (e.g. > > http://digital.library.villanova.edu/Catholica%20Collection/) > > * The first page of a result set for items in the collection > > (much like how the current author module works: e.g. > > > http://vufind.org/demo_trunk/Author/Home?author=Yeats%2C%20W.% > > 20B.%201865-1939.) > > * An archival tree display where available (see > > http://vufind.org/jira/browse/VUFIND-421) > > * Human-readable collection URLS (e.g. > > http://www.vufind.org/Collections/The+VuFind+Archive > > * Any other widget ... > > 2) A means of browsing/searching a list of collections > > > > Approach: > > 1) > > The cleanest design seems to be to create a new Vufind module > > (ie /web/services/Collections). > > > > In terms of where to get the collection data from, we were thinking > of > > having collection-level records (ie the absolute parent record for > the > > collection and records for any sub-collections) in the standard Solr > > biblio core. These records/Solr-documents would carry all the > > collection-level metadata need by the splash page. They could either > > be hidden from the normal result set or, when presented in a normal > > result, would link to the collection splash page rather than a normal > > record page. > > > > We would also need to use two Solr fields, the existing "collection" > > field and a new "head_of_collection" field. The collection field will > > be populated for all items in a collection and will contain a string > > of the title of the parent collection (i.e. either the name of the > > overall collection or the name of the sub-collection the item is in). > > The "head_of_collection" field will only be populated by the > > collection-level record and any sub-collection-level records, & will > > again contain the name of that collection. These values should allow > > us to display the correct information on the collection splash page. > > They will also allow easy faceting on items in a given collection > and, > > with some new apache rewrite rules, should allow urls of the form > > http://vufind.org/Collections/Name+From+Solr+Collection+Field. In > > MARC, we expect to populate these values using a custom beanshell > > script using values from 773 tags and/or the LEADER/07 (The National > > Library of Australia uses 773 and other tags to achieve something > > similar again with records in the biblio index, see > > http://catalogue.nla.gov.au/Record/4664435). Using Solr fields as the > > filter should hopefully make this pretty reusable for non-marc data, > > so long as you can map your collection info into the biblio Solr > > fields and populate these two filters fields discussed above. > > > > > > The Collection module uses CollectionRecord.php(like record uses > > record.php, but simpler in that we don’t envisiage different tabs at > > the moment) which will look up the item bib_id from the collection > > title in the url. CollectionRecord.php can then call a new > > RecordDriver function called getCollectionMetadata() from IndexRecord > > to retrieve information from the collection level record. > > CollectionRecord also has a Solr SearchObject child records for the > > initial result set (like the Author module) and things like facet > > counts etc. > > > > 2) A browse interface for collection-level recods should be > reasonably > > straight-forward using the two Solr fields above. > > > > Any thoughts or observations very welcome. David, we'd be > particularly > > interested to hear how this fits with VuDL/Vufind plans. We don't > want > > to reinvent the wheel (or pre-invent it badly!). > > > > Thanks > > Eoghan > > --------------------------------------------------------------------- > --------- > > Got Input? Slashdot Needs You. > > Take our quick survey online. Come on, we don't ask for help often. > > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > > http://p.sf.net/sfu/slashdot-survey > > _______________________________________________ > > Vufind-tech mailing list > > Vuf...@li... > > https://lists.sourceforge.net/lists/listinfo/vufind-tech > > -- > Alan Rykhus > PALS, A Program of the Minnesota State Colleges and Universities > (507)389-1975 > ala...@mn... > "It's hard to lead a cavalry charge if you think you look funny on a > horse" ~ Adlai Stevenson > > > ----------------------------------------------------------------------- > ------- > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > _______________________________________________ > Vufind-tech mailing list > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech |