2016-04-08 Meeting notes

Next steps for getting this in dev. queue

• Testing conslidated schematron
• Submit JIRA feature request

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:

1. Resources set to “published” at collection-level
2. Components (archival objects) set to “published” (ignores @audience attribute)
3. Notes (all levels) set to “unpublished”

Proposed Changes to current behavior:

1. Set imported resources to “unpublished” at collection-level by default unless @audience=”external”
2. Set all notes and components (archival objects) to “published” unless @audience=”internal”

• Handling barcodes for EAD import / export: see: AR-1409 - Getting issue details... STATUS
  • 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?

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?)