Purpose:

To support an option to create a new publication pattern, based on an existing, but already used (i.e. linked to predicted piece set) publication pattern for the same serial.

In cases where a publication pattern has already been used to create a predicted piece set, we will not support a direct “edit” of that publication pattern, but instead have an option to create a new publication pattern based on the existing one. The aim is that for the user this is a relatively seamless process that seems very much like the edit process, but ultimately creates a new publication pattern.

Note that although not in scope of this story, there is a future aim to support “Templates” for publication patterns where a publication pattern (or the JSON for a publication pattern) could be stored in the system as a template that could then be used when creating new publication patterns, to avoid re-keying data when there are many commonalities between the patterns. This is mentioned here due to potential overlap in how this feature and the template feature could work

User story statement(s):

As a Serials librarian
I want to create a new publication pattern using the details of an existing publication pattern that has already been used on the same serial
so that I can fix any issues or update the publication pattern even after it has been used to create a predicted piece set

Scenarios:

1.  

   Given the publication pattern view with associated predicted piece sets, and a user with permission ui-serials-management.rulesets.edit
   When I view the publication pattern
   There is an action menu with an active “Create modified pattern” option (the final terminology maybe subject to discussion with users)

2. 
   Given the publication pattern view WITHOUT associated predicted piece sets, and a user WITH permission ui-serials-management.rulesets.edit
   When I view the publication pattern
   There is an action menu with both the “Edit” and “Create modified pattern” option active

3.  

   Given the publication pattern view and a user withOUT permission ui-serials-management.rulesets.edit
   When I view the publication pattern
   There is no “Create modified pattern” option in the Action menu

4.  

   Given the publication pattern view
   When there are no visible options in the Action menu
   Then the action menu does not display

5. 
   Given the publication pattern view with an active create modified pattern option
   When I select Create modified pattern
   Then the Publication pattern create view is displayed pre-populated with all the information from the existing pattern
   NB this should not have (permanently) created the pattern at this point. The pattern should only be fully created when the user saves and closes the record. If they were to click cancel then no publication pattern would be added to the serial

6. 
   Given the publication edit view
   When I see the edit screen
   Then it lays out all the information for the publication pattern in an edit form that is the same as the current publication pattern creation form. Note that it is important that the labelling ordering and template tokens are preserved in the right order (i.e. if there are two enumerations and one chronology, then enumeration1 and enumeration2 and chronology1 are all preserved in the same way as when the pattern was created
   NB as per the “Edit” story we could consider splitting the Labelling into “Enumeration” and “Chronology” in both creation and edit form to make ordering of display and management more intuitive. The create and edit screens should be laid out in the same way

7. 
   Given the publication edit view with valid data
   Then the Save & Close button is active

8.  

   Given the publication edit view
   When I make changes that are invalid
   Then validation rules should operate as for the existing Create publication pattern form

9.  

   Given the publication edit view
   When I click “Cancel”
   Then the form should be closed, and the record should not be saved

10. 
    Given the publication edit view
    When I click “Save and close”
    Then the record should be saved and the form should be closed, and the user should be returned to the serials view (this is to be consistent with the current behaviour on creating a pattern)
    Question: Gill - should we change this behaviour? Also a question on editing a pattern