Currently

The linked data editor displays three actions to the cataloger when in edit mode:

• Cancel - exit edit mode without making changes

• Save & keep editing - save changes locally and stay in edit mode

• Save & close - exit edit mode and save changes to back end

In this context - ‘save’ has two meanings: saving to the browser, and saving to the back end.

The end user, however, will likely assume that ‘save’ has a single meaning and that is saving work to the back end.

Accordingly, the purpose of this card is to modify the behavior of the ‘Save & keep editing’ option, so that the action books changes to the back end, while keeping the cataloger within edit mode.

This card does not change the function of automatically saving work to the browser.

1. Default state

GIVEN that a cataloger is editing or creating a resource in the linked data editor

WHEN the cataloger enters edit mode (for Work or Instance)

THEN the application displays three action buttons: Cancel, Save & keep editing, Save & close

AND Cancel is enabled by default

AND both Save & keep editing, and Save & close are disabled by default

2. Editing - Action buttons enabled

GIVEN scenario 1

WHEN the cataloger makes keys in any values into the new or selected resource

THEN all three action buttons are enabled

3. Save & keep editing

GIVEN scenario 2

WHEN the cataloger selects Save & keep editing

THEN changes made to the resource are booked to the back end

AND the cataloger remains in edit mode

4. Save & close and Cancel

GIVEN scenario 2

WHEN the cataloger chooses either ‘Save & close’ or ‘Cancel’

THEN the either action works as expected

5. Auto save

GIVEN scenario 2

AND that the cataloger has not selected either Save & keep editing or Save & close

THEN the system will automatically save the changes to the local browser

AND the changes will not be booked to the back end.