Modifying Accession Importer for Multiple Agents and Subjects
I talked about this with Brian over e-mail, and he suggested I file a ticket on here.
Is it possible to modify the accession csv converter so that multiple agents and subjects can be brought in? I tried to do this using the same trick as the dates but Brian took a look and informed me that that wouldn't work because of how subjects/agents need to be created in the system (separate URI).
Importing CSV accession data needs to be supported as many repositories have that data in simple form in Excel.
But some repositories have more complicated accession data, either in relational dbms or at least with numerous agents and subjects. IMO, converting that data to XML and importing it to an accession xsd has been easier than trying to extend the CSV import template.
Perhaps if there is a strong desire to convert accession data to XML before importing it (and I too am a little confused about this), it would make most sense to convert our existing accession schema from JSON to XML.
There is an xsd in the AT that supports accession import. It's much more flexible regarding linked name and subject records. I presume it could be extended / modified to reflect other sub-records in the accession template.
Accession data is not governed by the EAD schema. It needs its own import pathway. The export pathway is in the various accession reports.
How many is multiple?
I think we have a bloat problem with the CSV importers. Accession template has over 113 columns (!!!).
CSV is not a good method of importing relational data, especially with many associations.
Also, defining out own XML schema seems like reinventing the EAD wheel?
People should be encouraged to use the API.
This might be better handled by developing / implementing an accessions xsd. That might make it possible to import all data associated with an accession.