Prediction patterns are used to create serial items in advance for receiving and claiming purposes. Prediction patterns allows users to:
MARC Holdings fields 853, 854, 855 can be added:
Multi-level serials prediction patterns can be created in a MARC Holdings record for more complex serials, such as a monthly serials with an annual index and an annual supplement:
Note: Predicted items use the “Issue date” from the "Next Predicted Items Information" + “Subscription interval” from the POL to create the Expected date of arrival
One of the following roles are required to create or edit holdings records:
Requirements to use prediction patterns in Alma:
MARC Holdings Records contain 4 basic components:
Prediction patterns use numeric values to represent months and seasons, unless description templates have been configured to allow the user to use the alphabetic representation of the month or season.
Required MARC Holdings fields for publication patterns:
MARC 853, 854, and 855 are made up of:
Other MARC Holdings fields (not required for publication patterns in Alma):
The following is required to use prediction patterns in Alma:
Description templates are used to format the item description for display in the item record and in Primo VE. Alma will use the default description template if no other description templates have not been configured by the institution. Description templates are created based on ANSI NISO standards or an institution’s internal policy.
One of the following roles is required to configure description templates:
To configure description templates:
Detailed FAQ on configuring description templates: https://slcny.libguides.com/c.php?g=986218&p=8187563
Requirements for the associated POL with an active subscription:
From the POL and the "Next predicted item's information" the expected date of arrival is determined:
“Issue date” + “Subscription interval” = “Expected date of arrival”
To add a MARC holdings 853 using a template:
NOTE: MARC Holdings 853 is being used as the example, but the same workflow can also be applied to MARC holdings 854 and 855.
To populate the "Next predicted item information":
To populate the “Expected Item Information”:
To create new predicted items from the “List of Items” the following is required:
To created new predicted items from the “List of Items”
NOTE: Any changes that need to be made to the predicted items and/or serials items publication pattern changes must be done in the MD Editor to be reflected.
Alma provides an out-of-the-box rules that are applied when holdings records are saved using "MARC21 holding normalize on save." The out-of-the-box tasks included in the "MARC21 holding normalize on save" rule are applied to a holdings record when it is saved and when items are received from predicted items. Additional tasks can be added to the "MARC21 holding normalize on save" rule that will automate summary holdings tasks for serials. Adding the tasks to the "MARC21 holding normalize on save" rule to automate summary holdings will not impact monograph holdings records.
The following summary holdings tasks for serials holdings records can be added to automate the creation and maintenance of holdings records:
Adding the three additional tasks will, when added in the correct order, delete MARC 863/864/865 and MARC 866/867/868 and created new MARC 863/864/864 and 866/867/888 automatically when items are received under Acquisitions>Receiving and Invoicing>Receive.
To edit the "MARC21 holding normalize on save" rule to automate summary holdings tasks:
IMPORTANT!!! READ BEFORE PROCEEDING: It is recommended to run a MARC holdings normalization rule/process on existing serials holdings records and add "$$8 9" to the MARC 863/864/865/866/867/868 fields the institution wants to retain prior to adding the additional tasks to automate summary holdings in Alma. If "$$8 9" is not added to these fields prior to adding the additional tasks, they will be deleted the next time the holdings record is saved or a predicted item is received. Note that any additional 866/867/868 will display in Primo VE with the library's holdings, which may cause confusion for the end user depending on how they have been structured.
Below is the "SUNY - Remove 863/4/5/6/7/8 (holdings)" normalization rule:
rule "delete 863 4 5 6 7 8 if it does not have subfield 8 9"
removeField "863" if (not exists "863.8.9")
removeField "864" if (not exists "864.8.9")
removeField "865" if (not exists "865.8.9")
removeField "866" if (not exists "866.8.9")
removeField "867" if (not exists "867.8.9")
removeField "868" if (not exists "868.8.9")
To duplicate the "SUNY - Remove 863/4/5/6/7/8 (holdings)" normalization rule: