Editing an Issue
You can modify an issue record so that it corresponds with the issue in hand. This feature is generally used in these circumstances:
|
•
|
To define the baseline issue. A baseline issue is the first issue that you receive using the Horizon Serials process. This becomes the baseline issue. The baseline issue determines the volume and issue numbers that Serials starts counting from. Because Serials initially predicts all issues as 1, you must specify what the correct starting issue and volume number should be. This issue becomes the baseline issue and the one on which subsequent issues’ enumeration are based. |
|
•
|
To change the enumeration of the issue that Serials expects but that looks different from the one in hand. For example, Serials may expect Vol. 5, No. 5. The one that arrives may be Vol. 5, No. 5‑6. Note that if Serials were expecting No. 5, but you received No. 6, you should first click Predict to see if Serials will predict No. 6. If it does, you would check that issue in and No. 5 would remain pending. |
|
•
|
To add free-text enumeration. You can enter any enumeration for a serial that you have flagged as free-text. For example, if you labeled the free-text enumeration for this serial as “pages,” you could now enter the actual page numbers for this serial issue in the “pages” field. You would choose Edit to add this free-text enumeration. Note that once you specify page numbers as free-text, the next predicted issue will appear with the same page numbers. You need to specify the correct page numbers for the issue in hand each time you check in an issue of this copy record. |
|
•
|
To change the chronology pattern. For example, Serials may display the chronology of the expected issue as July 2002. The actual chronology on the serial cover may be July 10, 2002. You would choose Edit to change the chronology pattern. Note that if the existing chronology pattern is wrong for all issues, you should edit the pattern in the Prediction Table window for the title. Choose Edit only if the chronology occasionally differs from the usual pattern. |
|
•
|
To change the issue date, end date, or expected date. For example, Serials expected Vol. 5, No. 5 (July 15, 2002), but the issue that you received was Vol. 5, No. 5 (July 12, 2002). You would need to change the issue and end dates from “7‑15‑02” to “7‑12‑02.” |
Often, you may need to edit more than one of the above aspects together. For example, Serials may expect Vol. 5, No. 5 (May 2002), but you received Vol. 5, No. 5‑6 (May‑June 2002) as a combined issue. You would need to change the enumeration from “5” to “5‑6,” the chronology pattern from “MonY” to “M‑My”, and the end date from “5‑01‑02” to “6‑30‑02.”
Once you check in an edited issue, Horizon returns to the original pattern and predicts the next issue accordingly.
To edit an issue
|
1
|
Search for the serials title you want and send it to Serials Checkin, if necessary. |
Horizon displays the Issues window.
|
2
|
Highlight the issue that you want to edit. |
|
3
|
If Serials does not display issues in the list, as in the case of newly subscribed titles, click Predict. |
Note: Issues with no prediction pattern set up for the copy record do not appear in the list. (For more information on checking in these issues, see Checking In Issues without Prediction Patterns.)
Horizon opens the Edit Issue window:
|
5
|
Enter the actual enumeration of the issue in hand in the enumeration fields. |
If the issue has been flagged for free-text enumeration, a blank field appears to enter that enumeration here. If the free-text enumeration was given a label in the copy record, such as “pages,” the label appears next to the field.
|
6
|
If the issue in hand contains a chronology different from that of the title’s usual chronology, you can enter the different pattern for the issue in the Chron. Pattern field. |
|
7
|
Enter the issue publication dates in these fields: |
|
•
|
Issue Date and End Date. Specifies the date of the issue in hand. In many cases, these dates will be the same. (For example, the January 2002 issue of a monthly title will have an Issue Date of 01‑01‑02 and an End Date of 01‑01‑02. If the issue spans a range of time, such as bimonthly issue, the Issue Date field displays the beginning of that range, and the End Date field displays the end of that range. |
|
•
|
Exp’d Date. Specifies when you expect the issue. When prediction is initially set up, Horizon designates the expected date of each issue to be the same as the issue date. |
|
•
|
Free‑text Chronology. Enter an undefined chronology. This field is useful for unexpected supplemental issues. |
|
•
|
PAC Note. Enter any comments about the issue to appear in PAC and staff searching. |
|
•
|
Description. Enter a description of the issue. |
|
9
|
Click Page Down or resize the window to display the Copies group in the Edit Issue window: |
The Copies group contains information about the issue, such as the date when Serials expects or received the issue, the vendor for the subscription, claim information, the status of the issue, and a note field to enter information about the issue.
Note: If you edited the chronology of the issue, the next expected issue fits the original chronology pattern in the Issue window.
© 1998-2017 Sirsi Corporation