As a cataloger, I need the ability to create a new Work from scratch (versus deriving a new Work from an existing one).

In scope

• Invoking a new work from landing page

• Invoking a new work from search results

• Displaying new blank workform for Work entity in edit form

Out of scope

• creating a new instance

• business rules for saving a new work

• deriving a new work from an existing work

This card builds on the development started in https://folio-org.atlassian.net/browse/UILD-218 so that a cataloger can create a new Work from scratch, leveraging the existing edit screen for Work entity.

Unlike Instance, the cataloger will not have the ability to initiate cataloging a new Work from within edit mode. Rather, a new ‘Actions’ drop down menu - displayed in the MARVA landing page - provides the cataloger with the option for creating a new work.

Initially, the Actions menu will display only one option ('New resource'), but additional as functionality is layered into the application, additional options will be integrated into the Actions menu.

The Actions menu will be displayed and available when the cataloger opens the MARVA editor, conducts a search, and/or inspects results in a search result set.

The Actions menu will not be displayed or available from any of the edit screens. The cataloger will have to exit edit mode (e.g. via the “Save & close” or “Cancel” buttons) first in order to access the Actions drop down.

When ‘New resource’ is selected from the Actions drop down menu, a new blank workform will be displayed in edit mode for Work entity. The workform will replicate the functionality developed for editing an existing Work (e.g. default components, repeatable components, lookup fields, etc.) except that all of the components of the entity will be empty but otherwise editable.

The edit mode will continue act as a section for the Instance entity, even when there are no instances associated with a Work. The ability to create a New Instance for an existing Work will be addressed separately as the focus for this card is on the Work entity.

There will be business rules associated with pairing Works with Instances.

• Every Work must have at least one Instance and

• All Instances must be associated with a single Work

However, these business rules are outside the scope of the card and will be addressed separately.

1. Base case

GIVEN a cataloger will be working in the MARVA application

WHEN the cataloger invokes MARVA

THEN the home screen / landing page is displayed

AND the existing / base functions are displayed (per UILD-xxx)

AND the Actions drop down menu is displayed

AND the Actions drop down menu shows ‘New resource’ as an option

2. New resource

GIVEN scenario 1

WHEN the cataloger selects ‘New resource’ from the Action drop down menu

THEN the edit mode for the Work entity is invoked

AND a new workform for the Monograph Work entity is displayed

AND the workform values are all empty

AND the section for Instance entity is displayed but empty

AND the ‘Cancel’ ‘Save & keep’ and ‘Save & close’ buttons are active

AND the ‘Actions’ drop down menu is not displayed

3. Edit

GIVEN scenario 2

WHEN the cataloger selects any of the components of the Work entity

THEN any edits made to the workform are displayed

4. Save & keep

GIVEN scenario 3

WHEN the cataloger selects Save & keep

THEN the edits made to the workform are saved locally in the browser

5. Save & close

GIVEN scenario 3

WHEN the cataloger selects Save & close

THEN the edits made to the work entity are saved to the database

AND the cataloger returns to the landing page / home page of MARVA

NOTE: We will need to discuss whether/how to fulfill this requirement in the short-term, understanding that business rules will eventually require the cataloger to add at least one Instance to a Work as a condition for saving the new entry to the database.

6. Cancel

GIVEN scenario 3

WHEN the cataloger selects Cancel

THEN the edits made to the Work entity are not saved

AND the cataloger returns to the landing page / home page of MARVA

NOTE: business rules will be addressed in a separate card. For now, it is not necessary to enforce saving rules that would otherwise control when data can and cannot be saved to the database.

Open

Open