This example shows how to set up prediction for a title that:
• | Is published bimonthly the entire year (6 issues) |
• | Has a chronology that looks like this: Mar/Apr. 2002 |
• | Has an enumeration that looks like this: VOLUME 24, NUMBER 1 |
• | Increases its volume and resets its issue number the first day of every calendar year (January 1) |
To set up a bimonthly prediction
1 |
|
Horizon displays the Copy List window.
2 | Choose the copy record with the media type for which you want to set up this prediction, or create a new copy record. (For more information, see Creating or Editing a Copy Record.) |
3 | Click Prediction. |
Horizon opens the Prediction Table window.
4 | Click New. |
Horizon opens the Edit Serials Prediction Table window, overlaid by the Edit Run Code and Applicability Date window.
5 | Enter the code for the main run in the Run field. |
6 | Enter the first of January and the current year in the Appl. Date field (for example, enter “01‑01‑03”). |
The applicability date represents the date when Serials should begin predicting issues, not the date when the title was first published or the date when you first started receiving the title. This means that you should enter a date that makes sense for Serials to use to predict future issues. (For example, if you started receiving a monthly title on 06/15/2003, then you should enter “01/01/2003” as the applicability date from which Serials should begin predicting issues.)
7 | Click OK, or press ENTER. |
Horizon returns to the first page of the Edit Serials Prediction Table window.
8 | Complete the fields on the window: |
Field |
Action |
Ord |
Enter “0”. |
Start mm‑dd |
Enter “01‑01”. |
End mm‑dd |
Enter “12‑31”. |
Claim Delay |
Leave the default setting. |
Summary of Holdings Note |
Mark the box so that it is active. |
No. of Rcpts. |
Leave the default setting. |
Sum of Delays |
Leave the default setting. |
The screen should resemble this example:
9 | Click Page Down or resize the window to display the Chron. Pattern field. |
10 | Enter the code for “month/month year” in the Chron. Pattern field, or click Codes to locate this pattern. |
This pattern causes Serials to display the chronology as two months separated by a slash (for example: June/July 2002). (If this chronology pattern does not exist, see Creating a Chronology Pattern.)
11 | Complete the frequency fields listed: |
The screen should resemble this example:
Note: You must enter numbers in the Instance String field in ascending order. In other words, you cannot enter lower numbers after higher numbers in the Instance String field. (For example, for a bimonthly issue that is published as a Dec./Jan. issue, enter “12/13” in the Instance String field. Serials reads the number “13” as January.)
12 | Display the page with the Enum. Pattern group. |
13 | Enter this information in the first of two group entries (you will have one entry for the volume level and one for the number level): |
Field |
Action |
Enum. Group |
Leave the default “0”. |
Level |
Enter “1”. |
Label |
Enter “VOLUME”. |
Data Type |
Mark Numeral. |
The group entry should resemble this example:
14 | Click New to display a second group entry. |
15 | Complete the second group entry for the number level: |
Field |
Action |
Enum. Group |
Leave the default “0”. |
Level |
Enter “2”. |
Label |
Enter “NUMBER”. |
No. Units/Level |
Enter “6” (6 issues). |
Data Type |
Mark Numeral. |
The second enumeration group entry should resemble this screen:
16 | Save your changes. |
17 | Click Close. |
Horizon opens the Prediction Table window.
18 | Click Test Prediction. |
Horizon opens the Test Prediction window:
19 | Click More to see more predictions in the list. |
20 | Click Close. |
Horizon returns to the List Prediction Table window.
© 1998-2017 Sirsi Corporation