2020-11-10 Metadata meeting notes

Nov 10, 2020 3-4pm EST

Join Zoom Meeting

https://emory.zoom.us/j/93063879737?pwd=b0FYK1NiNkgvN1hZTFhmdk9SVDJvZz09

Participants

@Elizabeth Roke
@Dallas Pillen
@James Griffin (Unlicensed)
@Kevin Schlottmann

Minutes

@Elizabeth Roke

Discussion Topics

Time	Item	Notes

Time	Item	Notes
5 min	Welcome
10 min	Jira tickets for TS-Metadata	“metadata_standards_subteam” label Bugs: https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=15 (1 current issue) Feature requests: https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=16 (no current issues)
10 min	Technical documentation strategy	Per last TAC meeting, strategy for how to approach technical documentation site
25 min	Review and update metadata standards list	@Dallas Pillen Review EAS 2020 survey: https://www2.archivists.org/groups/encoded-archival-standards-section/eas-2019-2020-section-survey-results
10 min	Automatic mappings research	Check-in on homework from last meeting: Research the automatic mappings/data dictionaries for documentation from software project (including the generation of documentation from the code base)
5 min	Next steps/homework

Action Items

Minutes

Issue with EAD may be due to local practice. We should document what it does and provide some guidance. Need to add to the EAD export spreadsheet. Questions about “what does the community need?” Is it to accommodate OCLC ingests? May want to doublecheck with AS institutions to confirm the use case for this data and send out over AS users listserv. Elizabeth will send a survey to the group for approval and then send to community.
Tech documentation strategy: risk of adding another way to do documentation, but this is a need for providing a consistent place for documentation. Want to push this back to TAC to start the discussion there and develop a solution.
EAS survey: primary goal was not to discovery the information TAC-metadata is seeking; there is some evidence that people are looking for EAC-CPF; MARC is not highly rated in the survey responses, but we want to continue to support it; no questions that really illuminate the use cases on the survey
- Survey shows us the standards people ARE using or that the system already supports
- Maybe add other standards based on opinions from this group such as Schema and Wikidata
- Maybe add the JSON mappings from the API to the XML mappings and make them clearer-- @James Griffin (Unlicensed) will talk to the API group about making AS metadata standards more accessible to JSON users
Automatic data mappings in the code: there is already a set of logic within the code that assigns it to fields and it is impossible to keep mapping docs up to date
- The MARC import mapping file is here. Looks like there might be code limitations (undefined functions) and the code would have to be refactored to use Yard automatic documentation
  - Option for now is to watch the github files for MARC, EAD, etc. impoarts exports so we can see the changes and at least update the mappings
    - Could we generate alerts from the Github actions? @James Griffin (Unlicensed) will review (possibly email and Slack)
  - Ideal outcome would be automatically generate documentation based in these mapping files.