| 2019-05-21 15:44:38 |
Rogan Hamby |
description |
Currently when item information is gathered for an item the CT field contains the FID_DESTINATION_LOCATION which seems to translate in Evergreen to the item's circ library. If there is a hold on the item the hold pickup library goes to the AP field.
The CT field is part of the 3M spec though the AP is not and the CT is defined as "current location" which is a bit ambiguous. The current interpretation causes issues for third party services that assume the actual current item location, i.e. hold pickup location, will be in the CT.
I'm divided on whether this is a bug and always changed or should be configurable to change. Are there currently any services using SIP that actually need the item's circulation library in the CT? |
The item's circulating library is returning in the AP field, that is the field that some services, based on their interpretation of SIP specification, use for hold pickup location. The 3M SIP2 specification actually refers to it as 'current location' and Evergreen takes a different interpretation of that. The actual pickup location is delivered in the CT field.
However, some services need the hold pickup library in the AP field.
I'm divided on whether this is a bug and always changed or should be configurable to change. Are there currently any services using SIP that actually need the item's fields as is?
[edited because I needed more coffee this morning] |
|
