Re: Discussion about previous proposal

I don’t know if this advances the discussion, but at my institution (Emory University) we’ve done some mapping of our EAD finding aids to schema, though not using any of the archives proposed properties yet.  As others have mentioned, this worked well at a collection level where the properties are fairly obvious and can be assigned relying on the EAD structure.  However, it was quite labor-intensive at lower levels of the EAD, required hand-encoding, and necessitated using properties from namespaces other than schema.org.  An example can be found here:  https://findingaids.library.emory.edu/documents/heaney960/rdf/

It’s worth mentioning that we did this project not for SEO purposes but rather to support a digital humanities project that explored EAD description and questions about archival collecting.  I’d argue that the real benefit of this work is to more fully open our data, in which case schema is one option among many.  The real end goal here, I think, is to provide some standard mappings for archives to expose our metadata in a consistent way through RDF.

I (and a few other archivists in the US) are planning to try a schema.org-EAD mapping to incorporate the proposed properties.  Perhaps it would be useful to see a couple of examples from others of how this markup might look with real world data?

Elizabeth
___________________________
Elizabeth Russey Roke
Digital Archivist
Stuart A. Rose Manuscript, Archives, & Rare Book Library
404.727.2345 | erussey@emory.edu

[cid:2BAD62EF-A8AA-4E26-A03B-6BA41E701220]

"The Stuart A. Rose Manuscript, Archives, & Rare Book Library collects and connects stories of human experience, promotes access and learning, and offers opportunities for dialogue for all wise hearts who seek knowledge.”

Read the Rose Library blog: https://scholarblogs.emory.edu/marbl/

Like the Rose Library on Facebook:  https://www.facebook.com/emorymarbl

Follow the Rose Library on Twitter: https://twitter.com/EmoryRoseMARBL

________________________________

This e-mail message (including any attachments) is for the sole use of
the intended recipient(s) and may contain confidential and privileged
information. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution
or copying of this message (including any attachments) is strictly
prohibited.

If you have received this message in error, please contact
the sender by reply e-mail message and destroy all copies of the
original message (including attachments).

Received on Monday, 20 February 2017 09:44:09 UTC