enable sending files from stacks to preservation

[andrewjbtw]

In testing structural metadata edits, I noticed that there's still one change to shelve/preserve permissions that we should try to support but which currently will always generate an error: changing "preserve=no" to "preserve=yes" when a file is stored only on Stacks.

Ideally, if a file is already on Stacks but not in preservation, it should be possible to do this:

• unlock the object
• edit the structural metadata to change "preserve=no" to "preserve=yes"
• close the object
• accessionWF copies the file from Stacks into preservation

Background

Last year, in #754 we covered copying files in the other direction: changing "shelve=no" to "shelve=yes" on a preserved file will copy the file from preservation to Stacks. This saved users a huge amount of time by eliminating some time consuming workflows that required them to reaccession entire sets of files just to change a shelve setting.

Sending shelved files to preservation is a less common activity but there are still real benefits to supporting it:

• it enables users to change their minds more easily if they decide they want to preserve files that have only been shelved
• it makes it easier to fix the occasional issue where users don't realize that certain filetypes are sent only to Stacks (based on the assembly-objectfile settings) unless they explicitly override the default settings in preassembly
  • reaccessioning the whole object is the only way to fix this issue currently
• it eliminates a class of accessionWF errors that would result from someone changing "preserve=no" to "preserve=yes" thinking that the system would support that change
  • the system will report that the file cannot be found in the /dor/workspace or /dor/assembly directories and halt
  • the only way to fix this issue at the moment is to edit the XML to change those settings back - in Cocina we would have to update the database to fix this

[ndushay]

@andrewjbtw is this part of "decouple from Fedora" workcycle? Should it go in that ready column?

[andrewjbtw]

We prevented people from making the edit (flipping the preserve "no" to "yes" from within Argo) that would cause an error here but it's still something I'd like to enable.

It was connected to the migration because fixing an error here used to require datastream editing. Now people can't cause the error but they still can't do what they'd like to do here, which would be to send a copy of the Stacks file into preservation.

[ndushay]

needs discussion; it's a couple days worth of work (JLitt work) - will require addition of a new robot.

[ndushay]

this ticket is morphing to Andrew asking for a report of what is missing from preservation and remediating those objects, rather than proceeding with this.

Andrew first thought he could just copy files from stacks but it's more complicated.

[edsu]

@andrewjbtw is evaluating whether this needs to be open or not.