Time | Item | Who | Notes |
---|
5 min | Roll Call | Noah | |
5 min | Announcement/Updates | BradleyW (Unlicensed), All | Discuss schedule and timeline for next release? How can this group help? |
10 min | Submitting feature request for Schematron validation | Terry/Noah | Next steps for getting this in dev. queue - Testing conslidated schematron
- Submit JIRA feature request
|
15 min | EAD import / export discussion | All | Review / discuss recent conversations on list and in JIRA: - Mark Custer's proposal for modifying "publish" behavior for EAD Importer
Current Default Behavior for EAD Importer: - Resources set to “published” at collection-level
- Components (archival objects) set to “published” (ignores @audience attribute)
- Notes (all levels) set to “unpublished”
Proposed Changes to current behavior:
- Set imported resources to “unpublished” at collection-level by default unless @audience=”external”
- Set all notes and components (archival objects) to “published” unless @audience=”internal”
- Handling barcodes for EAD import / export: see:
Jira Legacy |
---|
server | JIRA (archivesspace.atlassian.net) |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | AR-1409 |
---|
|
- EAD exporter inserts barcodes in label attribute: <container @label="Mixed_materials (D0123456$)">
- Should EAD importer parse content inside parents () and map to Barcode field in AS?
|
15 min | Support for EAD3? | All | If we want ASpace to support EAD3, how might we proceed? - Will it require changes to the data model?
- Should ASpace support both EAD2002 and EAD3 for some period of time?
- How should we organize / document work on this front?
- How should we sequence work (e.g. address exports then imports?)
|
5 min | Archon Migration docs | Phillip Suda (Unlicensed) | |