Example 6: Setting Up Prediction with an Exception

This example shows how to set up prediction for a title that:

Is published twice each month on the first and third weeks except for December, when one issue is published
Has a chronology for all months, except December, that looks like this: January 3, 2002
Has a chronology for only December that looks like this: December 2002
Has an enumeration for all issues that looks like this: V. 13 N. 1
Increases its volume and resets its issue number the first day of every calendar year (January 1)

For this prediction, you set up the frequency for the issues published every month, specifying that December is an exception to (or exempt from) the frequency. You then set up the frequency for the December issues. Because both setups are for issues belonging to the main run, Serials combines them in the correct chronological order. The Test Prediction window at the end of these steps illustrates this combined prediction.

To set up prediction with an exception

1 Search for the serials title you want and send it to Serials Control, if necessary.

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 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 for the current year in the Appl. Date field (for example, enter “01‑01‑02”).

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/2000, then you should enter “01/01/2000” 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 “0101”.

End mm‑dd

Enter “1231”.

Exceptions group Start mm‑dd

Enter “1201”.

Exceptions group End mm‑dd

Enter “1231”.

Claim Delay

Leave the default setting.

Summary of Holdings Note

Mark the box.

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 date year” in the Chron. Pattern field. Choose Codes to find this pattern.
11 Complete the frequency fields listed:

Field

Action

Instance string

Enter “1,3”.

Instance Unit

Mark Week of.

Every

Enter “1”.

A blank is the same as 1.

Calendar Unit

Mark Month.

The screen should resemble this example:

12 Click Page Down or resize the window to display 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

Leave the default “0”, or enter “1”.

Label

Enter “V”.

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 “N”.

Data Type

Mark Numeral.

Cal. Change

Enter “11”.

Calendar Reset

Mark the box.

The second group entry should resemble this example:

16 Save your changes.
17 Click Close.

Horizon returns to the Prediction Table window.

18 Click Test Prediction.

Horizon opens the Test Prediction window:

 

19 Click Close.

Horizon reopens the Prediction Table window. You are now ready to set up prediction for the December exception.

To set up the exception

1 Search for the serials title you want and send it to Serials Control, if necessary.

Horizon displays the Copy List window.

2 If no copy record exists, create a copy record for the title. (For more information, see Creating or Editing a Copy Record.)
3 Highlight the copy record with the media type for which you want to set up this prediction.
4 Click Prediction.

Horizon opens the Prediction Table window.

5 Choose New on the Prediction Table window.

Horizon opens the Edit Serials Prediction window, overlaid by the Edit Run Code and Applicability Date window.

6 Enter the code for the main run in the Run field.

Note: Since the December issue is considered part of the main run, make sure you enter the same run code as you did for the issues published twice monthly.

7 Enter the first of January for the current year in the Appl. Date field (for example, enter “01‑01‑02”).

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/2000, then you should enter “01/01/2000” as the applicability date from which Serials should begin predicting issues.)

Note: Since the December issue is considered part of the main run, make sure you enter the same applicability date as you did for the issues published twice monthly.

8 Click OK, or press ENTER.

You return to the first page of the Edit Serials Prediction Table window.

9 Complete the fields in the window:

Field

Action

Ord

Enter “1”.

Start mm‑dd

Enter “1201”.

End mm‑dd

Enter “1231”.

Claim Delay

Leave the default setting.

Summary of Holdings Note

Mark the box.

No. of Rcpts.

Leave the default setting.

Sum of Delays

Leave the default setting.

The screen should resemble this example:

10 Click Page Down or resize the window to display the Chron. Pattern field.
11 Enter the code for “month year” in the Chron. Pattern field, or click Codes to find this pattern.
12 Complete the fields on the window:

Field

Action

Instance string

Enter “2”.

Instance Unit

Click Week of.

Every

Enter “1”.

A blank is the same as 1.

Calendar Unit

Mark Month.

The screen should resemble this example:

13 Click Page Down or resize the window to display the Enum. Pattern group.

Horizon displays the fields already filled in since the exception is part of the main run and shares the enumeration of the other issues.

Important: If you change the enumeration for the exception, you will change it for the other issues.

14 Save your changes.
15 Click Close.

Horizon returns to the Prediction Table window:

16 Click Test Prediction.

Horizon opens the Test Prediction window:

 

17 Click More to see more predictions in the list.
18 Click Close.

Horizon returns to the Prediction Table window.

 


© 1998-2017 Sirsi Corporation