Where is it in RDA -- Bibliographic Records

PRE-RDA CONTEXT	RDA TERMINOLOGY	RDA LOCATION
Description	Description
Descriptive elements transcribed from the resource	Identifying manifestations and items	ch. 1-2
Physical description	Describing carriers	ch. 3
Notes on the content	Describing content	ch. 7
Acquisitions and access information	Providing acquisition and access information	ch. 4
Notes on the work and expression	Describing content   Recording primary relationships between works,   expressions, manifestations, and items	ch. 7 ch. 17
Notes citing other editions and works	Recording relationships between works, expressions,   manifestations, and items	ch. 24-28
Main entry	Authorized access point
Choosing the main entry	Recording the primary relationship between the   manifestation and the work embodied in the manifestation	17.8; ch. 6, 19
Constructing the main entry heading	Constructing the authorized access point	ch. 5-6, 8-11, 16
Added entries	Access points
Choosing added entries for persons, families, and   corporate bodies	Recording relationships to persons, families, and   corporate bodies associated with a resource	ch. 18-22
Constructing added entry headings for persons, families,   corporate bodies, and places as governments	Constructing the authorized access point representing a   person, family, or corporate body	ch. 8-11, 16
Choosing added entries for the work, expression, or   manifestation	Recording primary relationships between work,   expression, manifestation, and item	ch. 17
Choosing added entries for related works, expressions, or   manifestations (including analytic and series added   entries)	Recording relationships between works, expressions, and   manifestations	ch. 24-26
Constructing added entry headings for related works,   expressions, and manifestations	Constructing the authorized access point representing   related works, expressions, and manifestations	ch. 5-6
Subject headings	Subject access points
Constructing subject headings for persons, families,   corporate bodies, places as governments, works,    expressions, and manifestations	Constructing the authorized access point representing   persons, families, corporate bodies, places as governments,   works, expressions, and manifestations	ch. 5-6, 8-11, 16

Where is it in RDA -- Authority Records

PRE-RDA CONTEXT	RDA TERMINOLOGY	RDA LOCATION
Heading	Authorized access point
Constructing headings for persons, families, and   corporate bodies	Constructing the authorized access point representing a   person, family, or corporate body	ch. 8-11
Constructing headings for works, expressions, and   manifestations	Constructing the authorized access point representing a   work, expression, or manifestation	ch. 5-6
Constructing headings for places as governments	Constructing the preferred access point for places as   governments	ch. 11, 16
See references	Variant access points
For persons, families, and corporate bodies	Constructing variant access points representing persons,   families, and corporate bodies	ch. 8-11
For works, expressions, and manifestations	Constructing variant access points representing works,     expressions, and manifestations; recording relationships   between resources and persons, families, & corporate bodies	ch. 5-6 ch. 18-22
For places as governments	Constructing variant access representing places as   governments	ch. 11, 16
See also references	Authorized access points for related entities
For related persons, families, and corporate bodies	Recording relationships between persons, families, and   corporate bodies	ch. 29-32
For works, expressions, and manifestations	Recording relationships between works, expressions, and   manifestations	ch. 24-26
For related places as governments	Recording relationships between places as governments	ch. 11
Explanatory references	Explanations of relationships
For related persons (separate bibliographic identities)	Explanation of relationship for person	appendix E
Notes	Attributes of entities
Biographical or historical data	Recording attributes of persons, families, corporate bodies,   and places as governments (date associated with the person,   place of birth, corporate history, etc.)	ch. 8-11
Information about the work, expression, or  manifestation	Recording attributes of works, expressions, and   manifestations (date of  work, language of expression,  etc.)	ch. 5-6
Sources consulted	Sources consulted	ch. 5, 8, 24, 29
Cataloguer’s notes	Cataloguer’s notes	ch. 5, 8, 24, 29

MARC21 changes to support RDA

Although RDA is intended to be compatible with a number of encoding standards, including MARC21, MODS and Dublin Core, a majority of library systems utilise the MARC21 format. This document outlines the changes that have been made to MARC21 in order to accommodate resource descriptions created using RDA. It also outlines new RDA elements that can be accommodated by MARC21 without requiring any changes.

[1] RDA does not utilise field 245 $h. However, this subfield is still valid.

Content Types, Media Types, and Carrier Types
RDA replaces the general material designation (GMD) and the class of materials concept with three new data elements, Content Type, Media Type, and Carrier Type to assist users in fulfilling FRBR's “select” user task.[1]

Content Types (RDA Section 2, Chapter 6.9)

• Content Type relates to the form of communication through which the work is expressed and the human sense through which it is intended to be perceived. It is a core element in RDA.
• The general content type is already recorded with a one-character code in the LDR/06 in MARC Bibliographic records
• A new field 336 is provided in MARC Bibliographic records and in MARC Authority records to record more specific content type/s in textual form ($a) and/or in three-character coded form ($b). In bibliographic records, it is used in conjunction with LDR/06.
• A list of the terms and three-character codes for field 336 $a and $b, along with the corresponding Leader/06 codes, is available at: Term and Code List for RDA Content Types. The source code for this list to be recorded in field 336 $2 (Source) is rdacontent.

336

##

$a tactile notated music $b tcm $2 rdacontent

Media Types (RDA Section 1, Chapter 3.2)

• Media Type relates to the general type of intermediation device required to view, play, run, etc., the content of the resource. 
• Media Type may already be recorded in field 007/00 in MARC Bibliographic records.
• A new field 337 is provided in MARC Bibliographic records and in MARC Holdings records to record more specific media type/s in textual form ($a) and/or in one-character coded form ($b). In bibliographic records, it may be used as an alternative to or in addition to 007/00.
• A list of the terms and one-character codes for field 337 $a and $b, along with the corresponding 007/00 codes, is available at: Term and Code List for RDA Media Types. The source code for this list to be recorded in field 337 $2 (Source) is rdamedia.

337 ## $a audio $b s $2 rdamedia

Carrier Types (RDA Section 1, Chapter 3.3)

• Carrier Type relates to the format of the storage medium and housing of the carrier of the resource. It is a core element in RDA. Carrier Type is not the same as Extent, which is recorded in field 300.
• Carrier Type may already be recorded in field 007/01 in MARC Bibliographic records.
• Some new codes have been defined for the 007/01 Electronic resources, 007/01 Projected graphic and 007/01 Microform to facilitate the encoding of all RDA carrier types.
• A new field 338 is provided in MARC Bibliographic and in MARC Holdings to record more specific carrier type/s in textual form ($a) and/or in two-character coded form ($b). In bibliographic records, it may be used as an alternative to or in addition to 007/01.
• A list of the terms and two-character codes for field 338 $a and $b, along with the corresponding 007/01 and other codes, is available at: Term and Code List for RDA Carrier Types. The source code for this list to be recorded in field 338 $2 (Source) is rdacarrier.

338 ## $a online resource $b cr $2 rdacarrier

 
Attributes of Entities (Names and Resources)
Attributes of names and titles have typically been recorded in name headings (e.g., date of birth) or in uniform title headings (e.g., key for music), or they may have been included in the Authority record for the name or title.

Attributes of Persons, Families and Corporate Bodies (RDA Section 3)
New fields have been established in MARC Authority to allow some attributes of persons, families and corporate bodies to be recorded separately from the heading or as part of the heading (or both).

• Dates associated with the person, family, or corporate body described in the MARC Authority record may be recorded in field 046 - Special Coded Dates.
• The town, city, province, state, and/or country associated with the person, family, corporate body, work or expression described in the MARC Authority record may be recorded in field 370 - Associated Place.
• The address where the person or corporate body described in the MARC Authority record can be found or contacted may be recorded in field 371 - Address.
• The field of endeavor or area of expertise in which the person or corporate body described in the MARC Authority record is or was engaged may be recorded in field 372 - Field of Activity.
• Information about a group with which the person described in the MARC Authority record is or has been affiliated may be recorded in field 373 - Affiliation. Dates of affiliation may also be recorded.
• Information about the profession or occupation in which the person described in the MARC Authority record works or has worked may be recorded in field 374 - Occupation. Dates of work in the profession or occupation may also be recorded.
• Information about the gender of the person described in the MARC Authority record may be recorded in field 375 - Gender. Dates of identification with a specified gender may also be recorded.
• Information about the family described in the MARC Authority record may be recorded in field 376 - Family Information. This may include type of family, the name of a prominent member of the family, and hereditary title.
• The MARC language code identifying the language that the person or corporate body described in the MARC Authority record uses for publication, communication, etc, may be recorded in field 377 - Associated Language.

Attributes of Works and Expressions (RDA Section 2, Chapter 6)
New fields have been established in MARC Bibliographic and MARC Authority to allow some attributes of works and expressions to be recorded separately from the heading or as part of the heading (or both).

• Dates associated with the work or expression described in the MARC Authority record may be recorded in field 046 - Special Coded Dates.
• The form of communication through which the work described is expressed and the human sense through which it is intended to be perceived may be recorded in field 336 in MARC Bibliographic records and in MARC Authority records
• The class or genre to which a work belongs may be recorded in field 380 in MARC Bibliographic records and in MARC Authority records.
• Any characteristic that serves to characterize a work or expression but is not accommodated in a special field may be recorded in field 381 in MARC Bibliographic records and in MARC Authority records.
• The instrumental, vocal, and/or other medium of performance for which a musical work was originally conceived or for which a musical expression is written or performed may be recorded in field 382 in MARC Bibliographic records and in MARC Authority records.
• A serial number, opus number, or thematic index number assigned to a musical work by the composer, publisher, or a musicologist may be recorded in field 383 in MARC Bibliographic records and in MARC Authority records.
• The set of pitch relationships that establishes a single pitch class as a tonal centre for a musical work or expression may be recorded in field 384 in MARC Bibliographic records and in MARC Authority records.

Relationships between Entities

Relationships to Persons, Families, and Corporate Bodies associated with a resource (RDA Section 6)

• A relationship designator may be included when recording relationships between a resource and persons, families and corporate bodies associated with that resource, in order to make the nature of the relationship clear.
• These types of relationships may already be recorded using relator terms ($e) or codes ($4) in 1XX, 6XX, 7XX, and 8XX in MARC Bibliographic and 1XX, 4XX, and 5XX in MARC Authority.
• A list of possible relationships between a work, expression, manifestation or item and persons, families and corporate bodies is given in RDA Appendix I, e.g. author, editor, printer, former owner.
• The MARC Relator Code list will be augmented with RDA relationships that are not already in the list when the RDA list is final and available.

Relationships between Works, Expressions, Manifestations and Items (RDA Section 8)
The relationship between a work, expression, manifestation, or item and a related work, expression, manifestation, or item may be recorded, if considered important.

• RDA identifies several methods for recording these relationships; identifiers, notes, structured descriptions, and structured access points.
• identifiers may be recorded in many $o, $u, $x, $w, and $0 subfields, and field 856
• notes may be recorded in 5XX MARC Bibliographic and 6XX MARC Authority
• structured descriptions may be recorded in 76X-78X MARC Bibliographic
• structured access points may be recorded in 7XX MARC Bibliographic and 4XX and 5XX MARC Authority
• The Relationship information $i subfield has been added to MARC Bibliographic 7XX to specify these types of relationships, and redefined in Bibliographic 76X-78X and MARC Authority 4XX and 5XX.
• A list of over 400 relationships that may exist between works, expressions, manifestations and items is given in RDA Appendix J, e.g. preceded by, review of, bound with.

Relationships between Persons, Families, and Corporate Bodies (RDA Section 9)
The relationship between a person, family, or corporate body and a related person, family, or corporate body may be recorded, if considered important.

• The Relationship information $i subfield has been redefined in MARC Authority 4XX and 5XX to specify these types of relationships.
• A list of possible relationships between persons, families and corporate bodies is given in RDA Appendix K, e.g. alternate identity, predecessor.
• Other changes to MARC Bibliographic

Series statement (RDA Section 1, Chapter 2.12)
The ISSN $x subfield in field 490 - Series Statement has been made repeatable to accommodate the ISSN for both the series and the subseries when they both appear in a resource.

Describing carriers and Describing content (RDA Section 1, Chapter 3 and Chapter 7)
Some new codes have been defined for the 007/01 Non-projected graphic, 007/04 Map, 007/04 Globe, 007/04 Non-projected graphic, and 008/20 Music to facilitate the encoding of other information about content and carriers, such as format, extent, and base material.

Dissertation or thesis information (RDA Section 2, Chapter 7.9)
Additional subfields have been defined in field 502 - Dissertation Note to provide greater granularity and to support parsing of specific data elements relating to a dissertation.


Place and date of capture (RDA Section 2, Chapter 7.11)
Additional subfields have been added in field 033 - Date/Time and Place of an Event and field 518 - Date/Time and Place of an Event Note to provide greater granularity and to support parsing of specific data elements relating to place and date of capture.

Encoding URIs for controlled values and headings
Experimentation with a technique for including URIs for controlled values and headings will be undertaken within the existing MARC format. For further information see MARC Discussion Paper No. 2010-DP02.

Indicating the use of RDA rules and ISBD punctuation
The Description conventions $e subfield in Field 040 has been made repeatable and 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" or "c" to indicate the presence or absence of ISBD punctuation at subfield boundaries.

RDA in MARC

MARC 21 Updates 9, 10, and 11 include all changes to MARC for use with RDA approved through 2010. The list below has been updated to include changes under consideration in June 2011. Those not-yet-approved changes are indicated below as "proposed" or "under discussion", and are linked to their relevant MARBI Proposals and Discussion Papers.

Content, Media and Carrier Types and Characteristics

RDA Content Types
MARC already indicates content type in LDR/06.
RDA contains a list of English language content types for which a new field 336 was provided in MARC Bibliographic and in MARC Authority.
Field 336 may contain the RDA term ($a) or a code ($b); codes were established in MARC Update 10.
For a table that relates the MARC LDR/06 to the corresponding RDA content terms and MARC codes for RDA content terms see: Term and Code List for RDA Content Types.

RDA Media Types
MARC already indicates media type in field 007/00.
RDA contains a list of English language media types for which a new field 337 is provided in MARC Bibliographic and in MARC Holdings.
Field 337 may contain the RDA term ($a) or a code ($b); codes were established in MARC Update 10.
For a table that relates the MARC 007/00 to the corresponding RDA media terms and MARC codes for RDA media terms see: Term and Code List for RDA Media Types.

RDA Carrier Types
MARC already indicates carrier type in field 007/01.
RDA contains a list of English language carrier types for which a new field 338 is provided in MARC Bibliographic and in MARC Holdings.
Field 338 may contain the RDA term ($a) or a code ($b); codes were established in MARC Update 10.
For a table that relates the MARC 007/01 to the corresponding RDA carrier terms and MARC codes for RDA carrier terms see: Term and Code List for RDA Carrier Types

RDA Carrier Characterisitcs - proposed
MARC provides for recording carrier characteristics in Bibliographic fields 300, 340, and 5XX and in Bibliographic and Holdings field 007 (coded form).
RDA contains lists of English language terms that can be used to express carrier characteristics and also allows expression via notes.
RDA carrier characteristic notes – MARC Bibliographic fields 500 (new subfield $i (Display text) proposed)and other 5XX
RDA carrier characteristic terms in MARC Bibliographic format
Field 300 (Physical Description) (subfield $b repeatable, otherwise no change)
Field 340 (Physical Medium) (new subfields proposed)

New Bibliographic format fields proposed
344 – Sound Characteristics (R)
345 – Projection Characteristics of Motion Picture Film (R)
346 – Video Characteristics (R)
347 – Digital File Characteristics (R)

Attributes of Names and Resources
Attributes of names and titles are typically information that has been recorded in name headings (e.g., date of birth) or in uniform title headings (e.g., key for music) -- or they may have been included in a note in an Authority record for the name or title. With RDA they may be recorded separately from the heading or as part of the heading (or both). New fields for these attributes have been established for names and for resources (works and expressions).

New MARC Authority fields for name attributes:
046 - Special Coded Dates (R)
368 – Other Corporate Body Attributes (R) (NEW) (proposed) – use to indicate the jurisdiction types for names of places
370 - Associated Place (R)
371 - Address (R)
372 - Field of Activity (R)
373 - Affiliation (R) - extend the field to contain names of associated institutions for corporate bodies and rename field Associated Institution (proposed)
374 - Occupation (R)
375 - Gender (R)
376 - Family Information (R)
377 - Associated Language (R)
378 - Fuller Form of Name (R) (NEW) (proposed)

New MARC Authority and Bibliographic fields for work and expression attributes:
046 - Special Coded Dates (new subfields only)
336 - Content Type (R)
377 - Associated Language (proposed) - extend to include the language of an expression and add to MARC Bibliographic.
380 - Form of Work (R)
381 - Other Distinguishing Characteristics of Work or Expression (R)
382 - Medium of Performance (R) - additional subfields (under discussion)
383 - Numeric Designation of a Musical Work (R) - sdditional subfields (proposed)
384 - Key (NR)

Relationships
 
Name to resource
RDA Appendix I lists possible relationships between a resource and persons, families and corporate bodies, e.g., author, artist, cartographer.
MARC already records these types of relationships using relator terms ($e) or codes ($4) in 1XX, 6XX, 7XX, and 8XX in MARC Bibliographic and 1XX, 4XX, and 5XX in MARC Authority.
MARC Relator Code list will be augmented with RDA relationships that are not already in the list when the RDA list is final and available.

Resource to resource
RDA Appendix J lists over 400 relationships that may exist between works, expressions, manifestations and items, e.g., dramatized as (work), indexed in (work), sequel, digest of (expression), filmed with (manifestation), reproduction of (item).
RDA identifies several methods for specifying these relationships:
identifiers - e.g., many $o, $u, $x, $w, and $0 subfields, and field 856
notes - 5XX Bibliographic and 6XX Authority
structured descriptions - 76X-78X Bibliographic
structured access points - 7XX Bibliographic and 4XX and 5XX Authority
MARC addition: $i defined for the relationship term in Bibliographic 7XX and 76X-78X and in Authority 4XX and 5XX.

Name to name
RDA Appendix K lists possible relationships between persons, families and corporate bodies, e.g., employee, sponsor, descendent family, employer, predecessor.
MARC subfield $i added to 4XX and 5XX Authority is also used to specify these types of relationships.

Miscellaneous other changes to MARC for RDA
Additional subfield specificity in field 502 (Dissertation Note)
ISSN subfield made repeatable in field 490 (Series Statement)
Additional codes in various 007 and 008 character positions
Additional subfields in 033 (Date/Time and Place of an Event) and 518 (Date/Time and Place of an Event Note)
Field 040 $e made repeatable and 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.
Experimentation with a technique for including URIs for values (no MARC content designation change) (See Discussion Paper 2010-DP02 for general description.)
Additional fields or subfields proposed for RDA publication, production, distribution, and manufacture locations, agencies, and dates
Additional field or subfield proposed for copyright date that appears on the item

Sally McCallum
smcc@loc.gov
06/14/2011

Mengidentifikasi metadata berbasis RDA

(Dimuat di Majalah Visi Pustaka, Vol. 13, No. 1, April 2011 dengan judul "Mengenal Resource Description and Access (RDA) dan aplikasinya dalam dunia perpustakaan")

Dunia perpustakaan memasuki era baru seiring diperkenalkannya RDA menjadi standar baru pengatalogan menggantikan peran AACR2. Proyek kolaborasi ini memperkenalkan konsep entity-relationship model untuk mengakomodasi kebutuhan dunia analog dan digital. Kemunculan RDA tidak lepas dari berbagai kontroversi dan perdebatan dikalangan pustakawan itu sendiri. Secara singkat, tulisan ini menjelaskan latar belakang, konsep, karakteristik, dan bagaimana RDA diimplementasikan.

Sejak pertama kali diluncurkan pada tahun 1978, AACR2 telah mengalami beberapa kali revisi. Konferensi internasional mengenai prinsip-prinsip dan pengembangan AACR2 di Toronto, Kanada tahun 1997 mengidentifikasi adanya permasalahan substansial yang tidak bisa diatasi hanya dengan melakukan berbagai revisi. Fakta tersebut mendorong Joint Steering Committee (JSC) melakukan penataan ulang secara fundamental untuk bisa merespon tantangan dan peluang dunia digital.

AACR2 terdiri bab-bab khusus yang mengatur standar pengatalogan untuk monograf, terbitan berseri, rekaman suara, gambar bergerak, dan lain sebagainya. Perbedaan jenis pustaka kini semakin bias seiring perkembangan teknologi informasi dan multimedia. Banyak terminologi AACR2 masih merefleksikan era katalog kartu, misalnya “heading”, “main entry”, dan “added entry”. Memodifikasi istilah sesuai dengan perkembangan teknologi saat ini dianggap belum cukup untuk menjadikan AACR2 relevan dengan dunia digital.

Pada tahun 2005, Joint Steering Committee for the Revision of AACR meninjau kembali revisi bagian pertama dari AACR3. Setelah mempertimbangkan berbagai alternatif, JSC menuangkan visinya melalui penyusunan standar pengatalogan baru yang berisi panduan dan instruksi untuk deskripsi dan akses materi digital maupun analog. Pemberian nama RDA – Resource Description and Access merefleksikan perubahan tersebut.

RDA, sebuah proyek kolaborasi
RDA dikembangkan oleh Joint Steering Committee (JSC) for Development of RDA yang merupakan representasi dari American Library Association, Australian Committee on Cataloguing, British Library, Canadia Committee on Cataloguing, Chartered Institute of Library and Information Professionals, dan Library of Congress. Sedangkan badan yang mensupervisi proyek pengembangan RDA secara keseluruhan adalah The Committee of Principals (CoP) yang terdiri dari institusi-institusi tersebut di atas plus Library and Archives Canada. Proyek ini juga melibatkan Co-Publishers, yakni American Library Association, Canadian Library Association, dan Chartered Institute of Library and Information Professionals yang bertugas memberikan dukungan untuk masalah finansial dan produksi.

Kemunculan RDA didorong oleh adanya fakta bahwa perpustakaan kini beroperasi dalam dunia digital dan berbasis web yang membuat hubungan antara pembuat metadata dan pengguna di luar perpustakaan menjadi semakin penting. Oleh karena itu, pengembangan RDA dilakukan secara kolaboratif dan melibatkan banyak pihak, antara lain, Dublin Core dan komunitas web semantik untuk membandingkan model konseptual dan standar yang digunakan, Library of Congress Network Development and MARC Standards Office untuk memastikan kompatibilitas RDA dengan MARC21, IFLA Cataloguing Section untuk menjamin harmonisasi RDA dengan standar pengatalogan internasional, dan komunitas penerbitan yang telah memiliki daftar terminologi alat berdasarkan standar ONIX yang digunakan untuk dunia penerbitan maupun perpustakaan.

Mengapa RDA?
RDA dibangun di atas fondasi AACR2 dan menjadi standar baru pendeskripsian dan akses semua jenis konten dan media. RDA yang bertujuan membantu pengguna dalam mencari (find), mengidentifikasi (identify), memilih (select), dan mendapatkan (obtain) informasi yang diinginkan.

Implementasi RDA bertujuan, pertama, sebagai kerangka kerja yang lebih fleksiblel untuk mendeskripsikan semua jenis materi analog dan digital. Kedua, menyajikan data yang mampu beradaptasi dengan kemunculan struktur database yang baru. Dan yang ketiga, menampilkan data yang kompatibel dengan cantuman bibliografi yang telah ada dalam katalog perpustakaan online.

Struktur RDA terdiri dari 10 bagian yang berfokus pada perekaman attributes dari entities dan hubungan antar entities.

Recording attributes

• Section 1 – Recording attributes of manifestion and item
• Section 2 – Recording attributes of work and expression
• Section 3 – Recording Attributes of Person, Family, and Corporate Body
• Section 4 – Recording Attributes of Concept, Object, Event, and Place

Recording Relationships

• Section 5 – Recording Primary Relationships Between a Work, Expression, Manifestation, and Item
• Section 6 – Recording Relationships to Persons, Families, and Corporate Bodies Associated with a Resource
• Section 7 – Recording Subject Relationships
• Section 8 – Recording Relationships Between Works, Expressions, Manifestations and Items
• Section 9 – Recording Relationships Between Persons, Families, and Corporate Bodies
• Section 10 – Recording Relationships Between Concepts, Objects, Events, and Places

RDA disusun berdasarkan prinsip dan standar internasional yang dikembangkan oleh IFLA, yakni the International Cataloguing Principles (ICP). ICP merupakan pembaruan dari ‘Paris Principles’ yang merupakan landasan AACR2. Selain itu, RDA juga mengadopsi model konseptual Functional Requirements for Bibliographic Records (FRBR) dan Functional Requirements for Authority Data (FRAD) serta International Standard for Bibliographic Description (ISBD).

Model konseptual FRBR dan FRAD untuk memahami dunia nyata
Functional Requirements for Bibliographic Records (FRBR) dan Functional Requirement for Authority Data (FRAD) merupakan fondasi utama konstruksi RDA. Dengan demikian untuk mengetahui bagaimana RDA diimplementasikan, maka pemahaman mengenai konsep FRBR dan FRAD mutlak diperlukan. FRBR adalah sebuah proyek yang dikembangkan oleh IFLA Study Group (1992-1997) dan IFLA terus memonitor dan mempromosikan penerapan FRBR.

FRBR muncul sebagai respon atas semakin meluasnya perkembangan kerja sama pengatalogan di berbagai belahan dunia, gencarnya upaya penekanan biaya pengatalogan, dan ketidakpuasan pengguna terhadap katalog saat ini yang dianggap belum memenuhi kebutuhan mereka. Secara teknis, FRBR merupakan model konseptual dari entities, relationships, dan attributes yang digunakan untuk mendeskripsikan produk intelektual atau karya artistik. Entities kemudian dikelompokkan menjadi tiga:

1. Produk intelektual atau karya artistik (Works, Expressions, Manifestations, Items)
2. Pihak yang bertanggung jawab (Persons, Families, Corporate Bodies
3. Subjek (Concepts, Events, Events, Place)

Masing-masing entities dideskripsikan dengan attributes dan hubungan antar entities didefinisikan melalui relationships. Salah satu faktor mengapa model FRBR dimunculkan adalah agar sistem perpustakaan dapat menciptakan relasi antar database yang lebih baik yang berasal cantuman bibliografi yang dimiliki. Sebagai contoh, pada cantuman bibliografis RDA, seorang pengatalog dapat menambahkan informasi bahwa novel “Fellowship of the ring” memiliki sequel “the two towers” atau mendefinisikan Frank Seiberling adalah pendiri Goodyear Tire and Rubber Co.

Entities Grup 1 adalah area pendeskripsian cantuman bibliografis. Terminologi works dan expressions merefleksikan produk intelektual atau karya artistik dalam wujud yang masih abstrak, misalnya ide, konsep, alur cerita, dan lain sebagainya. Sedangkan terminologi manifestations dan items mengacu perwujudan fisik dan virtual dari suatu produk intelektual atau karya artistik, misalnya media, format, carrier, dan lain sebagainya. Pada dasarnya hubungan Works, Expressions, Manifestations, dan Items bukanlah sebuah struktur hirarkis melainkan sebuah urutan logis dari produk intelektual dan karya artistik yang digambarkan melalui model konseptual.

Works merepresentasikan konsep atau ide dari karya intelektual atau artistik seseorang yang masih merupakan entitas abstrak, misalnya karya Shakespeare yang berjudul Hamlet. Sedangkan Expressions adalah realisasi dari suatu karya dalam bentuk alfanumerik, notasi musik, suara, gambar, objek, dan lain-lain, sebagai contoh, teks Hamlet diterjemahkan ke dalam bahasa Swedia. Hamlet yang direalisasikan ke dalam bentuk karya adaptasi dan derivatif lainnya juga termasuk dalam kategori ini. Seperti halnya Works, Expressions masih merupakan konsep abstrak. Manifestations merepresentasikan semua objek fisik yang memiliki karakteristik yang sama dalam hal kandungan intelektual maupun bentuk fisiknya, misalnya seluruh edisi Hamlet dalam bahasa Swedia diterbitkan di Stockholm tahun 2008. Manifestations direpresentasikan dalam cantuman bibliografi. Kemudian. apabila salah satu copy-nya dimiliki dan diberi nomor panggil oleh perpustakaan, misalnya Library of Congress maka itu disebut sebagai items atau dengan kata lain items adalah eksemplar dari manifestations.

Entities grup 2 adalah pihak-pihak yang bertanggung jawab atas penciptaan produk intelektual atau konten artistik, distribusi dan produksi fisik, serta kepemilikan eksemplar atau copy. Entities grup 2 terdiri dari Person, Family, dan Corporate Body. Person yang didefinisikan dalam deskripsi bibliografis belum tentu nama asli karena kemungkinan adanya satu atau banyak pseudonyms. Attributes yang digunakan antara lain, tanggal kelahiran, kematian, aktivitas, afiliasi, gelar, gender, tempat (kelahiran, kematian, kediaman), bahasa, aktivitas, dan beberapa elemen lainnya.

Pengertian Family adalah dua orang atau lebih yang memiliki hubungan keluarga karena secara langsung maupun karena ikatan pernikahan, adopsi, perserikatan atas dasar status hukum tertentu, atau mereka yang menyatakan dirinya sebagai keluarga. Attributes yang digunakan diantaranya, jenis keluarga (klan, dinasti), tanggal yang berasosiasi dengan keluarga, tempat kediaman, aktivitas, sejarah keluarga, dan lain sebagainya.

Sedangkan Corporate body didefinisikan sebagai sebuah organisasi atau kelompok individu dan atau organisasi yang mengidentifikasikan dirinya dengan nama khusus sebagai nama dari kesatuan atau unit. Attributes yang digunakan yakni, tempat (lokasi), tanggal (kapan mulai aktif), bahasa, alamat, aktivitas, sejarah, status hukum, dan beberapa elemen lainnya.
Entities grup 3 terdiri dari concepts, objects, events, dan places. Pengertian Concepts mengacu ke ide atau konsep yang bersifat abstrak yang bisa diperluas atau dipersempit, misalnya teori, teknik, proses, praktek, dan lain sebagainya. Objects didefinisikan sebagai sebuah materi, baik bergerak maupun tidak bergerak yang merupakan ciptaan manusia atau terjadi secara alamiah, misalnya bangunan, kendaraan, dan tumbuhan. Events adalah tindakan atau kejadian yang dijadikan subjek, misalnya kejadian sejarah, periodisasi waktu. Places diartikan sebagai sebuah lokasi baik historis maupun saat ini, di bumi maupun tidak di bumi, misalnya kota, sungai, gunung, planet, dan lain-lain.

FRAD adalah daftar nama terkendali (name authority) yang beroperasi bersama-sama dengan FRBR. FRAD mendefinisikan entities dan juga memiliki attributes dan relationships, misalnya bentuk lama dan perubahan dari sebuah nama. Fungsi FRAD kurang lebih sama dengan daftar nama terkendali yang populer saat ini misalnya Library of Congress Name Authority (LCNA).
RDA memberikan penekanan pada beberapa hal, pertama, kaitan antara masing-masing entities FRBR. Kedua, hubungan antara suatu produk intelektual dengan yang lainnya. Ketiga, hubungan antara hasil karya dan penciptanya. Dan yang keempat adalah hubungan antara persons, families, dan corporate bodies.

Dari penjabaran di atas dapat disimpulkan bahwa FRBR dan FRAD merupakan sebuah konsep teoritis yang membantu kita memahami dunia nyata. Model konseptual ini menggunakan terminologi baru untuk memperjelas komunikasi di antara para pustakawan di seluruh dunia dan memastikan pengertian konsep pengatalogan dipahami secara luas. Konsep ini juga memungkinkan pustakawan mendiskusikan masalah-masalah pengatalogan dengan menggunakan terminologi dan pemahaman teoritis yang berlaku umum, juga untuk membandingkan data tidak terstruktur dengan persepsi atau cara yang sama
Mengidentifikasi metadata berbasis RDA

Perubahan mendasar RDA jika dibandingkan AACR2 adalah RDA kini menggunakan sistem kategorisasi yang menghapus GMDs (General Material Designation) dan SMDs (Specific Material Designation) dan menggantinya dengan penambahan tiga field MARC baru yaitu, 336 (content type), 337 (media type), dan 338 (carrier type).

Selain itu, pada field 040 (Cataloguing source) akan didefinisikan sebagai “040 $e rda” dan pada Leader/18 (cataloguing form) akan bernilai ‘i’ = ISBD punctuation or blank.

Penerapan “rule of three” AACR2 juga mengalami perubahan. Sebagai contoh, pada sebuah buku terdapat 7 editor yang terdiri dari 2 general editor dan 5 co-editor. Jika pada AACR2 yang dapat dicantumkan ke dalam “statement of responsibility” terbatas pada 2 general editor plus 1 co-editor, maka pada RDA semua editor dapat dicantumkan. Peraturan RDA 2.4.1.5 menyebutkan tidak dicantumkannya nama-nama diluar “rule of three” kini menjadi sebuah pilihan (optional omission). Namun demikian, RDA lebih mengarahkan pengatalog untuk mencantumkan semua nama. Nama-nama editor yang ada di “statement of responsibility” kemudian dicantumkan lagi sebagai entri tambahan pada field 700 (added entry for person). Meskipun titik akses untuk editor tidak menjadi penting dalam RDA, jika kebijakan pengatalogan perpustakaan memilih untuk mencantumkan nama editor, maka tidak ada batasan berapa banyak nama yang boleh dicantumkan.

Hal lain yang perlu diperhatikan adalah pada field 700 ada penambahan kata “editor” pada subfield $e (relator term). Subfield $e adalah “relationship designator” pada field-field yang menjadi titik akses untuk menunjukkan hubungan antara entities yang dicantumkan dengan bahan yang sedang dikatalog.

Untuk online resources, field 336, 337, 338 dapat membantu menerangkan lebih detail bahwa materi yang dikatalog adalah online resource dengan konten berupa gambar bergerak atau video. Informasi lain yang dapat ditambahkan di field 300 adalah encoding format yang digunakan. Misalnya, “300 $a1 online resource (1 streaming video file, 27:08) : $bRealvideo.”
Dalam cantuman bibliografi RDA, field 338 menjadi kunci utama yang membedakan materi online resources dan CD-ROM. Jika yang dikatalog adalah CD-ROM, maka pada field 338 pengatalog mencantumkan “computer disc.” Dan pada field 300, yang perlu ditambahkan adalah informasi mengenai isi CD-ROM dan tipe file yang digunakan. Seperti halnya AACR2, cantuman bibliografi RDA juga perlu menerangkan informasi mengenai system requirements (RDA 3.20.1.3).

Beberapa perbedaan lain RDA dan AACR2 dapat dilihat pada tabel di bawah ini.



Implikasi RDA pada MARC21
AACR2 dan MARC21 adalah dua standar berbeda yang didesain untuk tujuan yang berbeda pula. AACR2 digunakan sebagai content standard dan penyajian data sedangkan MARC21 adalah standar pengkodean (encoding standard). RDA yang sedang dikembangkan berfungsi sebagai standar konten bukan standar pengkodean. RDA berisi panduan dan instruksi perekaman data bibliografi dan authority records. Dalam hal ini, MARC21 adalah salah satu pilihan skema pengkodean untuk cantuman bibliografi RDA. Standar pengkodean lain yang dapat digunakan adalah MODS atau Dublin Core.

Adapun field-field MARC21 yang terimplikasi elemen RDA adalah:

• General Material Designation/MARC21 field 245, subfield $h
• MARC21 (bibliographic) Leader/18 (descriptive cataloguing form); MARC 21 (authority) 008/10 (descriptive cataloguing rules; description conventions code list)
• Subfield specifity pada field 502 (dissertation note)
• Subfield ISSN menjadi repeatable pada field 490 (series statement)
• Subfield tambahan pada 033 (date/time dan place of an event) dan 518 (date/time dan place of an event note)
• Pada field 040 subfield $e diberi kode “rda” untuk mengindikasikan penggunaan peraturan RDA untuk pendeskripsian. Leader/18 diberi kode “i”

Penambahan field-field MARC baru untuk attributes work dan exprression:

• 046 – special coded dates (new subfields only)
• 336 – content type
• 377 – Associated language (masih dalam proses diskusi) terkait dengan relevansinya dengan field 041 - language code)
• 380 – field of work
• 381 – Other distinguishing characteristics of work expression
• 382 – Medium of performance
• 383 – Numeric designation of a musical work
• 384 – Key

Penambahan field-field MARC baru untuk attributes nama (authority fields):

• 046 - Special Coded Dates
• 334 - Type of Geographic Entity or Jurisdiction
• 370 - Associated Place
• 371 - Address
• 372 - Field of Activity
• 373 - Affiliation
• 374 - Occupation
• 375 - Gender
• 376 - Family Information
• 377 - Associated Language
• 378 - Fuller Form of Name

Sebagian besar elemen-elemen data RDA dapat langsung menyesuaikan dengan struktur MARC21 yang ada saat ini. Dengan demikian, pengguna MARC21 tidak perlu melakukan perubahan-perubahan terkait dengan penyajian data.