4 thoughts on “EAC-CPF at the AMNH, Part 1”

  1. I’m in the process of migrating EADitor to bootstrap, and when I release the next beta of it in the next month or two, you’ll be able to hook it up to a xEAC installation for linking archival materials to corporate bodies, people, and families. Ultimately, I plan to implement an optional SPARQL endpoint publishing mechanism in both EADitor and xEAC which will link content in the two systems more seamlessly. EADitor is currently being beta tested by a New York archival consortium pilot group, as well as being used by the ANS in production. The idea is that EADitor and xEAC can be standalone applications in their own right (xEAC has a lot of scholarly potential outside of the traditional archival implementation of EAC-CPF), but can be hooked together with minimal effort.

    1. Thanks, Ethan! We were wondering if EADitor worked with xEAC. I’ll keep an eye out for the update. This is very timely as we plan to test some content management systems this summer. Out of curiosity, are you implementing the experimental “relations” tag in EADitor, or does the SPARQL endpoint address the overlap of the elements in both schemas? We definitely want to represent the relationships in both finding aids and entity records, but do not want to duplicate efforts if the “bioghist” links back to the entity record. It will be interesting to see how this develops and gets used in the archival community.

  2. As of right now, EADitor implements EAD 2002, not EAD v3, but I will be migrating to EAD 3 this summer. I’ve already written the XForms stuff for handling the control element, but it has not been incorporated into the main editing form. I haven’t given much thought to handling relations in EAD.

Comments are closed.