CURRENT HYPOTHESIS
Many sierra systems are configured to only allow bib level holds as a policy. this is to avoid “Sniping” - or targeting specific copies in order to jump the hold queue.
Normally (IIUC) in sierra, a bib level hold is converted into an item hold as soon as the system is an item comes free.
The current hypothesis is that Sierra has a policy enforcement option that will prevent DCB from placing an item hold in the virtual item just created.
In order to mitigate this, an option has been added to the Sierra HostLMS - the two options for sierra HostLMS implementations are:
Item hold
{
"id":"'`uuidgen --sha1 -n $HOSTLMS_NS_UUID --name TEST`'",
"code":"TEST",
"name":"Test",
"lmsClientClass": "org.olf.dcb.core.interaction.sierra.SierraLmsClient",
"clientConfig": {
....
"holdPolicy": "item"
....
}
}
Title hold
{
"id":"'`uuidgen --sha1 -n $HOSTLMS_NS_UUID --name TEST`'",
"code":"TEST",
"name":"Test",
"lmsClientClass": "org.olf.dcb.core.interaction.sierra.SierraLmsClient",
"clientConfig": {
....
"holdPolicy": "title"
....
}
}