Details
-
Type:
Bug
-
Status: Draft (View Workflow)
-
Priority:
P3
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Template:customfield_11100 44837
-
Development Team:Thor
Description
Problem:
We wish to hand item-specific call number and location to the ABLE client, to be used in printing the spine during the binding process. ABLE can only read data from MARC fields, it does not ask for an OPAC record, so the item's location and full call number will need to be added to a local field.
The call number and local will need to be available for post-processing like any other MARC field.
Proposed Solution:
In response to a barcode search (or possibly to any search where there is only one result) copy the permanent call number (all parts of it) of the matching item into a local field. Include the location code in it's own subfield.
Default to putting the data in a `952`, but allow tenant to configure that field to make sure the library can select a local field that they are not already using.
Proposed subfields:
| Subfield | Call no. data |
|---|---|
| k | effective call number prefix |
| h | effective call number |
| m | effective call number suffix |
| v | volume |
| e | enumeration |
| c | chronology |
| y | yearCaption |
| t | Copy no. |
TestRail: Results
Attachments
Issue Links
- blocks
-
ZF-25
SRU output tweaks to support ABLE bindery application
-
- Closed
-
- clones
-
ZF-30
Add item-specific call number and location to local field in record returned from barcode search.
-
- Closed
-
- is required by
-
ZF-25
SRU output tweaks to support ABLE bindery application
-
- Closed
-
- relates to
-
ZF-32
Optionally, restrict item-level MARC holdings info to item mentioned in barcode search
-
- Closed
-
