Notes from July 31 call

AS needs an accession XML import
we should reuse /extend schema already in AS
can subgroup do this?
there will probably no xml export, accession export could be managed through a report (CSV)

EAD 2002
AS needs to import compliant ead as fully as possible
Two requirements of EAD imported into AS
must be ead2002 valid
must also be AS compliant, which is largely based on DACs compliance

We should be testing that EAD come out schema-valid, and can then be reimported
This does not mean strict round-tripping, some differences are expected

EAD3
A 6 months dev. cycle is expected for AS to support EAD3
ead3 data maps must be created
in real-life, not alot of ead3 will be imported, emphasis will be on export (most imported ead3 will first have been exported from AS)

EAC
test import and export

Digital Objects
lots of different formats
no mets or dublin core export
no events, rights

Immediate priorities
EAD, EAC

Documentation:
Is excel the best way to show maps? Yes.
in the build there is doc that shows all the api names
ead to sql mapping is sufficient

Resources:
we should switch resources to concentrate on EAD

Tracer:
There is an AT migration tracer repository in test site that may be useful for our testing
tracer repos. has EAD instances that should be comprehensive
also accessioning and digital objects
(no EAC)

Browser not supported