UXPROD-4186 - Getting issue details... STATUS
Problem(s):
When user has made the decision to make a claim for a piece of material the user will be able to generate and share that information with the vendor
Requirements and Use Cases:
| Requirement | Status | Priority | Use Cases |
|---|---|---|---|
| (SAMPLE) Library must be able to print claim to pdf based on a specified template defined in Settings | PENDING | MEDIUM | Library has identified that a material due for receiving is "past due" based on expected arrival date and needs to notify the vendor of such. Library communicated a pdf via email. |
PENDING | HIGH | System identifies that a material due for receiving is "past due" based on expected receipt date. System alerts a user that the material is overdue so they can take action. | |
PENDING | LOW | User decides not to make claims for specific order... | |
PENDING | HIGH | User is not ready to claim material but wants the notification to appear again after a specific interval | |
PENDING | User is following up on a claim made by another librarian and that staff member is not available for consultation | ||
| Monographs Specific | |||
| Serials Specific | |||
Questions:
| Question | Status | Conclusion | Comments |
|---|---|---|---|
| What order and receiving fields are required? | OPEN | ||
| Can you provide examples of your current claim form? For serials and for monographs | |||
| Is there a use case in which in serials receiving a received issue does not trigger a claim for the prior unreceived issue? I.e., should receiving an issue automatically trigger a claim if the previous issue is unreceived? | OPEN | ||
| Is there a use case for searching open claims or viewing all open claims? | OPEN |