Contoh record RDA: Buku disertai CD/DVD (mix media)

Selayang  pandang: afirmasi pendidikan asli orang Papua

Chega! the final report ...

Outsiders: kisah para penunggang motor

Contoh record RDA: DVD film Indonesia

Film Soekarno (2014)

Film Habibie & Ainun (2013)

Contoh record RDA: USB flash drive, website, music, photograph

USB flash drive

Website

Music

Photograph

Publication of the RDA Element Vocabularies

The Joint Steering Committee for Development of RDA (JSC), Metadata Management Associates, and ALA Publishing (on behalf of the co-publishers of RDA) are pleased to announce that the RDA elements and relationship designators have been published in the Open Metadata Registry (OMR) as Resource Description Framework (RDF) element sets suitable for linked data and semantic Web applications.

The elements include versions "unconstrained" by Functional Requirements for Bibliographic Records (FRBR) and Functional Requirements for Authority Data (FRAD), the standard library models underpinning RDA, that are intended for use in applications by non-RDA communities.
The published version of the RDA element sets builds on several years of work by the DCMI/RDA Task Group. Earlier versions developed by the Group will remain available, but will be deprecated for further development and use, and redirected to the new version.

Gordon Dunsire, Chair of the JSC, said "The RDA element set is a distillation of modern approaches to resource discovery supporting rich descriptions of library and cultural heritage materials and detailed relationships between them at international level. The JSC has recently established a working group to assist in extending and refining the RDA elements, and hopes that they will be useful to other communities, ranging from close neighbours in library linked data to the global networks of general search."

Diane Hillmann of Metadata Management Associates said "We are extremely pleased to be able to make this new version available now in fully published form, ready for implementation by libraries and vendors. We look forward to discussing the important features available in this version with our colleagues at the upcoming ALA Midwinter meetings and beyond."
James Hennelly, Managing Editor of RDA Toolkit, said "This is an important update to the RDA Registry and a crucial step in the advancement of RDA's mission to be a standard that is accessible to both cataloging professionals, through the toolkit and print and ebook publications, and to application developers seeking to make use of library data, through the Registry's expression of the RDA elements and vocabularies."

The basic RDA element set namespace is rdaregistry.info and it contains a total of over 1600 properties and classes. Elements are distributed in sets (the number of elements in each set is given in brackets):

Agent properties [http://metadataregistry.org/schema/show/id/81.html] (226)
Expression properties [http://metadataregistry.org/schema/show/id/78.html] (236)
Item properties [http://metadataregistry.org/schema/show/id/80.html] (54)
Manifestation properties [http://metadataregistry.org/schema/show/id/79.html] (213)
Work properties [http://metadataregistry.org/schema/show/id/77.html] (232)
Unconstrained properties [http://metadataregistry.org/schema/show/id/82.html] (698)
Classes [http://metadataregistry.org/schema/show/id/83.html] (8)

Follow the links to see details of each element set.

Questions or comments on the content of the element sets may be addressed to the Chair of the JSC, Gordon Dunsire [jschair@rdatoolkit.org].


Questions and comments on the encoding of the vocabularies or on the Open Metadata Registry may be addressed to Diane Hillmann [metadata.maven@gmail.com].

Invalid ISBN and RDA

Questions:
If I have an invalid ISBN on my resource, do I qualify it with (invalid) e.g. 020 !z 1742084343 (invalid)? Is the MARC coding $z (Cancelled/invalid ISBN) enough to indicate an invalid ISBN? RDA 2.19.1.5

Answer:
The  correct MARC subfield coding should always be used, and is all that is required to satisfy the RDA requirement to indicate that the ISBN is invalid.  However, some areas are in the practice of also including a qualifier, and it is ok for this practice to continue if considered useful.
(From: NLA RDA FAQ)

This page lists some useful RDA resources:

1. ALCTS regularly offer 1-2 hour information webinars about RDA.  Some of the older presentations are freely available on their website http://www.ala.org/alcts/confevents/upcoming/webinar/cat.  The recordings require Windows Media software and a Codec "Patch", which can be downloaded for free from http://www.gotomeeting.com/code
2. See the ACOC RDA website to keep up to date on developments
3. Information on implementation in the US is available on the LC RDA webpage and some handy record examples
4. Questions and Answers from Stanford University http://lib.stanford.edu/metadata-department/stanford-rda-questions-and-answers. It has not been updated recently, but it does still contain useful information
5. PCC guidelines and standards http://www.loc.gov/aba/pcc/rda/PCC%20RDA%20guidelines/Post-RDA-Implementation-Guidelines.html
6. RDA Cafe http://www.facebook.com/#!/groups/RDACafe/?fref=ts|http://www.facebook.com/#!/groups/RDACafe/?fref=ts
7. Introducing RDA : a guide to the basics / Chris Oliver (YYq 2011-133)
8. Practical cataloguing : AACR, RDA and MARC21 / Anne Welsh and Sue Batley (YY 2012-3786)
9. The RDA primer : a guide for the occasional cataloger / Amy Hart (YY 2011-1321)
10. Describing electronic, digital, and other media using AACR2 and RDA : a how-to-do-it manual and CD-ROM for librarians / Mary Beth Weber, Fay Angela Austin (Sq 020 HOW no. 168)

RDA 2.4.1.5 Optional Omission

Pada metadata berikut ini diperlihatkan bagaimana “rule of three” yang ada di AACR2 mengalami perubahan. Sebuah buku memiliki 7 editor (2 general editor dan 5 co-editor). Dengan menggunakan rules RDA, semua editor dapat dicantumkan dalam “statement of responsibility.” Akan berbeda halnya jika menggunakan AACR2 yang hanya dapat mecantumkan 2 general editor plus 1 co-editor ke dalam “statement of responsibility”. Dalam aturan RDA 2.4.1.5 mengenai “statement of responsibility”, tidak dicantumkannya nama-nama kini menjadi sebuah pilihan (optional omission). Namun, RDA lebih mengarahkan cataloger untuk mencantumkan semua nama. Nama-nama editor yang ada di “statement of responsibility” kemudian dicantumkan lagi sebagai entri tambahan di field 700. Titik akses untuk editor tidak menjadi penting dalam RDA, akan tetapi jika kebijakan pengatalogan pada suatu institusi memilih untuk mencantumkan nama editor, maka tidak ada batasan berapa banyak nama yang akan dicantumkan.

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

Screenshots RDA Toolkit

Setelah login ke RDA toolkit, user bisa melihat lebih rinci aturan-aturan yang ada di RDA. Untuk memulainya dapat mengklik tanda “+” yang ada pada setiap section, chapter, dan subpart. Sebagai contoh, pada section 1: Manifestations and items, klik (chapter) 2: identifying manifestations and items, kemudian 2.3: title.

Setelah itu, instruksi 2.3 Title akan muncul di layar. RDA akan selalu menampilkan halaman awal instruksi secara cepat sebelum menampilkan instruksi yang dituju

Sama seperti AACR2, RDA juga memiliki instruksi "options" di mana user bisa memiliki beberapa pilihan dalam proses pengatalogan sesuai situasi yang dihadapi. Instruksi "options" selalu berwarna hijau yang memberikan alternatif instruksi, opsi menambahkan, dan menghilangkan informasi sejalan dengan kebutuhan atau kebijakan perpustakaan.

Jika tab "resources" diklik, maka muncul halaman yang memuat Library of Congress policy statements. Di masa yang akan datang, policy statements yang dibuat oleh perpustakaan nasional lainnya akan dimasukan atau dibuatkan link dalam RDA Toolkit

Jika diperlukan user bisa mencetak keseluruhan instruksi yang diperlukan atau bagian-bagian tertentu saja.

Element set view adalah informasi lain mengenai elemen-elemen RDA yang diatur menurut entities FRBR/FRAD dengan subgroup attributes dan relationship untuk masing-masing elemen. Element set view membantu user untuk menghubungkan RDA dengan FRBR/FRAD

CONSER MARC to RDA Core Elements untuk pengatalogan terbitan berseri

Skema entity-relationship sebagai model konseptual untuk memahami RDA

MARC Bibliographic to RDA Mapping membantu user mengidentifikasi instruksi RDA yang sesuai untuk masing-masing field MARC

Beberapa contoh record RDA untuk terbitan Indonesia

[click image to enlarge]

RDA: pencantuman (recording) data

Abreviasi atau singkatan tidak lagi digunakan dalam RDA dan ini menjadi salah satu kunci utama perbedaan dengan pendahulunya, AACR. RDA menggunakan abreviasi hanya apabila memang tercantum demikian pada bahan yang sedang dikatalog. Untuk lebih detailnya perhatikan contoh-contoh berikut:




Pada contoh dibaris terakhir, punktuasi titik (".") dicantumkan dua kali karena sesuai dengan perubahan instruksi ISBD, "." tetap diperlukan sebagai pemisah elemen. Sebelumnya, ISBD menginstruksikan bahwa jika data diakhiri dengan ".", maka punktuasi "." yang menjadi pemisah dengan elemen data selanjutnya dapat dihilangkan. Hal ini menimbulkan kontradiksi dengan prinsip penggunaan punktuasi pada umumnya di mana "." harus selalu digunakan meskipun harus mencantumkan punktuasi yang sama. Pada kenyataannya, sebagian besar sistem telah menggunakan prinsip pemisahan elemen (delimiter) sehingga meskipun punktuasi "." dicantumkan dua kali tetap akan terlihat satu pada sistem.




Jika pada AACR, penggunaan abreviasi bisa dilakukan sesuai dengan aturan yang ada pada AACR Appendix B, maka pada RDA pencantuman tempat terbit dan nama penerbit sesuai apa adanya sesuai yang ditemukan pada bahan yang katalog. Pada contoh di atas, istilah "Department" adalah corporate body yang bisa dijadikan access point.




Singkatan bahasa Latin yang biasa digunakan AACR untuk menandai penulisan data yang tidak tepat, penghapusan data, atau data tidak ditemukan kini tidak lagi relevan. RDA didesain untuk konteks internasional di mana tidak semua orang mengerti istilah dan makna bahasa Latin. Sebagai penggantinya, RDA menggunakan bahasa alami yang mudah dipahami. Gelar yang mengawali nama tidak dihilangkan dan dicantumkan apa adanya.

RDA 2.4.1.4: Recording Statements of Responsibility
Transcribe a statement of responsibility in the form in which it appears on the source of information. Apply the general guidelines on transcription given under 1.7.



Seperti yang terlihat pada contoh di atas, singkatan untuk data yang tidak diketahui digantikan dengan bahasa alami. Hal ini juga berlaku untuk tahun penerbitan, apabila tidak ditemukan dapat dicantumkan [date of publication not identified]. Meskipun demikian, RDA mendorong cataloger untuk tetap mencantumkan perkiraan tahun terbit sebab bagi RDA data tahun penerbitan merupakan salah satu elemen penting. Mencantumkan perkiraan tahun terbit jauh lebih baik daripada tidak ada sama sekali. Punktuasi "[]" kini digunakan untuk masing-masing element data dan tidak hanya di awal dan diakhir sebagai single set element data. Ini merupakan bagian dari perubahan punktuasi dalam ISBD karena pada dunia online perjalanan data katalog tidak lagi sebagai satu unit secara keseuluruhan akan tetapi sebagai elemen-elemen tunggal yang bisa digunakan untuk konteks yang berbeda-beda.



Singkatan Latin seperti, "sic" atau "i.e." untuk menandakan adanya kesalahan pengetikan (typographical errors) pada halaman judul tidak lagi digunakan. RDA menginstruksikan mencantumkan kesalahan pengetikan tersebut apa adanya sesuai yang tertera pada bahan yang dikatalog dan mengkoreksi melalui entri judul tambahan (variant title entry) pada field 246. Pengecualian untuk serials, apabila terdapat kesalahan pengetikann maka bisa langsung dikoreksi dengan pertimbangan bahwa mungkin kesalahan terjadi pada satu issue saja. Hal ini sebenarnya juga telah diatur di dalam AACR. Jika dianggap perlu, maka informasi kesalahan pengetikan tersebut dicantumkan pada daerah catatan.


RDA 2.3.1.4 Recording Titles
Exceptions
Inaccuracies. When transcribing the title proper of a serial or integrating resource, correct obvious typographic errors, and make a note giving the title as it appears on the source of information (see 2.20.2.4). In case of doubt about whether the spelling of a word is incorrect, transcribe the spelling as found.



RDA tidak menyarankan pencantuman informasi tambahan apabila informasi tersebut tidak ditemukan pada bahan yang sedang dikatalog. Namun demikian, khusus untuk gambar (picture) yang tidak memiliki judul, maka RDA menginstrusikan cataloguer untuk memberikan judul.



RDA memasukan parallel titles sebagai non-core element yang bermakna tidak harus untuk dicantumkan. Meskipun demikian, jika ingin dicantumkan, makan cataloguer harus mencantumkan keseluruhan parallel title pada field 246.




RDA menghilangkan aturan rule of three. Peoples, families, corporate bodies yang bertanggung jawab atas suatu hasil karya harus dicantumkan dan dibuatkan access pointnya.



Optional omission dapat dilakukan dengan menggunakan bahasa alami, misalnya "[and three others] seperti yang terlihat pada contoh di atas.




Jika dalam AACR punktuasi "..." atau "[]" yang tertera pada judul harus diubah menjadi "--" atau "()", maka RDA menginstruksikan sebaliknya, yakni mencantumkan apa adanya sesuai apa yang tertera pada bahan yang sedang dikatalog. Namun demikian, jika judul terlalu panjang maka dapat dihilangkan dengan punktuasi "..." dengan catatan, lima kata pertama tidak boleh dihilangkan.

RDA 2.3.1.4 Recording Title
Optional Omission
Abridge a long title only if it can be abridged without loss of essential information. Use a mark of omission (…) to indicate such an omission. Never omit any of the first five words.

Content, media, and carrier fields

Source: http://rdabasics.com/2012/09/10/content-media-and-carrier-fields/

A major change from AACR2 is the introduction of three MARC fields: content type, media type, and carrier type, which go in fields 336, 337, and 338, respectively. These replace the information that in AACR2 was contained in the general material designator (GMD), which went in the “$h” subfield of MARC field 245. The GMD was considered imprecise and will no longer be in use in RDA records. A description of the three new fields follows.

Content type (field 336) is “a categorization reflecting the fundamental form of communication in which the content is expressed and the human sense through which it is intended to be perceived” (RDA 6.9.1.1). Got that? It is most useful to look at the list of content type terms here: http://www.loc.gov/standards/valuelist/rdacontent.html. (The terms are also listed in the RDA Toolkit.) These include terms such as “performed music,” “spoken word,” “text,” and “two-dimensional moving image.” This is a closed list, and catalogers should not use terms that are not on the list.

Media type (field 337) is “a categorization reflecting the general type of intermediation device required to view, play, run, etc., the content of a resource” (RDA 3.2.1.1). (Note that content type is in chapter 6 of RDA because it describes expressions; media type is in chapter 3 because it describes manifestations.) Basically, media type tells you what you need to do to access the content of the resource. If you have only to cast your eyes upon it, it is “unmediated.” Otherwise, it may be “audio,” “computer,” “video,” etc. The list of 10 prescribed terms can be found here: http://www.loc.gov/standards/valuelist/rdamedia.html. Again, this is a closed list.

Carrier type (field 338) is “a categorization reflecting the format of the storage medium and housing of a carrier in combination with the type of intermediation device required to view, play, run, etc., the content of a resource” (RDA 3.3.1.1). Chris Oliver adds that “[c]arrier types are closely correlated with media types and can be considered as the next level of granularity for the media types” (53). For example, a resource with media type “audio” might have carrier type of “audio disc” or “audiocassette.” A resource with media type “video” might have carrier type “videocassette” or “videodisc.” The (long) list of possible carrier types can be found here: http://www.loc.gov/standards/valuelist/rdacarrier.html. Again, it’s a closed list.

All three fields are repeatable. For example, a CD may be able to be played in an audio device as well as a computer, so it might be given two media types: “audio” and “computer.”

The following are some examples of how these three fields will look for different resources.

A basic book would be coded in this way:
336 ## text $2 rdacontent
337 ## unmediated $2 rdamedia
338 ## volume $2 rdacarrier

The “$2” subfields are mandatory. A DVD would look like this:
336 ## two-dimensional moving image $2 rdacontent
337 ## video $2 rdamedia
338 ## videodisc $2 rdacarrier

An audiobook on CD would look like this:
336 ## spoken word $2 rdacontent
337 ## audio $2 rdamedia
338 ## audio disc $2 rdacarrier

And a Web site would look like this:
336 ## text $2 rdacontent
337 ## computer $2 rdamedia
338 ## online resource $2 rdacarrier

These fields are not display fields. Sirsi (or LMxAC) will have to design a way for the information contained in the 336-338 fields to map to a display in the OPAC. The display may be very similar to the GMD we have today and may thus mean a relatively small change for our users. However, the new fields may have important effects on the faceted searching (the “buttons”) provided by LMxAC, if these searches use information from the GMD. Information on content and carrier, etc., in the fixed fields will not change.

Daftar istilah dan kode untuk RDA Media Types, MARC Field 337

This list contains Resource Description and Access (RDA) terms and corresponding one-character lower case alphabetic codes for RDA Media types. These types can be recorded in MARC Bibliographic and Holdings records in textual form and/or in the one-character coded form in MARC field 337 (Media Type). They may also be recorded, sometimes in a more granular and sometimes in a more general form, with one-character codes in MARC 007/00 (Category of material), in most cases. In the following, the one-character codes and terms for field 337, subfields $b and $a, respectively, are listed along with the corresponding 007 codes.

The source code for this list in field 337 $2 (Source) is rdamedia.

RDA media terms -337 $a	MARC codes for RDA terms - 337 $b	MARC media codes - 007/00
audio	s	s - sound recording
computer	c	c - electronic resource
microform	h	h - microform
microscopic	p
projected	g	g - projected graphic m - motion picture
stereographic	e
unmediated	n	t - text k - non-projected graphic
video	v	v - videorecording
other	x	z - unspecified
unspecified	z	z - unspecified

Daftar istilah dan kode untuk RDA Carrier Type, MARC Field 338

This list contains Resource Description and Access (RDA) terms and corresponding two-character lower case alphabetic codes for RDA Carrier types. These types can be recorded in MARC Bibliographic and Holdings records in textual form and/or in the two-character coded form in MARC field 338 (Carrier Type). They may also be recorded, sometimes in a more granular and sometimes in a more general form, with one-character codes in the MARC 007/01 (Specific material designation) with a few exceptions (see tables). In the following, the two-character codes and terms for field 338 $b and $a, respectively, are listed along with the corresponding MARC 007 (or other) codes.

The source code for this list in field 338 $2 (Source) is rdacarrier.

Audio carriers

RDA carrier terms - 338 $a	MARC codes for RDA terms - 338 $b	MARC audio carrier codes - 007/01
audio cartridge	sg	g - 007/01 (Sound recording)
audio cylinder	se	e - 007/01 (Sound recording)
audio disc	sd	d - 007/01 (Sound recording)
sound track reel	si	i - 007/01 (Sound recording)
audio roll	sq	q - 007/01 (Sound recording)
audiocassette	ss	s - 007/01 (Sound recording)
audiotape reel	st	t - 007/01 (Sound recording)
other	sz	z - 007/01 (Sound recording)

Computer carriers

RDA carrier terms - 338 $a	MARC codes for RDA terms - 338 $b	MARC computer carrier codes - 007/01
computer card	ck	k - 007/01 (Electronic resource)
computer chip cartridge	cb	b - 007/01 (Electronic resource)
computer disc	cd	d - 007/01 (Electronic resource)
computer disc cartridge	ce	e - 007/01 (Electronic resource)
computer tape cartridge	ca	a - 007/01 (Electronic resource)
computer tape cassette	cf	f - 007/01 (Electronic resource)
computer tape reel	ch	h - 007/01 (Electronic resource)
online resource	cr	r - 007/01 (Electronic resource)
other	cz	z - 007/01 (Electronic resource)

Microform carriers

RDA carrier terms - 338 $a	MARC codes for RDA terms - 338 $b	MARC microform carrier codes - 007/01
aperture card	ha	a - 007/01 (Microform)
microfiche	he	e - 007/01 (Microform)
microfiche cassette	hf	f - 007/01 (Microform)
microfilm cartridge	hb	b - 007/01 (Microform)
microfilm cassette	hc	c - 007/01 (Microform)
microfilm reel	hd	d - 007/01 (Microform)
microfilm roll	hj	j - 007/01 (Microfilm)
microfilm slip	hh	h - 007/01 (Microform)
microopaque	hg	g - 007/01 (Microform)
other	hz	z - 007/01 (Microform)

Microscopic carriers

RDA carrier terms - 338 $a	MARC codes for RDA terms - 338 $b	MARC microscopic carrier codes - Bibliographic 008/33
microscope slide	pp	p - 008/33 (Visual Materials)
other	pz	no code

Projected image carriers

RDA carrier terms - 338 $a	MARC codes for RDA terms - 338 $b	MARC projected image carrier codes - 007/01
film cartridge	mc	c - 007/01 (Motion picture)
film cassette	mf	f - 007/01 (Motion picture)
film reel	mr	r - 007/01 (Motion picture)
film roll	mo	o - 007/01 (Motion picture)
filmslip	gd	d - 007/01 (Projected graphic)
filmstrip	gf	f - 007/01 (Projected graphic)
filmstrip cartridge	gc	c - 007/01 (Projected graphic)
overhead transparency	gt	t - 007/01 (Projected graphic)
slide	gs	s - 007/01 (Projected graphic)
other	mz	z - 007/01 (Motion picture)  z - 007/01 (Projected graphic)

Stereographic carriers

RDA carrier terms - 338 $a	MARC codes for RDA terms - 338 $b	MARC stereographic carrier codes - 007/01
stereograph card	eh	h - 007/01 (Non-projected graphic)
stereograph disc	es	s - 007/01 (Projected graphic)
other	ez	no code

Unmediated carriers

RDA carrier terms - 338 $a	MARC codes for RDA terms - 338 $b	MARC unmediated carrier codes
card	no	no code
flipchart	nn	no code
roll	na	no code
sheet	nb	no code
volume	nc	no code
object	nr	r - Bibliographic Leader/06
other	nz	no code

Video carriers

RDA carrier terms - 338 $a	MARC codes for RDA terms - 338 $b	MARC video carrier codes - 007/01
video cartridge	vc	c - 007/01 (Videorecording)
videocassette	vf	f - 007/01 (Videorecording)
videodisc	vd	d - 007/01 (Videorecording)
videotape reel	vr	r - 007/01 (Videorecording)
other	vz	z - 007/01 (Videorecording)

Unspecified carriers

RDA carrier terms - 338 $a	MARC codes for RDA terms - 338 $b	MARC unspecified carrier codes - 007/01
unspecified	zu	u - 007/01 (Unspecified)