MARS Authority Control

Automated Services for Libraries, Authority Control, Machine Matching, and Marcadia

Stats Page

No comments

Any time we process a file for your institution, we generate a Statistical Summary report.  Within this report, we list match-rates, types of records processed, as well as the number of fields changed during processing.  While this is all well and good, as soon as that report is sent out to you, those statistics have been forgotten.

We thought it would be a good idea to keep you informed of some of those statistics on a regular basis, all completely tailored to when you send us files for processing.  And we wanted to do this in a graphical way so that you’re not just looking at lists of numbers and confused as to their relevancy to your records.

As we started planning on what to do with the statistics, we realized early on that not everyone goes through our website to process their files.  Some of our clients use external FTP servers, while some use the website.  We never want our customers to feel left out on any functionality we have implemented.

Whenever a file is submitted to Backstage for processing, we keep track of certain statistics within our tables.  We have to keep track because this is how we generate that Statistical Summary report that we deliver for base files, ongoing current cataloging, and samples.  It doesn’t matter how the file reaches us (website, ftp, email, etc)—once we process it, we keep track of the data.

This statistical tracking helps us determine the busiest times of the year and how we should structure the time on our side to meet the expectations on your side.  We also realized that this could be a useful tool for you and your staff to track the trends in your own processing.  Throughout the year, how often do you send in files for processing?  What kinds of match-rates or types of records do you usually see?

We have created two sections for you:

  1. Record Statistics
  2. Match Statistics

For Record Statistics, we’ll show you how many books, serials, and other types of records were processed:

Of those records, how many were changed vs unchanged?

We’ll also plot how many records you sent throughout the year:

We think it makes sense to only include months where you send us bib files to process.  Each part of every graph has parts that can be clicked to determine more information, or isolate that part of the process for you.

With Match Statistics, we go a step further than our Statistical Summary report and tell you about the kinds of matches you’ve received on your records:

Finally, we wanted to also show you how many of your headings (1xx, 6xx, 7xx) found full or partial matches, as well as the number of unmatched headings:

Over the next few weeks, we plan on putting this information in place for all of our clients.  Whenever you log into our website to view your profile or current jobs, you can also view your stats.  Again, it doesn’t matter whether you send us your bibs through the website, ftp server, or email—once we process them, those stats will be added to your stats page.

As a bonus to those clients that do send us their files through the website, each one of those website bibliographic jobs will have its own set of graphic statistics as well.

We hope this information gives you the edge you may need for your staff.  As always, feel free to let us know if you would like to see other statistics.

New Optional Report – R08 Generic Names

Backstage has a new optional report that can be generated during Current Cataloging or Basefile processing.  The new report lists all generic name headings.  Below is a brief description of the report as well as a few examples of how headings on this report appear.

The fields in this report contain a primary name heading which is considered generic (i.e. names without qualifiers such as a date or fuller form of the name). Choosing to flip on generic name headings will give you a greater match rate, but it can cause mismatched headings. The MARS 2.0 software allows for the flip of all name authority headings including the generic heading if there is a match to a See reference (400) in the LC authority record.

.b42996120 700 1 $aAdams, Stefan.
.b43163178 100 1 $aAli, Souad Tagelsir.
.b43119815 700 1 $aBayly, Francis Trevelyan Villiers.
.b43105038 700 1 $aBillman, E.
.b42847254 700 1 $aBotkin, Perry.$4arr
.b43099828 700 1 $aCastor, Claude Hay.
.b42680025 700 1 $aChan, Chun-Yong.

Sometimes a national authority record just lacks some of the key information that your library needs. Maybe it’s an important cross-reference, a note, or some sort of field identifier. If you just receive the latest Library of Congress authority, for example, you could lose all that hard work that you and your staff have gone through to find the information and add it to your authorities.

If you’ve added information to some authorities that need to be preserved, we must have a way to retain it here so we can transfer the information to any future LC updates. Now that you’ve had time to see a need for it, we can get things set up.
This section is found in your Profile, Step 3, Question 11 (See this section).  It’s pretty short – shorter than I was thinking.  Basically you just need to mark the radial button and indicate what the $5 will be.  Here’s a (hopefully better) explanation of what I was trying to explain:

Say you have an authority to which you’ve added a local 500 see-also reference, and maybe you’ve modified an 022 and added a 670 note.  Say you want to preserve that 500, the modified 022 and the 670 field no matter what.  If you add a $5[code] to the end of those 3 fields and send us a copy of the authority, we can then take those 3 fields and put them into a table here, along with the authority's control number.  Then the next time LC updates that authority our system will match the control number with the table, find the fields that need to be preserved and add them to the updated authority we'll be sending to you.  When you load the authority back into your system it will overwrite the one you've already got, but it'll be okay because the fields you need preserved will be in the new record.  Here's an example of what I mean about marking the fields (I made up some of the info in this example - it's pretty bad - please forgive):

001    __    n  00001621
003    __    DLC
005    __    20001227110358.0
008    __    000204n| acannaabn          |n aaa
010    __    $an  00001621
022    __    $a0743-1643$l0743-1643$5SYM
040    __    $aDLC$beng$cDLC$dDLC
100    1_    $aHester, D. Micah
500    1_    $aAndrews, Joseph$5SYM
670    __    $aComputers and ethics in the cyberage, 2001:$bCIP t.p. (D. Micah Hester)
670    __    $aCommunity as healing, 2001: CIP t.p. (D. Micah Hester) data sheet, etc. (b. Jan. 16, 1966; Ph.D., asst. prof. of Biomedical Ethics, School of Medicine, Mercer Univ., Macon, Ga.)
670    __    $aCommunity as healing, 2001: CIP t.p. (Joseph Andrews, co-author)$5SYM

The bolded stuff in the 022, 500 and 670 is the info "added" and the red info is the code you should put on the field so we know it's what you want preserved.  I hope that all makes sense.  :-)

To get this going you need to do 3 things:

(1)  Decide what kind of a code you want in that $5, and then add it to all the fields in all the authorities you want preserved.  Most of our other clients just use a version of their library code ... for example, $5SYM.  But you can use whatever you'd like - just as long as we know what it is;
(2)  Send us a copy of the modified authorities so we can create a table;
(3)  Also send us a list of the fields you want preserved.  Example:  "We've modified some 050s, 022s, 400s, 500s, 670s - please preserve these tags if they have a $5SYM."

And that's pretty much it.  Your fields will be preserved every time we receive an update from LC.

If any of this seems unclear or if you have any questions at all, please don't hesitate to ask.

Thanks to our project manager for writing that up. Preserving fields is one of the services many of our libraries find most useful, and we have even more options than listed above when it comes to preserving your data for cases where adding a $5 would be unreasonable or impossible. so feel free to talk to on of our project managers about how we can help you with your situation.

Machine-Upgrade

Have bib records with a brief amount of information?  Are they good enough to keep but not bad enough to discard?

Backstage Library Works can upgrade your brief bib records against full MARC records from Library of Congress.  The matched records will replace your brief records, bringing them in line with current MARC21 standards and AACR2 formatting.

We have many different options for you to consider when upgrading your brief records.  What’s important is returning matches that enhance your collection.  Try our FREE Records Test today and see if the Machine-Upgrade service is right for you and your bibs.

Deduplication

Have a set of records that need to be consolidated?  Just acquired new records to add to your existing database?

Backstage Library Works combines your records into one manageable database.  Deduplication merges your duplicate records into one match.  Have holdings fields you want to also merge with the matched record?  We can retain any field you specify and even move data around based on your instructions.  Backstage Library Works lets you decide how strict or lenient the match criteria should be.

You receive a cleaner database, with all of your data intact and the peace of mind that comes from knowing another project can be crossed off of your list.

Custom Services

Need to rearrange the data within your records?  Have a subset of records that could benefit from a quick fix?

Backstage Library Works offers the ability to work within your expectations.  The way you want to modify your records is the right way and we can make that happen for you.  With our expertise in your corner, you no longer have to worry about when you will have the time to change your records.  We make the time for you and return it when you need it.

At Backstage Library Works, we don’t ask, “Why do you want to do that?”  We ask, “When can we make this happen for you?”

Maritta, the head of our cataloging and bibliographic services department asked if we could post this announcement on our blog, we’re always happy to share information about RDA with our readers, so here you go.

Backstage is pleased to announce its participation plan for the current US National Test for RDA.

Backstage will be participating in the test as one of two vendor institutions.  As a provider of cataloging services, Backstage will be evaluating the effects of RDA on costs and services to library and publisher clients in relation to cataloging, copy cataloging, retrospective conversion, and reclassification.  Specific attention will be paid to the ease and time of training entry level para-professionals for working in an RDA environment (compared with an AACR environment).

The test dates designated by the RDA Test administration panel are as follows:

July-September, training & practice time; familiarization with the RDA toolkit

October-December, the formal test & processing of test materials in RDA; complete surveys

January-March, Review and report by Test administration

Our schedule will follow the prescribed schedule as set by the Test administration panel: we will be processing material in October-November, and will be evaluating with a formal report in December.

For our test, we will be training the following staff in RDA: three experienced catalogers (trained and highly experienced in cataloging with AACR2), one para-professional with limited cataloging experience (newly trained and currently cataloging with AACR2), and one inexperienced paraprofessional (no prior cataloging training at all).  We will be running comparable side-by-side testing of material and training in AACR2.

In addition, Backstage is preparing for any RDA records anticipated by its automated services department, including Authority Control and Marcadia.  Data will be tested and systems will be ready to appropriately process RDA data starting October 1, 2010.

With all the excitement surrounding RDA at ALA Annual (and we’ll have an update about that up soon), we realized we didn’t have a quick recap of events from my point of view in DC.  I would like to fill you in on details from an operational point of view as concerns Backstage, letting Karen Anderson let you know about the RDA updates later.

On June 24, a few of us flew into Bethlehem, PA to visit our new offices out there.  As some of you may know, we acquired the preservation services (Digitization, Microfilm) from OCLC back in August 2009.  So it was an opportunity to get out and visit with our team, meeting Joan DaShiell and Joe Konrath, both of whom are widely respected in that business.

That next Friday we drove up to DC to take part in the sweltering outside heat and air-conditioned halls of the conference center.  The traffic going into DC made the trip an all-day affair, though the upside was it gave us a chance to catch up on our emails and plan out our schedules.

On Saturday, we had a great turnout for the Authority Control users breakfast as Clyde’s.  I mentioned a couple announcements (i.e., online stats to track your processing throughout the year, and our ability to process & return records in MARCXML now).  But the real star of the show was with Karen’s updates regarding RDA.  As Backstage is part of the ongoing testing effort with RDA, it was great to have Karen with us to field your questions.  She has written up a detailed response and we will post that very soon.

Much of the remainder of my time was occupied with chances to meet up with existing and potential clients.  It’s a great feeling to work with people all throughout the years and finally meet each one in person.

We think we have a fair number of lurkers on this blog and would encourage you to leave comments whenever you like.  We are always on the lookout to make the service easier and more efficient for you and your workflow, so please feel free to let us know how we can make things better.  Tell us what you want and we will see what we can do to make it happen.

Our RDA librarian, Karen, sent me this helpful blog entry with a lot of detail about RDA, without further ado, I present it to you.

Now that RDA has been published, there are lots of questions about when we will start seeing RDA records.  LC and OCLC have both asked that no RDA records, or records using RDA elements be sent out until October 1st, 2010 when the National RDA Test participants will start producing records officially.  Here are some links to policy statements and other information that may help you figure out what to expect.

http://www.loc.gov/catdir/pcc/RDA-Testing-PCC.pdf – This is the policy statement for PCC (NACO, BIBCO, CONSER) participants.

http://www.oclc.org/us/en/rda/policy.htm – this is OCLC’s policy statement about the RDA test.  It gives their protocols.  If you use OCLC, I highly recommend that you take a look at this.

http://www.oclc.org/us/en/rda/about.htm – OCLC’s main page about RDA where you can find the above link as well as a host of other information

http://www.loc.gov/catdir/cpso/RDAtest/rda_lcps.html – here are the LC Policy Statements (LCPSs) for the RDA rules.  These are the equivalent of the LCRI’s for AACR2.  The LCPSs are for the testers to use.  They will be reviewed after the evaluation of the test.

http://www.rda-jsc.org/workingnew.html – for complete examples of RDA bibliographic and authority records.  This is where the JSC (the group responsible for RDA) puts their working documents.  Be sure to make note of the note at the top.

http://www.loc.gov/catdir/cpso/RDAtest/rdaexamples.html – LC has also posted some examples that demonstrate some of the differences between RDA and AACR 2

LChelp4RDA@loc.gov - where anyone (whether participating or not) can ask questions about the national RDA test.

I hope these links will be helpful. Please feel free to comment or ask questions here (best), or email our listserv, and I’ll do my best to find an answer.   bslwac@mailman.xmission.com

Although the major international library communities who are planning on implementing RDA have agreed to the Oct. 1st starting date, there is certainly no guarantee that RDA records won’t start showing up.  But they shouldn’t cause problems as long as your system can recognize all the fields.  They should be able to exist alongside AACR2 records.  (We’re only talking MARC here.)  As an official test partner, Backstage will have our policies and processes to deal with RDA records (bibliographic and authority) in place by Oct. 1st.

So, here again (see RDA Changes in MARC Records) is the list of all the changes made to the MARC Bibliographic and Authority formats from 2008 through March 2010.  It includes changes approved at ALA Midwinter 2010.  Unfortunately, it does not include the changes approved at the ALA Annual meetings.  I haven’t been able to find those yet, but I’ll post them as soon as I do.

The changes are listed by tag, with the Bibliographic format changes first, then the Authority format changes following.  I have included the link to the tag description in the MARC21 Standards.  Also, after each change I’ve given the link to the MARBI proposal for that change in case you would like to see the reasoning behind it.  These will have the word “marbi” in the link and directly follow the actual change

Fields with changes made to directly or indirectly accommodate RDA are marked with an *.  For more information on how RDA is affecting MARC21 see the document “RDA in MARC” found on the MARC21 Standards home page:  http://www.loc.gov/marc/RDAinMARC29.html

Bibliographic format changes by field as of Mar. 2010

*Leader/18 – Descriptive cataloging form   http://www.loc.gov/marc/bibliographic/bdleader.html

Note: will be coded i with RDA

http://www.loc.gov/marc/RDAinMARC29.html

*007/01 – Electronic Resource (007/00=c)  http://www.loc.gov/marc/bibliographic/bd007g.html

New codes defined [2009]

d – disc, type unspecified

e – disc cartridge, type unspecified

k – computer card

http://www.loc.gov/marc/marbi/2009/2009-01-2.html

*007/01 – Projected Graphic (007/00=g)  http://www.loc.gov/marc/bibliographic/bd007g.html

Redefined code: [2009]

f – other or unspecified type of filmstrip (changed from Other type of filmstrip)

http://www.loc.gov/marc/marbi/2009/2009-01-2.html

*007/01 – Microform (007/00=h)  http://www.loc.gov/marc/bibliographic/bd007h.html

New codes defined: [2009]

j – microfilm roll

http://www.loc.gov/marc/marbi/2009/2009-06-3.html

h – microfilm slip

http://www.loc.gov/marc/marbi/2009/2009-01-2.html

*007/01 – Nonprojected Graphic (007/00=k)  http://www.loc.gov/marc/bibliographic/bd007k.html

New codes defined: [2009]

a – activity card

k – poster

p – postcard

q – icon

r – radiograph

s – study print

v – photograph, type unspecified

http://www.loc.gov/marc/marbi/2009/2009-01-2.html

*007/01 – Motion Picture (007/00=m)  http://www.loc.gov/marc/bibliographic/bd007m.html

New code defined: [2009]

o – film roll

http://www.loc.gov/marc/marbi/2009/2009-06-3.html

*007/04 – Map (007/00=a)  http://www.loc.gov/marc/bibliographic/bd007a.html

*007/04 – Globe (007/00=d)  http://www.loc.gov/marc/bibliographic/bd007d.html

*007/04 – Nonprojected Graphic (007/00=k)  http://www.loc.gov/marc/bibliographic/bd007k.html

New codes defined: [2009]

i – plastic

l – vinyl

n – vellum

v – leather

w – parchment

http://www.loc.gov/marc/marbi/2009/2009-01-2.html

007/04 – Videorecording (007/00=v)  http://www.loc.gov/marc/bibliographic/bd007v.html

New code defined: [2008]

s – Blu-ray disc

http://www.loc.gov/marc/marbi/2008/2008-09.html

*007/05 – Nonprojected Graphic (007/00=k)  http://www.loc.gov/marc/bibliographic/bd007k.html

New codes defined: [2009]

i – Plastic

l – Vinyl

n – Vellum

v – Leather

w – Parchment

http://www.loc.gov/marc/marbi/2009/2009-01-2.html

008/18-19 & 006/01-02 – Music – Form of Composition (also valid in field 047 – Form of Musical Composition Code)  http://www.loc.gov/marc/bibliographic/bd008m.html

New codes defined: [2009]

za – Zarzuelas

fl – Flamenco

vi – Villancicos

tl – teatro lirico

http://www.loc.gov/marc/marbi/2009/2009-09.html

*008/20 & 006/03 – Music – Format of Music http://www.loc.gov/marc/bibliographic/bd008m.html

New codes defined: [2009]

h – chorus score

i – condensed score

j – performer-conductor part

http://www.loc.gov/marc/marbi/2009/2009-01-2.html

008/23 & 006/06 – Books – Form of item  http://www.loc.gov/marc/bibliographic/bd008b.html

New codes defined: [2010]

o – Online

q – Direct electronic

http://www.loc.gov/marc/marbi/2010/2010-01.html

008/22 & 006/05 – Continuing Resources – Form of original item http://www.loc.gov/marc/bibliographic/bd008s.html

New codes defined: [2010]

o – Online

q – Direct electronic

http://www.loc.gov/marc/marbi/2010/2010-01.html

008/23 & 006/06 – Continuing Resources – Form of item  http://www.loc.gov/marc/bibliographic/bd008s.html

New codes defined: [2010]

o – Online

q – Direct electronic

http://www.loc.gov/marc/marbi/2010/2010-01.html

008/23 & 006/06 – Computer File – Form of item http://www.loc.gov/marc/bibliographic/bd008c.html

New codes defined: [2010]

o – Online

q – Direct electronic

http://www.loc.gov/marc/marbi/2010/2010-01.html

008/22-23 & 006/05-06 – Maps format – Projection  http://www.loc.gov/marc/bibliographic/bd008p.html

New codes defined: [2009]

bk – Krovak

bl – Cassini-Soldner

http://www.loc.gov/marc/marbi/2009/2009-04.html

008/23 & 006/06 – Music – Form of item  http://www.loc.gov/marc/bibliographic/bd008m.html

New codes defined: [2010]

o – Online

q – Direct electronic

http://www.loc.gov/marc/marbi/2010/2010-01.html

00823 & 006/06 – Mixed Materials – Form of item  http://www.loc.gov/marc/bibliographic/bd008x.html

New codes defined: [2010]

o – Online

q – Direct electronic

http://www.loc.gov/marc/marbi/2010/2010-01.html

008/24-27 & 006/07-10 – Books – Nature of content  http://www.loc.gov/marc/bibliographic/bd008b.html

New codes defined: [2008]

y – Yearbooks.  -  made obsolete in 1988, but is now being redefined

2 – Offprints

5 – Calendars

6 – Comics/graphic novels  – this replaces 008/33 and 006/16 code c (comic strip)

http://www.loc.gov/marc/marbi/2008/2008-04.html

008/24 & 006/07 – Continuing Resources – Nature of Entire Work  http://www.loc.gov/marc/bibliographic/bd008s.html

New codes defined: [2008]

y – Yearbooks – this code was made obsolete in 1988, but is now being redefined

5 – Calendars

6 – Comics/graphic

http://www.loc.gov/marc/marbi/2008/2008-04.html

008/25-27 & 006/08-10 – Continuing Resources – Nature of contents  http://www.loc.gov/marc/bibliographic/bd008s.html

New codes defined: [2008]

y – Yearbooks

5 – Calendars

6 – Comics/graphic novels

http://www.loc.gov/marc/marbi/2008/2008-04.html

008/29 & 006/12 – Map – Form of item  http://www.loc.gov/marc/bibliographic/bd008p.html

New codes defined: [2010]

o – Online

q – Direct electronic

http://www.loc.gov/marc/marbi/2010/2010-01.html

008/29 & 006/12 – Visual Materials – Form of item http://www.loc.gov/marc/bibliographic/bd008v.html

New codes defined: [2010]

o – Online

q – Direct electronic

http://www.loc.gov/marc/marbi/2010/2010-01.html

008/33 & 006/16 – Books format – Literary Form   http://www.loc.gov/marc/bibliographic/bd008b.html

Obsolete code: [2008]

c – Comic strips – made obsolete (replaced by a code 6 in 008/24-27 or 006/7-10 for Books format.)

http://www.loc.gov/marc/marbi/2008/2008-04.html .

017 – Copyright or Legal Deposit Number   http://www.loc.gov/marc/bibliographic/bd017.html

New subfield: [2008]

$z – Canceled/invalid copyright or legal deposit number (R)  [2008]

http://www.loc.gov/marc/marbi/2008/2008-08.html

*033 – Date/Time and Place of an Event   http://www.loc.gov/marc/bibliographic/bd033.html

New subfields defined: [2010]

$p – Place of event

$0 – Record control number

$2 – Source of term

http://www.loc.gov/marc/marbi/2010/2010-03.html

034 – Coded Cartographic Mathematical Data http://www.loc.gov/marc/bibliographic/bd034.html

New subfield: [2010]

$3 – Materials specified

http://www.loc.gov/marc/marbi/2010/2010-05.html

*040 – Cataloging Source http://www.loc.gov/marc/bibliographic/bd040.html

Subfield made repeatable [2010]

$e – Description conventions

code “rda” added to the MARC code list for Descriptive Conventions to indicate the use of the RDA rules for description. Leader/18 will be coded i with RDA.

041 – Language Code   http://www.loc.gov/marc/bibliographic/bd041.html

New first indicator [2008]

# – No information provided – Formerly undefined

http://www.loc.gov/marc/marbi/2008/2008-03.html

080 – Universal Decimal Classification Number http://www.loc.gov/marc/bibliographic/bd080.html

Redefined Indicator 1 – Type of edition – Prior to 2009 undefined
# – No information provided
0 – Full
1 – Abridged

http://www.loc.gov/marc/marbi/2009/2009-03.html

082 – Dewey Decimal Classification Number   http://www.loc.gov/marc/bibliographic/bd082.html

New subfields defined:  [2008]

$m – Standard or optional designation (NR)  code values:

a  – Standard

b – Optional

$q – Assigning agency (NR)

http://www.loc.gov/marc/marbi/2008/2008-01.html

083 – Additional Dewey Decimal Classification Number  http://www.loc.gov/marc/bibliographic/bd083.html

New field: [2008]

http://www.loc.gov/marc/marbi/2008/2008-01.html

http://www.loc.gov/marc/marbi/2008/2008-01.html#proposal01-5

085 – Synthesized Classification Number Components   http://www.loc.gov/marc/bibliographic/bd085.html

New field: [2008]

http://www.loc.gov/marc/marbi/2008/2008-01.html

http://www.loc.gov/marc/marbi/2008/2008-01.html#proposal01-6

257 – Country of Producing Entity   http://www.loc.gov/marc/bibliographic/bd257.html

Removed ‘for Archival Films’ from title.  Made tag repeatable.

Subfield redefined: [2009]

$a – Country of producing entity – subfield renamed & made repeatable

New subfield defined: [2009]

$2 –  Source

http://www.loc.gov/marc/marbi/2009/2009-08.html

*336 – Content Type   http://www.loc.gov/marc/bibliographic/bd336.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-2.html

*337 – Media Type   http://www.loc.gov/marc/bibliographic/bd337.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-2.html

*338 – Carrier Type   http://www.loc.gov/marc/bibliographic/bd338.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-2.html

New code under $b

ur – object

http://www.loc.gov/marc/marbi/2009/2009-06-3.html

*380 – Form of Work  http://www.loc.gov/marc/bibliographic/bd380.html

New field: [2010]

http://www.loc.gov/marc/marbi/2010/2010-04.html

*381 – Other Distinguishing Characteristics of Work or Expression   http://www.loc.gov/marc/bibliographic/bd381.html

New field: [2010]

http://www.loc.gov/marc/marbi/2010/2010-04.html

*382 – Medium of Performance   http://www.loc.gov/marc/bibliographic/bd382.html

New field: [2010]

http://www.loc.gov/marc/marbi/2010/2010-04.html

*383 – Numeric Designation of a Musical Work  http://www.loc.gov/marc/bibliographic/bd383.html

New field: [2010]

http://www.loc.gov/marc/marbi/2010/2010-04.html

*384 – Key    http://www.loc.gov/marc/bibliographic/bd384.html

New field: [2010]

http://www.loc.gov/marc/marbi/2010/2010-04.html

440 – Series Statement/Added Entry – Title

Field made obsolete  http://www.loc.gov/marc/bibliographic/bd440.htm – this link contains instructions for conversion to appropriate 490/830 fields.

http://www.loc.gov/marc/marbi/2008/2008-07.html

490 – Series Statement   http://www.loc.gov/marc/bibliographic/bd490.html

1st indicator redefined – Series traced, formerly Series traced differently

http://www.loc.gov/marc/marbi/2008/2008-07.html

Subfield redefined:

$x – made repeatable

http://www.loc.gov/marc/marbi/2009/2009-06-2.html

New subfield defined:

$3 – Materials specified

http://www.loc.gov/marc/marbi/2008/2008-06.html

502 – Dissertation Note   http://www.loc.gov/marc/bibliographic/bd502.html

New subfields defined: [2008]

$b – Degree type

$c – Name of granting institution

$c – Year degree granted

$g – Miscellaneous information

$o – Dissertation identifier

http://www.loc.gov/marc/marbi/2008/2008-05-4.html

510 – Citation/References Note   http://www.loc.gov/marc/bibliographic/bd510.html

New subfield defined:

$u – Uniform Resource Identifier (R)

http://www.loc.gov/marc/marbi/2009/2009-05.html

*518 – Date/Time and Place of an Event Note http://www.loc.gov/marc/bibliographic/bd518.html

New subfields defined: [2010]

$d – Date of event

$o – Other event information

$p – Place of event

$0 – Record control number

$2 – Source of term

http://www.loc.gov/marc/marbi/2010/2010-03.html

534 – Original Version Note   http://www.loc.gov/marc/bibliographic/bd534.html

New subfields:

$o – Other resource identifier (R) [2008]

http://www.loc.gov/marc/marbi/2008/2008-10.html

$3 – Materials specified [2009]

http://www.loc.gov/marc/marbi/2009/2009-10.html

542 – Information Relating to Copyright Status   http://www.loc.gov/marc/bibliographic/bd542.html

New field: [2008]

http://www.loc.gov/marc/marbi/2008/2008-02.html

588 – Source of Description Note   http://www.loc.gov/marc/bibliographic/bd588.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-07.html

*700, 710, 711, 730 –    http://www.loc.gov/marc/bibliographic/bd70x75x.html

New subfield: [2009] (see X00, X10, X11 sections for description)

$i – Relationship information

http://www.loc.gov/marc/marbi/2009/2009-06-1.html

*760, 762, 765, 767, 770, 772, 773, 774, 775, 776, 777, 780, 785, 786, 787 – Linking Entries   http://www.loc.gov/marc/bibliographic/bd76x78x.html

Subfields redefined [2009]

$g – Related parts (R) – renamed from Relationship information text

$i – Relationship information (R) - renamed from Display text and made repeatable

New subfield defined [2009]

$4 – Relationship code (added for RDA Appendix J)

http://www.loc.gov/marc/marbi/2009/2009-06-1.html

*787 – Other Relationship Entry   http://www.loc.gov/marc/bibliographic/bd787.html

Renamed from Nonspecific Relationship Entry [2009]

http://www.loc.gov/marc/marbi/2009/2009-06-1.html

800, 810, 811, 830 – Series Added Entries   http://www.loc.gov/marc/bibliographic/bd80x83x.html

New subfields defined: [2008]

$x – International Standard Serial Number

$3 – Materials specified

http://www.loc.gov/marc/marbi/2008/2008-06.html

$5 – Institution to which field applies [2010]

http://www.loc.gov/marc/marbi/2010/2010-02.html

*New Subfield – $0 – Authority Record Control Number

Added to the following fields

100, 110, 111, 130, 240, 600, 610, 611, 630, 648, 650, 651, 654, 655, 656, 657, 662, 700,                                     710, 711, 730, 752, 754, 800, 810, 811, 830

http://www.loc.gov/marc/marbi/2007/2007-06.html#p1

Authority format changes by field as of Mar. 2010

034 – Coded Cartographic Mathematical Data   http://www.loc.gov/marc/authority/ad034.html

New subfield codes: [2010]

$3 – Materials specified

http://www.loc.gov/marc/marbi/2010/2010-05.html

*040 – Cataloging Source http://www.loc.gov/marc/authority/ad040.html

$e – Description conventions – made repeatable [2010]

code “rda” added to http://www.loc.gov/marc/relators/reladesc.html

see http://www.loc.gov/marc/RDAinMARC29.html

*046 – Special Coded Dates  http://www.loc.gov/marc/authority/ad046.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-1.html

New subfield codes [2010]

$k – Beginning or single date created

$l – Ending date created

http://www.loc.gov/marc/marbi/2010/2010-04.html

080 – Universal Decimal Classification Number http://www.loc.gov/marc/authority/ad080.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-03.html

083 – Dewey Decimal Classification Number   http://www.loc.gov/marc/authority/ad083.html

New subfield: [2008]

$y – Table sequence number for internal subarrangement or add table

http://www.loc.gov/marc/marbi/2008/2008-01.html#proposal01-1

*336 – Content Type  http://www.loc.gov/marc/authority/ad336.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-2.html – proposal

*370 – Associated Place   http://www.loc.gov/marc/authority/ad370.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-1.html

*371 – Address   http://www.loc.gov/marc/authority/ad371.html

New field [2009] (see Marc standards for description)

http://www.loc.gov/marc/marbi/2009/2009-01-1.html

*372 – Field of Activity   http://www.loc.gov/marc/authority/ad370.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-1.html

*373 – Affiliation   http://www.loc.gov/marc/authority/ad373.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-1.html

*374 – Occupation   http://www.loc.gov/marc/authority/ad374.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-1.html

*375 – Gender   http://www.loc.gov/marc/authority/ad375.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-1.html

*376 – Family Information   http://www.loc.gov/marc/authority/ad376.html

New field: ([2009]

http://www.loc.gov/marc/marbi/2009/2009-01-1.html

*377 – Associated Language   http://www.loc.gov/marc/authority/ad377.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-1.html

*380 – Form of Work http://www.loc.gov/marc/authority/ad380.html

New field: [2010]

http://www.loc.gov/marc/marbi/2010/2010-04.html

*381 – Other Distinguishing Characteristics of Work or Expression http://www.loc.gov/marc/authority/ad381.html

New field: [2010]

http://www.loc.gov/marc/marbi/2010/2010-04.html

*382 – Medium of Performance http://www.loc.gov/marc/authority/ad382.html

New field: [2010]

http://www.loc.gov/marc/marbi/2010/2010-04.html

*383 – Numeric Designation of Musical Work http://www.loc.gov/marc/authority/ad383.html

New field: [2010]

http://www.loc.gov/marc/marbi/2010/2010-04.html

*384 – Key http://www.loc.gov/marc/authority/ad384.html

New field: [2010]

http://www.loc.gov/marc/marbi/2010/2010-04.html

*4XX, 5XX –

Subfield redefined (adjusted) [2009]

$i – Relationship information (done to accommodate RDA app. K and J)

http://www.loc.gov/marc/marbi/2009/2009-06-1.html

New subfield

$4 – Relationship code [2009]

http://www.loc.gov/marc/marbi/2009/2009-06-1.html

New subfield codes

$w/0 – r – Relationship designation in $i or $4 [2009]

http://www.loc.gov/marc/marbi/2009/2009-06-1.html

See Tracings and References–General Information -http://www.loc.gov/marc/authority/adtracing.html for instructions on using these subfields.

We have to congratulate Brigham Young University for their excellent commercial, Study Like A Scholar, about the benefits of studying at the library.

Enjoy

Email not displaying correctly?
View it in your browser.
Backstage at Houlihan's
No, it’s not a new approach to
the constitutional separation of powers.

It’s the semiannual
MARS AUTHORITY CONTROL BREAKFAST!

Join us at ALA, Saturday morning for breakfast at

Clyde's of Gallery Place

Clyde’s
707 7th Street NW
Washington, DC

Saturday, June 26, 2010
7:30 to 9:00 a.m.

(Clyde’s is just a few blocks from the convention center.
You can find a map on the RSVP page.)

Get the scoop on the latest features and upcoming enhancements.

Network with other MARS users and touch base with your Backstage crew.

The MARS team will lead a discussion with the user group from 8:00 to 8:30.
Drop in for a few minutes or stay the whole time.

Seating is limited, so please reserve your space online at:

www.bslw.com/RSVP

Can’t make the meeting? Want to invite a friend?
Feel free to pass this invitation along.

BACKSTAGE LIBRARY WORKS

AUTHORITY CONTROL • CATALOGING • DIGITIZATION
PRESERVATION MICROFILM • MICROFILM DUPLICATION & STORAGE
ILS DATA MIGRATION • ON-SITE SERVICES

You are receiving this message because you are a Backstage Library Works client or a Backstage representative has been in contact with you.

Unsubscribe ccluff@bslw.com from this list.

Our mailing address is:

Backstage Library Works

533 East 1860 South

Provo, Utah 84606

Add us to your address book

Copyright (C) 2010 Backstage Library Works All rights reserved.

Forward this email to a friend

Update your profile

Email Marketing Powered by MailChimp

Recently one of our Project Managers, Jeremy, sat down to watch the latest RDA webinar, these are his thoughts and notes from the webinar.

On June 17-18, Troy Linker from ALA Publishing presented a few webinars about how to make the most out of the open-access period for the RDA Toolkit.  This open-access will be from the launch of the RDA Toolkit in mid-June (any day now) until the end of August.   A few people from Backstage attended this webinar and here is a summary of what was presented.

First off, Troy went over a brief overview of what RDA and the RDA toolkit are and who created these.  This was a very brief and basic overview that didn’t really have any new information.

Next, the open-access period was discussed.  They still don’t have an exact date for when this will start, but it should be very soon.  There will be no charge to access the RDA toolkit during this time.  It is possible to pre-register for access right now on the RDA Toolkit website.

The RDA Toolkit has a built-in help system that will serve as a manual.  The website currently has an FAQ section with many questions about RDA.  There will be an RDA Toolkit Support Center for problems with the toolkit.  The website also has tools for presenting on RDA and a calendar of different training sessions.

After discussing these things, Troy did a demonstration of the toolkit.  Within the toolkit, there will be the text of RDA, the RDA element set view, mappings, user-contributed content, relationship diagrams, schemas, and also AACR2.

There are two ways to have access to the RDA Toolkit: either as a solo-user or as an institution.   User profiles can be created for every user, no matter how many users there are for each subscription.  With a user profile, you can save, create, and share user-created content through the toolkit.  For an institutional user, it is necessary to login as the institution and then to login as the user in order to access your personal user-created content.

The RDA toolkit has been designed to work well with all of the major internet browsers.  Once you have logged in to your account, you will be able to access all items in the RDA Toolkit.  You can personalize the toolkit with bookmarks, saved searches, workflows, and mappings through the “My Profile” link.  There is a link to the support center to report anything that is causing difficulties.

On the left-side of the page, there are tabs for RDA, Tools, and Resources.  The RDA tab has the full text of RDA that can be browsed through with an extensive hierarchy.  The Tools tab has the RDA element set view, mappings, workflows, mappings, and entity relationship diagrams.  Currently, the only mappings that are available are between RDA and MARC bibliographic and authority records.  They plan to add more mappings in the future and it is also possible to add your own mapping and share it with others.  It is also possible to create and share your own workflows.  The Resources tab will have content such as AACR2.

There are two options for searching: an RDA quick search and an advanced search.  With the quick search, you are only able to search the content of RDA and not the other resources provided in the toolkit.  With an advanced search, you can limit your search to any of the resources provided.  After you have completed a search, you can save it for future reference.

Troy briefly discussed subscription and pricing options, including an option to purchase a printed version of RDA.   The main thing that was emphasized with this is that they are able to work with libraries in specials situations, but they have to treat everyone equally.  Some special situations that may get special treatment would be pricing for consortiums, extra users for training purposes, etc.

There are a few future enhancements that they are looking at, such as linking from AACR2 to RDA, linking to other cataloging tools, improving user preferences, and integrating translations into the toolkit.

In the demo, Troy made everything look very user-friendly and easy to access.  Once the open-access period has begun, it will be interesting to see how easy it is to use when there are thousands to people constantly accessing it.

These webinars were recorded and will be available on http://www.rdatoolkit.org.  The questions that participant’s had will also be posted to the FAQ section of this website.

Powered by WordPress Web Design by SRS Solutions © 2010 MARS Authority Control Design by SRS Solutions