Subfield Setup Tasks

Horizon has several Cataloging features that you can activate to enhance cataloging workflow. These features affect how bib records retain and display information. This section summarizes the features you can activate. (For instructions on activating these features, see the Support documentation on the SirsiDynix web site.)

If you upgraded to Horizon from a previous release (6.0 or later), you may have chosen to complete these tasks as part of the upgrade process. If you are a new Horizon customer, you may have chosen to have SirsiDynix complete these tasks for you as part of the Horizon implementation process. If you have already activated these features, you do not need to activate them again.

You can implement any of these features:

Authority control by subfield. This feature lets you define authority control by subfield, so that only subfields that are defined as controlled have to match the corresponding subfield in the authority record. This lets you have different sets of controlled subfields within separate bib tags, even if those tags are controlled by the same authority record. (For example, if you activate this feature, you can set subfield v to be controlled in the 400 tag but not in the 600 tag, even when both bib tags are controlled by the same authority tag.) This feature is implemented with either the “Just Bib” or “Bib and Auth” option in the System Subfield Control field on the matham table.
Preservation of local authority-controlled subfields. This feature preserves information your library has added to local authority-controlled subfields when you upgrade or overlay bib records. You will most likely use this feature if you want to preserve subfield w on 4xx and 5xx tags. To implement this feature, you must also implement authority control by subfield (explained above). This feature is implemented with the “Bib and Auth” option in the System Subfield Control field on the matham table.
Authority matching ignores punctuation. This feature prevents Horizon from creating a new authority record if the only difference between the data in the bib record and the data in an existing authority record is end punctuation. This feature is implemented with the Auth Matching Ignores Punctuation field in the matham table.
Preserve original end punctuation. This feature keeps the original end punctuation in the bib record, instead of having Horizon replace it with the end punctuation in the authority record when the end punctuation in the two records is different. This feature is implemented with the Preserve Auth Punct. in Marc Recs field in the matham table.

Do not change the fields on the matham table that are related to these features without first reviewing the Support documentation on the SirsiDynix web site.

 


© 1998-2017 Sirsi Corporation