| Info |
|---|
Auf dieser Seite werden die Ticket-Bewertung der Zeitschriftenbearbeitung beschrieben. |
| Info | ||||
|---|---|---|---|---|
| ||||
|
| Info | ||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||
|
Proposal UB Leipzig and SLUB Dresden
| Info | ||
|---|---|---|
| ||
Proposals on claims for monographs (Google-Präsentation) |
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
- 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
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
- 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
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
- 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
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
- 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.