Access to Memory (AtoM)

This is not working as expected, though I feel like it did in the past. Tested this on my 2.4.x VM, after running vagrant-box-update to update to 2.4.0.1, and on http://atomqa24x.accesstomemory.org.

Lower levels of description are not being exported unless their parent is also exported. I added a collection that includes Series- and Item-level records to the clipboard and then limited the export to only those lower levels of description (see export-config.png). This resulted in no relevant archival descriptions being found.

[info] [2017-06-20 17:17:16] Job 2765 "CSV export": Job started.
[info] [2017-06-20 17:17:16] Job 2765 "CSV export": Starting export to /tmp/search_export_2765.
[info] [2017-06-20 17:17:16] Job 2765 "CSV export": Exported 0 descriptions.
[info] [2017-06-20 17:17:16] Job 2765 "CSV export": No relevant archival descriptions were found to export.
[info] [2017-06-20 17:17:16] Job 2765 "CSV export": Job finished.

Essentially, because I didn't select Collection or Fonds to be exported, a child record of that fonds is ALSO not being exported. I can see this being a problem - archivists might want to be able to export all items in a fonds, but not necessarily the fonds-level record.

In summary: in order to export a child record, you must also export its direct parent. So if you have a collection in this format:

- Fonds
-- Series 1
--- Item
--- Item
--- Item
-- Series 2
--- Item
--- Item
--- Item

you have to export the fonds and series records in order to export the item. You can't bypass the series and only export the fonds and items.

Hi Sara,

First, this ticket is in relation to the export of repository records. I think this comment might be better suited to issue #10000?

Second, note in your screenshot the help text found below the level selector:

"Descriptions that are descendants of levels not included in the export will also be excluded."

We did this because it's not easily possible to generate valid EAD XML that excludes the parent but includes the children - AtoM would essentially have to recreate a new hierarchy on the fly by temporarily reassigning child records to the next available parent, so the EAD didn't come out broken. For consistency and simplicity, we made the CSV export behave the same way, figuring it was easy enough for users to delete parent rows from a CSV if desired.

If you feel like we should revisit that, let's discuss further?

Tried with 504 repository records, and it worked well!

Awesome! Marking verified - we don't need to use the "Document" status as we're tracking documentation needs via the "Requires documentation" element, allowing us to verify issues that will be included in the release :)

Documentation added to 2.4 in the following commit:

• https://github.com/artefactual/atom-docs/commit/be46bc7329c5ece9b4700f09b3b38dd8fc319fe9