Difference between revisions of "Step 4.4"

From AC Wiki
Jump to: navigation, search
(marc 21 format)
(Step 4.4: Authority Segmentation by Usage)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
==STEP 4.4 : AUTHORITY SEGMENTATION BY USAGE==
+
==Step 4.4: Authority Segmentation by Usage==
[[Image:4a-1.png]]<br><br>
+
[[Image:a4-4.png]]<br><br>
 
MARS 2.0 can distribute authority records in single- or multiple-file combinations. The number of files that are used to distribute your authority records should '''mirror''' the setup of authority indexes in your system.
 
MARS 2.0 can distribute authority records in single- or multiple-file combinations. The number of files that are used to distribute your authority records should '''mirror''' the setup of authority indexes in your system.
  
Line 8: Line 8:
  
 
The following table shows the distribution of authority records by authority tag and bibliographic usage:
 
The following table shows the distribution of authority records by authority tag and bibliographic usage:
{| border="1" cellspacing="0" cellpadding="5" align="left"
+
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
 
! style="background:silver" | Files
 
! style="background:silver" | Files
 
! style="background:silver" | Authority Tags
 
! style="background:silver" | Authority Tags
Line 31: Line 31:
 
For instance, if your ILS requires Subjects be loaded separately, MARS 2.0 will send you one file with '''Subjects''' and one file with '''Names''' (which contains the combined authorities for Series, Title, and Genre).
 
For instance, if your ILS requires Subjects be loaded separately, MARS 2.0 will send you one file with '''Subjects''' and one file with '''Names''' (which contains the combined authorities for Series, Title, and Genre).
  
===names as subjects===
+
===Names as subjects===
 
Some authority records for names are coded for use as both a name and a subject. MARS 2.0 is able to distribute those names in the Name file, in the Subject file or in both files, as determined by the usage of the bib heading.
 
Some authority records for names are coded for use as both a name and a subject. MARS 2.0 is able to distribute those names in the Name file, in the Subject file or in both files, as determined by the usage of the bib heading.
  
===brief authority records===
+
===Brief authority records===
 
For headings in bibliographic records which do not '''fully''' match a heading in any of the selected authority files, MARS 2.0 automatically generates '''brief''' authority records in MARC 21 Authority Format.
 
For headings in bibliographic records which do not '''fully''' match a heading in any of the selected authority files, MARS 2.0 automatically generates '''brief''' authority records in MARC 21 Authority Format.
  
Line 41: Line 41:
 
Most modern local systems either do '''not''' require an authority record to index unmatched bibliographic headings or can generate authority records for any heading not linked to an authority record. Therefore, most libraries do not need to have brief authority records included in their authority distribution files.
 
Most modern local systems either do '''not''' require an authority record to index unmatched bibliographic headings or can generate authority records for any heading not linked to an authority record. Therefore, most libraries do not need to have brief authority records included in their authority distribution files.
  
===lc validation records===
+
===LC validation records===
 
MARS 2.0 includes LC validation records as part of the match and delivery processing.
 
MARS 2.0 includes LC validation records as part of the match and delivery processing.
  
===authority notification services===
+
===Authority notification services===
 
After completing your bibliographic basefile processing, Backstage retains a copy of your authority records to build a '''Master Authority File''' for your library. This file is used when you '''subscribe''' to the '''Authority Notification''' or '''Current Cataloging Services''' (see Step 6).
 
After completing your bibliographic basefile processing, Backstage retains a copy of your authority records to build a '''Master Authority File''' for your library. This file is used when you '''subscribe''' to the '''Authority Notification''' or '''Current Cataloging Services''' (see Step 6).
  
===authority file retention===
+
===Authority file retention===
 
Backstage retains archive copies of your authorities distribution files for a minimum of one year following completion of MARS 2.0 projects. The Master Authority File for users of the Authority Notification or Current Cataloging Services will remain archived for at least 3 years.
 
Backstage retains archive copies of your authorities distribution files for a minimum of one year following completion of MARS 2.0 projects. The Master Authority File for users of the Authority Notification or Current Cataloging Services will remain archived for at least 3 years.
  
===marc 21 format===
+
===MARC21 format===
 
All authority records provided by MARS 2.0 are in MARC 21 format. If necessary, files can also be output as MARCXML.
 
All authority records provided by MARS 2.0 are in MARC 21 format. If necessary, files can also be output as MARCXML.
  
==LINKS==
+
==links==
 
<center><font size="4">[[Step 4.1|4.1]] - [[Step 4.2|4.2]] - [[Step 4.3|4.3]] - [[Step 4.4|4.4]] - [[Step 4.5|4.5]] - [[Step 4.6|4.6]] - [[Step 4.7|4.7]]
 
<center><font size="4">[[Step 4.1|4.1]] - [[Step 4.2|4.2]] - [[Step 4.3|4.3]] - [[Step 4.4|4.4]] - [[Step 4.5|4.5]] - [[Step 4.6|4.6]] - [[Step 4.7|4.7]]
 
<hr>
 
<hr>
 
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center>
 
[[Step 1.0|1.0]] - [[Step 2.0|2.0]] - [[Step 3.0|3.0]] - [[Step 4.0|4.0]] - [[Step 5.0|5.0]] - [[Step 6.0|6.0]]</font></center>
 
[[category:Profile Guide]]
 
[[category:Profile Guide]]

Latest revision as of 12:35, 25 June 2015

Step 4.4: Authority Segmentation by Usage

A4-4.png

MARS 2.0 can distribute authority records in single- or multiple-file combinations. The number of files that are used to distribute your authority records should mirror the setup of authority indexes in your system.

If all authority records in the ILS are in a single file, regardless of whether a record links to a main/added entry heading or a subject heading, all files can be combined.

If the local authority file is divided into multiple files based on heading usage within bibliographic records, files should be separated to mirror your ILS.

The following table shows the distribution of authority records by authority tag and bibliographic usage:

Files Authority Tags Bibliographic Usage Authority Usage
Name 100, 110, 111 1XX*, 7XX* name
Subject 100, 110, 111, 150, 151 6XX* (excludes 655) subject
Series 130 4XX*, 8XX* series
Title 100, 110, 111 130, 440, 630, 730, 830 name.title, subject.title, series.title
Genre 155 655 genre

*excludes bib 130, 440, 630, 730, 830 for these entries with asterisk

It may be that your ILS requires certain combinations in order to load the indexes properly. MARS 2.0 can combine or separate the usage files in whatever method is desired.

For instance, if your ILS requires Subjects be loaded separately, MARS 2.0 will send you one file with Subjects and one file with Names (which contains the combined authorities for Series, Title, and Genre).

Names as subjects

Some authority records for names are coded for use as both a name and a subject. MARS 2.0 is able to distribute those names in the Name file, in the Subject file or in both files, as determined by the usage of the bib heading.

Brief authority records

For headings in bibliographic records which do not fully match a heading in any of the selected authority files, MARS 2.0 automatically generates brief authority records in MARC 21 Authority Format.

For libraries that subscribe to the Authority Notification Service (see Step 6), these brief authority records allow the program to track the library’s unmatched headings. During each update cycle, MARS 2.0 Notification Service uses these brief authority records to trigger distribution of new national-level authority records for unmatched headings in your database.

Most modern local systems either do not require an authority record to index unmatched bibliographic headings or can generate authority records for any heading not linked to an authority record. Therefore, most libraries do not need to have brief authority records included in their authority distribution files.

LC validation records

MARS 2.0 includes LC validation records as part of the match and delivery processing.

Authority notification services

After completing your bibliographic basefile processing, Backstage retains a copy of your authority records to build a Master Authority File for your library. This file is used when you subscribe to the Authority Notification or Current Cataloging Services (see Step 6).

Authority file retention

Backstage retains archive copies of your authorities distribution files for a minimum of one year following completion of MARS 2.0 projects. The Master Authority File for users of the Authority Notification or Current Cataloging Services will remain archived for at least 3 years.

MARC21 format

All authority records provided by MARS 2.0 are in MARC 21 format. If necessary, files can also be output as MARCXML.

links

4.1 - 4.2 - 4.3 - 4.4 - 4.5 - 4.6 - 4.7
1.0 - 2.0 - 3.0 - 4.0 - 5.0 - 6.0