An Action for Creating a Bag

[elizoller]

We've been conceptualizing a sort of preservation dashboard within Islandora and wonder if a potential enhancement to this module would be an action that would allow a user to fire a call (remote or local) to create a bag on a node.
I've attempted it (successfully as far as I can tell) here: master...asulibraries:bag_node_action
Does this seem like something that would be beneficial for this module?

[elizoller]

I should also mention that had a big chunk of copy/paste from the submitForm method and could definitely be refactored to remove that duplication.

[mjordan]

@elizoller totally, that is a great idea. I'll give this a test.

I am also interested in your idea of a preservation dashboard. Are you in a position to provide more detail at this point? I don't know if your dashboard would include any visualizations of preservation-related data, but in https://github.com/mjordan/islandora_riprap I've included a chart showing any fixity check failures, an idea I initially toyed with in https://github.com/mjordan/preservation_reports. I haven't paid much attention to Preservation Reports lately other than deciding the fixity failure report is probably better bundled with Islandora Riprap. However, a visualization of the file formats or file mimetypes in a repository is something we'd be interested in for sure. We should also check in with the UPEI team (tagging @ajstanley) since they might have done some work on this as part of their RDM development.

[mjordan]

@elizoller I haven't tested your new Action plugin yet, but one thing to watch out for is that if this Action is fired before all derivatives are created, the Bag may be incomplete. This risk is higher when running Islandora Bagger in local mode since a long-running derivative process might not have completed by the time Islandora Bagger is executed. In remote mode, the queue is processed at some time in the future (depending on cronjobs configured to process the queue), so the likelihood that derivatives have finished generating at the time the Bag is created is higher.

Better preemptive error checking in Bagger plugins would mitigate this somewhat. For example, the request for a specific derivative returns a 404, log this and skip Bag creation.

[elizoller]

Ah, ok. I hadn't been testing on local mode, only remote. I'll have to work on it more. Thanks