...
- Description:
- There is no functionality in Folio to manage periodical subscriptions and claimings.
- Proposals:
- The management of the subscription and its claiming should be located in the app Order (André Hohmann : or partly in the app serials).
- In each Purchase order (PO), the elements to manage the subscription and claiming are necessary.
- It could look like this in the app orders:
General description
- Terminology
- Subscription plan: A list of expected issues of a periodicals with defined values such as issue name, sort count, expected publication date.
- Claiming plan: A list of claiming information about each expected issue.
- In this analysis, both plans are combined in the accordion i.
- Subscription:
- In the PO, it should be possible to define standard values to facilitate the check-in of issues by automatically writing the standard values in the defined fields
- In each PO, the accordion “Subscription standard values” should be implemented.
- It must be possible to assess the most applied parameters in the settings as for example the location, loan types, statistical codes, … Thus, each institution can define its own set of parameters for the standard values. This could be configurable in the settings.
- It must be possible to enter basic information to create the issue caption automatically. This includes the number of volume, the number of issue, the first date of issuance, … It must be possible to agree on a specific set, which can be applied by all institutions, because specific functions need to be implemented.
- Claiming:
- In each PO, the accordions “Subscription caption values” and “Claiming information” should be implemented.
- It must be possible to enter basic information to derive the the dates on which the issues should be delivered. This includes the number of volume, the number of issue, the first date of issuance, … It must be possible to agree on a specific set, which can be applied by all institutions, because specific functions need to be implemented.
- It must be possible to manage the claiming process by an overview of received and expected issues and by implementing a batch claim process.
- Some values in “Claiming information” must be modifiable, in case of undeliverable issues, delays in delivery … as for example: caption, date due, claim 1-4, claim code
...
The following fields describe the dates, which are entered in the caption automatically.
- Claim 1
- The date when the first claim should be sent
- Claim 2
- The date when the second claim should be sent
- Claim 3
- The date when the third claim should be sent
- Claim 4
- The date when the fourth claim should be sent
- Claim code
- Located in the settings
- Definition of the claim periods on which the above mentioned claim dates are derived
The following functionality is necessary:
- A line can be deleted: This is necessary, when an issue is not published and neither needs not to be received nor claimed.
- A line can be edited: This is necessary, when an issue consists of two issues, as for example: "Bd.1 H. 7/8" for July and August issues. Theses use cases may not be regarded in the automatic creation of the subscription plan.
Accordion Subscription standard values
...