Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TimeItemWhoNotes
5 minRoll CallNoah

 

5 minAnnouncement/UpdatesBradleyW (Unlicensed), AllDiscuss schedule and timeline for next release? How can this group help?
10 minSubmitting feature request for Schematron validationTerry/Noah

Next steps for getting this in dev. queue

  • Testing conslidated schematron
  • Submit JIRA feature request
10 15 minEAD import / export discussion All

Review / discuss recent conversations on list and in JIRA:

  • Mark Custer's proposal for modifying "publish" behavior for EAD Importer
  • EAD imports should result in resource records marked as “unpublished” at the collection level unless the ead or archdesc element includes @audience="external"
  • The EAD importer should, by default, mark all components and notes as “published” unless EAD tags include

    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:
      Jira Legacy
      serverJIRA (archivesspace.atlassian.net)
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyAR-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?)

     

    ...