Skip to end of banner
Go to start of banner

01 Ticket-Bewertung (Zeitschriftenbearbeitung) - Funktionsanalyse

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Auf dieser Seite werden die Ticket-Bewertung der Zeitschriftenbearbeitung beschrieben.

Inhalt

Übersicht und Status

Status

VORGESTELLT IN D-ERWERBUNG

Kategorie

PROZESS

Ersteller

SLUB DRESDEN UB LEIPZIG

Unterstützer

-

Beginn

 

Proposal UB Leipzig and SLUB Dresden

Initial proposal on claims for monographs

Proposals on periodicals and subscriptions - extended version (Google-Präsentation)
https://docs.google.com/presentation/d/1kYU3yR00QgIjPTm6lIhRg4R-dLOSg02GLRFJdCi7x-g/edit#slide=id.g118aa0e053b_0_35 - Slides 04-07


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-194 - Getting issue details... STATUS

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.




  • No labels