Description

Libraries need the ability to adjust the display for both expected and received Receiving pieces in the receiving app in order to simplify various operations and to account for the arrival of unplanned pieces or pieces out of expected sequence. Additionally, libraries find it desirable to be able to share this sequence with public-facing catalog interfaces.

Approach

• Receiving pieces will automatically be assigned a sequence number which library staff will be able to edit.

  • Expected, Received and Unreceivable pieces all share the same sequencing

• Sequence number will be assigned in ascending order

• Sequences will be displayed in descending order (sortable)

• Manually reassigning a sequence number will automatically resequence any numbers.

  • By default, existing numbers equal to or greater than the assigned number will be incremented by 1

    • Example: A receiving title has 10 pieces

      • A new piece arrives that belongs in sequence 8. This new piece makes 11 total pieces.

      • User assigns the new piece sequence 8.

      • Existing sequence numbers 8, 9 and 10 are incremented to 9, 10 and 11

      • Sequence numbers 1-7 remain unchanged.

  • If a piece with a low number has a higher number assigned, numbers equal to the newly assigned number and greater than the previous number will have those numbers decremented by 1.

    • Example: A receiving title has 10 pieces

      • User assigns piece with sequence 4 to sequence 7

      • Sequence numbers 5, 6 and 7 will be resequenced to 4, 5 and 6

      • Sequence numbers 1, 2, 3, 8, 9 and 10 remain unchanged

• Sequence numbers associated with deleted receiving pieces will remain reserved and included in any sequencing calculations.

  • Example: A receiving title has 10 pieces

    • User deletes pieces 1-3

      • Resequencing does NOT occur

    • User adds a new piece

    • New piece has sequence number 11.

Assumptions

• Automatic sequence generation will be based on creation order. Simultaneous creation will also factor in publication date.

• Sequence adjustment will be uncommon and seldom involve more than a few pieces (i.e. accounting for unexpected or unpredictable pieces)

  • Even though over time a particular receiving title may accrue hundreds or thousands of receiving pieces, an adjustment of more than 20 or so pieces should be extremely rare.

  • The above is based on the presumption that receiving pieces will be generated annually as subscriptions are renewed.

In scope

• Add sequence number to display in receiving view and edit screens

• Make sequence number editable in edit screen

• Ensure sequence numbers generated from batch operations (such as Serials) are correct

  • based on publication date earliest to latest

• Ensure existing pieces receiving a sequence number based on publication date (if known) - migration story

Out of scope

• Sorting on chronology

• Application of sequence number outside of Receiving app

  • Current scope does NOT include modifications to Claiming

Additional info

See Approach 4 at