You define interpretation codes by specifying an interpretation string. An interpretation string is a string of units, separated by commas but no spaces. Units are the calendar units displayed, such as months of the year, seasons, and days of the week. This string operates as a closed set of calendar units for Horizon to use when displaying chronology. For example, this is a common interpretation string to provide seven units when displaying days of the week:
“Sunday,Monday,Tuesday,Wednesday,Thursday,Friday,Saturday”
When you enter numbers in the Instance String field for prediction setup, Horizon matches the numbers with the positions of the interpretation string units. For example, if you entered “2,5” in the Instance String field of the Edit Prediction window and selected Day as the Instance Unit, Horizon would display “Monday” (the unit that corresponds with two) and “Thursday” (the unit that corresponds with five).
Interpretation strings control these things:
• | The way Horizon interprets the display of a given calendar unit—whether the unit is abbreviated or completely spelled out. |
• | What unit equals the numbers entered in the Interpretation String field of a prediction setup. (For example, in one of the most common interpretation strings, shown below, Sunday equals “1,” Monday equals “2,” and so forth.) |
“Sunday,Monday,Tuesday,Wednesday,Thursday,Friday,Saturday”
Interpretation does not refer to the type of number used (such as Arabic or Roman); number displays are determined on the third page of the Edit Prediction window.
Chronology patterns use interpretation strings to specify how Horizon should display or interpret any calendar units in the chronology that need interpretation. Units might include:
• | Days of the week |
• | Months |
• | Seasons |
To set up interpretation codes
1 |
|
Horizon displays the Copy List window.
2 | Highlight the issue that you want to set up. |
3 | Click Prediction. |
Horizon opens the Serials Prediction Table window for the serial copy record.
4 | Click Page Down or resize the window to display these fields in the Edit Serials Prediction Table window: |
5 | Click Codes. |
Horizon opens the Code Lookup Chronology Pattern Codes window.
6 | Click Add. |
Horizon opens a blank Edit Chronology Pattern Codes window:
7 | Click Codes to the right of the Interpretation field. |
Horizon opens the Code Lookup Chronology Interpretation Strings window.
8 | Click Add. |
Horizon opens the Edit Chronology Interpretation Strings window:
9 | Enter the code Horizon uses to identify the interpretation string in the Interp. Code field. |
(For example, if you are defining an interpretation string that causes Serials to display abbreviated months, you might enter “MonAbbr” as the code.)
10 | Enter a description of the interpretation string in the Description field. |
(For example, an interpretation code “DoW” has little meaning unless a description accompanies it, such as “Full name of days of week.”)
11 | Specify the possible values in the Strings field that Horizon can display when using a given interpretation code. |
For example, if you are defining an interpretation code for abbreviated months, you would enter the following in the Strings field:
When a publication pattern is set up, the frequency refers to the string. (For example, a frequency of “3,6,9,12” that uses a Chron. Pattern code containing the “MonAbbr” interpretation string would look for the third entry in the string, “Mar.”, the sixth, “Jun.”, the ninth, “Sep.”, the twelfth, and “Dec.”, the fifteenth.)
Note: If you want punctuation, such as a period, to be included in the display for a given value, you must include that punctuation with each value in the strings list. Do not enter spaces in the string. Commas entered between each unit in the string are not included in the display. To cause a comma to be included in a display, use the Label entry box in the Edit Chronology Pattern Parts window. (For more information, see the next section.)
12 | Save the file. |
© 1998-2017 Sirsi Corporation