Hi, On 12/3/07, Chris Nighswonger <[EMAIL PROTECTED]> wrote: > On 12/2/07, Joshua Ferraro <[EMAIL PROTECTED]> wrote: > > Or perhaps it's 'bout time' we take advantage of Zebra's ability to index > > multiple formats and create a set of Dublin Core frameworks? :-) > > Whew! Just took a look at www.dublincore.org and it looks like I need > a Dublincore-101 course or the short version or something. :-)
FWIW, Dublin Core started out *as* the short version. :) If you ignore most of the cruft, http://www.dublincore.org/documents/dcmi-terms/ has the gist of it -- DC is just a relatively small set of elements for a metadata record describing a resource. > So explain a bit more. I was thinking of a "simple" mapping from MARC > to id3v2 frames. Are you suggesting MARC to DC to id3v2? And how does > Zebra fit in here? (Sorry if these are simple questions?) More like a mapping from id3v2 to DC, like one found at http://age.hobba.nl/audio/tag_frame_reference.html. I'm not vouching for that specific mapping, by the way, but it is an example. Once you map from id3v2, you can express DC as XML, then have Zebra index the DC natively. Throw in some XSLT to display the DC in the OPAC, and you can search and display this metadata without necessarily having to map to MARC. But if you want something to play with now, you can map your DC to MARC per LC's crosswalk (http://www.loc.gov/marc/marc2dc.html) and generate MARC records to load into Koha. Regards, Galen -- Galen Charlton Koha Application Developer LibLime [EMAIL PROTECTED] p: 1-888-564-2457 x709 _______________________________________________ Koha-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/koha-devel
