| Requirement | Status | Priority | Use Cases |
|---|
| (SAMPLE) Library must be able to print claim to pdf based on a specified template defined in Settings | | | Library has identified that a material due for receiving is "past due" based on the expected arrival date and needs to notify the vendor of such. Library communicates via email or submits a claim in the vendor system. Copyright Office will also send paper mail to certain vendors because they are required to send "Registered" mail that is signed and returned (often now they are sending pdf copies alongside that paper copy) |
| | | Copyright is actually sending claims to publishers. They manage claims differently from the rest of the library, with different legal wording in claims. |
| | | The system identifies that a material due for receiving is "past due" based on the expected receipt date. The system alerts a user that the material is overdue so they can take action. The system identifies the claiming deadline for the material in question so the user is aware of whether a claim can still be made, or how much time they have left to complete the claim. - LC groups rely on reports being generated from the ILS that identify what needs to be claimed OR users are manually identifying this (notice something is missing when opening a package or reviewing the list of expected issues)
|
| | | User is able to decide not to make claims for specific orders or based on the details of specific orders. |
| | | User is not ready to claim material but wants the notification to appear again after a specific interval |
| | | User is following up on a claim made by another librarian and that staff member is not available for consultation |
| | | The ability to run a report/generate a list of "past due" expected issues would be very helpful, so that we can pick and choose which issues we want to claim and send to the vendor in batches, rather than issue by issue. |
| | | Some vendors have very short claiming windows and LC does not have the staff to meet those deadlines in many cases. Automated electronic claiming would allow the library to meet those deadlines. If we don't meet the claiming window we often have to rebuy something and this value could be better sent elsewhere. |
| | | Audit trail is useful when claim deadlines are tight and claims must be submitted within a specific window for a given item. Generally the window is around 90 days. |
| Monographs Specific |
| | | User is able to open a claim for a single title on a specific order |
|
| | User is able to claim multiple titles from a given vendor. Often send a list of claims to EBSCO for example |
| Serials Specific |
| | | Irregular shipments of serial issues are especially prevalent with exchange partners. In the case that there are 2 copies ordered it can be difficult to determine which issue for which copy should be claimed. |
| | | User is able to open a claim for a single title volume/issue on a specific order |
|
| | User is able to claim multiple titles from a given vendor. Often send a list of claims to EBSCO for example |