• In German libraries, specific demands on the management of periodicals exist, which are mostly not available in Folio. Especially in big libraries the ordering, receiving, claiming, … of several subscriptions of one periodical title are necessary and should be assisted by automatisms. 

  • Example: SLUB Dresden holds 7.432 active print subscriptions and in 2021 (January until September) around 30.200 issues were checked in. 

• The aim of the presentation is to explain the necessary adjustments. To reach the aim, in the following sections planned developments and missing elements and functions are described. 

  • Jira-tickets concerning the claiming process in Folio

  • Functions, which should be implemented or improved in Folio

    • 01 Einleitung und Ticket-Bewertung (Zeitschriftenverwaltung) - Funktionsanalyse
    • 02 Abonnement-Verwaltung (Zeitschriftenverwaltung) - Funktionsanalyse
    • 03 Mahneinstellungen (Zeitschriftenverwaltung) - Funktionsanalyse
    • 04 Inventarisierung (Zeitschriftenverwaltung) - Funktionsanalyse
    • 90 Serials App | Erscheinungsmuster - Funktionsanalyse
    • 91 Serials App | fehlende Funktionen - Funktionsanalyse

     

https://folio-org.atlassian.net/browse/UIOR-253

• 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

https://folio-org.atlassian.net/browse/UIOR-254

• 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

https://folio-org.atlassian.net/browse/UXPROD-194

• 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

https://folio-org.atlassian.net/browse/UXPROD-1845

• 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.