ANW-616 - adding a spawn component feature to accession record toolbar

[quoideneuf]

Adds an "Archival Object" option to the "spawn" dropdown of the Accession toolbar.

Because components (i.e., Archival Objects) need to be situated in a Resource and a parent Archival object, the new Archival Object form now pops up two modals if the resource and parent aren't present in form or in the URL. See screenshots.

[brianzelip]

The above screenshot was taken after spawning a new Archival Object, then clicking the save button without filling in any further information about the newly spawned archival object. Two items to note here:

1. The "Archival Objects" breadcrumbs link leads to an "Unknown action" error with the following message: The action 'index' could not be found for ArchivalObjectsController.
2. The "Other Level" Basic Information field is marked with an asterisk to denote a required field, yet the validation warning message doesn't list "Other Level" as needing input as it does for "Number", "Type", and "Level of Description".

[mark-cooper]

This part should be updated to apply default values first then spawned values second. cf. #2686

https://github.com/archivesspace/archivesspace/blob/master/frontend/app/controllers/accessions_controller.rb#L42-L46
https://github.com/archivesspace/archivesspace/blob/master/frontend/app/controllers/resources_controller.rb#L48-L55

[quoideneuf]

Should be fixed in latest commit

[mark-cooper]

This has the effect of expanding the form sections in the UI (extents/dates/lang_materials). Is that intended? It's done for resources but I think those are all mandatory required fields in that context (and this is not done for accessions).

[quoideneuf]

See latest commit

[mark-cooper]

When spawning an archival object I think it might be useful to apply / update the resource and archival object id in the query string so it's transparent what is happening at all times. Without this if you hit refresh on the spawned object page it loses the resource / parent and you can't save [Must be a object (you provided a String)]. This also makes the "Select Resource" button inoperable.

You can spawn directly which is nice i.e. http://localhost:3000/archival_objects/new?accession_id=1&resource_id=1&archival_object_id=1 -- although using "Select Resource" after this does update the selection but not the url params (similar to above) so that could be confusing. Always updating the query params would be good I think, but not critical.

[mark-cooper]

The modal (resource) into modal (archival object) flow works nicely 👍

[brianzelip]

Looks good. I see the query parameters being updated as Mark pointed out.