Alternate Serials Control View – Designed for users who receive a larger number of issues and was designed for use in public libraries. Alternate Serial Control View is recommended for creating new subscriptions.
Serials Control View – Designed for users who work with smaller number of issues. Designed to accommodate workflows in academic and special libraries. Serials Control View is recommended for receiving serial issues.
Caption and Pattern objects – Define the same material that would be described in an 853, 854, or 855 MARC tags. Captions and patterns define how your issues will be captioned and how often you get them.
Copy Template – Defines the attributes for the copy-like “Unit” created when receiving an issuance. A copy template must be associated with every distribution, even if you do not intend to create copies.
Distribution – A distribution is created for each branch and defines the copies to be sent to each branch. A copy template is associated with a distribution. If you have 2 copies each needing a different copy template, you need 2 distributions.
“Expected date offset” field – The difference between the nominal publishing date of any given issue and the date that you generally expect to receive your copy. If a publication is dated with the first of each month, but you generally receive it five days before that, you would enter ”-5 days” into that field.
Issuance – Akin to a checkin box in Millennium. Represents a single issue of a periodical. Multiple “Units” can be created for a single issuance. Each “Unit” is associated with a “Stream.”
MARC Format for Holdings Data (MFHD) – Serial holdings statement. This can be a textual statement (e.g. “Past two years”) or may contain enumerations and captions. The MFHD can be used without serials receiving.
Routing Lists – (not yet implemented) Each stream can have an associated routing list. Lists can be routed to departments or to individual users.
Streams – Each stream represents one *recurring* copy of a serial. So if you have a library called Example Branch 1 (BR1 for short), and you want BR1 to get four copies for every issue, then you should create one distribution for BR1 and four streams for that distribution.
Subscription – Akin to a checkin record in Millennium, but with more levels of control. Subscriptions can have multiple distributions.
Units – Copy-equivilent objects that can have a barcode and will appear in the catalog and, optionally, circulate.