teaching rda: day 2 - nla web viewso always check which word has been used. ... note: some mills and...

Teaching RDA: Day 2

Discussion and questions from previous day

Discussion and questions relating to material from Day 1.

Module 6: Attributes of Manifestations & Items (RDA Section 1)

Resources:- Flip chart and Marker pens

- FRBR Report

- Killers in Eden (or other example book)

- Items for cataloguing exercise

Learning Outcomes:

- Understand structure and contents of section 1 of RDA

- Identify and record the attributes of manifestation and items

By the end of this module you will know where to find the instructions for re cording:

Title of a manifestation and statement of responsibility

Edition statements

Publication details

Content media and carrier types

Extent and dimensions

Teaching RDA (National Library of Australia, 2012)

Handbook: Page 44

of 30 Teaching RDA: Module 6 October 2012

Okay, so now we will get down to the bit you’ve all been waiting for – how do I catalogue using RDA?

In the next few modules, we’ll look at the text of RDA and use it to do some cataloguing exercises. We will begin with Section 1: Attributes of Manifestations & Items.

Before we start we will remind ourselves what are manifestations and items; and what are some of their attributes.

Manifestations and Items Activity

Can you tell me some of the parts of the catalogue record as we know it now that relate to manifestations and items? [Presenter: Pass round some items to encourage ideas. Write answers up on the board. Are looking for at least the following:]

[Full list available in FRBR]

Overview Section 1 of RDA contains the instructions for recording the information that relates to the FRBR/FRAD entities of manifestation and item - The sort of descriptive information that we put in the MARC bibliographic record.

This includes identifying information such as title and statement of responsibility, Physical characteristics and acquisitions and access information.

Handbook: Page 160


Structure in detailLike AACR, RDA always proceeds from the general to the specific. The first chapter of Section 1 is general guidelines for recording the attributes of Manifestations and items, and the subsequent chapters are about the specific detail of recording each attribute.

Within each Chapter [for example chapter 2] there are again, general instructions for the contents of the whole chapter, then specific instructions for each data element.

Even each data element is broken down the same way - general or “basic” instructions on recording that element and then specific instructions to use in particular situations. Eg. 2.3 Title starts with “Basic instructions on recording titles” followed by the different types of titles you might record. And within that, even further breakdown.

Each Chapter and subsection also begins with a scope statement which tells you what is covered in that section including, at the Chapter level, which FRBR user task the chapter addresses.

This structure is the same throughout RDA. Each Section, chapter and subsection proceeds from the general to the specific.

Of course it’s up to you where you start looking.

Being an online tool there is much more flexibility in how you move around and you will develop your own preferences. You could use the contents pane, search for a specific element (eg title proper) or use the the MARC and AACR2 mapping tools.

But it is still useful to understand this “general to specific” layout. If you can’t find the answer to a problem at the specific rule, try going back to more general rules, or vice versa. In many cases, specific rules refer you back to the general rules, just as AACR2 did, using statements like “as instructed under...” [See for example 2.3.6.3 Recording variant titles]


Chapter 1: General guidelinesThis chapter is very like the beginning of Chapter 1 in AACR2, covering the general issues to consider when recording the attributes of manifestations and items – terminology, functional objectives, Core elements, Language and script, transcription, type of description etc.

Each Section of RDA has such a chapter and it is important for you to know what these chapters contain. While you are learning, we recommend that you read these chapters right through before you start to catalogue using RDA.

We will take some time to draw out some key points from Chapter 1.

Handbook: Page 47


Exercise 7

Note to presenter: As you talk through Chapter One ask participants to answer questions about Rabbit

Droppings

Rabbit Droppings is an electronic journal distributed in PDF and published irregularly

Handbook: Page 161 and 162


1.1 TerminologyEach “General guidelines” chapter introduces some key terminology that will be used in the Section, with an explanation of their meanings within the context of the Section.

The key terms listed here are Resource - the thing you are trying to catalogue, and in this

context, means the manifestation or item Mode of issuance – is it a monograph or serial Type of description – three types of description Work, Expression, Manifestation, Item – reminder about FRBR/FRAD Group 1 entities

Though key terminology is always outlined in these general guidelines chapters, other terminology used throughout each section is usually defined within its context, and it is important to be alert to these terms and their meanings.

Question: What is the mode of issuance of Rabbit droppings? Serial

There is a terminology cheat sheet is in Appendix 2 of handbook

1.2 Functional objectives and principlesFunctional objectives and principles are also set out in each “General guidelines” chapter. They serve two purposes:

Outline for cataloguers what the data they record should enable users to do

Outline the principles applied in formulating the instructions in order to achieve that objective.

The objectives and principles are all based on FRBR, FRAD, and the International Cataloguing Principles, and will be different for each Section.


As well as being set out at the beginning of each section, scope statements in the individual chapters will also draw our attention back to these objectives. So we will always be able to understand why it is important to record certain information.

Question: What user tasks should data describing a manifestation achieve? Find, identify, select and obtain

1.3 Core Elements The core elements in Section 1 are all related to the manifestation. RDA does not regard any item elements as Core, but individual cataloguing agencies may wish to make them mandatory, as the National Library has done for some.

Question: What is the numbering of this issue of Rabbit droppings and is it a core element? December 2011, no. 76. It is core for serial

1.4 Language and scriptMost elements of manifestations should be recorded in the language and script in which they appear on the resource. Those that are not, and all item elements, should be recorded in the language and script appropriate to the agency.

Question: What language would you record the title of Rabbit droppings? English

1.5 Type of description Before you begin cataloguing, it is important to determine broadly what you are cataloguing. Is your description about a whole resource, a part of a resource (or part of a part), or the whole and its parts? This decision is important as it affects other decisions you will make when you catalogue: choice of title proper, who is responsible for the content, etc.

RDA has defined 3 different types of description to cover this:


Comprehensive description - describing the whole resource. This is the type of description that most of us use most of the time, for monographs, multi-part resources, serials, and collections.

Analytic description - describing a part, or parts of a resource: an issue of a serial, a volume in a series, part of a collection. Most of us have done this at some point, some more regularly than others.

Hierarchical description- The whole and its parts. Most commonly, this approach is used for large formed collections of resources.

How is this different to AACR2?

AACR2 briefly covers cataloguing the whole, or parts of resources, but doesn’t emphasise it as a key pre-cataloguing decision. In the card catalogue world, resources were generally catalogued comprehensively. For the exceptional circumstances that require analytical description, special rules were provided in Chapter 13. Hierarchical descriptions were not even mentioned.

As our collections have grown and become more varied, we are frequently using a combination of all three approaches to control them. So in RDA, the emphasis is on making this decision first, and then approaching the rest of your cataloguing from this standpoint.

Question: type of description would you apply for cataloguing this issue and for the whole serial of Rabbit Droppings? Analytic for this issue and Comprehensive for the whole serial

1.6 Changes requiring a new descriptionListed in this section are changes in a resource that RDA considers enough to warrant a new description. For external participants: Some of these may be new or changed practise for some cataloguers, so you should read this section before you start cataloguing

Question: If In 2013 the publishers of Rabbit droppings decide to publish monthly online. Will this require a new catalogue record for the serial? Yes – change in media. It does not come under change in mode of issuance (1.6.2.1)

1.7 TranscriptionWe talked already about the changes to the way we transcribe data, and this section sets out the general guidelines for transcription, including capitalisation, abbreviation, punctuation, diacritics, symbols, acronyms, numbers, etc. It also links to Appendix A and B, where detailed guidelines on capitalisation and punctuation are contained.


I should point out here that as you progress through RDA, you will be instructed either to “transcribe” data or to “record” data. If you are being asked to “record” data, there is more scope to adjust the information you have found. So always check which word has been used.

Order of elements?

Notably absent in the general guidelines Chapter is any information about the order of the elements, or punctuation between elements. As I’ve already mentioned, RDA is a content standard so data presentation is not included.

However, the ISBD standard is reproduced in Appendix D, with links back to the relevant RDA instructions.

This will be a useful reference for libraries that still use ISBD.

There is also extensive mapping between MARC and RDA that will help cataloguers with how to present RDA data in MARC.


Chapters 2-4: Recording attributes of manifestations and items

The rest of the Chapters in Section 1 are concerned with actually recording the catalogue data.

Chapter 2 – Identifying manifestations and items (title, statement of responsibility etc.)

Chapter 3 – Describing carriers (how many pages, type of devise)

Chapter 4 – Providing acquisitions and access information

The Core elements for manifestation and item are listed in Chapter 1, subsection 3, or “1.3” [Go to section 1.3] There is also a marker at each core element with RDA to let you know it is core and under what conditions.

For the purposes of this training, we will concentrate on the core elements, and in particular those where there is a significant change in practice from AACR2. You will then hopefully be able to apply the general principles to other elements.

Note: no Item elements are core in RDA. This may be because item information (holdings, acquisition details, access restrictions, etc.) is considered to be a local consideration that RDA did not want to mandate.

Chapter 2Chapter 2 covers the attributes of a manifestation typically used by producers of resources to identify their product, and that users rely on to determine if the resource is the one they are looking for.

A key question we have to ask when recording these attributes is “What is the source of information?”

RDA organises this information differently to AACR2.

There are two parts to “Sources of information”.

Use a resource to illustrate instructions for remainder of module.

We have used Killers in Eden by Danielle Clode

Handbook: Page 50


2.1 Basis for the Identification of the resource.

There is the decision about what you will use as basis for identifying the resource:

This is dependent on what type of description you chose at 1.5;

the mode of issuance (eg, monograph or serial), which can be determined following instructions at 2.13; and;

How many parts there are to the resource.

For Killers in Eden:

- Go to 1.5 and determine the type of description: Comprehensive

- Go to 2.13 and determine the mode of issuance: Monograph

- How many parts are there: One

Sources of information

Then there’s the decision about what part or parts of the resource to use as your “preferred source of information”, this was the “Chief source of information” in AACR2.

Here RDA has simplified things a lot.

Instruction on Sources of Information that was given in each chapter of AACR2 Part I have been brought together in 2.2 and condensed into three categories:

- Resources with pages, leaves, etc., or images of pages…,

- Moving images, and

- All other resources.

For Killers in Eden – which is a monograph – what category will we choose?


In 2.2 there are also instructions about multiple preferred sources and alternative sources of information.

Instructions about source of information are also found at each data element in RDA but mostly they refer you back to 2.2 unless there is a reason to differ.

So you should read this whole section before you start cataloguing.

RDA is less prescriptive about sources of information than AACR2, as indicated by the use of the term “preferred source”.

There are no references to “prescribed sources”.

While there is a preferred source (eg title page, title frame, fixed label etc.) any part of the resource can be used if the preferred source does not contain the information and you do not have to indicate that the information is not from the preferred source (eg with square brackets and/or a note).

You now only have to indicate the source of information when it is taken from outside the whole resource, and that is only for resources where you would normally expect to find the information in the resource (eg, still images, objects don’t normally carry any “bibliographic information”).

Killers in eden has a title page – so this is our preferred source of information.

Once you have decided on the type of description, mode of issuance and sources of information you can start cataloguing.

2.3 Title2.3 contains the instructions for recording the title of a manifestation. It is a “Core element” with an instruction attached.

Question: Is every part of the title is core?

Answer: Only the title proper is core.

This means that subtitles, parallel titles, variant titles, earlier and later titles, etc. are not required by RDA.

This is an example of where there are “conditions” to the core status of an element.

Note however that institutional policies may stipulate additional core elements. LC for example, has a policy statement at 2.3.4 for other title information [click on the green LCPS button] stipulating that subtitles are mandatory. They have similar statements for parallel titles and earlier and later titles. [For the National Library, these and also variant titles are also mandatory]


The actual instructions at 2.3 are again arranged from the general to the specific.

First there are basic instructions for recording titles at 2.3.1. All the following instructions for recording titles under 2.3 refer you back to here because it is the basic instruction they all stem from.

This is followed by instructions for all the different title types. If you look under one of the types, eg title proper at 2.3.2, you will see instructions for the sorts of situations you are likely to come across when recording the title proper, including instructions that relate to special types of resources (eg. Facsimiles/reproductions, resources with no title)

We will now look at recording the title proper.

Looking at the instructions in 2.3 to find out how to record a title proper.

If you go straight to the 2.3.2 Title proper it doesn’t tell you how to transcribe the title.

2.3.2.7 gives instructions for Recording title proper – but refers back to 2.3.1 for the general guidelines on constructing titles.

2.3.1.4 is where we find the instruction, “transcribe ... as it appears on the source of information”.

Even here we are referred back to the general guidelines on transcription at 1.7.

When you first start using RDA you might find this jumping back and forth a bit frustrating but as you become more familiar with the instructions and the Toolkit itself you will find this easier and probably have to do it less, just as is the case for you now with AACR2.

Transcribing titles is, in general, much as it was in AACR2.

There are a couple of key differences to remember when transcribing titles:

Don’t correct errors for monographs

Don’t change or remove punctuation to suit ISBD or cataloguing conventions


For our example book it’s pretty straight forward. Killers in Eden has a title page and the title also appears on the cover.

I simply transcribe the title as it appears on the preferred source, and in MARC, it will look like this:

245 1 0 $aKillers in Eden :$b.....

We will now look at some other key elements of manifestations and items.

We will not look at every element in chapter 2, but I will draw your attention to some key changes from AACR2

2.4 Statement of responsibilityRDA introduces some changes to the way we record the Statement of Responsibility particularly in terms of how much information we record here.

2.4 is a “core element”. However, like the title, it has a qualifying statement. Only the statement of responsibility relating to title proper is core.


Statements of responsibility relating to edition, series and subseries are all non-core elements and are only recorded if required by the cataloguing agency or to enhance accessibility.

Statement of responsibility relating to title proper – 2.4.2

At 2.4.2, we discover that even here the “core” statement is qualified.

If there are multiple statements, then only the first one is core. This does not apply to how many names are recorded, but how many statements. To illustrate:

“written by ...[1 or more names]” is a single statement

“written by ... [1 or more names] ; illustrated by ... [1 or more names]” are multiple statements

In RDA you only have to record the first statement.

Whether you record other statement(s) will be depend on cataloguer judgement or institutional policy. In AACR2 we recorded each statement.

Rule of three

We didn’t always record every name in each statement. If there were more than three people named in a statement only the first or most prominent was recorded.

The remaining names were omitted and replaced by the Latin abbreviation “...[et al]”. This is what we know as the “Rule of Three” and it was arbitrary and prescriptive.

In RDA the “Rule of three” is an “Optional omission” .

If you do choose to omit names according to the Optional omission, RDA no longer uses the abbreviation “...et al.”

2.4.1.5 instructs you to “Indicate the omission by summarising what has been omitted in the language and script preferred by the agency preparing the description. Indicate that the summary was taken from a source outside the resource itself”.

Killers in Eden has one author and no additional statement of responsibility.

We will transcribe it and in MARC it looks like this:


245 10 $a Killers in Eden / $c Danielle Clode.

Note that the punctuation is not prescribed by RDA – it is ISBD punctuation.

2.5 EditionThe key points of difference to note with edition are:

Edition statements are transcribed as found. Do not arbitrarily abbreviate.

Music presentation statements are classed as “edition” statements for the purposes of RDA.(However, the MARC 254 is still valid for this information)

Killers in Eden has 2nd ed. on the back of the title page.2.5.2.3 tells us to transcribe as it is on the resource.

Remember the second full stop after ed.

2.7 – 2.10 Production/Publication/Distribution/Manufacture

What we call the “imprint” statement has changed quite a bit with RDA.

In AACR2 publication and distribution were covered under a single data element with one set of instructions. Manufacture was added to the end if needed.

In RDA, publication, distribution and manufacture have been separated out into their own elements and a 4th has appeared, “production”


Production Statement – 2.7

Production statements apply to unpublished resources, such as manuscripts, objects, unpublished pictures etc. In this element, only the date is core.

Publication, distribution, manufacture – 2.8-2.10

2.8– 2.10 apply to published resources and could all potentially apply to any one published resource.

Of these elements, only the Publication Statement is unconditionally core.

The Distribution statement is only core if the publication statement is not identified and the Manufacture statement is only core if neither of the other two can be identified.

MARC 264 field

RDA does not prescribe in which marc field to record these elements but marc has created a new field, 264, which has greater scope than the 260 field. Now that RDA has provided separate elements for each of these, the new MARC 264 field allows for greater granularity of this information. The field allows you to indicate whether the information you are providing is about the producer, publisher, distributor or manufacturer. It can therefore be used instead of the 260 if you want to bring this information out. It will be National Library policy to use the 264 in preference to the 260.

The instructions at each of these four elements are similar to the AACR2 publication, distribution etc. element. However, there are a couple of key differences:

The name of a larger jurisdiction is only included if present on the source of information. However there is an optional addition to include the larger jurisdiction if important for identification or access

The name of the larger jurisdiction is only abbreviated if abbreviated on the source of information.

The Latin abbreviations used to indicate unknown place or name and unknown or uncertain date have been replaced with full phrase

o “Place of publication not identified” o “Name of publisher not identified”


o “Date of publication not identified”o “between [date] and [date]”, “not before [date]”, “not after [date]”

Note: Detailed information about recording approximate dates is in Chapter 1 at 1.9, which has a link to at each of instructions in 2.7-2.10 on recording dates

Also, although it is possible to use “Date of publication not identified” 2.8.6 implies that this should be a last resort. Date is a key element for both users and computers in identifying and sorting resources so cataloguers should always try to at least approximate a date.

2.11 Copyright date AACR2 copyright date or phonogram date was an optional addition to “date of publication, distribution, etc.” if it was different to the publication date.

It now has its own element and is core if there is no other date.

NLA has listed Copyright date as mandatory whether or not other dates are present.

Copyright dates can now be recorded in a separate 264 field, with a second indicator of 4. Note that if you are choosing to use the 264 in preference to the 260, the copyright date must go in a separate 264.

2.11 also now allows for multiple copyright dates that apply to different aspects of a resource to be recorded in a note.

Finally we can now use either the Copyright or Phonogram symbols, or spell out the words “Copyright” or “Phonogram” before the date.

Publication statement for Killers in Eden: 2.8.2 Place of publication – Melbourne, Victoria is recorded on the title page verso

2.8.4 Name of publisher – Transcribed as on the resource

2.8.6 Date of publication – As found on the resource

2.11 Copyright date – Not core to record as we have a publication date but we can record it.

All recorded in the 264 field. The publication 264 has a 2nd indicator of “1” to indicate it’s about publisher, and the copyright 264 is in a separate 264, with 2nd indicator number “4”


2.15 Identifier for the ManifestationThe instructions for Identifiers have not changed much from AACR2 except the definition of an identifier is now broader. In AACR2, any “identifier” other than an internationally agreed one (such as ISBN) was recorded in a note and not seen as a formal identifier. RDA now defines the identifier as:

ISBN, ISSN, ISMN etc.

URN (though not URL)*

Numbers assigned by the publisher, govt. pub, archival, etc.

*URN = Uniform Resource Name (URN) is intended to serve as a persistent, location-independent resource identifier. It is like a kind of “ISBN” for websites.

*URL = Uniform Resource Locator (URL) is simply the address of a website and may change over time. This is why it is not considered as a standard identifier. Recording URLs is covered at 4.6

If there is a prescribed display for an identifier, use that format. If not, record it as it appears on the resource

Because we are using MARC we still need to use the encoding conventions of the encoding scheme that we are using.

Therefore, for our Killers in Eden example the ISBN is still recorded without the hyphens

Other identifying elements The remainder of Chapter 2 contains instructions on other identifying elements for manifestations and items.

Manifestations

Series 2.12 Mode of Issuance 2.13 Frequency 2.14

Handbook: Page 55


Preferred citation 2.16Items

Custodial history (provenance) 2.17 Item identifier (eg holdings) 2.19 Immediate source of acquisition 2.18

NotesIn AACR2 Notes served two purposes:

Expand on information recorded in other elements and;

Provide information that didn’t fit in the other elements.

A lot of disparate information was recorded in Notes fields with little to distinguish the different types of information that was being recorded.

Though MARC does differentiate some areas a 500 note could contain information about the physical characteristics, content, form, relationships to other entities, provenance, ownership and subjects of resources.

In in RDA many things AACR2 instructed us to record as notes now have their own element, so any “Notes” instructions in RDA largely serve as a means of recording extra information about these elements (eg. Source of title, changes in imprint information, complications with serial numbering).

The instructions on notes are within the chapters for the elements to which they relate.

– Identifying Manifestation/Item 2.20

– Describing carriers 3.20

Not every chapter has a “notes” section.

If there is something you are used to placing in a note but you can’t find an instruction marked “Notes” it probably means it now has its own element in RDA.

For example, most of the information in Chapter 4 and Section 2 of Chapter 7 was in “Notes” sections of AACR2, but are now divided in separate elements.

For now, some of the information will still be recorded in a 5xx field in MARC because MARC still doesn’t have the elements of RDA.


Exercise 8: Cataloguing exercisesRecording attributes of manifestations and items (chapter 2)

Note for trainer: To limit the number of different questions that might arise during this exercise use resources that are similar – eg Mills and Boon, Government Reports. This will ensure trainees will have similar questions rather than lots of different questions. This suggestion arose out of time constraints of the course.

We will use Mills and Boon in print

Using the marc template provided record the following elements as appropriate:

a) Title proper and other title information

b) Statement of responsibility

c) Edition

d) Publication details

e) Identifiers

Note: Some Mills and Boon publications have Mills ♥ Boon. See 1.7.5 for instructions on recording symbols

Handbook: Page 163 - 164

Killers in Eden example is on Page 65 of the Handbook


Chapter 3 of RDA

Chapter 3 concerns attributes of manifestations that describe the physical characteristics of the resource.

Users rely on these attributes to help them decide if the resource is in a form that meets their needs in terms of the physical characteristics of the carrier or formatting or encoding of the information within the carrier.

These attributes also help with identifying resources.

Chapter 3 contains the instructions for media and carrier types.

The vocabularies for the terms are closed lists; that means you only use the terms in these lists. If more than one term is appropriate you can either use multiple terms or just assign the term representing the predominant or most substantial aspect. If no term is appropriate, give “other” as the term. If you are unable to determine what type is applicable you can use “undetermined”.

In the MARC fields for these elements the RDA term is recorded in subfield $a. Coding in subfield $2 indicates that the term used in subfield $a is an RDA content, media or carrier term; Subfield $3 is used if the term recorded in the field only applies to a part of the resource, to specific which part.

A subfield $b can also be added which contains a machine readable code established by MARC to go with the RDA term. These are listed in Term and Code lists for RDA Content, Media and Carrier terms, which can be found under “Other Value lists” on the Main MARC page (www.loc.gov/marc/ ). The link to these is in Appendix 1 your workbook under standards.

How these fields appear in the OPAC depends on the individual library and the OPAC they use. Some libraries will use icons rather than display the fields or will use the information as limits for searching.

Handbook: Page 58

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


3.2 Media TypeMedia type is a broad categorization of what type of device, if any, is needed to be able to see, hear, etc., the content of the resource.

Media Type is recorded in MARC field 337.

3.3 Carrier typeCarrier type gives more specific information about the format, housing, and type of device needed if any. Carrier type is given in MARC field 338.

Carrier type is that it is a separate element to the “Extent”. Extent is still recorded and is still in MARC 300 subfield $a.

It can be easy to confuse them because some of the terms you see in the Carrier Type list are the same as what we are used to recording in the 300 $a

6.9 Content typeContent is actually not covered in Chapter three, because it is an element of expression not manifestation, but they are grouped as the suite of elements that has replaced the GMD.

Content type tells the user how the content of the work is expressed: form of communication and which human sense is used.

Here is the content, media and carrier types for our book Killers in Eden:

- the content type in the 336 field is “text”

- the media type in the 337 field is “unmediated” because a book does not need a device for the content to be read


- the carrier type is “volume”

Exercise 9: Continue cataloguing exercise:

Add content, media and carrier types to the marc template for your resource started in the previous exercise

Extent 3.4Extent is the element that tells the user what kind and how many physical or logical units/subunits there are.

Extent in RDA covers what many cataloguers currently know as the Specific Material Designation - the MARC 300 $a subfield.

Extent is core, but only if the resource is complete or if extent of the complete resource is known.

There is similarity between “Extent” and “Carrier Type” but we need both as the information serves different purposes.

The Carrier Type terms are a controlled list to allow consistency for data sharing between online collecting communities. The Extent area is about describing the resource meaningfully for users and allows cataloguers more freedom in how that information is recorded.

The general instructions at 3.4.1 say to give the number of units/subunits, and an “appropriate term” for the type of carrier. The term can come from the Carrier type list at 3.3.1.3 (hence the confusion), or can be another term chosen by the cataloguer or a common use term preferred by your institution.

These are the general instructions. There are also several categories of resources covered by exceptions in RDA 3.4.1.3, including text, which we are used to having as the default instruction in AACR2 not the exception!

These exceptions have their own specific instructions and in some cases their own official lists of terms with little or no reference to the Carrier Type lists. So in many cases, the Extent term and the Carrier Type term will be different.

Handbook: Page 156-157

Handbook: Page 60


There are some general changes in Extent from AACR2. Abbreviations, Latin terms, and square brackets will no longer be used when recording extent in MARC 300 $a. These changes will make it easier for the user to understand the information.

There are also some changes in the terms that we’ll use in 300 $a. Some have moved to the Carrier Type list, while others are new or changed from AACR2. So it is a good idea, especially during the transition, to make sure you check these lists closely, to ensure you are using the right term in the right context.

Examples

This slide shows Extent in the 300 subfield $a and the Content, Media, and Carrier types in fields 336-338.

The 1st example is a book

In the 2nd example a term from the Carrier list “audio disc” is used in the Extent. The 300 $a and 338 $a have the same term. But the cataloger could have recorded the Extent in 300 $a as “1 CD.”

In the 1st example, the cataloger chose to use “1 DVD” in Extent rather than use the term “video disc” from the Carrier type list.

The 2nd example illustrates the extent for an online resource; in AACR2 the rule in chapter 9 is not to give extent for an online resource although there is an option that allows it. In this example the cataloger decided to use a term from the Carrier list as the term in Extent; the result is that the terms in 300 $a and 338 $a are the same.


This example shows the 336 field repeated for the different content types on the Web site.

Subfield $a is repeatable so it is also possible just to repeat subfield $a in a single field if all the terms are from the same vocabulary identified in subfield $2. For the RDA Test, we’ll always use the RDA vocabularies identified here in subfield $2 with these names.

3.5 DimensionsThe next element in Chapter 3 is the dimensions of the carrier and/or container of a resource. This is the information that goes in the MARC 300 $c subfield. This area is fairly straightforward, and has not changed much. There are general instructions at 3.5.1 and then specialist instructions for Maps (3.5.2) and still images (3.5.3). Note that dimensions of print material are again way down the list at 3.5.1.4.14, again demonstrating the de-emphasising of print materials in RDA.

There a couple of important things to highlight:

The RDA default measurement system for all resources is metric. This is not a change for us in general, except that this means it applies even to compact discs, which we have been measuring in inches, and manuscript collections which some institutions measure in linear feet (NLA uses metric).

There is an option to use your institution’s own measurement system, and LC has adopted this for computer discs and tapes of moving images, which they will continue to record in inches.

Another thing to note is that we will still use “m”, “cm” and “mm” in the same way we have been. This is because in the metric measurement system they are regarded as symbols, and not abbreviations.


Exercise 10: Continue cataloguing exercise

Add extent and dimensions to your resource

3.6-3.22 Other physical characteristicsThe rest of Chapter 3 contains instructions on other physical characteristics, most of which would go in the MARC 300 $b and notes fields. This does not include illustrative matter as that is consider to be an expression attribute, so we will look at that in the next module.

Characteristics covered in this section include system requirements, sound and video characteristics, etc. and item specific characteristics such as condition of item and imperfect holdings of serials. None of the elements are core elements, though LC and NLA have listed a couple of them as mandatory for cartographic materials.

During transition check the marc to RDA mappings to get familiar with the fields these belong in

Chapter 4The attributes covered in this chapter are concerned with access to and acquisition of resources, at both the manifestation and item level. They cover such things as terms of availability, contact information, holdings, access conditions, and URLs for website resources. We won’t go into this chapter in detail, as the instructions are not very different to what we’ve been used to. None of the elements in this chapter are core elements, though LC and NLA have marked some of them as mandatory.

Summary

Handbook: Page 163


Completed Example and exercises

Killers in Eden by Danielle ClodeRDA Reference

RDA Element

Notes MARC field

Data Recorded

1.5 Type of description

Comprehensive description

2.13 Mode of issuance

Single Unit Leader

2.2 Sources of information

Resources consisting of one or more pages…

1.7

2.3.1.4

2.3.2

General guidelinesRecording titlesTitle proper

Guidelines for transcribing titles

245 10 $a Killers in Eden

2.3.4 Other title information

Not core 245 $b the story of a rare partnership between men and killer whales

2.4.2 Statement of responsibility

245 10 $c Danielle Clode

2.5 Edition statement

Two full-stops in ISBD. Only one need for MARC systems

250 $a 2nd ed.

2.8.2 Place of publication

260 $a Melbourne, Victoria

2.8.4 Publisher 260 $b Museum Victoria2.8.6 Date of

publication260 $c 2011

2.11 Copyright date

Not core 260 $c ©2011

2.12 Series2.15 Identifier 020 $a 97809806190896.9 Content type 336 $a Text3.2 Media type 337 $a Unmediated3.3 Carrier type 338 $a volume3.4.5 Extent 300 $a 156 pages3.5 Dimensions 300 $c 24 cm


Mills and Boon Example Records

RDA Referenc

e

RDA Element

Notes MARC field

Data Recorded

1.5 Type of description

Comprehensive description

2.13 Mode of issuance

Single Unit Leader



1.7

2.3.1.42.3.2


Guidelines for transcribing titles

245 10 $a Prince of scandal


No other title on resource

245 $b

2.4.2 Statement of responsibility

245 10 $c Annie West


Transcribed as on resource

250 $a First Australian paperback edition

2.8.1.4

2.8.2

Place of publication

Transcribed as on resource

260 $a Chatswood, NSW

2.8.4 Publisher Take from same source as title proper1.7 transcribing symbols

260 $b Mills [rose device] Boon

2.8.6 Date of publication

260 #1$c 2011

2.11 Copyright date

Not core 260 #4$c © 2011

2.12 Series 490 0# $a Sexy2.15 Identifier ISBN – omit

dashes in MARC

020 $a 9781742770307

3.2 Media type 337 $a Unmediated3.3 Carrier type 338 $a Volume3.4.5 Extent 300 $a 185 pages3.5B.5.2

Dimensions 300 $c 17 cm

6.9 Content type 336 $a Text


RDA Ref-erence

RDA Ele-ment

Notes MARC field

Data Recorded

1.5 Type of de-scription

Comprehens-ive descrip-tion

2.13 Mode of is-suance

Single Unit Leader



1.7

2.3.1.4

2.3.2


Guidelines for transcrib-ing titles

245 14 $a

The hot-blooded groom


No other title on resource

245 $b

2.4.2 Statement of responsibil-ity

245 $c by Emma Darcy


250 $a First Australian paperback edition

2.8.1.4

2.8.2.3

Place of publication

264 #1$a

Chatswood, NSW

2.8.4 Publisher 264 $b Harlequin Mills [rose device] Boon

2.8.6 Date of pub-lication

264$c 2001

2.11 Copyright date

Not core 264 #4$c

© 2001

2.12 Series 490 0#$a

Passion

2.15 Identifier 020 $a 07335310083.2 Media type 337 $a Unmediated3.3 Carrier type 338 $a Volume3.4.5 Extent 300 $a 185 pages3.5

B.5.2

Dimensions 300 $c 17 cm

6.9 Content type 336 $a Text

teaching rda: day 2 - nla web viewso always check which word has been used. ... note: some mills and...

Documents