...
Time | Item | Notes |
|---|---|---|
5 min | Welcome | |
25 min | Review and update metadata standards list |
|
25 min | AS 3.0 |
Some resources Agents test server: http://aspace-anw-429.lyrtech.org/staff/ Original metadata maps related to Agents release: MARCXML authority records: https://docs.google.com/spreadsheets/d/1gHxjB0A4mrX82--SLIKA4pAck7hILNEKt3Idc9SOMDg/edit?usp=sharing For updates related to import/export/metadata maps in general: Look for the release milestone and issues with the labels https://github.com/archivesspace/archivesspace/issues?q=is%3Aissue+label%3A"import+%2F+export"+ https://github.com/archivesspace/archivesspace/pulls?q=is%3Apr+label%3Aupdate_import%2Fexport_maps+ We will be putting out a smaller release prior to agents in November (tentatively numbered 2.8.1). There are a few relevant pull requests for metadata. |
5 min | Next steps/homework |
Action Items
Notes
This Sub-team shall continue to meet monthly for now
Reviewing the Work Plan
Looking at the metadata standards list
Where we are committed to maintaining mappings
That lives in last year’s workplan, should this be moved?
This addresses the level of support for ArchivesSpace for Import/Export
Tiers of Support
Standards in first tier: EAD2002, DACS
Second Tier: Dublin Core, EAC-CPF, OAI
Difference between optimal and compliant support?
From last year, the first tier would be that we go as far as possible with near-optimal support
For MARC this is impossible, as it is complex and doesn’t map to the ASpace data model
Objective is to provide a mechanism for getting standards-compliant records out of the system
What comes out of ArchivesSpace will be valid, but there might still need to be some transformation to account for additional data elements
Tickets and Enhancement Requests
This sub-team guides this on behalf of the community
Christine DiBella is aware of this
The Sub-Group took this upon themselves
Regarding the list of existing mappings
Does anything need to be moved?
Does anything need to be added?
EAC-CPF work: Kevin notes that this requires some additional updates regarding the encoding and support for agents
Additional Mappings
Elizabeth is aware that Schema.org and other mappings were added to the code base, but this has not been documented for the public
Where do we find these mappings published on the WWW?
There isn’t an explicit mapping for some of these
In ArchivesSpace itself, it was implemented by Mark Custer
Christine will be looking to identify this
Elizabeth will add this to the list
Moving EAC-CPF up a tier?
We’re not finished with EAD and MARC yet
Have we done a standard survey to see what users are getting in exports and imports? This might be an interesting step to take
There was data from the EAS survey, and Dallas is aware of those who have access to the data
Not many in the community were using EAC-CPF, but there were definitely interested parties
Placement of the documentation
Should this be published elsewhere? Where might it need to go?
It might be best to explore using another space, such as https://archivesspace.github.io/archivesspace/user/migration-tools-and-data-mapping
Request for an update for phrasing
Community members have the ability to issue a pull request against the GitHub repository
There is another URL for this information: https://archivesspace.org/using-archivesspace/migration-tools-and-data-mapping
ArchivesSpace 3.0
Timeline and where this sub-team can assist with supporting the release
There is going to be a minor release before 3.0 addressing Agent exports
On the GitHub repository, please monitor active Pull Requests