AC Wiki - User contributions [en]

Profile Guide Chapter 7

2012-01-12T20:59:48Z

Jeremy: /* Partial Matches and Free-Floating Subdivisions */

Step 7 lists three Optional Services for your library. Each one of these services will incur an additional fee (please consult with your Backstage Library Works Sales representative for details). 

== Step 7.1 Question ==
=== Authority Remaster ===
Some libraries already have a locally established MARS 2.0 authority file that they add to and modify. Many times this file represents a larger group of bibliographic records than the records being sent for MARS 2.0 Authority Control. The library can choose to have this authority file remastered.

To remaster your existing authority file, MARS 2.0 will match the file against the latest national database files using the MARS 2.0 Remaster Service and return the updated MARC authority records to the library. In this case the local authority records are not used to override standard heading practice, but rather as a means of selecting and forwarding national authority records in the library. This will bring your entire authority database up to current national standards.

=== Parts of a Remaster ===
There are four parts during the MARS 2.0 Remaster Service:<ol><li>File Segmentation<li>National Database Matching<li>Control Number Location<li>Distribution</ol>

=== File Segmentation ===
[[Image:7-1a.png]] 

For best results the authority files submitted to Backstage should be separated by: Name, Subject, Series and Title. The library should follow the same file separation procedures as they do when loading authorities. For example, if a library maintains two authority files (Names, Subjects) then Backstage will return two updated authority files to sync with the library’s loading procedures.

=== National Database Matching ===
[[Image:7-1b.png]] 

Libraries have the option of choosing which national database to search for their authority matching. The record searching is performed based on the control number within the library’s authority records. If a control number is not present, then the heading is searched as a string. Sometimes these are simply old heading that are no longer in the national database or they have missing or malformed control fields. Records that cannot be found via string match are retained in the client brief file for later searching as part of Notification Services (see Step 6 of the Planning Guide).

=== LC Control Number Location ===
[[Image:7-1c.png]] 

The file of client authorities is searched against national master files based on control number (usually the 001 field, unless otherwise specified—some libraries require the 010 $a). Again, any authority records which do not find a match on the control number will have their headings searched in a string match.

=== Distribution ===
[[Image:7-1d.png]] 

In addition to distributing their updated authorities, libraries have the choice of whether they want their associated Brief authorities (unmatched headings) as well as an Unmatched Headings Report. Both of these can be useful in helping libraries determine what actions they would like to take with their unmatched authority records.

== Step 7.2 Question ==
[[Image:7-2.png]] 

=== Overview ===
MARS 2.0 Manual Review provides visual examination of authority controlled headings in your bibliographic records. MARS 2.0 Manual Review is performed by experienced MARS 2.0 staff librarians and library technicians, and results in a catalog of records with fewer errors and inconsistencies than machine processing alone can provide.

MARS 2.0 Manual Review editors examine electronic files of headings in your database, including the following fields: 
     100, 110, 111, 130 
     400, 410, 411, 440, 490 
     600, 610, 611, 630, 650, 651, 655 
     700, 710, 711, 730 
     800, 810, 811, 830 

These headings, found in reports R06 & R07 (see Step 5 of the Planning Guide), are reviewed for errors and then matched against the Library of Congress authority databases to determine if the heading can be matched. Manual Review consists of a careful scan of all headings in these reports coupled with a review of the bibliographic record where these headings reside to determine if the heading can be matched. Additionally, upon request, other reports may be considered as candidates for Manual Review.

=== Review Choices ===
The majority of the headings eligible for review are found in '''R06—Partially Matched Headings''' and '''R07—Unmatched Primary Headings''' reports (see Step 5 of the Planning Guide). Each library’s partially matched and unmatched headings will be divided into categories and reported to you. You can choose which categories you want reviewed and you can pick unmatched, partially matched or both types of headings for review. If you choose this service a report will be delivered before and after the review so you can follow the progress of your headings and evaluate the value of our servce.

The example of Reports R06 and R07 (found in Step 5 of your Summary Report) will give you an idea of which categories are going to be populated with unmatched and partially matched headings. A quick review of your summary report should give you an idea of what areas need to be looked at. Simply contact your MARS 2.0 Project Manager and indicate what additional categories you would like us to review.

In order to calculate the cost of MARS 2.0 Manual Review, we will run a sample of 300 records through our services. The price is usually between $0.15 to $0.45 per heading reviewed and will be determined based on how the sample fared during manual review.

=== Partial Matches and Free-Floating Subdivisions ===
Typically there will be a proportionately high number of partially matched headings. Usually about 75% of the total number of headings reported for manual review will be found in the partially matched headings report with most residing in the topical (650) and geographical (651) areas. The reason these areas are high in partial matches is because of the high use of the free-floating subdivisions for topical and geographical subject headings.

The MARS 2.0 software only considers a heading to be a full match if all subdivisions are established in a continuous string in the Library of Congress authority file. If some of those elements are not established or are established separately as free-floating subdivisions (18X) then the heading is considered a partial match. A partially matched heading could be a legitimate authority heading, but because some of its subdivisions are free-floating the MARS 2.0 software will consider it a partial match and add it to Report R06.

=== Elements Reviewed ===
The MARS 2.0 Manual Review editors look for and correct errors in:<ul><li>Spacing, punctuation, capitalization, and spelling<li>Consistency in form of names<li>Abbreviations<li>Initial articles<li>Period subdivision dates<li>Missing, invalid, or incorrect usage of MARC21 subfield codes<li>Series headings (excluding volume/sequential designations)<li>Conference names<li>Mistagged names<li>Main heading/subdivision combinations in LC subject headings<li>Geographic, form, and language subheadings in MeSH headings</ul>

=== Corrections ===
Although most corrections are accomplished during MARS 2.0 Authority Control machine processing, unique and unusual errors often cannot be corrected solely with fully automated processing. Some types of errors require manual correction to bring headings into conformity with current standards and practices.

=== Special Heading Updates ===
Some special types of heading updates supported during Manual Review include:<ul><li>Direct geographic subdivisions in LC headings<li>Jurisdictional splits and mergers<li>Subdivision simplification<li>Location of '''Mrs.''' in name headings<li>Presence of maiden name in headings<li>City “Flip” (conversions)<li>Pre-AACR2 usage of subfields $b in 650 Topical Subject Headings</ul>

=== Types of Headings Reviewed ===
The types of headings that are examined during Manual Review are based on the options selected in Step 3. In Step 3.8, for example, one of the options for processing LC Children’s headings is “Match against LC only / Retain unmatched headings.” If a library selects this option, many of their LC Children’s headings will be converted to LC Adult headings during automated MARS 2.0 Authority Control. Those that are not converted would be examined during Manual Review. The Manual Review editors would convert as many Children’s headings to Adult, as long as:<ol><li>The concept expressed by the heading is clear<li>An equivalent LC Adult heading has been established</ol>

Alternately, if a library chose the '''Do not process''' option for their LC Children’s headings, they would not be submitted for Manual Review.

=== Manual Review Service Request ===
Indicate whether you want MARS 2.0 Manual Review. The MARS 2.0 staff recommends Manual Review if your catalog has never been under authority control or contains a large number of older or retrospective conversion records.

Choose the headings you would like reviewed and whether the MARS 2.0 reviewers should check the Paritally Matched Headings report and/or the Unmatched Report. If you have special manual review requirements that are not covered in the standard review please attach a copy of your request to Step 7.

=== After Manual Review ===
Following Manual Review, the corrected headings are run through the automated MARS 2.0 Authority Control a second time. A second statistical report is created that is the same as the first. It will include a summary report followed by reports of all the headings still unmatched. This second phase of authority control results in:<ul><li>Additional heading updates due to corrections made during Manual Review<li>An increase in the number of matched headings<li>Distribution of additional authority records to the library</ul>

=== Additional Corrections ===
Manual Review editors often correct an additional 10% of a library’s bibliographic record headings (percentage varies widely among catalogs). Manual Review greatly improves a catalog with older records cataloged over a number of decades, while fewer corrections are made in catalogs of recent records consistently cataloged in accordance with current cataloging standards and practices.

=== Interim Return of Records ===
Local considerations, particularly in larger libraries, may make return of interim corrections essential. An initial set of all bibliographic and authority records can be distributed to the library following the first phase of authority control (pre-Manual Review).

After Manual Review and the second phase of automated authority control have been completed, MARS 2.0 provides the library with a second set of files. These files contain the records with the headings corrected during Manual Review, plus the additional authority records matched due to headings that have changed during Manual Review.

== Step 7.3 Question ==
[[Image:7-3.png]] 

=== MARS 2.0 TOC Enrichment ===
Backstage Library Works has partnered with Blackwell’s Book Services to provide an optional Enriched Content service to your bibliographic records. This service provides TOC (Table of Contents) notes at the chapter level, Summaries from dust jackets and Author affiliation information.

The advantage of contracting for TOC services through Backstage Library Works is you don’t have to send data to two places or coordinate multiple data deliveries. You send your bibliographic records to Backstage Library Works for MARS 2.0 processing and we take it from there. We have your bibs enriched at Blackwell’s then run your records through the MARS 2.0 process for bibliographic validation and authority control processing.

'''Note''': ''Please contact your sales representative for pricing information on Blackwell’s TOC solution. A separate profile will be sent to you to define the TOC service''.

=== Blackwell TOC Solution ===
Blackwell Book Service, Table of Contents Enrichment Services, contains imprints dating back to 1991. Contents of 40,000 titles are added each year. Titles purchased by academic, special and public libraries are included in their database. In addition to Table of Contents, Title Summaries from dust jackets and Author Affiliation Information can be added to your records for the same price.

You have several options when choosing Blackwell as your TOC provider. All are incorporated into one convenient price. Please see your sales representative for pricing on a Blackwell TOC solution.

=== TOC Format Options ===
Three enrichment formats are available for Table of Contents data:<ol><li>Basic USMARC 505 field—TOC added to $a of the 505 field in conformity with USMARC Standards<li>Enhanced USMARC 505 field—Blackwell provides an enhanced 505 field<li>Locally defined field—TOC can be added to a local 9XX field</ol>

=== Descriptive Summaries & Author Affiliations ===
Descriptive summaries and Author affiliation information are gathered from the book dust jackets to further enrich your data:<ul><li>Descriptive Summaries—Can be added to the 520 fields<li>Author Affiliations—Can be added to the 9XX fields</ul>

== Step 7.4 Question ==
[[Image:7-4.png]] 

=== Overview ===
Backstage Library Works offers a third ongoing service product that we call Bibliographic Record Update Service. This service updates your bibliographic records during our Notification Service.

The process of importing and updating the library's authority records is straightforward. Control numbers are matched and the newly imported record overlays the old authority record. However, for some ILS systems updating of the authority heading is done by a string match on the 1XX or the 4XX of the authority record. If the 1XX or the 4XX are not the same as the old bibliographic authority heading, some ILS systems will not automatically match the new authority heading with the authorized heading in the bibliographic record. Typically, this is done through reports but the effort to reconcile or to populate the authorized heading in the bibliographic record can be partially manual and be time-consuming depending on the ILS and the library.

Because of the acceleration of Library of Congress updates to the name and subject files, we have noticed an increase in the amount of updates coming to Backstage each week. As a result, we have developed a service that updates the library's bibliographic record at the same time we update the authority heading. We call this service '''Bibliographic Record Update Service'''.

With this service, Backstage Library Works maintains your bibliographic records along with your authority records. When Notification Services run on your database, our Bibliographic Record Update Service will also run. Backstage will update or reconcile your bibliographic database at the same time as we update your authority file. We will deliver to you updated bibliographic records along with your updated and new authority files.

=== Getting Started ===
To start this process, the library will send Backstage Library Works a MARC export of their entire bibliographic database. Each bibliographic record must contain a unique control number when exported. This is for matching purposes when the updated record is returned to the library from Backstage Library Works.

The next time Notification or Current Cataloging Services are run for the library, Backstage will update the library's bibliographic record with changes made to the authority headings.

=== Record Output ===
The library has three options for output of updated bibliographic records. The first option is to return the updated MARC records in MARC format for overlay into their ILS system. The second option is to send in all bibs. The third option is to receive a MARC Transaction Record from Backstage Library Works.

'''Example MARC Transaction Record'''
Leader: 00187naa a22000061z 4500
001 000118229
710 2 $aR. Deputazione di storia patria per le Marche.$9MAT
710 2 $aRegia Deputazione di storia patria per le Marche.$9ADD

'''Note''': ILS input of a MARC transaction record may not be standard to your ILS system. Check with your vendor to make sure a transaction record can be imported and overlaid on your system. Each bib record has to have a unique control number you export & import in order to update our log.

=== Control Number Location ===
The library can specify which field contains the '''unique identifier''' within the bibliographic record. This will be the field that the library will use to overlay any updated bibs returned from BSLW. Usually, the unique control number is located in the 001, 035, or 907 field within the bib record. If unsure, please check with your vendor before filling out this portion of the profile.

=== Maintenance ===
Library updates to their bibliographic database must be sent to Backstage Library Works before the Bibliographic Update Service is processed. About a week before the process is scheduled to run, the library will need to send Backstage its changed bibliographic records.

If this routine maintenance is not done and the library overlays the updated bibliographic record from Backstage, the internal library updates that took place between the time the original bibs were sent and the time our process was run will be lost. If the library's ILS system has the ability to merge incoming bibliographic records they may not need to send Backstage their internal bibliographic updates.

=== Bib Update Service Flow-Chart ===
[[Image:7-4flow.jpg]] 

== Step 7.5 Question ==
=== Bowker TOC ===
Backstage has partnered with Bowker’s Syndetic Solutions to provide our customers with another choice when it comes to table of contents (TOC) enrichment. The Bowker service is designed to complement and serve as an alternative to our existing TOC service through Blackwell.

Our clients who use the Bowker service will see immediate benefits in:
1. Lower cost
2. Faster turnaround

For the new service, we host the entire Bowker database on our servers and integrate regular weekly updates. Because the database resides locally, we are able to repurpose some of our highly efficient MARS routines, fully automating the enrichment process and keeping costs on our end to a minimum. Then we pass those savings on to you.

In addition to Table of Contents field (505), we also provide Summaries (520) and Fiction Profiles (69X). And we only charge you for the enrichments your records actually receive, regardless of how many options you may have selected. Housing the database locally allows us to track how many and what type of enrichments a record receives, so we can bill at a lower price for records that are only enriched on one or two elements.

Besides lowering the cost of enrichment, hosting the Bowker data at Backstage dramatically reduces the time your records spend out of your system for processing. Your records will be processed and returned to you with the same quick turnaround you’ve come to expect on your authority control.

With the database in-house, we can integrate the entire TOC enrichment workflow into your Current Cataloging process, or you can select groups of records for stand-alone enrichment.

Because each library’s ILS configuration is unique, we allow you to choose where you prefer to place the Bowker data. For example, you can place the 505 data from the Bowker record in a 970 field on your record.

You may prefer that existing data in your records be retained over potential Bowker matches in the same field. If you like, we can keep your content and not enrich on that particular element.

If you are interested in the Bowker TOC service, speak with your MARS 2.0 Project Manager about the options and obtaining a free sample.

== Step 7.6 Question ==
=== MARS Authority Express (MAX) ===
MARS Authority Express (MAX) can be used as an alternative to Current Cataloging or in addition to your normally scheduled Current Cataloging service. MAX can return your processed Current Cataloging bibs typically in less than an hour (our system can process about 20,000 recs/hr). This service is especially useful for libraries that need their records processed & returned immediately.

The great thing about MAX is that there is no minimum fee or schedules that need to be fussed over; simply send in your records through our website any time of the day in whatever size file works for you and we will get the results back to you fast.

Let your MARS 2.0 Project Manager know if you would be interested in the MAX service, and we can run a sample with you to demonstrate MAX's abilities.

[[category:Profile Guide]]

File:RDA 1.5.jpg

2012-01-09T20:15:43Z

Jeremy: uploaded a new version of "File:RDA 1.5.jpg"

File:RDA 4.3.jpg

2012-01-09T18:27:38Z

Jeremy: uploaded a new version of "File:RDA 4.3.jpg"

File:RDA 2.2.jpg

2012-01-09T18:27:23Z

Jeremy: uploaded a new version of "File:RDA 2.2.jpg"

RDA 7.1

2012-01-09T18:25:25Z

Jeremy: /* STEP 7.1 : RDA AUTHORITY CONTROL OPTIONS */

==STEP 7.1 : RDA AUTHORITY CONTROL OPTIONS==
[[File:RDA_7.1.jpg]]
===option 1 - aacr2 & rda -> aacr2===
This is the MARS 2.0 default processing option for your RDA bibs.

When an AACR2 authority already exists, current LC policy inserts an RDA authority heading into the AACR2 authority master as a 700 field with 2nd indicator 4. If an AACR2 authority does not exist, then a new RDA authority is generated (040 $e rda).

This option does not match 700 x4 in AACR2 authority. It also does not match against the RDA authority file at all:

{| border="1" cellspacing="0" cellpadding="5" align="left"
|-
| match 1XX in AACR2 master || AACR2 & RDA bibs
|-
| ignore 7XX in AACR2 master || AACR2 & RDA bibs
|-
| ignore RDA master || AACR2 & RDA bibs
|}
<div style=clear:both></div>

MARS 2.0 copies all AACR2 authorities with 700 x4 into our RDA master. In this scenario, the old 700 x4 (RDA) becomes the new 100 field in the RDA master, with the previous 100 field (AACR2) becoming a new 400 field:


'''AACR2 authority n 00010837:'''
100 1 $a Brashares, Ann
700 14 $a Brashares, Ann, $d 1967-

'''RDA authority generated from AACR2 authority above:'''
100 1 $a Brashares, Ann, $d 1967-
400 1 $a Brashares, Ann


===option 2 - separate out rda bibs===
RDA bibs are separated out to not process at all, and instead saved or discarded as desired by your library:

{| border="1" cellspacing="0" cellpadding="5" align="left"
|-
| match 1XX in AACR2 master || AACR2 bibs only
|-
| ignore 7XX in AACR2 master || AACR2 bibs only
|-
| ignore RDA master || AACR2 bibs only
|}
<div style=clear:both></div>

===option 3 - aacr2 -> aacr2, rda -> rda===
Your AACR2 bibs are first matched against the AACR2 master file. Any headings that are unmatched are next searched against RDA (if desired).

Your RDA bibs are first matched against the RDA master file. Any headings that are unmatched are next searched against AACR2 (if desired).

This option matches the current PCC standard for processing RDA bibs:

'''AACR2 Bibs'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
|-
| match 1XX in AACR2 master || AACR2 bibs only
|-
| ignore 7XX in AACR2 master || AACR2 bibs only
|-
| match RDA master || AACR2 nonmatches only
|}
<div style=clear:both></div>

'''RDA Bibs'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
|-
| match 1XX in RDA master || RDA bibs only
|-
| ignore 7XX in AACR2 master || RDA bibs only
|-
| ignore AACR2 master (incl 700 x4) || RDA nonmatches only
|}
<div style=clear:both></div>

===option 4 - aacr2 & rda -> aacr2===
This is a modified version of Option 1. What differs is that the 700 x4 in AACR2 master is included, but the matched bib heading will flip to the 1XX form within
the AACR2 authority:

{| border="1" cellspacing="0" cellpadding="5" align="left"
|-
| match 1XX in AACR2 master || AACR2 & RDA bibs
|-
| match 7XX in AACR2 master || AACR2 & RDA bibs
|-
| ignore RDA master || RDA bibs only
|-
| match RDA master || AACR2 nonmatches only
|}
<div style=clear:both></div>

If an AACR2 heading does not find a match against the modified AACR2 master (which includes the 700 x4 for this option), then the unmatched heading is
checked against the RDA master.

At this point in the process, the RDA master will consist of new RDA authorities only, with no equivalent in the AACR2 master (i.e., no AACR2 with 700 x4 has been converted to an RDA authority to match against).

==LINKS==
<center>[[RDA_7.1|7.1]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 6.3

2012-01-09T18:25:11Z

Jeremy: /* STEP 6.3 : OPTIONAL REPORTS */

==STEP 6.3 : OPTIONAL REPORTS==
[[File:RDA_6.3.jpg]]
===optional rda reports===
The primary factor in the number of optional or custom reports you request is the availability of the staff for additional record maintenance. Each library needs
to determine, based on their local circumstances, if any post-processing review will be done.

===R132 gmd retained===
The following GMD's were retained in the 245$h, even if the Content,
Media, and Carrier types were added to the 33X fields.

===R133 gmd copied to another field===
The GMD was copied to a field other than the 245 $h (e.g. 500 $a).
===R134 gmd added===
In order to create hybrid AACR2/RDA records, the following RDA
records had a GMD added to the 245 $h.
===R141 department abbreviations spelled out===
In each of the fields listed in this report, the abbreviation "dept." has
been spelled out to "Department." This may include any X10 or X11
field.
===R143 relator term abbreviations spelled out===
Relator term abbreviations which have been spelled out are included
in this report. The applicable fields/subfields include X00 $e, X10 $e,
and X11 $j.

===R144 imprint abbreviations spelled out===
The imprint fields (260 $a, $b, $c) listed within this report have had
one or more abbreviations spelled out to the fuller form of the term.

===R145 physical description abbreviations spelled out===
Abbreviations within the physical descpription (300 field) have been
spelled out. This inlcudes abbreviations within the extent (300 $a),
other physical details (300 $b), and the dimensions (300 $c).

===R146 other abbreviations spelled out===
Other abbreviations that have been spelled out are on this report.
The following types of abbreviations may have been corrected: Bible
Testament abbreviations, series numbering, abbreviations within the
notes field (500), music abbreviations, and edition statement (250)
abbreviations.
===R153 imprint field updates===
Updates made to the 260 field are listed. This includes fixing brackets
around multiple subfields and moving [i.e.] information to a 500
note field. Changes made to the 260 $a and $b to replace the Latin
abbreviations S.l. and s.n. are included on the R144 report.

===R154 statement of responsibility flag===
If the statement of responsibility (245 $c) had [et al.] or ellipsis (...),
then that data is removed and the record is flagged on this report.
If desired, someone can manually add additional information to the
statement of responsibility so that more than three contributors are
included.

===custom reports===
Backstage can generate custom reports that include information meeting many
different criteria. If the report options presented in Step 6 do not adequately
address your needs, please discuss your requirements with your project
manager.

Many different types of reports can be created using the characteristics
described in this section (e.g., fields to include, format of the report, sort order).
Reports that fall outside the scope of the options in Step 6 can be requested by
filling out additional details in your online profile.

==LINKS==
<center>[[RDA_6.1|6.1]] - [[RDA_6.2|6.2]] - [[RDA_6.3|6.3]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 6.2

2012-01-09T18:25:00Z

Jeremy: /* STEP 6.2 : STANDARD REPORTS */

==STEP 6.2 : STANDARD REPORTS==
[[File:RDA_6.2.jpg]]
===standard rda reports===
MARS 2.0 provides many of the most commonly used reports as a standard part of every RDA project. They are available for review (or not) at your discretion. Custom reports can be developed for conditions not covered by any of the RDA optional reports. Standard reports are listed above.

===R121 statistical summary===
Includes both high-level and detailed statistical information about
the files processed. Also includes the number of times selected
actions were taken and the number of headings that contain specific
conditions related to database and heading maintenance.

===R122 side-by-side record comparison===
Bibliographic records which were changed, showing both the input
and output records. Updated fields are highlighted in this side-by-side
report.

===R131 gmd converted to cmc===
Content, Media, and Carrier types were added to the 33X fields (based
on the value of the GMD in the 245 $h, position 06 of the Leader, 007,
and 008) in the records listed on this report.

===R135 unrecognized gmd===
If Backstage's GMD tables do not contain a particular GMD variant,
that GMD will be included in the Unrecognized GMD report. Records
listed on this report did not have the Content, Media, or Carrier types
added to the 33X fields.

===R142 date abbreviations spelled out===
Abbreviations within date subfields (X00 $d, X10 $d, X11 $d, X30 $d)
have been spelled out to the fuller term.

===R151 access field updates===
Changes made to access fields are listed in this report. The two
types of access field changes are updating the punctuation between
conference place names and updating the main entry if no 1XX field
exists.

===R152 title field updates===
Title fields (240, 245, & 246) which have been updated are included in
this report.

===R155 title contains [sic] or [i.e.] flag===
Spelling errors in the title field (245) should no longer be marked with
[sic]. Instead, the spelling error is retained and a 246 can be added
with the corrected version. Mistakes within the title field may have
also been marked with [i.e.]. Fields within this report have had the [sic]
and [i.e.] information removed. These fields are added to this report so
that a necessary 246 fields can be added manually.

==LINKS==
<center>[[RDA_6.1|6.1]] - [[RDA_6.2|6.2]] - [[RDA_6.3|6.3]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 6.1

2012-01-09T18:24:49Z

Jeremy: /* STEP 6.1 : REPORTS DISPLAY */

==STEP 6.1 : REPORTS DISPLAY==
[[File:RDA_6.1.jpg]]
===report format===
If you choose to display the bib ID within the report, please provide the location of the bib control numbers in your records (e.g. 001 or 907 $a).

Backstage can also obtain a control number for a secondary source field if the primary field is not present.

If bib control numbers are not included in your RDA reports, a field contained in ten bibliographic records will appear in the report only once.

Displaying only the number of records for each field within a report is usually requested by libraries with an ILS that offers robust global update tools.

When bib control numbers are included in a report, a field contained in ten bibliographic records would be included in your report ten times, each time with a different bibliographic control number.


'''display bib ID (4 separate entries for same heading):'''
ocm47933106: 650 0 $a Keith, Millie (Fictitious character).
ocm48085387: 650 0 $a Keith, Millie (Fictitious character).
ocm49033700: 650 0 $a Keith, Millie (Fictitious character).
ocm49033707: 650 0 $a Keith, Millie (Fictitious character).

'''display number of records (1 entry for all 4 headings):'''
4 records 650 0 $a Keith, Millie (Fictitious character).


===report segmentation===
Each report contains HTML code to insert a page break after every significant portion of displayed text. The page break is not viewable in the report display.

This is useful for when you want to print out the reports and perhaps assign them to staff for further review.

==LINKS==
<center>[[RDA_6.1|6.1]] - [[RDA_6.2|6.2]] - [[RDA_6.3|6.3]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 5.4

2012-01-09T18:24:37Z

Jeremy: /* STEP 5.4 : RECORDS TO FLAG */

==STEP 5.4 : RECORDS TO FLAG==
[[File:RDA_5.4.jpg]]
===flagged records===
There are a few rules in RDA that cannot be fully completed through an automated process. For these types of changes, a minor change can be made to the record and then the field is added to a report for you to review and make any further changes that may be necessary:
* If the statement of responsibility (245$c) has ellipsis ... and [et al.], then this data is removed and the record flagged. If desired, someone at the library can manually add additional information to the statement of responsibility so that more than three contributors are included.
* Spelling errors in the title field (245) should no longer be marked with [sic]. Instead, the spelling error is retained and a 246 can be added with the corrected version. MARS 2.0 will remove [sic] and then flag the record so that a cataloger can add any necessary 246 fields.
* Other indicators of a mistake within the title may have been marked with [i.e.] in the 245 field. As with the spelling errors, MARS 2.0 will remove the [i.e.] information and flag the record so that an appropriate 246 can be added manually.

==LINKS==
<center>[[RDA_5.1|5.1]] - [[RDA_5.2|5.2]] - [[RDA_5.3|5.3]] - [[RDA_5.4|5.4]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 5.3

2012-01-09T18:24:26Z

Jeremy: /* STEP 5.3 : IMPRINT UPDATES */

==STEP 5.3 : IMPRINT UPDATES==
[[File:RDA_5.3.jpg]]
===imprint updates===
When using AACR2, mutliple subfields could be enclosed within the same set of square brackets. RDA has changed this rule, so now each subfield should be enlosed within its own set of square brackets when the information was not taken from the title page (or verso).

If the 260 $a has [i.e.], then that information should be removed from the 260 field and a new 500 field should be added with the data.


'''original fields''':
260 $a [New York : $b Columbia University Press], $c 1911.
260 $a [Place of publication not identified : $b publisher not identified], $c 1963.
260 $a Hammersmith [i.e. London] : $b The Doves Press, $c 1913.

'''updated fields''':
260 $a [New York] : $b [Columbia University Press], $c 1911.
260 $a [Place of publication not identified] : $b [publisher not identified], $c 1963.
260 $a Hammersmith : $b The Doves Press, $c 1913.
500 $a Published in London.


==LINKS==
<center>[[RDA_5.1|5.1]] - [[RDA_5.2|5.2]] - [[RDA_5.3|5.3]] - [[RDA_5.4|5.4]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 5.2

2012-01-09T18:24:16Z

Jeremy: /* STEP 5.2 : TITLE FIELD UPDATES */

==STEP 5.2 : TITLE FIELD UPDATES==
[[File:RDA_5.2.jpg]]
===selections to works===
If 240 $a contains Selections, then the following change is made:


'''original field''':
240 10 $a Selections.

'''updated field:
240 10 $a Works. $k Selections.


===bracketed title information===
If the LDR position 06 is not equal to e or the 007 position 00 is not m then certain terms within the 245 $b which are enclosed in square brackets (e.g. announcement, novel, poems, proceedings, program, selections) will be deleted. If there is nothing remaining in the $b, the $b will be deleted:


'''original field''':
245 00 $a Seattle Film Festival : $b [program].

'''updated field:
245 00 $a Seattle Film Festival.


===parallel titles===
If there is an equal sign = preceeding the $b, then the text that follows the equal sign will be copied into a 246 field with indicators of 31. The new 246 will not be added if the exact same 246 field already exists:


'''original field''':
245 00 $a International meteorological vocabulary = $b Vocabulaire météorologique international = Mezhdunarodnyi meterologicheskii slovar' = Vocabulario meteorologico internacional.

'''updated fields:
245 00 $a International meteorological vocabulary = $b Vocabulaire météorologique international = Mezhdunarodnyi meterologicheskii slovar' = Vocabulario meteorologico internacional.
246 31 $a Vocabulaire météorologique international
246 31 $a Mezhdunarodnyi meterologicheskii slovar'
246 31 $a Vocabulario meteorologico internacional


===statement of responsibility===
Within the 245 $b, certain terms which come right before the $c will be moved into the $c. This includes the following terms: a novel, dramatised adaptations, novel, research and text, and stories:


'''original field''':
245 10 $a Characters From Dickens : $b dramatised adaptations / $c by Barry Campbell.

'''updated field:
245 10 $a Characters From Dickens / $c dramatised adaptations by Barry Campbell.


===[et. al] changes to [and others]===
Within the statement of responsibility (245 $c), … [et. al.] will be changed to [and others]. This will also be flagged on report R154 in case you would like to add additional contributors to the statement of responsibility:


'''original field''':
245 10 $a Second growth : $b community economic development in rural British Columbia / $c Sean Markey ... [et al.].

'''updated field:
245 10 $a Second growth : $b community economic development in rural British Columbia / $c Sean Markey [and others].


==LINKS==
<center>[[RDA_5.1|5.1]] - [[RDA_5.2|5.2]] - [[RDA_5.3|5.3]] - [[RDA_5.4|5.4]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 5.1

2012-01-09T18:24:06Z

Jeremy: /* STEP 5.1 : ACCESS FIELD UPDATES */

==STEP 5.1 : ACCESS FIELD UPDATES==
[[File:RDA_5.1.jpg]]
===conference place name update===
In AACR2, multiple place names in an X11 were separated by a comma and the word and. In RDA, a semi-colon is to be used instead:


'''original field''':
111 2_ $a Anglo-Dutch Historical Conference $n (2nd : $d 1962 : $c Utrecht, Netherlands, and Amsterdam, Netherlands)

'''updated field:
111 2_ $a Anglo-Dutch Historical Conference $n (2nd : $d 1962 : $c Utrecht, Netherlands; Amsterdam, Netherlands)


===main entry update===
If a record is a title main entry (245 1st indicator is 0 and no 1XX field exists) and a 700 field exists, the first 700 field should be changed to 100 and the 245 1st indicator updated from 0 to 1:


'''original fields''':
245 04 $a The Enzymes / $c edited by Paul D. Boyer.
700 1_ $a Boyer, Paul D.

'''updated fields:
100 1_ $a Boyer, Paul D.
245 14 $a The Enzymes / $c edited by Paul D. Boyer.


==LINKS==
<center>[[RDA_5.1|5.1]] - [[RDA_5.2|5.2]] - [[RDA_5.3|5.3]] - [[RDA_5.4|5.4]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 4.6

2012-01-09T18:23:52Z

Jeremy: /* STEP 4.6 : OTHER ABBREVIATIONS */

==STEP 4.6 : OTHER ABBREVIATIONS==
[[File:RDA_4.6.jpg]]
===bible testaments===
O.T. and N.T. should no longer be used, but the terms should be expanded as Old Testament or New Testament. With AACR2, a Biblical book title within an X30 field had an additional subfield containing either Old Testament or New Testament.

With RDA, the Testament subfield is removed when a Biblical book is in the next subfield. Koran is also now replaced with Qur'an:


'''original fields''':
130 _0 $a Bible. $p O.T.
630 _0 $a Bible. $p N.T. $p Acts.
730 _0 $a Koran.

'''updated fields''':
130 _0 $a Bible. $p Old Testament.
630 _0 $a Bible. $p Acts.
730 _0 $a Qur'an.


===series numbering===
The following table lists abbreviations that will be expanded in the numbering subfield ($v) of series fields (4xx/8xx):

{| border="1" cellspacing="0" cellpadding="5" align="left"
! style="background:silver" | Abbreviated
! style="background:silver" | Expanded
! style="background:silver" | Abbreviated
! style="background:silver" | Expanded
|-
| bd. || band || nr. || nummer
|-
| bk. || book || pt. || part
|-
| jaarg. || jaargang || ptie. || partie
|-
| jahrg. || jahrgang || pties. || parties
|-
| lfg. || lieferung || ser. || series
|-
| livr. || livraison || t. || tomo
|-
| mer. || meros || v. || volume
|-
| no. || number || vol. || volume
|}
<div style=clear:both></div>


'''original fields''':
490 1_ $a Music literature outlines ;$v ser. 1
830 _0 $a Journal of feminist family therapy ; $v v. 3, no. 1.

'''updated fields''':
490 1_ $a Music literature outlines ;$v series 1
830 _0 $a Journal of feminist family therapy ; $v volume 3, number 1.


===notes fields===
All abbreviations that are expanded for any applicable field listed in this planning
guide can be expanded in the 500 notes field as well.

===music abbreviations===
Certain abbreviations should no longer be used in the arranged statement for music (240 $o, 6XX $o, 7XX $o):

{| border="1" cellspacing="0" cellpadding="5" align="left"
! style="background:silver" | Abbreviated
! style="background:silver" | Expanded
|-
| acc. || accompanied
|-
| arr. || arranged
|-
| unacc. || unaccompanied
|}
<div style=clear:both></div>


'''original field''':
240 00 $a Wedding of Gloriana. $k Selections; $o arr.

'''updated field''':
240 00 $a Wedding of Gloriana. $k Selections; $o arranged.


===edition statement===
This table lists abbreviations that will be expanded in 250 $a (edition statement):

{| border="1" cellspacing="0" cellpadding="5" align="left"
! style="background:silver" | Abbreviated
! style="background:silver" | Expanded
|-
| 1st || First
|-
| 2nd || Second
|-
| 3rd || Third
|-
| 4th || Fourth
|-
| 5th || Fifth
|-
| 6th || Sixth
|-
| 7th || Seventh
|-
| 8th || Eigth
|-
| 9th || Ninth
|-
| 10th || Tenth
|-
| ed. || edition
|-
| rev. || revised
|}
<div style=clear:both></div>


'''original field''':
250 $a 3rd rev. ed.

'''updated field''':
250 $a Third revised edition.


==LINKS==
<center>[[RDA_4.1|4.1]] - [[RDA_4.2|4.2]] - [[RDA_4.3|4.3]] - [[RDA_4.4|4.4]] - [[RDA_4.5|4.5]] - [[RDA_4.6|4.6]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 4.5

2012-01-09T18:23:41Z

Jeremy: /* STEP 4.5 : PHYSICAL DESCRIPTION ABBREVIATIONS */

==STEP 4.5 : PHYSICAL DESCRIPTION ABBREVIATIONS==
[[File:RDA_4.5.jpg]]
===extent===
This table lists extent abbreviations that will be expanded in the 300 $a:

{| border="1" cellspacing="0" cellpadding="5" align="left"
! style="background:silver" | Abbreviated
! style="background:silver" | Expanded
! style="background:silver" | Abbreviated
! style="background:silver" | Expanded
|-
| approx. || approximately || obl. || oblong
|-
| ca. || approximately || p. || pages
|-
| cov. || cover || p.l. || preliminary leaves
|-
| dia. || diameter || pent. || pentagram
|-
| fold. || folded || pp. || pages
|-
| irr. || irregular || unnum. || unnumbered
|-
| l. || leaf || unp. || unpaged
|-
| lvs. || leaves || v. || volumes
|-
| numb. || numbered || vol. || volumes
|}
<div style=clear:both></div>

Some additional changes that are made to the 300 $a include the following:
*A number followed by brackets with i.e. will be changed to that is:
**'''48 [i.e. 52] p.''' becomes '''48, that is 52, pages'''.
*Brackets around a number will be changed to unnumbered:
**'''[16] p.''' becomes '''16 unnumbered pages'''.

===other physical details===
Abbreviations within the 300 $b (other physical details) that will be expanded include the following:

{| border="1" cellspacing="0" cellpadding="5" align="left"
! style="background:silver" | Abbreviated
! style="background:silver" | Expanded
! style="background:silver" | Abbreviated
! style="background:silver" | Expanded
|-
| b&w || black and white || illus. || illustrations
|-
| col. || color || phot. || photographs
|-
| fac. || facsimiles || photo. || photographs
|-
| facs. || facsimiles || port. || portrait
|-
| facsim. || facsimiles || ports. || portraits
|-
| facsims. || facsimiles || sam. || samples
|-
| fold. || folded || samp. || samples
|-
| gen. || genealogical || sd. || sound
|-
| geneal. || genealogical || tab. || tables.
|-
| ill. || illustrations || ||
|}
<div style=clear:both></div>

===dimensions===
Many abbreviations are still allowed in the dimensions subfield (300 $c). For instance, cm and in are still authorized to represent centimeters and inches. The following table lists the abbreviations that will be changed in the 300 $c:

{| border="1" cellspacing="0" cellpadding="5" align="left"
! style="background:silver" | Abbreviated
! style="background:silver" | Expanded
! style="background:silver" | Abbreviated
! style="background:silver" | Expanded
|-
| fol. || folio || fol. || folio
|-
| 4to || quarto || fold. || folded
|-
| 8vo || octavo || irr. || irregular
|-
| 12mo || duodecimo || lvs. || leaves
|-
| 16mo || sixteenmo || numb. || numbered
|-
| 24mo || twenty-fourmo || obl. || oblong
|-
| 32mo || thirty-twomo || p. || pages
|-
| 48mo || fourty-eightmo || pent. || pentagram
|-
| ca. || approximately || pp. || pages
|-
| cov. || cover || unnum. || unnumbered
|-
| dia. || diameter || ||
|}
<div style=clear:both></div>


'''original fields''':
300 $a 300 p. : $b ill. ; $c 4to.
300 $a [unp.] : $b ill. (some col.) ; $c 6 in.
300 $a 3 v. : $b facsims., ports. ; $c 24 x 36 cm.
300 $a 3 p.l., ca. 245 pp. : $b geneal. tables ; $c fol.
300 $a 92 [i.e. 96] pp. : $b sd., col. ; $c 24mo.
300 $a [16] p. of plates : $b col. illus. ; $c 12mo.

'''updated fields''':
300 $a 300 pages : $b illustrations ; $c quarto.
300 $a [unpaged] : $b illustrations (some color) ; $c 6 in.
300 $a 3 volumes : $b facsimiles, portraits ; $c 24 x 36 cm.
300 $a 3 preliminary leaves, approximately 245 pages : $b genealogical tables ; $c folio.
300 $a 92, that is 96, pages : $b sound, color ; $c twenty-fourmo.
300 $a 16 unnumbered pages of plates : $b color illustrations ; $c duodecimo.


==LINKS==
<center>[[RDA_4.1|4.1]] - [[RDA_4.2|4.2]] - [[RDA_4.3|4.3]] - [[RDA_4.4|4.4]] - [[RDA_4.5|4.5]] - [[RDA_4.6|4.6]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 4.4

2012-01-09T18:23:31Z

Jeremy: /* STEP 4.4 : IMPRINT ABBREVIATIONS */

==STEP 4.4 : IMPRINT ABBREVIATIONS==
[[File:RDA_4.4.jpg]]
===imprint abbreviations===
Several abbreviations in the imprint field (260) in AACR2 are not valid with RDA.
Here are several options for expanding these imprint abbreviations.

===latin abbreviations===
AACR2 used latin abbreviations for the 260 $a and 260 $b when either the place
of publication or publisher name were not available. With RDA, new phrases
have replaced these Latin abbreviations.


'''original field''':
260 $a [S.l. : $b s.n.], $c 1963.

'''updated field''':
260 $a [Place of publication not identified] : $b [publisher not identified], $c 1963.


===month names===
With RDA, names of months of the year are not to be abbreviated in the 260.
This rule uses the same month abbreviation table as is used for the X00/X10/
X11/X30 fields (see Step 4.2):


'''original field''':
260 $a Paris : $b Le Robert, $c Jan. 2010.

'''updated field''':
260 $a Paris : $b Le Robert, $c January 2010.


===geographic names===
Geographic place names (e.g. states, countries, etc.) should no longer be
abbreviated. MARS 2.0 uses a list of many different geographic terms and their
common abbreviations which will be expanded:


'''original field''':
260 $a Hoboken, N.J. : $b Wiley, $c 2009.

'''updated field''':
260 $a Hoboken, New Jersey : $b Wiley, $c 2009.


===department===
As with the X10/X11 fields, dept. should no longer be abbreviated in the 260
field; it is to be expanded to department. The Library of Congress is currently
keeping department as an abbreviation:


'''original field''':
260 $a Raleigh : $b State Dept. of Archives and History, $c 1954.

'''updated field''':
260 $a Raleigh : $b State Department of Archives and History, $c 1954.


===ca.===
In the 260 $c and $g, ca. is no longer used to represent circa or approximately.
Instead, a question mark ? should be added after the date:


'''original field''':
260 $a London : $b O. Hodgson, $c [ca. 1830]

'''updated field''':
260 $a London : $b O. Hodgson, $c [1830?]


===dashes representing unknown numbers===
With AACR2, a dash could be used to represent an unknown number within a
date. In using RDA, the dash is no longer used. A range of dates encompassing
the unknown number should now be used.

If there is a question mark included in the date, the question mark should
remain at the end of the date range:


'''original fields''':
260 $a New York : $b A. E. Chasmar, $c [188-]
260 $a London : $b J.T. Pickburn, $c [18--?]

'''updated fields''':
260 $a New York : $b A. E. Chasmar, $c [between 1880 and 1889]
260 $a London : $b J.T. Pickburn, $c [between 1800 and 1899?]


===printing/pressing/copyright/phonogram===
Printing or pressing dates should now be enclosed within square brackets with a
question mark at the end of the date.

When either a c or p is the character right before a date, they should be changed
for either the copyright symbol © or phonogram symbol ℗.

If only a copyright date is included, RDA dictates that [place of publication not
identified] should be added:


'''original fields''':
260 $a New York : $b Alfred A. Knopf, $c 2010 printing.
260 $a Berlin : $b Louis Gerschel, $c c1964.
260 $a New York : $b Anchor Books, $c p2001.

'''updated fields''':
260 $a New York : $b Alfred A. Knopf, $c [2010?]
260 $a Berlin : $b Louis Gerschel, $c [date of publication not identified], ©1964.
260 $a New York : $b Anchor Books, $c ℗2001.


==LINKS==
<center>[[RDA_4.1|4.1]] - [[RDA_4.2|4.2]] - [[RDA_4.3|4.3]] - [[RDA_4.4|4.4]] - [[RDA_4.5|4.5]] - [[RDA_4.6|4.6]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 4.3

2012-01-09T18:23:15Z

Jeremy: /* STEP 4.3 : RELATOR TERM ABBREVIATIONS */

==STEP 4.3 : RELATOR TERM ABBREVIATIONS==
[[File:RDA_4.3.jpg]]
===relator terms===
In AACR2, many relator terms were not included on headings. With RDA, the
relator terms are retained and expanded if they are in their abbreviated form.
MARS 2.0 will retain all relator terms in X00 $e, X10 $e, and X11 $j. The following
relator term abbreviations will be expanded:

{| border="1" cellspacing="0" cellpadding="5" align="left"
! style="background:silver" | Abbreviated
! style="background:silver" | Expanded
|-
| ill. || illustrator
|-
| illus. || illustrator
|-
| comp. || compiler
|-
| arr. || arranger
|-
| tr. || translator
|-
| auth. || author
|-
| jt. || joint
|}
<div style=clear:both></div>


'''original fields''':
100 1_ $a Jackson, Myles W., $e jt. auth.
710 2_ $a Sahitya Akademi, $e comp.

'''updated fields''':
100 1_ $a Jackson, Myles W., $e joint author.
710 2_ $a Sahitya Akademi, $e compiler.


==LINKS==
<center>[[RDA_4.1|4.1]] - [[RDA_4.2|4.2]] - [[RDA_4.3|4.3]] - [[RDA_4.4|4.4]] - [[RDA_4.5|4.5]] - [[RDA_4.6|4.6]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 4.2

2012-01-09T18:23:01Z

Jeremy: /* STEP 4.2 : DATE ABBREVIATIONS */

==STEP 4.2 : DATE ABBREVIATIONS==
[[File:RDA_4.2.jpg]]
===date abbreviations===
There are many different abbreviations in $d (i.e., date) of 1XX, 6XX, 7XX, and
8XX fields that can be expanded. The majority of these date changes only take
place within X00 fields. The main exception is expanding month names in X10,
X11, and X30 fields.

===birth date===
RDA rules say that there are two possibilities for when the abbreviation b. has
been used in a date. The first option is to remove b. and add a hyphen after the
birth date. The other option is that b. can change to born. Current LC policy is to
add the hyphen after the birth date:


'''original field''':
100 1_ $a Mort, Paul R., $d b. 1894.

'''updated field''':
100 1_ $a Mort, Paul R., $d 1894- ''LC policy
OR
100 1_ $a Mort, Paul R., $d born 1894.


===death date===
As with the birth date, there are also two options for expanding the abbreviation
for a death date. When a d. is encountered, a hyphen can be added before the
death date with the d. being removed or else d. can be changed to died. Current
LC policy is to add the hyphen before the date:


'''original field''':
100 1_ $a Lewis, Georgina King, $d d. 1924.

'''updated field''':
100 1_ $a Lewis, Georgina King, $d -1924. ''LC policy
OR
100 1_ $a Lewis, Georgina King, $d died 1924.


===flourished => active===
There are two different ways that fl. or flourished can be changed using RDA
guidelines. The first way is to change these to active in the same position of the
$d (typically right before the date). The other way to handle this is to expand fl.
to flourished. Current LC policy is to change these to active:


'''original field''':
100 1_ $a Brown, John, $d fl. 1854.

'''updated field''':
100 1_ $a Brown, John, $d active 1854. ''LC policy
OR
100 1_ $a Brown, John, $d flourished 1854.


===month names===
In AACR2, month names were generally abbreviated. In RDA, month names
should be expanded. The following table shows the changes that will be made
with month names.

{| border="1" cellspacing="0" cellpadding="5" align="left"
! style="background:silver" | Abbreviated
! style="background:silver" | Expanded
|-
| Jan. || January
|-
| Feb. || February
|-
| Mar. || March
|-
| Apr. || April
|-
| Jun. || June
|-
| Jul. || July
|-
| Aug. || August
|-
| Sep. || September
|-
| Sept. || September
|-
| Oct. || October
|-
| Nov. || November
|-
| Dec. || December
|}
<div style=clear:both></div>


'''original fields''':
100 1_ $a Einhorn, Richard, $d 1952 Aug. 2-
730 _0 $a Geneva Conventions $d (1949). $k Protocols, etc., $d 2005 Dec. 8.

'''updated fields:
100 1_ $a Einhorn, Richard, $d 1952 August 2-
730 _0 $a Geneva Conventions $d (1949). $k Protocols, etc., $d 2005 December 8.


===other date abbreviations===
A few additional abbreviations that can be expanded in date subfields include the following:

{| border="1" cellspacing="0" cellpadding="5" align="left"
! style="background:silver" | Abbreviated
! style="background:silver" | Expanded
|-
| ca. || approximately
|-
| cent. || century
|-
| cen. || century
|}
<div style=clear:both></div>


'''original fields''':
100 1_ $a Fenton, Geoffrey, $d ca. 1539-1608.
600 10 $a Seghers, Hercules, $d 17th cent.
700 0_ $a Raol, $d 12th cen.

'''updated fields:
100 1_ $a Fenton, Geoffrey, $d approximately 1539-1608.
600 10 $a Seghers, Hercules, $d 17th century.
700 0_ $a Raol, $d 12th century.


==LINKS==
<center>[[RDA_4.1|4.1]] - [[RDA_4.2|4.2]] - [[RDA_4.3|4.3]] - [[RDA_4.4|4.4]] - [[RDA_4.5|4.5]] - [[RDA_4.6|4.6]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 4.1

2012-01-09T18:22:51Z

Jeremy: /* STEP 4.1 : DEPARTMENT ABBREVIATIONS */

==STEP 4.1 : DEPARTMENT ABBREVIATIONS==
[[File:RDA_4.1.jpg]]
===dept. => department===
One of the most talked about changes in abbreviations has been the change
from abbreviating the term department. The abbreviation dept. has been
widely used in Corporate Names (X10) and Meeting Names (X11).

The Library of Congress has not yet made an official statement dictating
whether they will begin expanding this abbreviation.

MARS 2.0 can expand dept. to department in all of the X10/X11 fields, or only in
the fields which you specify:


'''original fields''':
110 1_ $a New York (State). $b Dept. of Motor Vehicles.
610 10 $a United States. $b Army. $b Dept. of the Columbia.

'''updated fields''':
110 1_ $a New York (State). $b Department of Motor Vehicles.
610 10 $a United States. $b Army. $b Department of the Columbia.


==LINKS==
<center>[[RDA_4.1|4.1]] - [[RDA_4.2|4.2]] - [[RDA_4.3|4.3]] - [[RDA_4.4|4.4]] - [[RDA_4.5|4.5]] - [[RDA_4.6|4.6]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 3.4

2012-01-09T18:20:53Z

Jeremy: /* STEP 3.4 : CMC to GMD */

==STEP 3.4 : CMC to GMD==
[[File:RDA_3.4.jpg]]
===cmc to gmd===
If you are choosing to have the RDA processes upgrade your existing RDA bib
records, MARS 2.0 provides the option to add a GMD in the 245 $h if it is missing
in order to create a hybrid AACR2/RDA record.

While PCC guidelines suggest GMD and CMC can co-exist in the same record, it
does not recommend adding a GMD to an existing RDA bib record.

==LINKS==
<center>[[RDA_3.1|3.1]] - [[RDA_3.2|3.2]] - [[RDA_3.3|3.3]] - [[RDA_3.4|3.4]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 3.3

2012-01-09T18:20:43Z

Jeremy: /* STEP 3.3 : GMD TO CMC OPTIONS */

==STEP 3.3 : GMD TO CMC OPTIONS==
[[File:RDA_3.3.jpg]]
===other gmd to cmc options===
Some libraries may not want to retain the GMD in the 245 $h, but they would
like this information retained elsewhere in their bibliographic record. MARS
2.0 provides the option to copy the GMD to a 500 note or other field/subfield
specified by your library.

==LINKS==
<center>[[RDA_3.1|3.1]] - [[RDA_3.2|3.2]] - [[RDA_3.3|3.3]] - [[RDA_3.4|3.4]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 3.2

2012-01-09T18:20:34Z

Jeremy: /* STEP 3.2 : RETAIN OR REMOVE GMD */

==STEP 3.2 : RETAIN OR REMOVE GMD==
[[File:RDA_3.2.jpg]]
===retain or remove gmd===
The PCC guideline for converting AACR2 records to RDA says to retain the GMD
in the 245 $h. This allows for the record to contain hybrid AACR2 and RDA
elements, which may facilitate ILS display or discovery.

MARS 2.0 also provides the option to remove the GMD in the 245 $h if you
determine that it is no longer needed after the Content, Media, and Carrier
types have been added in the 33X fields.

==LINKS==
<center>[[RDA_3.1|3.1]] - [[RDA_3.2|3.2]] - [[RDA_3.3|3.3]] - [[RDA_3.4|3.4]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 3.1

2012-01-09T18:20:22Z

Jeremy: /* STEP 3.1 : GMD TERMS */

==STEP 3.1 : GMD TERMS==
[[File:RDA_3.1.jpg]]
===gmd term list===
MARS 2.0 has two lists of GMD terms that can be used to determine what
Content, Carrier, and Media types should be added in the 33X fields. These lists
are also used in the GMD Standardization section of the Bibliographic Validation
(Step 2.1). If a bib record has a GMD which is not on the list that you choose for
creating the CMC fields, then the record will be reported on R135 so that you
can review the record to add the correct 33X fields.

===aacr2 standard terms===
The AACR2 Standard Terms list contains the terms authorized in the current
edition of AACR2. Most libraries will want to select this level of GMD to CMC
processing.
{| border="1" cellspacing="0" cellpadding="5" align="left"
| activity card || flash card || object
|-
| art original || game || picture
|-
| art reproduction || kit || realia
|-
| braille || manuscript || slide
|-
| cartographic material || microform || sound recording
|-
| cartographic material (tactile) || microscope slide || technical drawing
|-
| chart || model || text
|-
| chart (large print) || motion picture || text (large print)
|-
| diorama || multimedia || toy
|-
| electronic resource || music || transparency
|-
| filmstrip || music (braille) || videorecording
|}
<div style=clear:both></div>

===common practice terms===
In their local catalog, some libraries use GMDs which are not included in the
AACR2 list of authorized GMDs (AACR2 paragraph 1.1C). The GMD Common

Terms list contains "common" terms used in many libraries.
For example, using the Common Terms table, the GMD $h [audiocassette] could
be used, while the AACR2 Standard Terms option would use the GMD $h [sound
recording].

{| border="1" cellspacing="0" cellpadding="5" align="left"
| activity card || globe || record
|-
| art original || government document || serial
|-
| art reproduction || graphic || slide set
|-
| atlas || kit || sound recording
|-
| audiocassette || large print || sound recording (cassette)
|-
| braille || laser disc || sound recording (compact disc)
|-
| cartographic chart || LP || sound recording (CD)
|-
| cartographic material || manuscript || sound recording (LP)
|-
| cartographic material (tactile) || map || study print
|-
| CD recording || map (tactile) || technical drawing
|-
| CD-ROM || microfiche || text
|-
| CDV || microfilm || text (large print)
|-
| chart || microform || toy
|-
| chart (large print) || microopaque || transparency
|-
| compact disc || microprint || US document
|-
| diorama || microscope slide || VHS
|-
| DVD || model || video CD
|-
| DVD-ROM || motion picture video || single disc
|-
| electronic resource || music || videocassette
|-
| electronic resource (CD-ROM) || music (braille) || videodisc
|-
| federal document || newspaper || videodisc (DVD)
|-
| filmstrip || periodical || videorecording
|-
| flash card || photograph || videorecording (DVD)
|-
| floppy || picture || videorecording (VHS)
|-
| game || realia || VSD
|}
<div style=clear:both></div>

===unrecognized terms===
If MARS 2.0 GMD tables do not contain a particular GMD variant, that GMD will
be included in the Unrecognized GMD Report (See Step 6.2, R135). If there are
unrecognized terms that appear frequently, they may be added to our list of
common GMD terms in the future.

==LINKS==
<center>[[RDA_3.1|3.1]] - [[RDA_3.2|3.2]] - [[RDA_3.3|3.3]] - [[RDA_3.4|3.4]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 2.3

2012-01-09T18:19:16Z

Jeremy: /* STEP 2.3 : CATALOGING SOURCE DESCRIPTION CONVENTION */

==STEP 2.3 : CATALOGING SOURCE DESCRIPTION CONVENTION==
[[File:RDA_2.3.jpg]]
===cataloging source (040)===
In records that are converted from AACR2 (or another standard) to RDA,
Backstage will add $e rda to the existing 040 (if not currently present), or else
add a new 040 with this subfield if the field does not exist.

==LINKS==
<center>[[RDA_2.1|2.1]] - [[RDA_2.2|2.2]] - [[RDA_2.3|2.3]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 2.2

2012-01-09T18:18:57Z

Jeremy: /* STEP 2.2 : LEADER UPDATES */

==STEP 2.2 : LEADER UPDATES==
[[File:RDA_2.2.jpg]]
===leader updates===
Leader position 18 is used for encoding the descriptive cataloging form. The
default option will be to change LDR[18] from a (AACR2) to i (ISBD punctuation is
included). Another option is available if you would like this position changed to c
instead of i, meaning that the ISBD end of field punctuation is omitted.

Other values of LDR[18] (i.e. #, c, i, u) will not be changed. If you would like other
values in the leader changed, speak with your project manager to discuss your
options.

==LINKS==
<center>[[RDA_2.1|2.1]] - [[RDA_2.2|2.2]] - [[RDA_2.3|2.3]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 2.1

2012-01-09T18:18:31Z

Jeremy: /* STEP 2.1 : BIBLIOGRAPHIC VALIDATION */

==STEP 2.1 : BIBLIOGRAPHIC VALIDATION==
[[File:RDA_2.1.jpg]]
===[[Step_2.0|bibliographic validation]]===
Prior to beginning the RDA processing, MARS 2.0 makes sure that the
bibliographic records are up to the latest AACR2 standard. Records which were
cataloged using an older standard (e.g., AACR1) can be brought up to current
AACR2 standards before being converted to RDA standards.

The steps taken during Bibliographic Validation are the same steps taken during
our authority control processing. To find more detailed information about these
steps, please review [[Step_2.0|Step 2]] from the [[Step_1.0|MARS 2.0 Authority Control Planning
Guide]]. Below you will find an overview of each type of change that will take
place during this step as well as the corresponding page number in our MARS
2.0 Authority Control Planning Guide with more detailed information.

===[[Step_2.1|step 2.1 : validate 010, 020, 022, 034 fields]]===
MARC fields that are incorrectly formatted often cause user searches to fail and
prevent items in the collection from being included in the system indexes. MARS
2.0 can clean up spacing, hyphens, prefixes, and suffixes of the 010, 020, 022,
and 034 fields.

===[[Step_2.2|step 2.2 : leader & fixed field updates]]===
Bibliographic validation processing provides a variety of updates and corrections
to values in the Leader and Fixed fields (006, 007, 008). These updates mainly
consist of changing one value to another based on the type of record format
(book, map, etc.).

===[[Step_2.3|step 2.3 : field updates &deletes]]===
Changes to the MARC 21 communications format have made many fields
obsolete. If one field has been replaced by another, the update changes the tag
number. If the field has been made obsolete without being replaced, the field
is simply deleted from the bib record. There are 22 fields that are changed to
another field. Currently, 16 fields are removed from the bib record in this step.

===[[Step_2.4|step 2.4 : subfield updates & deletes]]===
Many subfields are no longer valid within certain fields and so the subfield
marker is changed from one (invalid) to another (valid). There are also a number
of subfields which no longer have any corresponding use in the bib record and
these are removed as part of the bibliographic validation processing. Relator
term entries are included in this step. There are 15 subfields changed to another
subfield, with 24 fields that have obsolete subfields removed altogether.

===[[Step_2.5|step 2.5 : indicator updates]]===
In order to bring the indicators (both 1st & 2nd) in line with current MARC 21
standards, many fields in this step have their indicators changed from one value
(invalid) to a specific value (valid). There are 32 fields with the 1st indicator
updated and 26 fields with the 2nd indicator updated.

===[[Step_2.6|step 2.6 : field conversions & additions]]===
A number of MARC update conversions are more complex than simply changing
a field tag or subfield code to the current value. Some fields, such as the 007,
often need to be added to a record.

Step 2.6 adds missing format data, missing subfield data, and makes complex
field conversions. There are 12 fields in this step that are affected.

===[[Step_2.7|step 2.7 : initial article & filing indicators]]===
MARS 2.0 supports the standard practice of omitting most initial articles even if
a nonfiling character indicator has been defined for the field. Initial articles are
retained, and the filing indicator correctly set, for the 245 and 440 fields.

You can also choose to have corporate heading fields checked for initial articles. This applies to the $t in the X10 fields.

There is also an extensive list of each initial article with its associated filing
indicator, sorted by language.

===[[Step_2.8|step 2.8 : gmd standardization]]===
MARS 2.0 also updates obsolete General Material Designations (GMD) to the
current authorized form, and corrects most incorrectly spelled GMD variants. If
brackets are missing, these can also be added in this step. GMD standardization
also helps convert this information to the Content, Media, and Carrier types
listed in Step 3 of this planning guide.

The AACR2 Standard Terms Table (Level 1 - p. 57) is used by default in this step.
However, Common Terms Table (Level 2 - p. 58), andcustom options are also
available, depending on your preference.

==LINKS==
<center>[[RDA_2.1|2.1]] - [[RDA_2.2|2.2]] - [[RDA_2.3|2.3]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 1.5

2012-01-09T18:18:17Z

Jeremy: /* bibliographic change stamps */

==STEP 1.5 : CHANGE STAMP==

==bibliographic change stamps==
[[File:RDA_1.5.jpg]]

Backstage can stamp each bibliographic record with one or more of the
following identifiers or only those bibliographic records that were changed
during the RDA processing.

Indicate in Step 1.5 which, if any, of the following stamp options you would like
in your bibliographic records:
*040 — MARC Organization Code UtOrBLW can be added to the modifying agency $d in the 040 field. A new 040 field is added to any record lacking an 040 field.
*005 — Backstage can update an existing 005 date and time of latest transaction field to the date and time that the record is being processed. If this option is requested and a record does not contain an 005 field, one will be added.
*9XX — The text MARS can be added in a $a in a field you specify (e.g., 945 $a MARS).
*Other — If you have other methods in mind for adding a change stamp to the record, please contact your Backstage project manager.

==LINKS==
<center>[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 1.5

2012-01-09T18:18:09Z

Jeremy: /* bibliographic change stamps */

==STEP 1.5 : CHANGE STAMP==

==bibliographic change stamps==
[[File:RDA_1.5.jpg]]
Backstage can stamp each bibliographic record with one or more of the
following identifiers or only those bibliographic records that were changed
during the RDA processing.

Indicate in Step 1.5 which, if any, of the following stamp options you would like
in your bibliographic records:
*040 — MARC Organization Code UtOrBLW can be added to the modifying agency $d in the 040 field. A new 040 field is added to any record lacking an 040 field.
*005 — Backstage can update an existing 005 date and time of latest transaction field to the date and time that the record is being processed. If this option is requested and a record does not contain an 005 field, one will be added.
*9XX — The text MARS can be added in a $a in a field you specify (e.g., 945 $a MARS).
*Other — If you have other methods in mind for adding a change stamp to the record, please contact your Backstage project manager.

==LINKS==
<center>[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 1.4

2012-01-09T18:17:19Z

Jeremy: /* STEP 1.4 : FILE DOWNLOAD AND FILE FORMAT */

==STEP 1.4 : FILE DOWNLOAD AND FILE FORMAT==
[[File:RDA_1.4.jpg]]
===utf-8 vs marc-8 format===
The MARC-8 character set uses 8-bit characters. Due to the limitation of
characters that this allows, MARC-8 also includes methods to extend the
displayable characters: spacing based characters (for cursor movement) and
non-spacing characters (diacritics).

MARC-8 also employs the use of alternate character sets in order to tackle the
diacritic display issue. This is done by using escape sequences, which are special
codes to indicate which character set is being selected for display: subscripts,
superscripts, CJK characters, etc.

While these methods allow for many additional characters to be used, it is still
limited and somewhat burdensome.

UTF-8 is a standard based on 16-bit characters. It is a method of encoding
characters into sequences of from 1 to 3 bytes. Unicode has definitions for nonspacing
characters like MARC-8, except these characters are handled differently
for UTF-8.

UTF-8 also includes many precomposed characters. These are spacing
characters that are equivalent to one or more diacritic characters and a spacing
character. To handle the various ways a composite character could be displayed,
normalization forms have been defined.

Normalization Form Decomposed (NFD) and Normalization Form Composed
(NFC) are standardized forms for handling composite characters.

In NFD, every character that can be decomposed is converted to its most
decomposed form following rules for canonical decomposition.

In NFC, the characters are first decomposed as in NFD, then composed into
precomposed (composite) forms following canonical rules. This may result in
the sequence of characters for a given character changing into an alternate,
equivalent form.

==LINKS==
<center>[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 1.3

2012-01-09T18:17:10Z

Jeremy: /* STEP 1.3 : RECORDS RETURNED */

==STEP 1.3 : RECORDS RETURNED==
[[File:RDA_1.3.jpg]]
===all bib records===
When converting AACR2 records to RDA, all records will have some changes
made (even if the only change is updating the Leader and adding 040 $e rda). If
you are choosing to do the full crosswalk from AACR2 to RDA, you would need
every bib record returned to replace your existing record in your ILS.

===changed bibs only===
This option encompasses all changes made during the RDA processing. If you
would like the RDA processing to only take place when upgrading and validating
existing RDA bib records, then you could choose to have only changed bib
records returned.

===bibliographic file segmentation===
ILS limitations or requirements for loading and indexing updated records are a
consideration in determining maximum bibliographic output size.

The response time in some local systems is sometimes degraded during
prolonged loads. In other ILS, essential online system tasks cannot be
performed during a load.

While Backstage can handle files in excess of 1,000,000 records, we can also
distribute files broken up into more appropriate chunks to facilitate the loading
and indexing processes at your side.

==LINKS==
<center>[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

RDA 1.2

2012-01-09T18:16:58Z

Jeremy: /* STEP 1.2 : TYPE OF RDA PROCESSING */

==STEP 1.2 : TYPE OF RDA PROCESSING==
[[File:RDA_1.2.jpg]]
===records to process===
The steps taken in this profile can be used to convert all of your bibliographic
records from AACR2 (or an older standard) to RDA, upgrade existing RDA bib
records (as designated by the 040 $e rda), or create hybrid AACR2/RDA bib
records.

===convert all bib records to rda===
If you choose to convert all records to RDA, then every AACR2 record that is
processed will be updated to include the RDA updates chosen in the rest of this
profile.

===upgrade existing rda records===
When you choose to have Backstage upgrade your existing RDA bibliographic
records, our processes will validate and correct standard information within
only records that already contain 040 $e rda.

===create hybrid aacr2/rda records===
The PCC is working on guidelines for creating a hybrid AACR2/RDA bibliographic
record. Options within this profile can help you upgrade your existing AACR2
and RDA bib records to be hybrid records as outlined by the PCC standard.

==LINKS==
<center>[[RDA_1.1|1.1]] - [[RDA_1.2|1.2]] - [[RDA_1.3|1.3]] - [[RDA_1.4|1.4]] - [[RDA_1.5|1.5]]
<hr>
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]] - [[RDA_7.0|7.0]]</center>
[[category:RDA Profile Guide]]

File:RDA 7.1.jpg

2012-01-09T18:16:39Z

Jeremy:

File:RDA 6.3.jpg

2012-01-09T18:16:31Z

Jeremy:

File:RDA 6.2.jpg

2012-01-09T18:16:24Z

Jeremy:

File:RDA 6.1.jpg

2012-01-09T18:16:18Z

Jeremy:

File:RDA 5.4.jpg

2012-01-09T18:16:10Z

Jeremy:

File:RDA 5.3.jpg

2012-01-09T18:16:01Z

Jeremy:

File:RDA 5.2.jpg

2012-01-09T18:15:52Z

Jeremy:

File:RDA 5.1.jpg

2012-01-09T18:15:43Z

Jeremy:

File:RDA 4.6.jpg

2012-01-09T18:15:35Z

Jeremy:

File:RDA 4.5.jpg

2012-01-09T18:15:25Z

Jeremy:

File:RDA 4.4.jpg

2012-01-09T18:15:00Z

Jeremy:

File:RDA 4.3.jpg

2012-01-09T18:14:38Z

Jeremy:

File:RDA 4.2.jpg

2012-01-09T18:14:32Z

Jeremy:

File:RDA 4.1.jpg

2012-01-09T18:14:26Z

Jeremy:

File:RDA 3.4.jpg

2012-01-09T18:14:19Z

Jeremy:

File:RDA 3.3.jpg

2012-01-09T18:14:13Z

Jeremy:

File:RDA 3.2.jpg

2012-01-09T18:14:06Z

Jeremy:

File:RDA 3.1.jpg

2012-01-09T18:14:00Z

Jeremy:

File:RDA 2.3.jpg

2012-01-09T18:13:53Z

Jeremy:

File:RDA 2.2.jpg

2012-01-09T18:13:46Z

Jeremy: