This is fantastic. The EAD tag library springs to mind as a useful abstract model, but ASpace would benefit from the additional implementation details.
My list of elements would include: Field Description Allowable Attributes Where fields/mixins are stored internally Data type and/or range restrictions User interface mappings -- for example what fields are used where in the Digital Object creation interface Mappings to external data standards (MODS, EAD, RDA, MARC) Usage examples John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 -----Original Message----- From: Runyon, Carolyn [mailto:[email protected]] Sent: Wednesday, November 29, 2017 9:18 AM To: Archivesspace Users Group <[email protected]> Subject: [Archivesspace_Users_Group] Data Dictionary Hi All, The ArchivesSpace User Advisory Council Reports Sub-team is working on a data dictionary. As we are building this document, we are soliciting feedback from the community to ensure a usable, value-added product. In that spirit, do you have a specific use case for a data dictionary? What elements would you like to see in a data dictionary? If you have suggestions, please feel free to respond to the list or to me directly. I appreciate your feedback! All the best, Carolyn Carolyn Runyon Leader, UAC Reports Sub-team Assistant Head of Collection Services and Director of Special Collections University of Tennessee at Chattanooga Library 615 McCallie Ave., Chattanooga, TN 37403 [email protected], (423) 425-4503 Dept. 6456, LIB 439D _______________________________________________ Archivesspace_Users_Group mailing list [email protected] http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list [email protected] http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
