...
Regrets:
Goals
Discuss the results of the community survey and begin brainstorming ideas
...
Time | Item | Notes | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2-3 mins | Welcome and logistics |
| |||||||||||||||||
30 min | Review and discuss community Survey Survey results: https://docs.google.com/presentation/d/15rY6enVGmV6alV1r7ICcfksHcktO2yV_/edit?usp=sharing&ouid=115124479135431310074&rtpof=true&sd=true Open ended questions: https://docs.google.com/document/d/1iAof5Ei44C5OEWCLwsBPLtYgAfIhDWKfKyIXo5H1i5M/edit?usp=sharing |
Most folks are using spreadsheet data instead of XML to import; Some repositories are using EAD 3 for import (they’ve likely built their own system to do EAD 3 import), Repositories have built plugins to edit (not create) metadata;
Facilitate information sharing around imports/export tools, standards, new plugins, etc. Christine suggested the Awesome ArchivesSpace Github repository: https://github.com/archivesspace/awesome-archivesspace Prioritize tickets based on the community survey results (less focus on MARC imports, more focus on spreadsheet importer, etc)
Most archives primarily work with EAD 2002 (import/export) - Work closely with Christine and Aspace team to make sure that we maintain backward compatibility with EAd 2002 for however long the transition period takes, but make sure we’re moving forward as EAD evolves. Library of Congress is developing EAD 3 import in order to migrate their records into Aspace. They are embarking on this project this Fall, possibly by the end of the calendar year there might be something for MS sub-team to take a look at (mapping, etc)
| |||||||||||||||||
Jira TICKETS | 2-3 minutes | Action items | Jira Ticket: Review and Prioritize Jira tickets in next meeting related to the community survey results: Diane will work with Kate to identify Jira tickets in need of review.
|