RDA Authority Records in Voyager. Jenifer Marquardt (UGA) email@example.com And Julie Dyles (UGA) firstname.lastname@example.org. What we will cover. Fields, codes and example records Entire words versus abbreviations Family as author, creator, etc.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Jenifer Marquardt (UGA) email@example.com
Julie Dyles (UGA) firstname.lastname@example.org
“z” for other
|e Description conventions
|f is Birth date and |g is Death date
(Note that information comes from the 670.)
(Again, this shows up in the 670)
|a Place of birth
|b Place of death
|c Associated country
|f Other associated places
|g Place of origin of work
This is used for both postal and
|a Type of family (clan, dynasty, royal)
|b Name of prominent member
|c Hereditary title
(what is relationship between
the 4xx/5xx and the 1xx)
GIL Users Group Meeting 2011
In RDA, various changes have been made to the way that dates are recorded for persons (described now in AACR2 22.17):
The abbreviation “fl.” will no longer be used when a period of activity is known but the exact years of a person’sbirth and death are unknown.
It appears that “flourished” is another option in accordance with RDA rules. As of this time, there are no sample records in OCLC using “flourished” in the name heading.
Note that while AACR2 placed a time period restriction on using “fl.” dates (22.17A), there is no such restriction on recording time periods of activity in RDA.
Currently, “b.” is used when the year of death is unknown but the person is no longer living (LCRI 22.17), and “d.” is used when the year of birth is unknown but the year of death is known.
Other abbreviations that will be eliminated are thosein additions to titles of musical works. For example, the current abbreviation “arr.” …
Under RDA rules, families can now be considered contributors to and creators of works.
Distinct families can be given main entry on bibliographic records.
This means that separate records will exist for family names in LC/NAF and LCSH.
Note that this record is particularly for those Hammons that are from or have some connection with West Virginia, and that the 667 specifies it is invalid for use as a subject.
The name in the heading for the family should be in the established form of the heading for that name, but the delimiter d before the dates is not included.
RDA 8.1.2 defines a person as “an individual or an identity established by an individual (either alone or in collaboration with one or more other individuals).” While AACR2 21.6D1 also allows for main entry under shared pseudonyms, the scope statement at RDA 9.0 goes further in stating that personhood can include all fictitious entities.
This differs from AACR2 (21.4C1) which does not allow for fictitious entities to be treated as authors.
We might see something like this. Under RDA rules, fictitious entities can be established as name headings and represented as creators if they are presented as such on the resource being cataloged. The headings for these persons are not qualified by (Fictitious character).
Similarly, the Library of Congress Policy Statement relating to RDA 9.0 extends the scope of this rule to real non-human entities which have roles as creators or contributors. So while you currently see:
When will we see headings like this in our catalogs?Current LC policy states that until there is a decision aboutimplementation of RDA by LC, no changes of this kind will be made in the LCSH database. A list of subject headings like these is being compiled by the Policy and Standards Division for possible deletion if RDA is implemented.
What changes will you notice as more and more RDA records begin to come in to our catalogs?
So works about (or representing a version of) the New Testament or Old Testament would now have headings without the N.T. and O.T. abbreviations.
These popular Bible changes are likely to occur even if RDA is not fully implemented. So we will need to watch for these to appear in future global change queues.
Another split file situation
This 700 is used in RDA bib. record
A further complication of this split file problem is when the 700 form in the author authority record is used to create new uniform title authority records.
Each one of these uniform titles is using the unauthorized RDA form of heading which appears in the 700 field of the authority record.
* A few more examples *Note that the plain name heading shows that it is a 700 field in the authority record. And it is used as a 100 in the three uniform title records.
The new uniform title uses the RDA form for the heading.