...
Feedback from the Sub-Team:
This is a weird history, as people have not encoded language; They have chosen to use mixed content
Language of description is not a DACS elements; Only language of material is
We should still attempt to export this information in a structured way
We’re encoding EADs with mixed content given that the toolkit encoded it as such
EAD3 was the intended version for enhanced support for extended language encoding
EAD2002 is far more restrictive in structure
Next steps: Reach out to Corey to determine if there was any intent here, and if there was, determine what the next step would be for the Sub-Team
Another Ticket: https://archivesspace.atlassian.net/browse/ANW-805
This was raised by Dev. Pri., but the process for forwarding this to the Metadata Standards was not in place
Issue was how the “published” status should work, it seemed to be that there was a lot of discussion in the comments for this
The interaction between the “published” status for the Digital Object in ArchivesSpace, and how this is encoded within the EAD
This will be added to the agenda for the next scheduled meeting
Ideas from December TAC Meeting
...