RDA

RDA and Koha

From David Schuster

Joy M. Banks Catalog Librarian came up with these starting points for Koha and RDA

The system needs to be able to uniformly display both the GMDs (Generic Media Descriptors) that are in current AACR2 (Anglo-American Cataloguing Rules 2) records and the new 3xx fields that RDA (Resource Description and Access) would implement to replace GMDs (this is a big one since I don’t know about anyone else, but we have no intention of going back to update all of our AACR2 records to RDA)
The system needs to take into account a new FRBR (Functional Requirements for Bibliographic Records) model that will both serve the needs of patrons who wish to find every manifestation of a particular work and also those who wish to see specific manifestations
The system needs to be able to perform global updating for authorities so that changes made to authority records will be automatically applied to the bibliographic records to which they are attached
Any development with authorities and display also needs to take into account what will soon be a proliferation of $e’s in 1xx and 7xx fields (this one is fuzzier for me… I’m not quite sure if I’ve captured this change). These subfields should only affect the bibliographic records, not the authorized forms of the headings.

She also suggested this: Mac Elrod has developed a kind of cheat sheet (http://slc.bc.ca/cheats/aacr22rda.htm) that highlights some of the major RDA changes. It’s from September, but at least it’s something that we can consider.

From the NZ National Library

MARC changes

In order to accomodate records created using RDA, there have been changes to the MARC format. These changes are summarised in the document RDA in MARC which is available at: http://www.loc.gov/marc/RDAinMARC.html The changes include the following:

Three new fields

MARC field 336 - Content type: a term and/or code indicating type of content e.g. text, sounds, performed music
MARC field 337 - Media type: a term and/or code showing what kind of general device is need to view a resource e.g. computer, projected, unmediated
MARC field 338 - Carrier type: a term and/or code giving the specific carrier of the content supplied in field 337 e.g. online resource, audio disc

These fields collectively replace the '$h' subfield of the MARC 245 (title) field. The 'h' subfield currently contains the "general material designation" and is used mainly for non-print or non-textual resources.

RDA fields on a record
... 336 $a text $b txt $2 rdacontent 337 $a unmediated $b n $2 rdamedia 338 $a volume $b nc $2 rdacarrier ...
An example of RDA fields.

You can create several categories of authorized values based on the following lists:

Keep in mind $a subfields are not codes, therefore you should use the language defined on 040$b.

RDA code

MARC field 040 - Cataloging Source - subfield 'e' "Description conventions" - contains a code 'rda' for records created using the new rules

Relator terms

Relator terms show the role or relationship between added entries and the item being described. They are already valid in MARC as subfield 'e' or '4' of various access fields, however more terms have been added and a new subfield 'i' has been added for linking fields (76X-78X)

Other new fields are described in the document referred to above.

From the Australian National Library

As the Australian implementation of Resource Description and Access (RDA) approaches, Libraries Australia will be implementing a number of changes.

System changes

We will be implementing a number of changes in the Cataloguing service including:

Support for new MARC field 264 which will replace field 260 in RDA records
Replacement of the current Libraries Australia Cataloguing Client templates with new RDA templates
Changes to the Record Import Service (RIS) matching and merging to give preference to RDA records over records created according to Anglo American Cataloging Rules 2nd edition (AACR2) and older standards.

These changes will be implemented towards the end of February or early in March. The Libraries Australia Training system will also be updated at that time. We will advise you of the exact date as soon as possible.

The Libraries Australia Cataloging system already supports the use of 33X fields via RIS and the Cataloguing Client. A list of all the MARC21 changes that have already been made to support RDA can be found at: http://www.nla.gov.au/librariesaustralia/files/2012/07/MARC21_RDA_code_changes_v5_0_12.pdf It is also possible to search for RDA bibliographic and authority records via the Cataloguing Client using the command f sou rda. The Libraries Australia Search service will be updated in February to support the searching and display of RDA data elements. The Document Delivery service will be updated in March. We will advise you when these changes are to be implemented.

We will be adding RDA fields 336, 337 and 338 to the LA Search WebCat input form in March. In the meantime if you wish to add these fields through WebCat there is a workaround. After saving your record, and saving again at the second save prompt, you are taken to a window which displays the MARC record that you have just created. At this point it is possible to add the 33X tags in MARC format by editing the record directly.

Trove will be updated in March to support RDA data elements in bibliographic and authority records.

Cataloguing Policy changes

As previously advised, with the introduction of RDA, Libraries Australia is replacing the current Minimum Record Standard (http://www.nla.gov.au/librariesaustralia/services/cataloguing/) with a new standard called Required Data Elements (http://www.nla.gov.au/librariesaustralia/services/cataloguing/required_data_elements_provisional/). In addition to the RDA changes the new standard includes a small number of additional codes and fields that will make matching and merging more accurate and result in fewer duplicate records. Most records sent to the Libraries Australia already meet the new standard, except for the new RDA data elements, and we hope that it will not be onerous for contributing libraries.

From March onwards RDA will be the standard for new records added to Libraries Australia. However, we realize that in the coming year libraries will be at different stages of their RDA implementations therefore AACR2 records will continue to be accepted for at least the next year.

From March onwards when Catalogers use an existing non-RDA record for copy cataloging they may choose to upgrade it to RDA; however, this is not compulsory. If upgrading a record, the entire record must be examined and upgraded before changing the coding to RDA. Catalogers may choose to add selected RDA data elements to existing non-RDA records. However, the coding of the record should not be changed to RDA unless the entire record has been examined and upgraded.

The standard documentation on the Libraries Australia website will be updated during February and March.

Data changes

Libraries Australia is already in the process of changing selected Authority records to reflect RDA practice. These include headings for the Bible and Koran, and spelling out abbreviations for musical terms and “Dept.”. These changes will appear in the LA Cataloging service as soon as they made but some won’t appear in LA Search until it is replaced later in the year.

We will also investigate opportunities for global changes to selected bibliographic records so that they more closely reflect RDA practice. These may include addition of 33X fields (where there is no ambiguity) and the spelling out of abbreviations in some fields.

If you have any questions about the Libraries Australia RDA implementation please contact the Help Desk: Make a new Libraries Australia enquiry (http://librariesaustraliaref.nla.gov.au/reft100.aspx?key=LA).

More information about the Australian implementation of RDA, including the availability of RDA training courses, may be found on the ACOC RDA web site (http://www.nla.gov.au/acoc/resource-description-and-access-rda-in-australia).

RDA

Contents