Currently, all claiming is manual, but the admin module enables you to build claim policies and specify the action(s) that users should take to claim items.
The claim policy link enables you to name the claim policy and specify the organization that owns it.
Select an org unit from the drop-down menu. The org unit indicates the organizational units whose staff can use this claim policy. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Administration → Server Administration → Organizational Units).
The rule of parental inheritance applies to this list.
The claim type link enables you to specify the reason for a type of claim.
Select an org unit from the drop-down menu. The org unit indicates the organizational units whose staff can use this claim type. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Administration → Server Administration → Organizational Units).
The rule of parental inheritance applies to this list.
The claim event type describes the physical action that should occur when an item needs to be claimed. For example, the user should notify the vendor via email that the library is claiming an item.
Select an org unit from the drop-down menu. The org unit indicates the organizational units whose staff can use this event type. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Administration → Server Administration → Organizational Units).
The rule of parental inheritance applies to this list.
If this claim is initiated by the user, then check the box adjacent to Library Initiated.
Currently, all claims are initiated by a user. The ILS cannot automatically claim an issue.
The claim policy action enables you to specify how long a user should wait before claiming the item.
You can create claim cycles by adding multiple claim policy actions to a claim policy.