Story: Save Work | BF Thin Thread

Current situation or problem:

As a cataloger, I need to continually save work performed on a resource description, so that I can minimize the amount of effort that would have to be reconstructed due, for example, to a system failure. 

In scope

• Saving work automatically over a set period of time (e.g. every 60 seconds) over the duration of a session

• Saving work manually at any time during the session

• Returning and displaying a resource description from its most recent save state

Out of scope

• "Undo" / "Redo"

• Closing work on a resource description

• Publishing a completed resource description to the database

• Deleting a completed resource description to the database

• Restoring a resource description to anything other than the most recently saved state

• Recording administrative data for actions taken during a session

Use case(s)

1. Automatic save - success

• Given a cataloger has pulled up a resource description in the BIBFRAME editor

• The system should update and save any edits made to the resource description automatically every 60 seconds

• So the resource description is current within the previous 60 seconds in the database

2. Automatic save - fail

• Same scenario as 1, except that the automatic save is not successfully executed, 

• The cataloger can continue cataloging, but the resource description will be saved only through the last save action successfully executed

3. Manual save - success

• Same as scenario 1

• Except the cataloger chooses to save the work performed, by manually by clicking a 'Save' icon and/or button

• When the save action is successful, a visual cue is displayed to the cataloger confirming the save action

• And the resource description is updated in the database

4. Manual save - fail

• Same as scenario 3

• Except the manual save action failed

• So no confirmation cue is displayed to the cataloger 

• And the resource description in the database is current only through the previous save action (e.g. automatic save)

When the cataloger has successfully made changes to a resource description (automatically or manually), then the next time staff pull up the resource description, the system displays the values from the most recent version of the edited resource description

Proposed solution/stories

Links to additional info

Questions

• After a successful manual save, should the automatic save cycle be recalibrated with the manual save, or should the cadence be determined when the resource description is first called up in the editor?

• Changes to schemas may affect whether a field/component is a literal or a link - we'll need to settle on a tactic for accommodating such changes