| 2022-10-06 15:11:24 |
Dale Rigney |
bug |
|
|
added bug |
| 2022-10-06 15:12:10 |
Dale Rigney |
description |
An item at system 1 with an age protection set up to system level can be captured for a hold at system 2 when the pickup library has an actor.org_unit_proximity record containing the absolute_adjustment flag set to true. You can duplicate the issue with the following settings/org unit setup:
Consortium |
|
SyS1 Sys2
| |
BRN1 BRN2 BRN3 BRN4
|
Locker1
Place a hold with the requestor of Sys2 and the pickup library of Locker1
Create an Age protection rule with item age = 3 mons and Allowed Proximity of 2.
Create an Item with circ and owning lib = BRN1.
Add the age protection rule to the item created above.
Create an actor.org_unit_proximity_adjustment record with Hold Pickup library = Locker1, Hold Request Lib = SYS2, Position = 0, Proximity Adjustment = 0, and absolute_adjustment = True.
Set library setting circ.holds.calculated_age_proximity for BRN1 = True.
Evergreen will allow the created item to fill the hold at Locker1 when requested by Sys2. I believe Evergreen is overriding the correct proximity value with a value of 0 due to the absolute_adjustment flag being set to true in the actor.org_unit_proximity record. When you change the absolute_adjustment flag to false the hold is rejected with the config.rule_age_hold_protect.prox. If the items owing library is not using the circ.holds.calculated_age_proximity library setting this hold would also be rejected. |
An item at system 1 with an age protection set up to system level can be captured for a hold at system 2 when the pickup library has an actor.org_unit_proximity record containing the absolute_adjustment flag set to true. You can duplicate the issue with the following settings/org unit setup:
Consortium
|
SyS1 Sys2
| |
BRN1 BRN2 BRN3 BRN4
|
Locker1
Place a hold with the requestor of Sys2 and the pickup library of Locker1
Create an Age protection rule with item age = 3 mons and Allowed Proximity of 2.
Create an Item with circ and owning lib = BRN1.
Add the age protection rule to the item created above.
Create an actor.org_unit_proximity_adjustment record with Hold Pickup library = Locker1, Hold Request Lib = SYS2, Position = 0, Proximity Adjustment = 0, and absolute_adjustment = True.
Set library setting circ.holds.calculated_age_proximity for BRN1 = True.
Evergreen will allow the created item to fill the hold at Locker1 when requested by Sys2. I believe Evergreen is overriding the correct proximity value with a value of 0 due to the absolute_adjustment flag being set to true in the actor.org_unit_proximity record. When you change the absolute_adjustment flag to false the hold is rejected with the config.rule_age_hold_protect.prox. If the items owing library is not using the circ.holds.calculated_age_proximity library setting this hold would also be rejected. |
|
| 2022-10-06 16:40:13 |
Tiffany Little |
tags |
|
circ-holds circulation |
|
| 2022-10-07 13:59:02 |
Dale Rigney |
description |
An item at system 1 with an age protection set up to system level can be captured for a hold at system 2 when the pickup library has an actor.org_unit_proximity record containing the absolute_adjustment flag set to true. You can duplicate the issue with the following settings/org unit setup:
Consortium
|
SyS1 Sys2
| |
BRN1 BRN2 BRN3 BRN4
|
Locker1
Place a hold with the requestor of Sys2 and the pickup library of Locker1
Create an Age protection rule with item age = 3 mons and Allowed Proximity of 2.
Create an Item with circ and owning lib = BRN1.
Add the age protection rule to the item created above.
Create an actor.org_unit_proximity_adjustment record with Hold Pickup library = Locker1, Hold Request Lib = SYS2, Position = 0, Proximity Adjustment = 0, and absolute_adjustment = True.
Set library setting circ.holds.calculated_age_proximity for BRN1 = True.
Evergreen will allow the created item to fill the hold at Locker1 when requested by Sys2. I believe Evergreen is overriding the correct proximity value with a value of 0 due to the absolute_adjustment flag being set to true in the actor.org_unit_proximity record. When you change the absolute_adjustment flag to false the hold is rejected with the config.rule_age_hold_protect.prox. If the items owing library is not using the circ.holds.calculated_age_proximity library setting this hold would also be rejected. |
An item at system 1 with an age protection set up to system level can be captured for a hold at system 2 when the pickup library has an actor.org_unit_proximity record containing the absolute_adjustment flag set to true. You can duplicate the issue with the following settings/org unit setup:
Consortium
|
SyS1 Sys2
| |
BRN1 BRN2 BRN3 BRN4
|
Locker1
Place a hold with the requestor of Sys2 and the pickup library of Locker1
Create an Age protection rule with item age = 3 mons and Allowed Proximity of 2.
Create an Item with circ and owning lib = BRN1.
Add the age protection rule to the item created above.
Create an actor.org_unit_proximity_adjustment record with Hold Pickup library = Locker1, Hold Request Lib = SYS2, Position = 0, Proximity Adjustment = 0, and absolute_adjustment = True.
Set library setting circ.holds.calculated_age_proximity for BRN1 = True.
Evergreen will allow the created item to fill the hold at Locker1 when requested by Sys2. I believe Evergreen is overriding the correct proximity value with a value of 0 due to the absolute_adjustment flag being set to true in the actor.org_unit_proximity record. When you change the absolute_adjustment flag to false the hold is rejected with the config.rule_age_hold_protect.prox. If the items owing library is not using the circ.holds.calculated_age_proximity library setting this hold would also be rejected. |
|
| 2022-10-07 13:59:34 |
Dale Rigney |
description |
An item at system 1 with an age protection set up to system level can be captured for a hold at system 2 when the pickup library has an actor.org_unit_proximity record containing the absolute_adjustment flag set to true. You can duplicate the issue with the following settings/org unit setup:
Consortium
|
SyS1 Sys2
| |
BRN1 BRN2 BRN3 BRN4
|
Locker1
Place a hold with the requestor of Sys2 and the pickup library of Locker1
Create an Age protection rule with item age = 3 mons and Allowed Proximity of 2.
Create an Item with circ and owning lib = BRN1.
Add the age protection rule to the item created above.
Create an actor.org_unit_proximity_adjustment record with Hold Pickup library = Locker1, Hold Request Lib = SYS2, Position = 0, Proximity Adjustment = 0, and absolute_adjustment = True.
Set library setting circ.holds.calculated_age_proximity for BRN1 = True.
Evergreen will allow the created item to fill the hold at Locker1 when requested by Sys2. I believe Evergreen is overriding the correct proximity value with a value of 0 due to the absolute_adjustment flag being set to true in the actor.org_unit_proximity record. When you change the absolute_adjustment flag to false the hold is rejected with the config.rule_age_hold_protect.prox. If the items owing library is not using the circ.holds.calculated_age_proximity library setting this hold would also be rejected. |
An item at system 1 with an age protection set up to system level can be captured for a hold at system 2 when the pickup library has an actor.org_unit_proximity record containing the absolute_adjustment flag set to true. You can duplicate the issue with the following settings/org unit setup:
Consortium
|
SyS1 Sys2
| |
BRN1 BRN2 BRN3 BRN4
|
Locker1
Place a hold with the requestor of Sys2 and the pickup library of Locker1
Create an Age protection rule with item age = 3 mons and Allowed Proximity of 2.
Create an Item with circ and owning lib = BRN1.
Add the age protection rule to the item created above.
Create an actor.org_unit_proximity_adjustment record with Hold Pickup library = Locker1, Hold Request Lib = SYS2, Position = 0, Proximity Adjustment = 0, and absolute_adjustment = True.
Set library setting circ.holds.calculated_age_proximity for BRN1 = True.
Evergreen will allow the created item to fill the hold at Locker1 when requested by Sys2. I believe Evergreen is overriding the correct proximity value with a value of 0 due to the absolute_adjustment flag being set to true in the actor.org_unit_proximity record. When you change the absolute_adjustment flag to false the hold is rejected with the config.rule_age_hold_protect.prox. If the items owing library is not using the circ.holds.calculated_age_proximity library setting this hold would also be rejected. |
|
| 2022-10-07 14:00:49 |
Dale Rigney |
description |
An item at system 1 with an age protection set up to system level can be captured for a hold at system 2 when the pickup library has an actor.org_unit_proximity record containing the absolute_adjustment flag set to true. You can duplicate the issue with the following settings/org unit setup:
Consortium
|
SyS1 Sys2
| |
BRN1 BRN2 BRN3 BRN4
|
Locker1
Place a hold with the requestor of Sys2 and the pickup library of Locker1
Create an Age protection rule with item age = 3 mons and Allowed Proximity of 2.
Create an Item with circ and owning lib = BRN1.
Add the age protection rule to the item created above.
Create an actor.org_unit_proximity_adjustment record with Hold Pickup library = Locker1, Hold Request Lib = SYS2, Position = 0, Proximity Adjustment = 0, and absolute_adjustment = True.
Set library setting circ.holds.calculated_age_proximity for BRN1 = True.
Evergreen will allow the created item to fill the hold at Locker1 when requested by Sys2. I believe Evergreen is overriding the correct proximity value with a value of 0 due to the absolute_adjustment flag being set to true in the actor.org_unit_proximity record. When you change the absolute_adjustment flag to false the hold is rejected with the config.rule_age_hold_protect.prox. If the items owing library is not using the circ.holds.calculated_age_proximity library setting this hold would also be rejected. |
An item at system 1 with an age protection set up to system level can be captured for a hold at system 2 when the pickup library has an actor.org_unit_proximity record containing the absolute_adjustment flag set to true. You can duplicate the issue with the following settings/org unit setup:
Consortium
|
SyS1 Sys2
| |
BRN1 BRN2 BRN3 BRN4
|
Locker1
Place a hold with the requestor of Sys2 and the pickup library of Locker1
Create an Age protection rule with item age = 3 mons and Allowed Proximity of 2.
Create an Item with circ and owning lib = BRN1.
Add the age protection rule to the item created above.
Create an actor.org_unit_proximity_adjustment record with Hold Pickup library = Locker1, Hold Request Lib = SYS2, Position = 0, Proximity Adjustment = 0, and absolute_adjustment = True.
Set library setting circ.holds.calculated_age_proximity for BRN1 = True.
Evergreen will allow the created item to fill the hold at Locker1 when requested by Sys2. I believe Evergreen is overriding the correct proximity value with a value of 0 due to the absolute_adjustment flag being set to true in the actor.org_unit_proximity record. When you change the absolute_adjustment flag to false the hold is rejected with the config.rule_age_hold_protect.prox. If the items owing library is not using the circ.holds.calculated_age_proximity library setting this hold would also be rejected. |
|
| 2022-12-16 21:57:46 |
Susan Morrison |
bug |
|
|
added subscriber Susan Morrison |
