1. MARC 21, FRBR, RDA
Review terminology (especially for non-native English speakers)
Conceptual models
Elements
Attributes
Future: Probably not a bib record, but the information will be there and can be assembled for displays in response to a user’s search or packaged for export as a record at the click of a button
RDA covers all formats – all kinds of things we have now or can anticipate having into the future – not arranged by the type of materials, but instead by the identifying characteristics that we want to bring out about the things we are cataloging. You will be applying RDA to the regular materials you have to catalog.
A book, a CD, and a film could embody/contain the same work – such as the story of one of the Harry Potter stories. We can use identifying information from that work to bring together all of the resources we have in our library that contain that work. We can also use expression level information to sort or filter our search of those resources – for example, by language. And we can use manifestation information to help meet the user tasks of identifying and selecting – for example:
to identify the resource we want, we include the elements of its title proper and statement of responsibility and publishing information
to select the resource we want, we include the carrier type, such as a volume or a videodisc 1

2. Objectives
Connect MARC fields and subfields to the appropriate entity and attribute of FRBR
Recognize how RDA uses MARC
You might be wondering what this course is about.
There was confusion during the US RDA test during October-December 2010 about how to apply an RDA instruction in MARC.
The history of MARC was closely intertwined with the Anglo-American Cataloguing Rules – both of which started in the late 1960’s – both to create printed catalog cards to file in our catalogs at that time. We’ve been cataloging with AACR and MARC for so long, we often think of an AACR2 rule or ISBD statement by the MARC tag or subfield number – for example, a “statement of responsibility” is a 245 $c.
MARC still remains very closely tied to the printed catalog CARD environment, even though we have founds ways to use the data in MARC records in online catalogs.
But RDA is fundamentally different, due to the FRBR structure of entities and relationships. We will still need to use MARC for some time to come, so we need to look at MARC again with the FRBR idea in mind, what piece of information am I recording? Where does it need to go?
We covered FRBR in earlier sessions to give you an overview of the basic conceptual model and what things we are talking about in our bibliographic universe and how they are related and how we identify them (with data elements), but because MARC is the way in which we encode the recorded information, we will focus our attention in this session on RDA data in the MARC Format instead of focusing exclusively on expressing FRBR in MARC. 2

3. What is the difference? FRBR is a conceptual model
How information is described and organized
RDA is a content standard (as is AACR2)
What information is recorded and how
MARC is a communication format
Computer code to consistently handle the data recorded
They are not the same thing
Be careful of your vocabulary
MARC was created to be a carrier – a communication format for information needed to print on a catalog card or to exchange bibliographic data with other libraries. It was never meant to be a record of the rules themselves.
Be careful of your wording. Don’t use a MARC field code to refer to an RDA instruction– you are setting yourself up for confusion. Some people do this with AACR2, and it can cause trouble. For example, the 245 $a is not the title proper, it is a container for the title proper in AACR2, and also in RDA it is a container for the title proper from the Manifestation but also can be an inferred preferred title of the Work. Actually $a is a portion of the title proper – it could also include the part information in $n and $p when that applies.
The numbers and subfield codes in MARC are there for the computer, not really meant for us humans. But the coding has become a shorthand for identifying the bibliographic and authority data that we need to record.
As this slide shows – FRBR is a conceptual model that describes the things of interest to libraries, how they are identified and related; RDA is the content standard to instruct us about what information we need to identify and relate the entities of interest and MARC for now is the package where we put the information. 3

4. MARC field ≠ RDA instruction
MARC fields are containers for content
Not a one-to-one relationship to a specific RDA instruction
RDA describes content to be recorded that sometimes ends up in different fields
There is not always a one-to-one relationship between content to be recorded and the field or subfield where we need to record it. That’s why we cannot just say an RDA element and know which MARC tag it is – sometimes there may be more than one There are some consistent associations for many fields, but not always.
With RDA we are adding more labeled attributes (elements) and relationships in our bibliographic and authority data for users now and in the future. And we expect this data to be re-used for many different kinds of displays – not just the typical ISBD citation in a linear display. 4

5. MARC data What does the MARC bibliographic record contain?
A “mashup” of WEMI and sometimes also person/family/corporate body information
What does the MARC authority record contain?
Identifying information for the described entity (person, family, corporate body, creator/work/expression), including the “authorized access point” to be used in the MARC environment
This means that information for different parts of a MARC record are found in very different parts of RDA. Once you know what entity you are actually describing and what identifying data or “element” you want to use for identification of that entity, you will know where to look it up in RDA, but you won’t know this well if you start with the MARC code.
We saw in the earlier sessions how the MARC record contains bits of information about the contained work and expression as well as describing the manifestation and also can include data about the specific item that we hold in our collection. This “mashup” of information in a MARC record can be a barrier to helping us understand RDA and how it can be used. In the long run, RDA will be better than AACR2, but right now, MARC makes it somewhat difficult both to see and to properly take advantage of the structure of relationships that RDA offers. It isn’t all MARC’s fault, of course. There is also the factor of how systems use MARC records, and shortcut practices that leave out relationship information also contribute to the problem.
MARC authority records will mostly be for all the identifying information for the Group 2 entities: person, family, corporate body; but also will be used to record work and expression information – for now think of the “uniform title” authority records we created under AACR2. However, we often will just document the contained work and expression through data in the bibliographic record. 5

6. Change in RDA from AACR2/MARC-thinking
No “main entry” in RDA
No “entry under” a heading in RDA
One of the big changes is that with RDA the idea of “entry under a heading” disappears – so the MARC 1XX fields for the “main entry” in RDA just become a place to identify the creator of the contained work – not more important than other identifying characteristics, but can be used to order displays of citations. The MARC record is a container for the various elements – the identifying characteristics of many of the FRBR entities – work, expression, manifestation, item, person, corporate body, and so on. Let’s see how that works.

7. MARC bibliographic record and FRBR Entities: summary
1XX = person, family, corporate body, work, expression
130/240 = work, expression
, 490 = manifestation
300 = expression, manifestation
other 3XX = work, expression, manifestation
5XX = work, expression, manifestation, item
= person, family, corporate body, work, expression
= related work, expression, manifestation
8XX = work, expression, manifestation
Here is a summary view for you as a reminder of where information on different Group 1 and Group 2 entities can be found now – identifying elements as well as relationships.
The 1XX is usually for the related creator of the work (a person, family, or corporate body in a creator relationship to the work), but sometimes also can include the preferred title or other elements of the work and/or expression.
The and 490 series statement is mostly transcribed data, which is manifestation information.
The 300 is a mixture of data about the physical item (manifestation) – its extent in $a, its dimensions in $c,
but it also includes some expression elements, such as the artistic content – illustrations – in $b.
Notice in the note field – 5XX, we can have elements describing an item. It is not common to have item-level information here for most records, but it does happen often enough that it should be mentioned – for example to note an autographed copy or something else special about the copy we hold.
The fields are where we can record relationships to Group 2 entities or works or expressions,
likewise for the relationships in the
and the series connections in the 8XX, but as you know, now LC does not include that controlled series data. You are likely to find it on copy cataloging.
Slide modified from Judy Kuhagen’s Module A presentation on RDA 7

8. Example 1A: Identify the FRBR entity and attribute
Creator of Work (relationship) 1
Title of Work 2
Language of Expression 3
Title of Manifestation 4
(LCCN )
Notice in a concentrated few fields, I have information on work, expression, and manifestation, as well as a relationship expressed (Creator in the 100 field). And I would add that these are some of the most important fields in RDA, as they are essential to the user task “to identify”.
Note that in the 100 field, we not only have the name of the creator, but also a relationship designator in the $e – author – that’s from Appendix I in the RDA Toolkit.
COIN 8 8

9. Example 1B: Identify the FRBR entity and attribute
Other title information of Manifestation 1
Statement of Responsibility of Manifestation 2
NOTE: “Other title information” is not specifically listed in FRBR as part of a “Title of manifestation”, but it is most certainly included in RDA (2.3.4) as an element to identify the manifestation.
The 245 information about this being an English translation is a relationship to the original work and reflects that we have a new expression.
Note of Translation (relationship) Expression 3
COIN 9 9

10. Example 1C: Identify the FRBR entity and attribute
Publisher, Pub Place, Pub Date of Manifestation
Extent & Dimensions of Manifestation 2
Subjects of Work (relationship) 3
The 1XX and 7XX also are where we record other kinds of relationships, but not always. For the 7XX in particular it’s important to use the relationship designator to show what the relationship is. So, in this example, we have 700 $e translator. We could also add $e illustrator for the photographer who provided the illustrative photos – notice we’d not treat him as a co-creator, because these photos are intended to illustrate the crocheting techniques.
However it is important to note that we do not have to indicate what the specific relationship is (optional – but highly encouraged) – all that is required is to show that the relationship exists.
Translator of (relationship) Expression 4
COIN 10 10

11. Example 1D: Identify the FRBR entity and attribute
Index as Supplementary content
Expression 1
Note with Summary of content
Expression 2
COIN 11 11

12. Conclusions
One bib record has attributes from many entities of the FRBR structure
Attribute data (identifying characteristics of the entity) may be in a subfield or a field in a MARC record
So what can we conclude from these observations?
A MARC bibliographic record includes data identifying many FRBR entities – the Group 1 entities of work, expression, manifestation, and sometimes item, as well as sometimes the persons, families, corporate bodies – and relationships.
We also have seen that the identifying characteristics – the attributes, or as RDA calls them, the elements may be stored in a MARC record in a subfield or a field.
We will do our best to put the information where we can in MARC records for now. 12

13. What about the 008? Attribute information is also recorded in the 008
Repeated information and new information
Here we have some new information, but mostly repeated information in the 008.
The publication date and the copyright date of 2011 is old information.
The index code and the language code is repeated information from other fields in the bib record. What entity do I identify when I say what language? Expression
And the fact that there is an index included, identifies a component of this particular expression of the work.
What other types of information do we often see here in the 008?
What entity/attribute does it belong to?
EXAMPLE 1E 13 13

14. What about the 008?
Other attributes that may show up in the 008: illustrations, target audience, etc.
Illustrations: Expression attribute illustrative content
Target audience: Work attribute intended audience
EXAMPLE 1F 14 14

15. What about the 008?
Other attributes that may show up in the 008: conference publication
(LCCN )
Here is another example from a different bibliographic record. This one is for a conference publication.
EXAMPLE 1G 15 15

16. What about the 008?
Other attributes that may show up in the 008: Festschrift
(LCCN )
And here is another example from a different bibliographic record. This one is for a Festschrift.
EXAMPLE 1H 16 16

17. 008: What entity or attribute is it?
Target audience (juvenile)
Nature of contents
Illustrations (optional)
Date
Place of publication
Gov publication
Work
Expression
Expression
Work, Expression or Manifestation
Manifestation
These are the fields that are most commonly used for monographs. What entity/attribute is it?
Most of the time, the date info is manifestation information, that is standing in for the work and expression – because we probably don’t know the actual date when those ideas came to the creator or when they were first expressed other than when they appeared in the first manifestation..
Manifestation 17

18. 006 & 007 : What entity or attribute is it?
006 Additional Material Characteristics
Manifestation level
If basically same as 008, then can be work/expression information
007 Physical Description
For the 006 and 007 – we’ll go over this very quickly – these will be important for those of you dealing with special sessions on non-book materials.
If we are dealing with the physical resource and have a physical characteristic that applies to all copies of that resource, we are identifying the manifestation. 18

19. So, now what?
So, now we will look at specific fields that may offer challenges as we apply RDA
Now that we’ve taken a general look at the information that is found in a bibliographic record, and connected to the appropriate FRBR entity/attribute, let’s consider how things are changing. 19

20. Fields with things to note
1XX, 7XX fields can use the $e or $i subfield (relationship designators)
130 for the contained work
-may be seen more, with qualifiers to break title conflicts in some cases
-will be seen less for some compilations
240 may be used in places it wasn’t used before for some compilations
Although AACR2 allowed them and MARC Format has had the $e as the place to put them, the relators – or as RDA calls them, the relationship designators now take on greater importance to show relationships.
In the bibliographic records, they can be added to the 1XX or the 7XX fields.
RDA requires us to identify the contained work – the intellectual or artistic content, so we may see more use of the 130 for the preferred title of the work and possibly expression level data, like language – or that information could be placed in a 7XX field. 20

21. 130 with qualifiers?
This work is a prime example of when we are going to have to break conflict where before we did not. The publisher for the Grum award for the best new Slovenian play apparently likes to use the exact same title for each year it publishes. How helpful. The year isn’t in there, but we still want to indicate to our user that these are different plays are in each year’s published award. So here we use the date of the award as the way to break the conflict and add it into a 130 as a qualifier. What attribute is it? Other distinguishing characteristic of the Work.
EXAMPLE 2

22. 130 or 240 field
New title proper, not revised = new manifestation with 240 for the original work’s “preferred title” (same as AACR2)
Same title proper, but revised content = new expression: no 240 needed (same as AACR2)
New title proper, revised content = new expression plus 240 for the original work’s “preferred title” (NOT same as AACR2)
500 &/or 775 option for earlier edition, NOT title or name/title added entry (NOT same as AACR2)
It’s best not to use the 780 for these expression differences.
We suggested using the 775 in the special topic session on related editions. 22

23. 240
Here we have Macroeconomics by Breedon, Miles, and Scott. It’s the 3rd edition – which is a new expression – do you see why? RDA chapter 6 is for works and expressions and we find (for a new edition, treat as a new expression and use the authorized access point of the previously existing work) – so when we search online <CLICK> we find the 2 earlier editions – with Miles as the 1st named creator. NOTE: the third edition has a new first-named author. Because we are now looking at the WORK as being established from the first manifestation of it, we maintained the authorized access point from the original’s first-named author.
In RDA , last paragraph, RDA says if the order alone changes, go with the order of the first one received. (This is also covered in the special topic session for revised editions.) – So what about the preferred title of the work? Does this one need a 240? The answer here is no, it does NOT need a 240, because the title proper of the third edition – a new expression – matches the title of the first edition, the first expression that established the preferred title for this work. So here the 245 is doing double duty as identifying both the work’s preferred title and also providing the title proper of the manifestation.
Only the second edition had a different title, therefore it is the one that would require a 240 under RDA in order to relate it to the contained work and enable collocation of all the various manifestations of that work. (Under AACR2, it got a note and a 700 related work added entry.) <CLICK>

24. 240
Animation: the search screen fades in on one click, then fades out on second click, once you have pointed out the difference in titles between first, second, and third edition/expression. EXAMPLE 3A and B
Here we have Macroeconomics by Breedon, Miles, and Scott. It’s the 3rd edition – which is a new expression – do you see why? RDA chapter 6 is for works and expressions and we find (for a new edition, treat as a new expression and use the authorized access point of the previously existing work) – so when we search online <CLICK> we find the 2 earlier editions – with Miles as the 1st named creator. NOTE: the third edition has a new first-named author. Because we are now looking at the WORK as being established from the first manifestation of it, we maintained the authorized access point from the original’s first-named author.
In RDA , last paragraph, RDA says if the order alone changes, go with the order of the first one received. (This is also covered in the special topic session for revised editions.) – So what about the preferred title of the work? Does this one need a 240? The answer here is no, it does NOT need a 240, because the title proper of the third edition – a new expression – matches the title of the first edition, the first expression that established the preferred title for this work. So here the 245 is doing double duty as identifying both the work’s preferred title and also providing the title proper of the manifestation.
Only the second edition had a different title, therefore it is the one that would require a 240 under RDA in order to relate it to the contained work and enable collocation of all the various manifestations of that work. (Under AACR2, it got a note and a 700 related work added entry.) <CLICK>

25. 130/240 field $s (version) – some PCC and others, but limited LC use
$a Ṭeṿye der milkhiḳer. $l English $s (Katz)
[English translation by Miriam Katz of Sholem Aleichem work]
$a Ṭeṿye der milkhiḳer. $l English $s (Halkin)
[English translation by Hillel Halkin]
$o is spelled-out in musical works
$a Piano music. $k Selections; $o arranged
This slide is here to alert you that we will see these subfields when we get copy cataloging. The $s for version may be used more by some PCC libraries, but LC will limit the use to differentiation of expressions for a small subset of categories.
For the $o for arranged – no more abbreviations of arranged. RDA usually avoids abbreviations and here would spell out “arranged” – however this RDA instruction is being proposed for revision, so may be changing in the future. 25

26. Fields with things to note
300
Repetition of the field
$b for illustrative content is now optional except for resources intended for children (Expression attribute)
use of $e (not new, but possibly more frequent)
recording duration for Music (Expression attribute)
5XX
500 – more variety of information
502 – we now use subfields instead of just text
505 – more frequent usage
546 – not just for language; non-roman uses it for script; music uses this for form of musical notation
Here are some of the fields that will be done differently with RDA for most records.
The 300 field is still fundamentally doing the same task, but it is being used with more flexibility than before, because now it can be repeated for multimedia resources. If you have a book and a CD, then each format can have its own 300 field, as well as its own 33X fields (for type of content, media, and carrier). Or you can use the $e subfield (accompanying material), as we have done before. Or you can fall back on the 5XX note to record the other types of media (prefer not to use this).
I would also point out that the 300 field overlaps the 33X fields somewhat, because it records the more specific pieces of information that the 33X’s have already told us about. So when the 336 says text and 338 says volume, the 300 $a tells us how many pages in that volume. When the 336 says spoken word and the 337 says audio and the 338 says audio disc, the 300 $a tells us that it is a CD-ROM specifically. This is actually good, in case you were wondering, since audio disc technology will undoubtedly change in the future. Taken together, all these pieces of information will allow the computer to narrow or broaden the searches for the users based on different questions. Next are the notes fields – the 5XX’s
502 for dissertations now have specific subfields, 505 contents (whole/part relationship to identify the parts), 546 for languages and the script or notation
5XX uses that have not changed:
504 for bibliographies and indexes
520 (and 856) – summarization of content for children (not new) You may also remember the $3 – as in the 546 – is used to cite the materials covered by the language note. $3 is defined for many fields where you need to say something about just a part of the resource. 26

27. 3XX fields repeated 300 repeated for the parts Content Type Media Type
Carrier Type
Note the parallel 300’s (mix of expression – illustrations; and manifestation information – extent – 368 pages and 1 DVD-ROM; and dimensions – 27cm or 4 ¾ in.
as well as the parallel 336, 337, 338 fields. (LCCN )
EXAMPLE 4

28. Fields with things to note
7XX is used in many more ways, though many of them are optional
The use of the $e or $i subfield to describe relationships
700/710/711/730/740 : not truly different
7XX name/title entries used more for some compilations
Linking fields offer many more options
Here are some more the fields where RDA brings changes for most records.
A fundamental approach of FRBR sees the individual works contained in a publication as separate entities. We have an LCPS requiring that we only identify the first work, but it’s up to cataloger’s judgment to add more.
Our LC policy allows using $i for the relationship designator, but we don’t need to use it when the field or the indicator already tells us the relationship – like 1XX is the creator – and remember the linking entry fields…. 28

29. Fields with things to note
7XX linking fields
Serials use is unchanged
Now available
775: Other edition (i.e., other expression)
776: Additional physical form entry (i.e., other manifestation)
Can be used to express FRBR relationships, especially the content relationships, such as adaptation of, contains (expression), reprint of, revision of, etc.
Use the $i subfield
Found in RDA Appendix J
For serials, the usual fields for preceding and succeeding titles are 780 and 785, which are essentially earlier/later relationships.
NOTE: the $i subfield is available for all of the 7XX fields, except the 780 and 785 for serials, as those have very specific display constants generated by the indicators.
The 775 (other edition)/776 (added physical form) fields have indicators 1st indicator=0 and 2nd indicator=8 with the use of the $i subfield.
The batches have the 1st indicator based on name type or filing indicators for title, and 2nd indicator is analytical vs. related added entry.
There are other 7XX fields, but these are the ones you will most often encounter.
Recording these types of relationships are definitely cataloger’s judgment, but it certainly enhances the record. And we want to make it easier for you to use them, when your judgment so decides.
Types of work relationships possible are found in Appendix J of RDA: a general “related”, derivative, descriptive, whole/part, accompanying work, sequential work and expression relationships, which include all of those used for works, and then we have the equivalent manifestation and various item relationships. 29

30. 775 in action
Here the 775 is linking the described resource to a previous publication (manifestation). Notice the $i used for the relationship designator from RDA Appendix J.
EXAMPLE 5

31. 776 in action
Note that this is a web resource that is linking to the print version, so the user can find both.
(In order to fit this on the page, I deleted several 6XX fields for the screenshot, so the actual record will look different.)
EXAMPLE 6

32. New bibliographic fields
Closed vocabularies (RDA/ONIX Framework)
Repeat the field rather than repeat the $a (term) (LC policy)
$3 (Materials specified) is your judgment
$b (code) is pass-through element (LC policy)
Same information may be found in 300 or 500 with different details
336 : (RDA 6.9) Content type 337 : (RDA 3.2) Media type 338 : (RDA 3.3) Carrier type
$a will be the place to put the RDA term and $b is the corresponding code – which we do not need to include, but would pass through any found on copy cataloging.
Notice that the 338 would use the controlled vocabulary of “computer disc” from the types of carriers, but we could have a 300 field or a note using a more informal term, such as saying 1 DVD-ROM.
$3 Materials specified
338 ##$asheet$2rdacarrier$3liner notes
Use if helpful to specify which component the data applies to
EXAMPLE 7 32

33. Turning to the authority record
RDA tells us what to record, a little about how, nothing about where to record it
LC policy tells us more about how and definitely where
Name attributes are now being recorded in many distinct fields, as well as the 670, by cataloger judgment
Specific attributes used to break conflict are still additions in the authorized access point (1XX)
Okay, we’ve been concentrating pretty intently on the bibliographic fields, since they have the biggest struggles in fitting the specific RDA elements into the MARC changes.
In the authority record, we will be recording a lot more information than before, and most of it is in new fields, so it doesn’t cause the same kind of confusion as in the bib record, where we are often subtly changing how we are using the fields we already have.
Remember that RDA is the content code, telling us what to record: the content or data that we are gathering to identify the resource – and whether that is transcribed as we find it for bibliographic data or recorded from information readily available to the cataloger, or should be supplied by the cataloger.
Where we record it is governed by the MARC Format and LC Policy. 33

34. New authority fields
046 : associated dates (Work, Expression, Person, Family, Corporate Body)
336 : content type (Work, Expression)
370 : associated place (Work, Expression, Person, Family, Corporate Body)
371 : address (Person, Family, Corporate Body)
372 : field of activity (Person, Family, Corporate Body)
373 : associated group (Person, Family, Corporate Body)
374 : occupation (Person, Family, Corporate Body)
375 : gender (Person)
376 : family information (Family)
377 : associated language (Expression , Person, Family, Corporate Body)
The next few slides show you the new authority fields to accommodate some of the RDA elements to identify entities. 34

35. New authority fields, continued
380 : form of work (Work)
381 : other distinguishing characteristic of work or expression (Work, Expression)
368 : other person and corporate body attributes
378 : fuller form of personal name
382 : medium of performance (Work)
383 : numeric designation of a musical work (Work)
384 : key (Work)
368 : a place to put qualifiers to corporate body names when the name does not indicate it’s a corporate body
EXAMPLE 8B

36. Fields with things to note (authority records)
111 : ongoing conferences – individual authorities for each one with qualifiers (change for monographs); continue without qualifiers for serials
100 $q : LC-PCC practice on optional addition
378 : can record fuller form even if not needed in 100 $q
LC-PCC PS for : LC practice/PCC practice for Optional addition:
New Authority Records: Apply the option to provide a fuller form of name if a part of the forename or surname used in the preferred name is represented by an initial or an abbreviation, if the cataloger considers it important for identification. Add unused forenames or surnames only if needed to distinguish one access point from another.
Existing Authority Records: Unless otherwise changing an existing heading (e.g., conflict), do not change an existing AACR2 or RDA heading merely to add or remove a fuller form of name.

37. Relationships
Entities and attributes (“elements” in RDA) are found in the bibliographic and authority fields. Where are the relationships?
Given by the cataloger: 1XX & 7XX $e/$i, 7XX linking fields, 5XX text notes, 490/8XX
Transcribed from the resource: 245 $c
Sometimes not specified
Examples in authority records: earlier/later, links between persons/corporate bodies, etc.
Remember that FRBR is an entity-relationship model, let’s remind ourselves: how and where are the relationships expressed in MARC?
Part of the answer is that sometimes they are NOT made explicit. We have the relationships, but not always what that relationship IS.
Or sometimes it is implied – the 1XX is for the creator of the work – which is a relationship between the work and the Group 2 entity that created it.
Another example – we may make a 700 for a co-author, but unless we use $e, we have no way in MARC to say that person is also the creator.
Relationships will mostly be seen in bibliographic records, but they can also appear in authority records, for example earlier/later relationships, and relationships between persons and corporate bodies. 37

38. SUMMARY Work attributes found in what field
SUMMARY Work attributes found in what field? (bibliographic/authority record)
preferred title : 1XX $t, 130, 240, 245, 7XX $t
form of work : 1XX $t, 130, 240, 7XX, 380
date of work : 1XX $t, 130 $a or $f, 240 $a or $f, 046
other distinguishing characteristic of the work : depends on what the distinguishing characteristic is : 1XX $t, 130 $a, 240 $a, 381
intended audience : 008/22, 521, 6XX $v [Juvenile ...], NEW: 385 (not yet implemented)
key : 240, 130, 7XX, 384
medium of performance : 240, 130, 7XX, 382
numeric designation of a musical work : 240, 130, 7XX, 383
coordinates of cartographic content : 255
equinox : 255 $e
A date of work can be an addition to the preferred title, e.g., in a 130 $f – but is often inferred from the date of the manifestation in the 264 $c.
Notice that the same attribute can appear in multiple places in MARC , so MARC is not a one-to-one match with RDA instructions, as we mentioned before.
EXAMPLE 10 38

39. SUMMARY Expression attributes found in what field
SUMMARY Expression attributes found in what field? (bibliographic/authority record)
content type : 336
date of expression : $f of expression access point (usually), 046
language of expression : 008/35-37, 041, 546, 130/240 $l, 7XX $l
summarization of content : 520
other distinguishing characteristic : depends on the characteristic, 381
scale [Core for cartographic resources] : 255, 507
EXAMPLE 11 39

40. SUMMARY Manifestation attributes found in what bibliographic record field?
title proper : 245 $a $n $p
statement of responsibility for the title proper : 245 $c
edition statement : 250 $a
place of publication/distribution/manufacture/ production : 264 $a
publisher/distributor/manufacturer/producer : 264 $b
date of publication/distribution/manufacture/ production : 264 $c
series statement : 490
EXAMPLE 12A

41. SUMMARY Manifestation attributes found in what field? (continued)
carrier type : 338
media type : 337
extent : 300 $a
dimensions : 300 $c
identifier for the manifestation : 020, 024, etc.
mode of issuance : Leader/07
physical medium (base material, applied material, mount, generation, layout, book format, font size, polarity) : 340 various subfields
URL : 856
frequency : 310/321
note on changes in carrier characteristics : 500
There are also specialized fields for the attributes of restrictions on access – in RDA 4.4 and MARC field 506; and the restrictions on use in RDA 4.5 and MARC 540.
EXAMPLE 12B 41

42. SUMMARY Manifestation attributes found in what field? (continued)
digital file characteristics : 347
digital representation of cartographic content : 352
layout : 340 $k
equipment or system requirement : 538
There are also specialized fields for the attributes of restrictions on access – in RDA 4.4 and MARC field 506; and the restrictions on use in RDA 4.5 and MARC 540.
EXAMPLE 12C 42

43. SUMMARY Item attributes found in what bibliographic record or item record field?
restrictions on use : 5XX (also 845 in holdings format)
item identifier : barcode in item record
access restrictions on the item : 506
Only the restrictions on use is a core element for item, but we will include the item identifier – the barcode – in the Item record.
There also may be specific provenance and other item-specific elements for rare materials.
EXAMPLE 13 43

44. SUMMARY Person attributes found in what field
SUMMARY Person attributes found in what field? (authority/bibliographic record)
preferred name for the person : 100/700 $a
title of person : 100/700 $c, 670
dates associated with the person (birth/death/ period of activity) : 100/700 $d, 046
place of birth : 370 $a, 670
place of death : 370 $b, 670
associated country : 370 $c, 670
place of residence : 370 $e, 670
gender : 375, 670
Title of the person is given for royalty, nobility, or ecclesiastical rank or office of a term of address for a person of religious vocation
EXAMPLE 14A 44

45. SUMMARY Person attributes found in what field? (continued)
fuller form of name : 100/700 $q, 378
other designation associated with the person (for saints, spirits, persons named in sacred scriptures, fictitious and legendary persons, real non-human entities, etc.) : 100/700 $c
profession or occupation : 100/700 $c, 374, 670
EXAMPLE 14B 45

46. SUMMARY Person attributes found in what field? (continued)
affiliation : 373, 670
address : 371
language of person : 377, 670
field of activity : 372, 670
biography : 670, 678
undifferentiated name identifier : 008/32
other informational elements associated with the person : 670
EXAMPLE 14C 46

47. preferred name for the family : 100 $a
SUMMARY Family attributes found in what field? (authority/bibliographic record)
preferred name for the family : 100 $a
type of family : 100 $a, 376 $a, 670
date associated with the family: 100 $d, 046, 670
place associated with family: 100 $c, 370, 670
prominent member of the family: 100 $g, 376 $b, 670
hereditary title : 376 $c, 670
EXAMPLE 15 47

48. SUMMARY Corporate Body attributes found in what field
SUMMARY Corporate Body attributes found in what field? (authority/bibliographic record)
preferred name of the corporate body : 110 or 111 $a
number of a conference, etc. : 111 $n
place associated : 110, 111 $c, 370, 670
date associated : 046, 110, 111 $d, 670
associated institution : 110/111, 373, 670
other designation associated with the corporate body: 368
EXAMPLE 16 48

49. SUMMARY Corporate Body attributes found in what field
SUMMARY Corporate Body attributes found in what field? (authority/bibliographic record)
language : 377
address : 371
field of activity : 372
history : 678, 670
other information associated with the corporate body: 670
EXAMPLE 16 49

50. Exercises
Look at the handouts, and we’ll work through them to identify the entity and attribute of the different fields
Instructions for how to use the accompanying records in a class exercise.
There are two options for how to handle this exercise, depending on if you want independent or instructor-led exercises.
Independent work option
There are twelve records in this package. Assign twelve different groups/pairs/individuals to each record. Ask them to identify as many attributes and relationships as they can for the entire record, starting at the 010 and stopping with the 8XX. If they want to try, they can also attempt to identify the 008 fields in use. When bring the class back together, please ask them to identify at least five of those attributes in their specific field or subfield. An important question to focus on would be any attributes that appear in multiple locations, such as language.
Instructor-led option
Go through the packet of records as a group. The instructor will ask for individuals to identify specific attributes or relationships in specific fields/subfields from each record. How many you choose will depend on how much time you have and what attributes you want to point out or discuss.
Attached are the complete list of attributes for the WEMI entities.