Re: [RDA-L] RDA questions
Richard Moore helpfull posted:
The only one of these I can attempt to answer concerns fictitious
persons and places. As I understand it, fictitious persons will only be
established in the LC/NAF, coded 100, when considered creators or
contributors.
A distinction I find it diffult to grasp. It seems to me once
Geronimo Stilton writes something, the name should be considered a
pseudonym.
Personally I don't find the current situation with fictitious persons
satisfactory, as we potentially have two different access points,
formulated differently and with different MARC tags, for the same
entity.
Agreed. The possible uses of a name should be coded in a single
authority record, just as LCFGT should have been integrated with LCSH
using codes to indicate usage.
__ __ J. McRee (Mac) Elrod (m...@slc.bc.ca)
{__ | / Special Libraries Cataloguing HTTP://www.slc.bc.ca/
___} |__ \__
[RDA-L] RDA questions
Autocaters:
In preparing RDA procedures for our clients, we have questions we have
not been able to answer.
How many illustrations should an item contain to have 336 still image
added to 336 text? At the moment we are assuming half, e.g., an
exhibition catalogue. How much in the way of audio and video files
should an e-resource have to add spoken word and/or two-dimensional
moving image?
Is anyone doing repeated $a in 336, as opposed to repeating 336's? If
repeating $a, I assume only one $2? I prefer repeating $a, and our IT
person says either would work for him.
If fictitious people are to be in 600 as opposed to 650, should
fictitious places be in 651 as opposed to 650?
Since LC and OCLC do not agree on 040 subfield order, may we use the
order we find easiest, i.e., alphabetical. (We would never add a $d
after $e as some have done.) LAC has not answered us concerning what
they intend to do.
LAC has told us that they intend to use $4 relator codes as opposed to
$e relator terms, due to their bilingual situation. Will many be
adding $e or $4 apart from illustrators of children's books? (All but
one of our clients has said they want neither, so if we add them, we
would have to remove them on export.)
Those are just a small sampling from our three page list of decisions
to be made.
Thanks for your advice.
__ __ J. McRee (Mac) Elrod (m...@slc.bc.ca)
{__ | / Special Libraries Cataloguing HTTP://www.slc.bc.ca/
___} |__ \__
MARC21 Fields for RDA Content, Media Type, and Carrier Terms
14 October 2011
336 Content type
Follow each 336 term with $2rdaontent; except
follow thoseo in brackets with $2mricontent
For systems requiring 245$h, field 336 is exported as second half of
compound GMD, , truncated as shown, e.g., 245$h[online resource : text]
cartographic dataset }
cartographic image } [Consider displaying
cartographic moving image} cartographic with
cartographic tactile image } exact unit name, e.g.,
cartographic tactile three-dimensional form } map, globe.]
cartographic three-dimensional form }
computer dataset
computer program
[form]
[globe][
image*
[large print text]
[map]
[moving image]
notated movement
notated music
performed music
sounds
spoken word
still image [Unit name is specific term, e.g., engraving, painting.]
tactile image}
tactile notated movement }
tactile text } [Consider displaying just
tactile three-dimensional form } tactile with exact unit name.
text
three-dimensional form [Consider displaying form.]
three-dimensional moving image } [Consider displaying moving image.]
two-dimensional moving image }
337 Media type
Follow each term except electronic with $2rdamedia; follow
electronic with $2isbdmedia.
audio
electronic [Consider ISBD Area 0 term. rather than RDA's computer.]
microform
microscopic
projected
stereographic
unmediated
video
338 Carrier type
Follow each term with $2rdacarrier; except follow
equipment and kit with $2mricarrier.
1) Audio carriers
audio cartridge
audio cylinder
audio disc
sound-track reel
audio roll
audiocassette
audiotape reel
2) Electronic carriers
computer card
computer chip cartridge
computer disc
computer disc cartridge
computer tape cartridge
computer tape cassette
computer tape reel
online resource
3) Microform carriers
aperture card
microfiche
microfiche cassette
microfilm cartridge
microfilm cassette
microfilm reel
microfilm roll
microfilm slip
microopaque
4) Microscopic carriers
microscope slide
5) Projected image carriers
film cartridge
film cassette
film reel
film roll
filmslip
filmstrip
filmstrip cartridge
overhead transparency
slide [Use for photographic slides only]
5) Stereographic carriers
stereograph card
stereograph disc
6) Unmediated carriers
card
[equipment]
flipchart
[kit]
object
roll
sheet
volume
7) Video carriers
video cartridge
videocassette
videodisc
videotape reel
==
MARC codes for RDA carriers
http://www.loc.gov/standards/valuelist/marccarrier.html
Re: [RDA-L] RDA Questions
Quoting Mike Tribby mike.tri...@quality-books.com: How does open-ended instruction on just how to note birth and death dates achieve the interchangeability and all-important granularity that RDA is purported to advance? Cataloging rules do not achieve interchangeability, no matter how precise and no matter how much they are followed, without a data format. RDA does not define a data format. So we have, at best, only one half of what we need to create data. To anyone doing data processing, it is obvious that -1873 is a display form of something that needs to be encoded for machine processing in a data element for a death date with a specific format, e.g. . It is unfortunate that RDA mixes decision-making (how you decide which data to record) with display instructions. It is even more unfortunate that no effort has been undertaken to create at least one data format for RDA. (And, no, re-using MARC for RDA is not a solution.) RDA purports to be format neutral but in fact it is format hostile because it forces certain displays (the famed p. v. pages) that not only do not acknowledge that the data should be meaningfully encoded for machine processing, but the use of language terms irrevocably negates RDA as suitable for international use. kc If I record Lee Perry as Perry, Lee, 1936- and another cataloging agency records him as Perry, Lee, b. 1936 how does that achieve anything other than confusion? If confusion is our goal, I'm all for it at this point. But somehow I doubt that's what we're pursuing here. Mike Tribby Senior Cataloger Quality Books Inc. The Best of America's Independent Presses mailto:mike.tri...@quality-books.com -Original Message- From: Resource Description and Access / Resource Description and Access [mailto:rd...@listserv.lac-bac.gc.ca] On Behalf Of Robert Maxwell Sent: Friday, October 08, 2010 10:35 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: Re: [RDA-L] RDA Questions RDA only says to record the birth or death date. It does not specify how you mark the data as referring to birth or death. If you will look at 9.3.2 (date of birth) you will see that RDA simply says to record the date, e.g. 1974. It is the same for other dates associated with a person. RDA doesn't say how you should tell the user of the data that the date is, for example, a birth date. That is left to the cataloging agency to decide. In MARC, since we don't have a separate field or subfield for birth date and death date the data needs to be marked in some other way. Possibilities include using the word born or b. before the birth date and died or d. before the death date. Another possible way to mark the data is to append a dash to the end of the year if the number represents a death date and append a dash to the beginning of the year if the number represents a death date. LC has chosen, for the test, to use dashes to designate the number as a birth date or a death date. If the dash comes after the number, it is a birth date. If it comes before the number, it is a death date. It is the same whether we have only the birth date, only the death date, or both. This is LC's local cataloging agency decision, but I think it would be good idea for others to follow it. The decision seems quite sensible to me and will be much better for indexing than interposition of a word in front of the number, and less capricious than the former NACO practice of establishing a name with a dash after the date if we thought the person was still alive at the time, and instead using b. if we thought the person was dead-with the arbitrary result that a person was established with a b. or a dash solely depending on when his/her name was established. I realize a dash before a death date without a birth date looks strange, but I suspect we'll get used to it. Bob Robert L. Maxwell Head, Special Collections and Formats Catalog Dept. 6728 Harold B. Lee Library Brigham Young University Provo, UT 84602 (801)422-5568 From: Resource Description and Access / Resource Description and Access [mailto:rd...@listserv.lac-bac.gc.ca] On Behalf Of Thompson, Rebecca L Sent: Wednesday, October 06, 2010 9:54 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: [RDA-L] RDA Questions My colleague and I have a couple of questions: First, we are confused by the print versions pertaining to RDA on the ALA website. The RDA: Resource Description and Access and RDA: Element Set View have the exact same description, except the latter has the statement RDA: Element Set View is an innovative way of sorting the RDA instructions by element, such as Title, Place of Publication etc. We were under the impression this is what RDA was to begin with. Is this a printed out version of what is under the tools tab in the RDA Toolkit? Could anyone explain the differences between the two
Re: [RDA-L] RDA Questions
Karen Coyle schrieb: ... RDA purports to be format neutral but in fact it is format hostile because it forces certain displays (the famed p. v. pages) that not only do not acknowledge that the data should be meaningfully encoded for machine processing, but the use of language terms irrevocably negates RDA as suitable for international use. For anyone actively involved in library computing, this is self-evident. How, then, could it happen? This has annoyed me enough to suggest English as the working language for German libraries. So far, however, they insist on German. This is somewhat ironic because the decision to migrate to AACR2 and then later RDA was based on an understanding that we should improve international interoperability of our data. Now a large measure of support for interoperability will likely come from the implementation and use of VIAF. This, however, was conceived in pre-RDA times and with the underlying idea that changes in national cataloging rules were unlikely and could be avoided with VIAF... B.Eversberg
Re: [RDA-L] RDA Questions
On the topic of data formats for dates, it looks like MARC authority records in the RDA test are also carrying the RDA date elements in ISO 8601 format as the default in 046 subfields: RDA Test authority record for Coleridge, Samuel Taylor, 1772-1834 has: 046 __ |f 17721020 |g 18340725 100 1_ |a Coleridge, Samuel Taylor, |d 1772-1834 For complex dates, such as approximate dates, it appears that the source, edtf (Extended Date/Time Format) is to be specified. From http://www.loc.gov/marc/authority/ad046.html: 046 ##$f1831?$2edtf 100 1#$aSmith, James,$dborn 1831? [probable year of birth] which LC (Library of Congress Policy Statements 9.3.2.3) intends to display as Smith, James, 1831?- The Extended Date/Time Format (edtf) looks to be a work in progress: http://www.loc.gov/standards/datetime/ Thomas Brenndorfer Guelph Public Library From: Resource Description and Access / Resource Description and Access [rd...@listserv.lac-bac.gc.ca] On Behalf Of Karen Coyle [li...@kcoyle.net] Sent: October-11-10 10:17 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: Re: [RDA-L] RDA Questions Quoting Mike Tribby mike.tri...@quality-books.com: How does open-ended instruction on just how to note birth and death dates achieve the interchangeability and all-important granularity that RDA is purported to advance? Cataloging rules do not achieve interchangeability, no matter how precise and no matter how much they are followed, without a data format. RDA does not define a data format. So we have, at best, only one half of what we need to create data. To anyone doing data processing, it is obvious that -1873 is a display form of something that needs to be encoded for machine processing in a data element for a death date with a specific format, e.g. . It is unfortunate that RDA mixes decision-making (how you decide which data to record) with display instructions. It is even more unfortunate that no effort has been undertaken to create at least one data format for RDA. (And, no, re-using MARC for RDA is not a solution.) RDA purports to be format neutral but in fact it is format hostile because it forces certain displays (the famed p. v. pages) that not only do not acknowledge that the data should be meaningfully encoded for machine processing, but the use of language terms irrevocably negates RDA as suitable for international use. kc If I record Lee Perry as Perry, Lee, 1936- and another cataloging agency records him as Perry, Lee, b. 1936 how does that achieve anything other than confusion? If confusion is our goal, I'm all for it at this point. But somehow I doubt that's what we're pursuing here. Mike Tribby Senior Cataloger Quality Books Inc. The Best of America's Independent Presses mailto:mike.tri...@quality-books.com -Original Message- From: Resource Description and Access / Resource Description and Access [mailto:rd...@listserv.lac-bac.gc.ca] On Behalf Of Robert Maxwell Sent: Friday, October 08, 2010 10:35 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: Re: [RDA-L] RDA Questions RDA only says to record the birth or death date. It does not specify how you mark the data as referring to birth or death. If you will look at 9.3.2 (date of birth) you will see that RDA simply says to record the date, e.g. 1974. It is the same for other dates associated with a person. RDA doesn't say how you should tell the user of the data that the date is, for example, a birth date. That is left to the cataloging agency to decide. In MARC, since we don't have a separate field or subfield for birth date and death date the data needs to be marked in some other way. Possibilities include using the word born or b. before the birth date and died or d. before the death date. Another possible way to mark the data is to append a dash to the end of the year if the number represents a death date and append a dash to the beginning of the year if the number represents a death date. LC has chosen, for the test, to use dashes to designate the number as a birth date or a death date. If the dash comes after the number, it is a birth date. If it comes before the number, it is a death date. It is the same whether we have only the birth date, only the death date, or both. This is LC's local cataloging agency decision, but I think it would be good idea for others to follow it. The decision seems quite sensible to me and will be much better for indexing than interposition of a word in front of the number, and less capricious than the former NACO practice of establishing a name with a dash after the date if we thought the person was still alive at the time, and instead using b. if we thought the person was dead-with the arbitrary result that a person was established with a b. or a dash solely depending on when his/her name was established. I realize a dash before a death date without a birth date looks strange, but I suspect we'll get
Re: [RDA-L] RDA Questions
RDA only says to record the birth or death date. It does not specify how you mark the data as referring to birth or death. If you will look at 9.3.2 (date of birth) you will see that RDA simply says to record the date, e.g. 1974. It is the same for other dates associated with a person. RDA doesn't say how you should tell the user of the data that the date is, for example, a birth date. That is left to the cataloging agency to decide. In MARC, since we don't have a separate field or subfield for birth date and death date the data needs to be marked in some other way. Possibilities include using the word born or b. before the birth date and died or d. before the death date. Another possible way to mark the data is to append a dash to the end of the year if the number represents a death date and append a dash to the beginning of the year if the number represents a death date. LC has chosen, for the test, to use dashes to designate the number as a birth date or a death date. If the dash comes after the number, it is a birth date. If it comes before the number, it is a death date. It is the same whether we have only the birth date, only the death date, or both. This is LC's local cataloging agency decision, but I think it would be good idea for others to follow it. The decision seems quite sensible to me and will be much better for indexing than interposition of a word in front of the number, and less capricious than the former NACO practice of establishing a name with a dash after the date if we thought the person was still alive at the time, and instead using b. if we thought the person was dead-with the arbitrary result that a person was established with a b. or a dash solely depending on when his/her name was established. I realize a dash before a death date without a birth date looks strange, but I suspect we'll get used to it. Bob Robert L. Maxwell Head, Special Collections and Formats Catalog Dept. 6728 Harold B. Lee Library Brigham Young University Provo, UT 84602 (801)422-5568 From: Resource Description and Access / Resource Description and Access [mailto:rd...@listserv.lac-bac.gc.ca] On Behalf Of Thompson, Rebecca L Sent: Wednesday, October 06, 2010 9:54 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: [RDA-L] RDA Questions My colleague and I have a couple of questions: First, we are confused by the print versions pertaining to RDA on the ALA website. The RDA: Resource Description and Access and RDA: Element Set View have the exact same description, except the latter has the statement RDA: Element Set View is an innovative way of sorting the RDA instructions by element, such as Title, Place of Publication etc. We were under the impression this is what RDA was to begin with. Is this a printed out version of what is under the tools tab in the RDA Toolkit? Could anyone explain the differences between the two? Our second question relates to the use of the terms born and died (b. or d. in AACR2) in name headings. In 9.19.1.3, the examples (copied below) show the use of these terms. However, at the ALA RDA101 pre-conference in June and the ALCTS Introduction to RDA webinar last Wednesday, the examples always showed use of a dash (examples below) and we were told to not use the terms born and died. Since both of these trainings were officially sanctioned, I am wondering what is correct. Has there been a change and the toolkit has been updated yet? Or was there a change and it just hasn't filtered down the trainers yet? Thank you for your time and help. Examples from 9.19.1.3 Smith, John, 1978- Smith, John, 1718-1791 Smith, John, born 1787 Smith, John, died 1773 Examples from pre-conference and webinar Smith, John, 1978- Smith, John, 1718-1791 Smith, John, 1787- Smith, John, -1773 Becky Thompson Assistant Professor of Library Science Missouri State University 901 South National Meyer Library 108F Springfield, MO 65897 417.836-5745 417.836.4764 (fax) rthomp...@missouristate.edu I looked at all the caged animals in the shelter.. the cast-offs to human society. I saw in their eyes love and hope, fear and dread, sadness and betrayal; and I was angry. God, I said, this is terrible! Why don't you do something??? There was silence for a moment and then the voice whispered softly, I have done something; I created You!? ~Author Unknown ý Towards a Sustainable Future - do you really need to print this?
Re: [RDA-L] RDA Questions
How does open-ended instruction on just how to note birth and death dates achieve the interchangeability and all-important granularity that RDA is purported to advance? If I record Lee Perry as Perry, Lee, 1936- and another cataloging agency records him as Perry, Lee, b. 1936 how does that achieve anything other than confusion? If confusion is our goal, I'm all for it at this point. But somehow I doubt that's what we're pursuing here. Mike Tribby Senior Cataloger Quality Books Inc. The Best of America's Independent Presses mailto:mike.tri...@quality-books.com -Original Message- From: Resource Description and Access / Resource Description and Access [mailto:rd...@listserv.lac-bac.gc.ca] On Behalf Of Robert Maxwell Sent: Friday, October 08, 2010 10:35 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: Re: [RDA-L] RDA Questions RDA only says to record the birth or death date. It does not specify how you mark the data as referring to birth or death. If you will look at 9.3.2 (date of birth) you will see that RDA simply says to record the date, e.g. 1974. It is the same for other dates associated with a person. RDA doesn't say how you should tell the user of the data that the date is, for example, a birth date. That is left to the cataloging agency to decide. In MARC, since we don't have a separate field or subfield for birth date and death date the data needs to be marked in some other way. Possibilities include using the word born or b. before the birth date and died or d. before the death date. Another possible way to mark the data is to append a dash to the end of the year if the number represents a death date and append a dash to the beginning of the year if the number represents a death date. LC has chosen, for the test, to use dashes to designate the number as a birth date or a death date. If the dash comes after the number, it is a birth date. If it comes before the number, it is a death date. It is the same whether we have only the birth date, only the death date, or both. This is LC's local cataloging agency decision, but I think it would be good idea for others to follow it. The decision seems quite sensible to me and will be much better for indexing than interposition of a word in front of the number, and less capricious than the former NACO practice of establishing a name with a dash after the date if we thought the person was still alive at the time, and instead using b. if we thought the person was dead-with the arbitrary result that a person was established with a b. or a dash solely depending on when his/her name was established. I realize a dash before a death date without a birth date looks strange, but I suspect we'll get used to it. Bob Robert L. Maxwell Head, Special Collections and Formats Catalog Dept. 6728 Harold B. Lee Library Brigham Young University Provo, UT 84602 (801)422-5568 From: Resource Description and Access / Resource Description and Access [mailto:rd...@listserv.lac-bac.gc.ca] On Behalf Of Thompson, Rebecca L Sent: Wednesday, October 06, 2010 9:54 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: [RDA-L] RDA Questions My colleague and I have a couple of questions: First, we are confused by the print versions pertaining to RDA on the ALA website. The RDA: Resource Description and Access and RDA: Element Set View have the exact same description, except the latter has the statement RDA: Element Set View is an innovative way of sorting the RDA instructions by element, such as Title, Place of Publication etc. We were under the impression this is what RDA was to begin with. Is this a printed out version of what is under the tools tab in the RDA Toolkit? Could anyone explain the differences between the two? Our second question relates to the use of the terms born and died (b. or d. in AACR2) in name headings. In 9.19.1.3, the examples (copied below) show the use of these terms. However, at the ALA RDA101 pre-conference in June and the ALCTS Introduction to RDA webinar last Wednesday, the examples always showed use of a dash (examples below) and we were told to not use the terms born and died. Since both of these trainings were officially sanctioned, I am wondering what is correct. Has there been a change and the toolkit has been updated yet? Or was there a change and it just hasn't filtered down the trainers yet? Thank you for your time and help. Examples from 9.19.1.3 Smith, John, 1978- Smith, John, 1718-1791 Smith, John, born 1787 Smith, John, died 1773 Examples from pre-conference and webinar Smith, John, 1978- Smith, John, 1718-1791 Smith, John, 1787- Smith, John, -1773 Becky Thompson Assistant Professor of Library Science Missouri State University 901 South National Meyer Library 108F Springfield, MO 65897 417.836-5745 417.836.4764 (fax) rthomp...@missouristate.edu I looked at all the caged animals in the shelter.. the cast
Re: [RDA-L] RDA Questions
Which is why I suggest that we follow LC's lead in this matter. Robert L. Maxwell Head, Special Collections and Formats Catalog Dept. 6728 Harold B. Lee Library Brigham Young University Provo, UT 84602 (801)422-5568 -Original Message- From: Resource Description and Access / Resource Description and Access [mailto:rd...@listserv.lac-bac.gc.ca] On Behalf Of Mike Tribby Sent: Friday, October 08, 2010 9:42 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: Re: [RDA-L] RDA Questions How does open-ended instruction on just how to note birth and death dates achieve the interchangeability and all-important granularity that RDA is purported to advance? If I record Lee Perry as Perry, Lee, 1936- and another cataloging agency records him as Perry, Lee, b. 1936 how does that achieve anything other than confusion? If confusion is our goal, I'm all for it at this point. But somehow I doubt that's what we're pursuing here. Mike Tribby Senior Cataloger Quality Books Inc. The Best of America's Independent Presses mailto:mike.tri...@quality-books.com -Original Message- From: Resource Description and Access / Resource Description and Access [mailto:rd...@listserv.lac-bac.gc.ca] On Behalf Of Robert Maxwell Sent: Friday, October 08, 2010 10:35 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: Re: [RDA-L] RDA Questions RDA only says to record the birth or death date. It does not specify how you mark the data as referring to birth or death. If you will look at 9.3.2 (date of birth) you will see that RDA simply says to record the date, e.g. 1974. It is the same for other dates associated with a person. RDA doesn't say how you should tell the user of the data that the date is, for example, a birth date. That is left to the cataloging agency to decide. In MARC, since we don't have a separate field or subfield for birth date and death date the data needs to be marked in some other way. Possibilities include using the word born or b. before the birth date and died or d. before the death date. Another possible way to mark the data is to append a dash to the end of the year if the number represents a death date and append a dash to the beginning of the year if the number represents a death date. LC has chosen, for the test, to use dashes to designate the number as a birth date or a death date. If the dash comes after the number, it is a birth date. If it comes before the number, it is a death date. It is the same whether we have only the birth date, only the death date, or both. This is LC's local cataloging agency decision, but I think it would be good idea for others to follow it. The decision seems quite sensible to me and will be much better for indexing than interposition of a word in front of the number, and less capricious than the former NACO practice of establishing a name with a dash after the date if we thought the person was still alive at the time, and instead using b. if we thought the person was dead-with the arbitrary result that a person was established with a b. or a dash solely depending on when his/her name was established. I realize a dash before a death date without a birth date looks strange, but I suspect we'll get used to it. Bob Robert L. Maxwell Head, Special Collections and Formats Catalog Dept. 6728 Harold B. Lee Library Brigham Young University Provo, UT 84602 (801)422-5568 From: Resource Description and Access / Resource Description and Access [mailto:rd...@listserv.lac-bac.gc.ca] On Behalf Of Thompson, Rebecca L Sent: Wednesday, October 06, 2010 9:54 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: [RDA-L] RDA Questions My colleague and I have a couple of questions: First, we are confused by the print versions pertaining to RDA on the ALA website. The RDA: Resource Description and Access and RDA: Element Set View have the exact same description, except the latter has the statement RDA: Element Set View is an innovative way of sorting the RDA instructions by element, such as Title, Place of Publication etc. We were under the impression this is what RDA was to begin with. Is this a printed out version of what is under the tools tab in the RDA Toolkit? Could anyone explain the differences between the two? Our second question relates to the use of the terms born and died (b. or d. in AACR2) in name headings. In 9.19.1.3, the examples (copied below) show the use of these terms. However, at the ALA RDA101 pre-conference in June and the ALCTS Introduction to RDA webinar last Wednesday, the examples always showed use of a dash (examples below) and we were told to not use the terms born and died. Since both of these trainings were officially sanctioned, I am wondering what is correct. Has there been a change and the toolkit has been updated yet? Or was there a change and it just hasn't filtered down the trainers yet? Thank you for your time and help. Examples from 9.19.1.3 Smith, John, 1978- Smith, John, 1718-1791 Smith
Re: [RDA-L] RDA Questions
Understood, but RDA is supposed to enable catalogers beyond LC's orbit to create records that all can use. Sadly not every cataloging agency in the bibliographic universe follows LC policy. Mike Tribby Senior Cataloger Quality Books Inc. The Best of America's Independent Presses mailto:mike.tri...@quality-books.com -Original Message- From: Resource Description and Access / Resource Description and Access [mailto:rd...@listserv.lac-bac.gc.ca] On Behalf Of Robert Maxwell Sent: Friday, October 08, 2010 10:48 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: Re: [RDA-L] RDA Questions Which is why I suggest that we follow LC's lead in this matter. Robert L. Maxwell Head, Special Collections and Formats Catalog Dept. 6728 Harold B. Lee Library Brigham Young University Provo, UT 84602 (801)422-5568 -Original Message- From: Resource Description and Access / Resource Description and Access [mailto:rd...@listserv.lac-bac.gc.ca] On Behalf Of Mike Tribby Sent: Friday, October 08, 2010 9:42 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: Re: [RDA-L] RDA Questions How does open-ended instruction on just how to note birth and death dates achieve the interchangeability and all-important granularity that RDA is purported to advance? If I record Lee Perry as Perry, Lee, 1936- and another cataloging agency records him as Perry, Lee, b. 1936 how does that achieve anything other than confusion? If confusion is our goal, I'm all for it at this point. But somehow I doubt that's what we're pursuing here. Mike Tribby Senior Cataloger Quality Books Inc. The Best of America's Independent Presses mailto:mike.tri...@quality-books.com -Original Message- From: Resource Description and Access / Resource Description and Access [mailto:rd...@listserv.lac-bac.gc.ca] On Behalf Of Robert Maxwell Sent: Friday, October 08, 2010 10:35 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: Re: [RDA-L] RDA Questions RDA only says to record the birth or death date. It does not specify how you mark the data as referring to birth or death. If you will look at 9.3.2 (date of birth) you will see that RDA simply says to record the date, e.g. 1974. It is the same for other dates associated with a person. RDA doesn't say how you should tell the user of the data that the date is, for example, a birth date. That is left to the cataloging agency to decide. In MARC, since we don't have a separate field or subfield for birth date and death date the data needs to be marked in some other way. Possibilities include using the word born or b. before the birth date and died or d. before the death date. Another possible way to mark the data is to append a dash to the end of the year if the number represents a death date and append a dash to the beginning of the year if the number represents a death date. LC has chosen, for the test, to use dashes to designate the number as a birth date or a death date. If the dash comes after the number, it is a birth date. If it comes before the number, it is a death date. It is the same whether we have only the birth date, only the death date, or both. This is LC's local cataloging agency decision, but I think it would be good idea for others to follow it. The decision seems quite sensible to me and will be much better for indexing than interposition of a word in front of the number, and less capricious than the former NACO practice of establishing a name with a dash after the date if we thought the person was still alive at the time, and instead using b. if we thought the person was dead-with the arbitrary result that a person was established with a b. or a dash solely depending on when his/her name was established. I realize a dash before a death date without a birth date looks strange, but I suspect we'll get used to it. Bob Robert L. Maxwell Head, Special Collections and Formats Catalog Dept. 6728 Harold B. Lee Library Brigham Young University Provo, UT 84602 (801)422-5568 From: Resource Description and Access / Resource Description and Access [mailto:rd...@listserv.lac-bac.gc.ca] On Behalf Of Thompson, Rebecca L Sent: Wednesday, October 06, 2010 9:54 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: [RDA-L] RDA Questions My colleague and I have a couple of questions: First, we are confused by the print versions pertaining to RDA on the ALA website. The RDA: Resource Description and Access and RDA: Element Set View have the exact same description, except the latter has the statement RDA: Element Set View is an innovative way of sorting the RDA instructions by element, such as Title, Place of Publication etc. We were under the impression this is what RDA was to begin with. Is this a printed out version of what is under the tools tab in the RDA Toolkit? Could anyone explain the differences between the two? Our second question relates to the use of the terms born and died (b. or d. in AACR2) in name headings. In 9.19.1.3, the examples
Re: [RDA-L] RDA Questions
If we are using authority records from LC, anything other than following their lead would not make sense. Brenda Resource Description and Access / Resource Description and Access RDA-L@LISTSERV.LAC-BAC.GC.CA writes: Which is why I suggest that we follow LC's lead in this matter. Robert L. Maxwell Head, Special Collections and Formats Catalog Dept. 6728 Harold B. Lee Library Brigham Young University Provo, UT 84602 (801)422-5568 -Original Message- From: Resource Description and Access / Resource Description and Access [mailto:rd...@listserv.lac-bac.gc.ca] On Behalf Of Mike Tribby Sent: Friday, October 08, 2010 9:42 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: Re: [RDA-L] RDA Questions How does open-ended instruction on just how to note birth and death dates achieve the interchangeability and all-important granularity that RDA is purported to advance? If I record Lee Perry as Perry, Lee, 1936- and another cataloging agency records him as Perry, Lee, b. 1936 how does that achieve anything other than confusion? If confusion is our goal, I'm all for it at this point. But somehow I doubt that's what we're pursuing here. Brenda Parris Parker Technical Services/Reference Librarian Brewer Library Calhoun Community College Decatur, AL
Re: [RDA-L] RDA Questions
If we are using authority records from LC, anything other than following their lead would not make sense. Again, not every cataloging agency follows LC's lead. This kind of option in the RDA rules serves no purpose that I can see. And haven't we heard plenty in the recent past about not relying on LC for everything? If the rules allow deviations in practice, deviations are sure to occur. Moreover, LC does _not_ prepare every authority record in the shared authority file. Mike Tribby Senior Cataloger Quality Books Inc. The Best of America's Independent Presses mailto:mike.tri...@quality-books.com -Original Message- From: Resource Description and Access / Resource Description and Access [mailto:rd...@listserv.lac-bac.gc.ca] On Behalf Of Brenda Parris Parker Sent: Friday, October 08, 2010 10:59 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: Re: [RDA-L] RDA Questions If we are using authority records from LC, anything other than following their lead would not make sense. Brenda Resource Description and Access / Resource Description and Access RDA-L@LISTSERV.LAC-BAC.GC.CA writes: Which is why I suggest that we follow LC's lead in this matter. Robert L. Maxwell Head, Special Collections and Formats Catalog Dept. 6728 Harold B. Lee Library Brigham Young University Provo, UT 84602 (801)422-5568 -Original Message- From: Resource Description and Access / Resource Description and Access [mailto:rd...@listserv.lac-bac.gc.ca] On Behalf Of Mike Tribby Sent: Friday, October 08, 2010 9:42 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: Re: [RDA-L] RDA Questions How does open-ended instruction on just how to note birth and death dates achieve the interchangeability and all-important granularity that RDA is purported to advance? If I record Lee Perry as Perry, Lee, 1936- and another cataloging agency records him as Perry, Lee, b. 1936 how does that achieve anything other than confusion? If confusion is our goal, I'm all for it at this point. But somehow I doubt that's what we're pursuing here. Brenda Parris Parker Technical Services/Reference Librarian Brewer Library Calhoun Community College Decatur, AL No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.448 / Virus Database: 271.1.1/3183 - Release Date: 10/07/10 18:34:00
Re: [RDA-L] RDA Questions
No set of rules can ultimately determine the form of a name heading, because that will inevitably depend on the information available to the person creating the authority record. Two people with different information can create different headings for the same person following the same rule set. Authority files are the only way to determine a shared form of name heading. That being the case, I'm more concerned about not having authority control split between an RDA file and an AACR2 file. We'll better served by a convention which treats established AACR2 headings as RDA compatible and treats RDA headings as AACR2 compatible, thereby enabling a single authority record and, more importantly, a single authority file to be used for both AACR2 and RDA bib records. We already have much more aggresive conventions when it comes to updating authorities than we used to, so we could expect a steady migration of headings and authority records in the direction of RDA. The advantages of authorizing against a single file rather than starting up a second parallel file during this transition would be considerable. I can understand the reasons for using 7XX authority links during the trial period, since it's less intrusive on the relationship of AACR2 established headings and bibs; but it's not going to be the best transition strategy when real implementation begins. Stephen On Fri, Oct 8, 2010 at 11:05 AM, Mike Tribby mike.tri...@quality-books.comwrote: If we are using authority records from LC, anything other than following their lead would not make sense. Again, not every cataloging agency follows LC's lead. This kind of option in the RDA rules serves no purpose that I can see. And haven't we heard plenty in the recent past about not relying on LC for everything? If the rules allow deviations in practice, deviations are sure to occur. Moreover, LC does _not_ prepare every authority record in the shared authority file. Mike Tribby Senior Cataloger Quality Books Inc. The Best of America's Independent Presses mailto:mike.tri...@quality-books.com -Original Message- From: Resource Description and Access / Resource Description and Access [mailto:rd...@listserv.lac-bac.gc.ca] On Behalf Of Brenda Parris Parker Sent: Friday, October 08, 2010 10:59 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: Re: [RDA-L] RDA Questions If we are using authority records from LC, anything other than following their lead would not make sense. Brenda Resource Description and Access / Resource Description and Access RDA-L@LISTSERV.LAC-BAC.GC.CA writes: Which is why I suggest that we follow LC's lead in this matter. Robert L. Maxwell Head, Special Collections and Formats Catalog Dept. 6728 Harold B. Lee Library Brigham Young University Provo, UT 84602 (801)422-5568 -Original Message- From: Resource Description and Access / Resource Description and Access [mailto:rd...@listserv.lac-bac.gc.ca] On Behalf Of Mike Tribby Sent: Friday, October 08, 2010 9:42 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: Re: [RDA-L] RDA Questions How does open-ended instruction on just how to note birth and death dates achieve the interchangeability and all-important granularity that RDA is purported to advance? If I record Lee Perry as Perry, Lee, 1936- and another cataloging agency records him as Perry, Lee, b. 1936 how does that achieve anything other than confusion? If confusion is our goal, I'm all for it at this point. But somehow I doubt that's what we're pursuing here. Brenda Parris Parker Technical Services/Reference Librarian Brewer Library Calhoun Community College Decatur, AL No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.448 / Virus Database: 271.1.1/3183 - Release Date: 10/07/10 18:34:00 -- Stephen Hearn, Metadata Strategist Technical Services, University Libraries University of Minnesota 160 Wilson Library 309 19th Avenue South Minneapolis, MN 55455 Ph: 612-625-2328 Fx: 612-625-3428
Re: [RDA-L] RDA Questions
Stephen Hearn said:
We'll better served by a convention which treats established AACR2
headings as RDA compatible and treats RDA headings as AACR2
compatible, ...
Last time around, we called this superimposition. And no, that's not
a Julie Andrews' song.
__ __ J. McRee (Mac) Elrod (m...@slc.bc.ca)
{__ | / Special Libraries Cataloguing HTTP://www.slc.bc.ca/
___} |__ \__
Re: [RDA-L] RDA Questions - make staging area as Relational Database Management Systems
Stephen:
This can be done if we make our staging area for ETL (Extract,
Transform, and Load) process as separate relational database management
systems.
I saw how it was done by financial industries when they have to track
name changes of their customers. They do not have choice but to support
backward compatibility. This is under the assumption that we are going
to handle the ETL process using database systems.
In the meantime, at data input point, we should also have the option to
handle it manually by:
1. recording ACCR2 headings as alias, and RDA headings as established
form of name;
2. using subfield $2 to designate RDA headings and AACR2 headings;
3. indexing and searching both headings;
4. browsing and displaying RDA headings;
5. exchanging the appropriate form of headings according to service
agreement among data exchange partners, and systems types;
Hope it helps!
Thanks!
Amanda Xu
Information Technology Librarian for Collection Management
James E. Walker Library
Middle Tennessee State University
P.O. Box 13
1301 E. Main Street
Murfreesboro, TN 37128
615-904-8510 (office)
a...@mtsu.edu mailto:a...@mtsu.edu(office mail)
axu...@gmail.com mailto:axu...@gmail.com (personal email)
On 10/8/2010 2:44 PM, J. McRee Elrod wrote:
Stephen Hearn said:
We'll better served by a convention which treats established AACR2
headings as RDA compatible and treats RDA headings as AACR2
compatible, ...
Last time around, we called this superimposition. And no, that's not
a Julie Andrews' song.
__ __ J. McRee (Mac) Elrod (m...@slc.bc.ca)
{__ | / Special Libraries Cataloguing HTTP://www.slc.bc.ca/
___} |__ \__
Re: [RDA-L] RDA Questions--Element Set View
I agree. Including cross references taking you from the AACR2 term to the
RDA term and vice versa would be extremely useful, especially during this
transition period.
Marjorie
Marjorie E. Bloss
2827 West Gregory Street
Chicago, IL 60625
USA
1-773-878-4008
1-773-519-4009 (mobile)
marjorie_bl...@msn.com
- Original Message -
From: J. McRee Elrod m...@slc.bc.ca
To: RDA-L@LISTSERV.LAC-BAC.GC.CA
Sent: Wednesday, October 06, 2010 1:46 PM
Subject: Re: [RDA-L] RDA Questions--Element Set View
Mary Mackay quoted:
The RDA: Element Set View is a re-ordering of a subset of RDA content, =
arranged first by FRBR entity and then (alphabetically) by name of the =
RDA element or subelement.
Ordering by ISBD element and/or MARC21 field would make consultation much
easier.
The difficulty with alphabetical ordering is changing terminology,
e.g., main entry, prime entry, preferred entry.
__ __ J. McRee (Mac) Elrod (m...@slc.bc.ca)
{__ | / Special Libraries Cataloguing HTTP://www.slc.bc.ca/
___} |__ \__
[RDA-L] RDA Questions
My colleague and I have a couple of questions: First, we are confused by the print versions pertaining to RDA on the ALA website. The RDA: Resource Description and Access and RDA: Element Set View have the exact same description, except the latter has the statement RDA: Element Set View is an innovative way of sorting the RDA instructions by element, such as Title, Place of Publication etc. We were under the impression this is what RDA was to begin with. Is this a printed out version of what is under the tools tab in the RDA Toolkit? Could anyone explain the differences between the two? Our second question relates to the use of the terms born and died (b. or d. in AACR2) in name headings. In 9.19.1.3, the examples (copied below) show the use of these terms. However, at the ALA RDA101 pre-conference in June and the ALCTS Introduction to RDA webinar last Wednesday, the examples always showed use of a dash (examples below) and we were told to not use the terms born and died. Since both of these trainings were officially sanctioned, I am wondering what is correct. Has there been a change and the toolkit has been updated yet? Or was there a change and it just hasn't filtered down the trainers yet? Thank you for your time and help. Examples from 9.19.1.3 Smith, John, 1978- Smith, John, 1718-1791 Smith, John, born 1787 Smith, John, died 1773 Examples from pre-conference and webinar Smith, John, 1978- Smith, John, 1718-1791 Smith, John, 1787- Smith, John, -1773 Becky Thompson Assistant Professor of Library Science Missouri State University 901 South National Meyer Library 108F Springfield, MO 65897 417.836-5745 417.836.4764 (fax) rthomp...@missouristate.edu I looked at all the caged animals in the shelter.. the cast-offs to human society. I saw in their eyes love and hope, fear and dread, sadness and betrayal; and I was angry. God, I said, this is terrible! Why don't you do something??? There was silence for a moment and then the voice whispered softly, I have done something; I created You!? ~Author Unknown ý Towards a Sustainable Future - do you really need to print this?
Re: [RDA-L] RDA Questions--Element Set View
Here is amplified copy about the Element Set View that has recently been uploaded to the ALA Store, and I hope it helps clarify: The RDA: Element Set View is a re-ordering of a subset of RDA content, arranged first by FRBR entity and then (alphabetically) by name of the RDA element or subelement. The RDA content includes the RDA element definition, any RDA-defined vocabularies used in recording the element, and the relevant RDA instructions for recording the element. The RDA: Element Set View is available both on the Tools tab in the RDA Toolkit and in print. The RDA Toolkit offers links from the RDA: Element Set View to the full text of the instructions in RDA, as well as links to current and evolving encoding standards documentation (for example current MARC 21 documentation). Mary Mackay Director, Marketing, ALA Publishing 312-280-1532 mmac...@ala.org . From: Resource Description and Access / Resource Description and Access [mailto:rd...@listserv.lac-bac.gc.ca] On Behalf Of Thompson, Rebecca L Sent: Wednesday, October 06, 2010 10:54 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: [RDA-L] RDA Questions My colleague and I have a couple of questions: First, we are confused by the print versions pertaining to RDA on the ALA website. The RDA: Resource Description and Access and RDA: Element Set View have the exact same description, except the latter has the statement RDA: Element Set View is an innovative way of sorting the RDA instructions by element, such as Title, Place of Publication etc. We were under the impression this is what RDA was to begin with. Is this a printed out version of what is under the tools tab in the RDA Toolkit? Could anyone explain the differences between the two? Our second question relates to the use of the terms born and died (b. or d. in AACR2) in name headings. In 9.19.1.3, the examples (copied below) show the use of these terms. However, at the ALA RDA101 pre-conference in June and the ALCTS Introduction to RDA webinar last Wednesday, the examples always showed use of a dash (examples below) and we were told to not use the terms born and died. Since both of these trainings were officially sanctioned, I am wondering what is correct. Has there been a change and the toolkit has been updated yet? Or was there a change and it just hasn't filtered down the trainers yet? Thank you for your time and help. Examples from 9.19.1.3 Smith, John, 1978- Smith, John, 1718-1791 Smith, John, born 1787 Smith, John, died 1773 Examples from pre-conference and webinar Smith, John, 1978- Smith, John, 1718-1791 Smith, John, 1787- Smith, John, -1773 Becky Thompson Assistant Professor of Library Science Missouri State University 901 South National Meyer Library 108F Springfield, MO 65897 417.836-5745 417.836.4764 (fax) rthomp...@missouristate.edu I looked at all the caged animals in the shelter.. the cast-offs to human society. I saw in their eyes love and hope, fear and dread, sadness and betrayal; and I was angry. God, I said, this is terrible! Why don't you do something??? There was silence for a moment and then the voice whispered softly, I have done something; I created You!? ~Author Unknown ý Towards a Sustainable Future - do you really need to print this?
Re: [RDA-L] RDA Questions
On Wed, Oct 6, 2010 at 10:54 AM, Thompson, Rebecca L rthomp...@missouristate.edu wrote: My colleague and I have a couple of questions: First, we are confused by the print versions pertaining to RDA on the ALA website. The RDA: Resource Description and Access and RDA: Element Set View have the exact same description, except the latter has the statement “RDA: Element Set View is an innovative way of sorting the RDA instructions by element, such as Title, Place of Publication etc.” We were under the impression this is what RDA was to begin with. Is this a printed out version of what is under the tools tab in the RDA Toolkit? Could anyone explain the differences between the two? Basically, the Element Set View just lists the RDA elements (and their instructions) in a different order--by FRR entities. If you have a copy of the Toolkit handy now or recall it from the open access period, the Element Set View is the first one listed under the Tools tab. ALA Publishing has admitted that the description for this volume isn't clear and will make amends, though I don't know when. Our second question relates to the use of the terms born and died (b. or d. in AACR2) in name headings. In 9.19.1.3, the examples (copied below) show the use of these terms. However, at the ALA RDA101 pre-conference in June and the ALCTS Introduction to RDA webinar last Wednesday, the examples always showed use of a dash (examples below) and we were told to not use the terms born and died. Since both of these trainings were officially sanctioned, I am wondering what is correct. Has there been a change and the toolkit has been updated yet? Or was there a change and it just hasn't filtered down the trainers yet? The only use hyphens instructions is LC practice during this RDA testing period; see the LCPS for 9.3.2.3 and 9.3.3.3.* RDA allows for a more open interpretation of how to record dates for persons. * http://www.loc.gov/catdir/cpso/RDAtest/rda_lcps.html; Also available via Cataloger's Desktop -- Mark K. Ehlert Minitex Coordinator University of Minnesota Bibliographic Technical 15 Andersen Library Services (BATS) Unit 222 21st Avenue South Phone: 612-624-0805 Minneapolis, MN 55455-0439 http://www.minitex.umn.edu/
Re: [RDA-L] RDA Questions--Element Set View
Mary Mackay mmac...@ala.org wrote: Here is amplified copy about the Element Set View that has recently been uploaded to the ALA Store, and I hope it helps clarify: Thanks for posting this. That's what I get for not checking the ALA Store before replying. -- Mark K. Ehlert Minitex Coordinator University of Minnesota Bibliographic Technical 15 Andersen Library Services (BATS) Unit 222 21st Avenue South Phone: 612-624-0805 Minneapolis, MN 55455-0439 http://www.minitex.umn.edu/
Re: [RDA-L] RDA Questions
I was also at the ALA RDA 101 preconference, so I checked my notes and the pattern Smith, John, 1825- Smith, John, -1859 IS in the notes. I added LC test beside these examples, so, apparently, this is LC's application of RDA in the test phase. Hope this helps, Scott M. Dutkiewicz Special Formats Cataloger Assistant Librarian Clemson University Libraries scot...@clemson.edu [cid:image001.png@01CB655A.7F3DF520] From: Resource Description and Access / Resource Description and Access [mailto:rd...@listserv.lac-bac.gc.ca] On Behalf Of Thompson, Rebecca L Sent: Wednesday, October 06, 2010 11:54 AM To: RDA-L@LISTSERV.LAC-BAC.GC.CA Subject: [RDA-L] RDA Questions My colleague and I have a couple of questions: First, we are confused by the print versions pertaining to RDA on the ALA website. The RDA: Resource Description and Access and RDA: Element Set View have the exact same description, except the latter has the statement RDA: Element Set View is an innovative way of sorting the RDA instructions by element, such as Title, Place of Publication etc. We were under the impression this is what RDA was to begin with. Is this a printed out version of what is under the tools tab in the RDA Toolkit? Could anyone explain the differences between the two? Our second question relates to the use of the terms born and died (b. or d. in AACR2) in name headings. In 9.19.1.3, the examples (copied below) show the use of these terms. However, at the ALA RDA101 pre-conference in June and the ALCTS Introduction to RDA webinar last Wednesday, the examples always showed use of a dash (examples below) and we were told to not use the terms born and died. Since both of these trainings were officially sanctioned, I am wondering what is correct. Has there been a change and the toolkit has been updated yet? Or was there a change and it just hasn't filtered down the trainers yet? Thank you for your time and help. Examples from 9.19.1.3 Smith, John, 1978- Smith, John, 1718-1791 Smith, John, born 1787 Smith, John, died 1773 Examples from pre-conference and webinar Smith, John, 1978- Smith, John, 1718-1791 Smith, John, 1787- Smith, John, -1773 Becky Thompson Assistant Professor of Library Science Missouri State University 901 South National Meyer Library 108F Springfield, MO 65897 417.836-5745 417.836.4764 (fax) rthomp...@missouristate.edu I looked at all the caged animals in the shelter.. the cast-offs to human society. I saw in their eyes love and hope, fear and dread, sadness and betrayal; and I was angry. God, I said, this is terrible! Why don't you do something??? There was silence for a moment and then the voice whispered softly, I have done something; I created You!? ~Author Unknown ý Towards a Sustainable Future - do you really need to print this? inline: image001.png
Re: [RDA-L] RDA Questions--Element Set View
Mary Mackay quoted:
The RDA: Element Set View is a re-ordering of a subset of RDA content, =
arranged first by FRBR entity and then (alphabetically) by name of the =
RDA element or subelement.
Ordering by ISBD element and/or MARC21 field would make consultation much
easier.
The difficulty with alphabetical ordering is changing terminology,
e.g., main entry, prime entry, preferred entry.
__ __ J. McRee (Mac) Elrod (m...@slc.bc.ca)
{__ | / Special Libraries Cataloguing HTTP://www.slc.bc.ca/
___} |__ \__
