Purpose: To provide the user a way to create a new bibliographic record within the quickMARC UI.

User story statement(s): As a cataloger, I need the ability to create a new MARC bibliographic record so that I can catalog original materials within the quickMARC UI when no other record exists.

Requirements: 

• Use the same flow as derive, the data-import job profile will be the same. UI will use the same mod-quick-marc endpoint to create a record.

  • Retain the same validation & error messaging as edit/derive

  • Retain the same edit (including authority linking capabilities) as edit/derive

  • Retain the same save functionality as derive ("Save & close")

• Generate and populate an HRID in the 001

• Generate and populate the date/time stamp of creation in the 005

• Generate and populate the 999 UUID

• Populate new record with default Leader values

  • ||Leader Position||Default Value||
    |00-04|Generate the length of the record|
    |05|n|
    |06|"\" (invalid value, if user does not change, show validation error)|
    |07|"\" (invalid value, if user does not change, show validation error)|
    |08|"\"|
    |09|a|
    |10|2|
    |11|2|
    |12-16|Generate the length of the leader + directory|
    |17|u|
    |18|u|
    |19|"\"|

• Create a 245 field with a "\" as the first and second indicator values, with an empty subfield $a in the field

• Requirement Deferred: Create an 008 field containing blank default positions applicable to all materials and add below the 005

  • 00-05: Date entered on file File)

  • 06: Type of date/publication status (DtSt)

  • 07-10: Date 1 (Start date)

  • 11-14: Date 2 (End date)

  • 15-17: Place of publication, production, or execution (Ctry)

  • 35-37: Language (Lang)

  • 38: Modified source (MRec)

  • 39: Cataloging source (Srce)

Scenarios:

1. Scenario:

   • Given the user is creating a new MARC bibliographic record

   • When the user hits "Save & close"

   • Then the 001, 005, and 999 should be populated

2. Leader Defaults Scenario:

   • Given the user selects the option to add a new MARC Bib Record from the  "Actions" menu within the Inventory app search page

   • When the new record appears in the quickMARC UI

   • Then the Leader values should be populated system generated positions and default values for editable positions

   • AND the user should be able to edit positions 5, 6, 7, 8, 17, 18, and 19

3. 245 Defaults Scenario:

   • Given the user selects the option to add a new MARC Bib Record from the  "Actions" menu within the Inventory app search page

   • When the new record appears in the quickMARC UI

   • Then the record should contain a 245 field with "\" as the first and second indicator values and an empty $a in the field

4. Deferred 008 Defaults Scenario:

   • Given the user selects the option to add a new MARC Bib Record from the  "Actions" menu within the Inventory app search page

   • When the new record appears in the quickMARC UI

   • Then the record should contain an 008 field, with empty positions applicable for all materials AND the 008 should appear under the 005

5. 008 Default Scenario - see https://folio-org.atlassian.net/wiki/display/MM/Original+MARC+Bibliographic+Cataloging for full scenarios:

   • Given the user selects the option to add a new MARC Bib Record from the  "Actions" menu within the Inventory app search page

   • When the user edits the LDR/06-07 values

   • Then the available positions for the 008 should add the applicable positions, matching existing functionality for derive and edit records

6. Edit/Derive Leader Editing Scenario

   • Given a user changes a Leader position that is not 5, 6, 7, 8, 17, 18, and/or 19

   • When the user either hits "Save & close"

   • Then the user should be presented with an error message that says "Only positions 5, 6, 7, 8, 17, 18, and/or 19 in the Leader can be edited" (existing functionality for derive and edit)

7. Editing Scenario - Repeatable / Non-repeatable

   • Given the user adds an additional 245 field

   • When the user either hits "Save & close"

   • Then the user should be presented with an error message that says "Record cannot be saved with more than one field 245"

8. Editing Scenario - 999

   1. Given the user adds a 999 field

   2. When the user either hits "Save & close"

   3. Then the record should be saved, the user should not receive and error message, but the additional 999 should be removed

9. System-generated Leader positions - create

   1. Given the user selects the option to add a new MARC Bib Record from the  "Actions" menu within the Inventory app search page

   2. When the new record appears in the quickMARC UI

   3. The system should generate the 00-04 and the 12-16 based on the current length of the record and the directory

10. System-generated Leader positions - save

    1. Given the user is creating a new MARC bibliographic record

    2. When the user either hits "Save & close"

    3. The system should regenerate the 00-04 and 12-16 Leader positions based on the length of the record and the length of the directory (this number should be updated to reflect any updates made to the record