Creating Prediction Patterns
Overview of Prediction Patterns
Examples for common prediction patterns can be found at: Serials - Prediction patterns guide and examples.docx
Prediction Pattern Maintenance
As stated in slide 13 (see PowerPoint link above), it is only possible to use Expand from Template to create the initial 853/854/855 field(s) in the holdings record; subsequent 853/854/855 field(s) must be created manually without the use of a template. Details that may need maintenance include caption changes, frequency changes, etc.
The example below shows a quarterly serial holdings record with an existing 853 & next predicted item's information already entered as shown by the presence of the binoculars icon next to the 853 field:
For example, if the frequency changes to annual in 2017, you can create a new 853 and update the next predicted item's information without the use of a template:
- Click on the binoculars icon, which will display the next predicted item's information
- Click Remove
- Put the cursor at the end of the 863 field. Hit the F8 key to add a new field
- Manually type in a new 853 field reflecting the new annual frequency: 853 2 0 $$8 2 $$a (year) $$w a
- Put the cursor at the beginning of the second 853 field and hit the F3 key to add the predicted item information for the next 2017 annual issue (see screenshot below)
- Click Close. Note that the Issue Date in the next predicted item's information must be in the eight-digit format shown in the screenshot below, otherwise you will receive a "subscription not active" error message when attempting to open the next set of predicted items.
- Save record (Control+S or go to File, then Save).
- Before opening the next predicted item for 2017, edit the subscription interval in the POL associated with the holdings above to reflect the new frequency (in this example, the subscription interval was changed to 545). Click Save in the POL after updating the subscription interval.
- You can open the new set of predicted items by navigating back to the holdings record in the MD Editor or navigating to the List of Items. In the new MD editor, click on Record Actions, and select Open Predicted Items, and hit Save. In the List of Items, click on the Manage Selected drop-down menu and select Open Predicted Items, and hit Save).\
- Save and release the holdings record in the MD Editor.
Suggested Alma Subscription Interval Values
Before opening predicted items, make sure that the subscription interval in the Alma order record is accurate. The table below provides suggested subscription interval values:
Frequency | Suggested Subscription Interval |
Weekly | 7-10 |
2x/month | 14-25 |
Monthly | 30 |
6x/year | 50-60 |
Quarterly | 50-90 |
3x/year | 80-120 |
2x/year | 95-180 |
Unknown frequency | 90-180 |
Annual | 360-545 |
After the prediction pattern has been created and the new set of items predicted, certain fields in the item records will need to be edited.
Updating Fields in New Predicted Items
The following fields will need to be updated manually at the point of receipt or (if permissions allow) by batch updating item records by creating an itemized set and running a job after opening newly predicted items in Alma (migrated predicted items will not require updating of these fields):
- Temporary locations: the location of newly predicted items will be the permanent location specified in the holdings record linked to the POL (i.e. you cannot specify a temp. loc. when opening predicted items in Alma unlike in Aleph).
- Material type: the material type of newly predicted items will be ISSUE in all circumstances, regardless of the material type specified in the POL. The 853X subfield o populated with material type (usually ISSBD) does not have any functionality in Alma.
- Item policy: the item policy will be blank in newly predicted items.
Also note that newly predicted items in Alma have process type Acquisitions.
Notes on Prediction Patterns Migrated from Aleph
Barcodes
Newly predicted items in Alma do not have a hyphenated barcode as they did in Aleph, so you cannot distinguish between predicted and non-predicted items based on barcode format. Predicted items migrated from Aleph to Alma will retain their hyphenated barcode after migration.