A prediction record contains information about a particular issue such as enumeration, chronology, and number of copies expected. A prediction record is the basis of information for issues on the Expected, Received, and Claimed tabs, although the issues that appear and the information that is included on each of these tabs varies based on the activity for each issue. For the most complete information regarding a particular prediction record, use the Show Issue Detail helper.
Prediction records may be created in a variety of ways:
| • | The final steps when creating a control record is to generate predictions. |
| • | If the Allow Automatic Prediction of Issues check box is selected on the Patterns tab of a serial control, predictions may be generated as part of the receipt process once the last predicted issue has been received. |
| • | The Generate Predictions for Expected Issues helper may be used at any time a serial control is being created or modified. |
| • | A single prediction record may be created or modified on the Expected tab of serial control. |
| • | A special or combined issue may be created at the time of receipt using the Different Issue option during the Check In Issues of a Serial wizard. |
Important Considerations When Working with Prediction Records
| • | When prediction records are auto-generated when only an enumeration pattern or only a chronology pattern is defined, you must click either Chronology or Enumeration in the Form of Name to Display on the OPAC Display tab to match the defined value. If you click Both, the defined value will appear in duplicate, like the following. |
| • | APR 1999 APR 1999 |
| • | You cannot generate predictions that have a chronology date, date expected, and date first prediction earlier than 1970. SirsiDynix Symphony will display an appropriate error message indicating that you are not able to create issues prior to this date. To represent historical holdings, you can do the following. |
| • | Update the MARC holdings record with a summary statement in the 866 tag that reflects the range of issues. |
| • | Do not create predictions. Instead, use the Check In Issues of a Serial wizard to receive special issues. Because you are not following a pattern when you use the special issue work flow, you are able to avoid the pre-1970 date limitation, and you can receive an issue with any date in the Chronology field. |
Prediction Record Fields
When a basic prediction record is being created or modified, the following fields may appear.
| • | Chronology |
| • | Comment |
| • | Date Expected |
| • | Date Prediction |
| • | Date to Claim |
| • | Enumeration |
| • | Fiscal Cycle |
| • | Holdings Link |
| • | Library |
| • | Number Expected |
| • | Serial Holding Override |
The Chronology field contains the date published on the issue. When generating prediction records, the chronology pattern value begins with the date of the next issue of prediction records you want to generate. Each subsequent chronology pattern value in a list of predicted issues will follow the same format, sequentially, of the first issue. The format for entering the originating date into the Chronology field is dependent on the name pattern stated in the Chronology Type field of the Patterns tab.
This field allows you to add a free-text comment up to 80 characters in length specific to this predicted issue.
This field contains the expected receipt date of an issue as defined by the library. This field is used when generating prediction records, and will indicate the date that the next issue for this generated prediction is expected to be received by the library. Use the Calendar gadget to enter a date into this field.
The issue’s expected or predicted date of publication is displayed in this field. This field is used when generating prediction records, and will indicate the date that the first issue for this generated prediction is expected to be published. The date prediction typically correlates with the issue’s Chronology field. The Date Prediction links the prediction’s chronology to the publication pattern of the serial control record. In most cases, the date prediction and the date expected would be the same. However, when titles that are behind schedule, or have very regular dates that do not vary from month to month, the date prediction can be used to provide more useful information.
The Date to Claim contains the date to begin claiming unreceived copies of the issue. It is calculated by adding the number of Days to Wait Before Claiming in the serial control record to the Date Expected in the prediction record. This is done automatically by the Prediction As Late report. If the value in the Days to Wait Before Claiming field is zero, then the Date to Claim is set to NEVER.
Enumeration identifies an issue of a serial title by the numeric information printed on a particular issue. This may generally be defined as the volume, issue, and any item numbers displayed on the issue. Each prediction record includes an enumeration field. Enumeration patterns are defined on the Patterns tab associated with serial control record creation or modification.
This field identifies a particular funding period. The funding period may be in quarters, calendar years, or fiscal years.
The Holdings Link number specifies the linking number of the 853 entry to which the record should be linked. It may be modified at the time of receipt or before an issue is received. This field also requires an override, although changing this field from zero (unlinked) can be done without an override. This field may also be modified with the Prediction MARC Holding Status report. These linking number fields can be edited to correct any mistakes made by linking additional holdings records to a serial control record, after that serial control record has been in production
Note: This field displays only if the serial control is linked to a MARC holdings record.
Serial control records (controls, vendors, predictions, claims) are assigned to a library. Which libraries may display your library’s serial control records is governed by the Serial Display Libraries attribute of the Library policy. Which libraries may maintain your library’s serial control records is governed by the Serial Maintenance Libraries attribute of the Library policy.
This is the number of copies expected for an entire issue, and should equal the Copies to Receive value on the Subscription tab. If the number of copies received does not equal the copies expected, partially received predictions will remain on the expected tab even after that issue’s Date Expected has passed. However, a claim record will also be created automatically for the unreceived issues, with a date claimed of NEVER.
The Holdings Link number which specifies the linking number of the 853 entry to which the record should be linked requires an override, although changing this field from zero (unlinked) can be done without an override. Under normal circumstances, you should not need to change the linking number. If you do not know the override code, contact your supervisor or system administrator.
Note: This field displays only if the serial control is linked to a MARC holdings record.
Related topics
FAQs: Creating and Modifying Publication Patterns
© 2006, 2014 SirsiDynix