The Distribution tab displays only if your library is configured to use serial distributions. The Distribution tab displays current distribution information in a table format. Through distributions, one centralized processing unit may check in issues for other libraries. For example, the control record may be owned by the main library. This tab may include a distribution record list for Main, Branch 1, and Branch 2. You may also create distribution records for different locations within the same library.
The following fields appear for each distribution record.
| • | Copies Expected |
| • | Copies to Add to Catalog |
| • | Holding Code |
| • | Update Holdings |
From the Distribution tab, you may be able to use the Create a Distribution Tool tool to create a new distribution record if there are more copies to receive (in the Subscription tab) than are currently distributed.
Using the Change a Distribution Tool tool, you can modify an existing distribution record to change the distribution and/or create a list of distributions which will assign additional copies being checked in to different libraries/locations.
Using the Remove a Distribution Tool tool, you can remove distribution records.
The following fields are defined for the Distributions tab for serial control.
This field indicates the number of copies expected to be received for a particular distribution. The sum of all the Copies Expected fields on the Distribution tab of the serial control record should equal the Copies to Receive value on the Subscription tab. The default number of copies expected when the first distribution is created is also based on the Copies to Receive value.
This field in a Distribution record indicates the number of copies expected for a particular serial distribution that should have item records created in the catalog. The default value for this field is zero. In a single library, this field displays in the OPAC Display tab. This field may also be referred to as the number of copies to add to catalog.
A holding code is a short code that represents copy-level information, such as Item Type and Location. The holding code is used to provide required copy-level information at the time the record is loaded as a process of cataloging, acquisitions, or serial control. Each Holding Code policy definition provides several pieces of necessary information which is expanded into data when an item record is loaded into SirsiDynix Symphony. Holding Codes are maintained in the Holding Code wizard of the Cataloging Configuration wizard group.
On the Distribution tab, selecting the holding code name will display that holding code’s details such as the library, location, and item type. When creating or modifying a distribution, the Holding Code field may be selected from the list. If your library uses serial distributions, the library and location updated in MARC holdings will always correspond to the library and location of the distribution holding code.
Note: The Item Maintenance and MARC Holdings Maintenance library groups do not limit the automatic creation of items or MARC holdings in the Check In Issues of a Serial wizard. Users can select a holding code for any library, even if that library is not included in their Item Maintenance or MARC Holdings Maintenance library groups.
If your library is configured to use serial distributions, the Update Holdings field must be selected for each distribution record that you want to create MARC holdings. In order for this field to be selected, however, the Automatically Update MARC Holdings field on the OPAC display tab must also be selected. If the OPAC value is not selected, this Distribution value cannot be edited. If the field on the OPAC Display tab is selected when a serial control is created, a linked holdings record and a distribution that is selected to automatically update MARC holdings is created. When both of the MARC holdings update fields are selected, each holdings record linked to a serial control displays in the catalog listed first by library, then location, then the collapsed issue statement.
For example:
MAIN--
Location:
STACKS
Holdings: v.1:no.9 (2002:May 1) - v.1:no.15 (2002:Sept.1),
v.2:no.7 (2003:July 1)- v.2:no.8 (2003:Aug. 1)
Related topics
FAQs: Call Number, Item, and MARC Holding Maintenance Library Attributes
© 2006, 2014 SirsiDynix