Review and revise accession import




Lydia Tang
February 28, 2020, 2:04 PM

Dev. Pri. discussed this ticket on Wednesday and decided to leave it open with the current status of Awaiting More Info because it is a useful pointer ticket for subtasks.

Christine Di Bella
October 26, 2018, 3:36 PM

- this issue and the linked issues are not currently being worked on so the statuses are unchanged from the statuses currently indicated. Particularly for the linked issue about importing accession records as XML (), there would need to be a mapping/schema provided for it to be able to be picked up by a developer.

Lydia Tang
October 26, 2018, 12:17 PM

, what is the status of this? Thanks!

Lydia Tang
May 28, 2018, 2:28 AM


I just wanted to check on the status of this ticket and its subtasks, since it was created three years ago. Would someone (maybe \:) ) be able to verify if the subtasks have been addressed to date and if any remaining subtasks still address the needs for a more robust accession import capability? Prepping this ticket for a future Dev. Pri. meeting. Thanks!

Mark Custer
May 6, 2016, 8:06 PM

We'll look at the XSD Accession schema used by the AT to see if that would be feasible to use. If so, we'll look into adding a new import option for accession records that will support multiple agent/subject headings.

Your pinned fields
Click on the next to a field label to start pinning.