Auf dieser Seite werden die Ticket-Bewertung der Zeitschriftenbearbeitung beschrieben.
Proposal UB Leipzig and SLUB Dresden
Initial proposal on claims for monographs
Proposals on claims for monographs (Google-Präsentation)
https://docs.google.com/presentation/d/1GOSz3n8ui8MYAIs7aBpOrexZ1G-reoAXL41HX2MkTHY/edit#slide=id.g118bacca5e6_0_15 - Slides 4-10
UXPROD-194 - Getting issue details... STATUS
- Description:
- Problem: User has to add each expected piece individually. Pieces are added almost daily while ordering is active and this can consume a significant amount of time. Patterns might also trigger automated claiming when an issue is overdue
- Workflow mockups: https://drive.google.com/drive/folders/1EDEZAWpteiV-NZc_W9sjfTWlr4bpmd7N?usp=sharing
UIOR-253 - Getting issue details... STATUS
- Description:
- If check-in pattern and frequency can be discerned, create pending check-in pieces automatically, e.g. if monthly, with annual renewal, create 12 pending check-in pieces
UIOR-254 - Getting issue details... STATUS
- Description:
- If a user checks in a piece on an ongoing order, and there's no pending piece, create the next pending piece automatically. Maybe use the most recent existing item record as the default/template for the next one, so the user only has to change the enumeration/chronology and barcode
UXPROD-1845 - Getting issue details... STATUS
- Description:
- Claims are filed via multiple communication methods (Eg. EDIFACT, e-mail or printed). This is different depending on if this is an ongoing order (maybe based on prediction or patterns) or one-time order (based on order date and expected delivery period from vendor). Consider splitting in order to prioritize feature.