Format and print of spine labels

Purpose:
Definition: A Spine label is a small typed or printed label affixed to the lower spine of a book or other bibliographic item at the time it is received and being processed, getting ready for circulation. The spine label is displaying the location symbol and call number, for use in re-shelving and to assist the user in retrieving the item from the shelf once the call number has been found in the library catalog. The printed label is typical printed on a special printer for labels, e.g. XXX or by using a special print application, e.g. SpineOMatic which is a Windows application.

Overview: The system will need to have a way to take call number info, location info, and possibly other parameters, and generate spine label print files in the format the library needs, and then send that print file to a printer. This will be covered in Inventory. Usually libraries don't store the formatted spine label data in their database, just the underlying data that is used to format the spine label, E.g. GOBI does a lot of formatting for shelfready customers.

To do: Capture the need to be able to format and print spine labels from FOLIO cataloging records:
Following task/requirements is needed:

1. define what data do we need to capture to produce the spine label
   • exactly how the call number should be stacked
   • whether leading decimals are removed in 1st Cutters for LC/NLM numbers
   • how any prefixes or suffixes are determined and formatted (all caps, space before or after the call number)
   • whether those prefixes/suffixes are location based, or based on something else (e.g. oversized or format designations)
   • whether copy numbers are required - hopefully not
   • how volume/enumeration is handled for items in sets and serials
2. configure the label (text and size) on the Settings page: Settings > Inventory > Label printing
3. configure the output format of the label on Settings page: Settings > Inventory > Label printing
4. interaction with a configurable third-party print solutions and send a file as input to that third-party solution

Documentation:

• GAPs analysis - composite_to_folio_inventory, row #63: https://docs.google.com/spreadsheets/d/1JnvLq-pQ861pNnW_AEn0xsSujr9yTuM8MOHSWJ_XSZA/edit#gid=348285033
• Slide deck (6/26/2020): https://docs.google.com/presentation/d/1V3uQ5Pt1V16xtktzuapAlR6hgFYQWwiLqtoD-wT5agc/edit#slide=id.p