You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to modify the task to only operate on the current version of a druid - whichever version happens to be in the process of going through the workflow. That would allow us to take the version parameter out of the command.
Why? I've only used this task to resolve workflow errors when a druid is currently in a workflow. If there's an issue with a previous version of a workflow, I use the rails console. Having to specify the version in a parameter means:
if there's a batch of druids with the same problem, you can't loop through a list and run the same task on all the druids without looking up their current versions
if you get the version number wrong, the rake task will modify a step on a previous version whether you wanted it to or not. That can cause issues, such as a druid having a workflow error that isn't immediately visible because it's attached to a previous version.
The text was updated successfully, but these errors were encountered:
There's a rake task for setting specific workflow steps to specific statuses. It currently requires:
Example:
bin/rake workflow:step[druid:nt586gf9125,accessionWF,sdr-ingest-transfer,1,waiting]
I would like to modify the task to only operate on the current version of a druid - whichever version happens to be in the process of going through the workflow. That would allow us to take the version parameter out of the command.
Why? I've only used this task to resolve workflow errors when a druid is currently in a workflow. If there's an issue with a previous version of a workflow, I use the rails console. Having to specify the version in a parameter means:
The text was updated successfully, but these errors were encountered: