...
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
Looks like there might be code limitations (undefined functions) to doing this that would create bugs 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. exports so we can see the changes and at least update the mappings