At A&M we are in the beginning stages of implementing Primo as a way of searching across our different library and archives collections—across the Voyager catalog (books), various article databases, DSpace institutional repository, and even Archon (which holds EAD finding aids for our archival collections). We will also be able to provide a Primo instance for just the Cushing Memorial Library and Archives. This way, our patrons will be able to search for all of our materials (books, articles, digital images, finding aids, T&Ds)—but limit their search to items in Cushing.
Because of the way I have used Dublin Core (DC) in the past, I have always thought of it as just a way to describe digital objects. Hearing that Primo uses DC as the basic metadata schema to which other schemas are mapped—in order to allow searching across the various platforms using different metadata schemas—made me think of DC as having an additional value that I had not previously considered. The Open Archives Initiative’s Metadata Harvesting Protocol use of DC points to a similar value—what Clifford Lynch calls “the value of unqualified Dublin Core for lowest common denominator cross-domain resource discovery.” Although limitations of DC have been recognized, its use seems to be increasing—particularly with its use in Content Management systems (such as Content DM), institutional repository software (such as DSpace), Archon and Archivists Toolkit (both allow for creation of EAD finding aids and provide access to those aids), and through its key use in the Metadata Harvesting Protocol.
Keep in mind that I am an archivist who does digital projects–not a cataloger or a metadata specialist. I would love to hear everyone’s thoughts on all this, and whether you think the use of DC is expanding.
Mary Manning, Texas A&M University
