![]() |
Sarah Shepherd (she/her)
|
|
Scottish Rite Masonic Museum & Library
|
|
|
Archivist
|
|
|
Web www.SRMML.org
|
|
|
33 Marrett Road, Lexington, MA 02421
____________________________________________________________________________________ |
|
|
|
|
|
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you received this email in error please forward to the correct person, or contact the sender.
|
|
--
You received this message because you are subscribed to the Google Groups "Archivesspace_Users_Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to Archivesspace_User...@lyrasislists.org.
To view this discussion visit https://groups.google.com/a/lyrasislists.org/d/msgid/Archivesspace_Users_Group/CH0PR19MB7935304FA61AF9C90AE0230FA5F3A%40CH0PR19MB7935.namprd19.prod.outlook.com.
I’m also in a very early stage of exploring use of the Gateway for harvesting our ArchivesSpace records (at UCLA) to OCLC. One aspect of the workflow really puzzles me: If “During the harvest, the Gateway transforms the Dublin Core records to WorldCat MARC records” (as described here), why doesn’t the Gateway accept OAI MARC as one of the schemas it can harvest? ArchivesSpace can serve OAI MARC, but the Gateway accepts only OAI DC. In translating to Dublin Core and then to MARC, granular semantics in the original AS descriptions are lost and the MARC records made less standards compliant.
I wonder if the Gateway accepts only OAI DC because that schema aligns well enough with the simpler metadata applied to traditional digital collections, compared to which archives metadata are an edge case. If this is so, perhaps the archives community should initiate a discussion with OCLC to plan a separate harvesting mechanism.
Francis