Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

Auf dieser Seite werden vorhandene Tickets bezüglich der Zeitschriftenbearbeitung Zeitschriftenverwaltung bewertet.


Info
iconfalse
titleInhalt

Table of Contents

Proposal UB Leipzig and SLUB Dresden

Info
titleInitial 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 03-07

Introduction

  • 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
      Child pages (Children Display)
      pageZeitschriftenverwaltung - Funktionsanalyse

Description Jira-tickets

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUIOR-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

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUIOR-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

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-194

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1845

...