Skip to content

Detect when captured originals are modified outside of the workbench and prompt for action #2

Open
gregjan opened this Issue Jan 20, 2011 · 2 comments

1 participant

@gregjan
UNC Chapel Hill Libraries member
gregjan commented Jan 20, 2011

If the original folder has a change to a previously captured resource (additional file or modified file), then we need to prompt the user for next steps..
For a modified file, do we:

  • stage the modified file, replacing previous staged version
  • leave it alone

For a file added to a captured folder, do we:

  • capture the new file (and stage)
  • leave it alone

To generalize we could call these two kinds of "changes" to captured material. Then the prompt to the user is really whether or not to accept/reject each change. (Sort of like Git.)

Seems like a dialog that presents a table with checkboxes.

@gregjan gregjan was assigned Aug 17, 2011
@gregjan
UNC Chapel Hill Libraries member
gregjan commented May 16, 2012

Also handle the scenario when a file is moved from it's old location, i.e. the file vanishes from the perspective of the workbench.. The file might be temporarily detached, like a removable drive, or it might be deleted or moved.

See #74

@gregjan
UNC Chapel Hill Libraries member
gregjan commented May 16, 2012

Make the following operations safely deal with files not found:

  • staging the file
  • deleting the file from arrangement
  • capturing the file (originals area not refreshed, but the file is gone)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.