If you attempt to open items and nothing happens, make sure your subscription record is LINKED to the HOL

If you attempt to open items and get a Remote Service Error message – “No attached level-x lines” check the 853X, subfield 9 data. This is the subscription record number! If it doesn’t match the number for the active subscription record, edit subfield 9, save, and try to open items again.

If your pattern produces issues that look like this: v.13:no.1(2006:01), v.13:no.2(2006:02), v.13:no.3(2006:03), etc … numbers produced instead of months, check the HOL 008 language code, it’s probably “mul”. Change it to whatever language code is appropriate for the issues.

Before checking-in the last issue in a cycle, open the items for the next cycle. The act of checking-in an issue triggers a change in the “Item Processing Status” of the next issue to “EX” and displays in the OPAC as “Expected/Expected on [date]”

For suppressing captions (“v.”, “no.”, etc), but not their corresponding numbers, use “(*)”

For “chronology only” patterns (no captions or numbers) use “^” as a place-saver in the 853, subfield a, then enter chronology data in subfields i-m. You still need a corresponding subfield a in the 853X field, but you can enter any number and it won’t affect the resulting pattern.

If using “o” (for “omit”) in subfield y - use an alpha code in subfield w (frequency) (example: “b” for bimonthly; “m” for monthly; “s” for semimonthly, etc.)

If using “p” (for “published”) in subfield y - use a number in subfield w (frequency) (example: “4” for four no. yearly, “6” for six no. yearly, etc.)

Subfield 3 in the 853X field: The date in subfield 3 plus the number of days in the first claim field of the subscription form create the “expected arrival date” (if an issue is not checked in by the “expected arrival date,” the issue will appear on the next claim report)

In Aleph, for patterns where there is a regularly combined issue (or issues), subfield u (#units/next higher level) should have the number of units as if no combo existed. (example: monthly with Nov./Dec. combo, subfield u should have 12, not 11) NOTE! This was critical in version 15.2, but may not be as critical in 16.2!

In Aleph, for patterns where there is a regular omission (or omissions), subfield u (# units/next higher level) should have the actual number of issues (example: monthly with no issues in July or Aug. should have a subfield u value of 10) NOTE! This was critical in version 15.2, but not as critical in 16.2

For subfield w (frequency) the value (code or number) should equal or exceed the number of issues actually published. For example, if a journal has 8 issues yearly, a monthly frequency should be entered and a subfield y used to indicate the months in which no issues are published (reported negatively) OR, alternatively, the number “8” may be entered in subfield w and the months in which issues are published may be listed in subfield y (reported positively)