We are in the process of implementing persistent identifiers (ARKs via EZID) for finding aids so that links from the library catalog and digital collections wouldn't need to be changed as we migrated from exported PDFs to the eventual use of the ArchivesSpace public interface and linked data or whatever else we decide to use in the future. However, EAD 2002 doesn't have a good spot for this other than the url attribute in the eadid element, stored as ead_location in ArchivesSpace. (The LOC best practices also use it this way.)
However, EAD3 reserves EAD Location for the URI of the EAD XML file, NOT any other representation. We anticipate our persistent identifiers will link to the PDF or HTML representation (+RDFa, eventually) which is supported in EAD3 with a representation element instead. ArchivesSpace (at least v1.5, which we are currently running) doesn't have a corresponding field. Noah and Trevor, would ya'll be inclined to add such a field to the interface in this development cycle, or should I plan on creating a plugin when the time comes for us to migrate to EAD3?
Hi , our current approach is to develop a new export pathway that exports valid EAD3 without modifying the current ArchivesSpace data model (adding new fields). Hopefully this basic EAD3 exporter will be available in a September-ish release.
I think once there is some kind of basic, working EAD3 exporter available for folks to test, then the community can start providing feedback on areas where we might tweak the ASpace data model to better align with EAD3. There are several areas, like the one you point out, where EAD3 is more expressive than the current ASpace data model. Dates and extents are probably the most obvious areas.
If you wrote a plugin to add a new field for the PDF or HTML representation of a finding aid, I suppose parts of that plugin could eventually get merged into the master code. Seems like adding a field shouldn't be too controversial.
Sounds like a good plan to me. I just wanted to make sure I was in line with the development efforts.
This is a master ticket meant to corral all tickets related to EAD3.
, could you follow up on creating the new import ticket? Let me know if I/Lydia need to add any links (if your permissions don’t allow it).
I’ve created it as a subtask. Can’t make any edits to it, but I’m not sure I need to.