Once you begin checking in issues, Serials maintains and displays an accurate summary of holdings. The Bibliographic Detail window shows the summary of holdings display:
However, Horizon cannot know to include issues received before the date when you implemented Serials. Consequently, to display holdings for those issues, you need to edit each copy record’s summary of holdings to reflect those issues.
For issues you receive after you implement Serials, Horizon creates the summary of holdings using the information from its prediction of expected issues. (For more information on prediction, see Prediction Setup.) When issues are published in the expected pattern, Horizon automatically collapses the issues in the summary of holdings. (For example, if you receive a monthly publication every month for a year, then Horizon collapses the issues into a range in the summary of holdings like this: “Vol 1 No. 1 (Jan 2002) – Vol. 1 No. 12 (Dec 2002)”.)
Sometimes, there are occurrences that break up the predicted publication pattern. In these cases, Horizon creates a break in the summary of holdings by starting a new line of published issues. Here are the conditions in which Horizon automatically creates a break in the summary of holdings:
• | If a received issue has free enumeration, chronology, or there is a note in the publication pattern. |
• | If there is a gap or break as determined by an immediately preceding issue that has a status of “Expected,” “Claimed,” “Not Available,” or “Not Published.” |
• | If an issue has a combined enumeration and chronology and no instance list (or string). (For more information on the instance string, see Specifying the Frequency .) |
• | If there is a change in the run code or applicability date that changes the enumeration pattern or the chronology pattern. |
• | If a received issue has enumeration that is out of sequence when compared to its order among other issues as determined by issue date. |
This could be the result of an issue being published out of sequence or if there is a reset of the enumeration.
• | If there are more than two levels of enumeration and the value for the higher level changes. |
• | If a row is complete as determined by having a following row with no break, but there is only one level of enumeration. |
Horizon uses only the first enumeration group to determine when it should collapse issues. If there is no enumeration, then Horizon uses dates and break checks to determine when it should collapse issues.
However, there may be times when you need to make changes based on which issues you really receive and when. (For example, Horizon may have predicted that you would receive an issue on Easter Friday for a Monday through Friday publication, but the publication does not normally publish on this holiday.)
Here is how the summary of holdings is affected when you make certain changes:
• | Deleting an issue. |
(For example, if a Monday through Friday publication does not normally publish on Easter Friday, you would delete the issue Horizon predicted.)
This causes a break in the summary of holdings only if you delete a particular issue and it causes the sequence of enumeration of the remaining issues to be broken. If you have a series of issues that have only chronology, deleting an issue does not cause a break.
• | Changing the issue date before any issues are received. |
(For example, if a publication changes its issue date due to a holiday, you would change the issue date that Horizon predicted for that issue.)
This causes a break in the summary of holdings only if the issue date is changed to be less than that of the preceding issue, or greater than that of the subsequent issue, thereby placing its enumeration out of sequence with respect to the other issues.
• | Receiving an issue where both the preceding and subsequent issues have already been received and are represented in the summary of holdings. |
One summary of holdings line that encompasses the issues of both ranges of preceding and subsequent issues replaces the previously existing two lines. Issues with combined chronology require an instance list (or instance string) to be specified in the publication pattern in order for this collapsing to take place. (For more information on the instance string, see Specifying the Frequency .)
• | Changing the status of an issue to “Not Available” or “Not Published.” |
As with an issue that is expected or claimed, Horizon creates a break in the summary of holdings.
© 1998-2017 Sirsi Corporation