However, you will find her as a 700. ************************************** ************************************** Aleta Copeland, MLS Head of Technical Services Ouachita Parish Public Library 1800 Stubbs Ave. Monroe, LA 71201 318-327-1490 ex. 3015
-----Original Message----- From: Resource Description and Access / Resource Description and Access [mailto:[email protected]] On Behalf Of Kathleen Lamantia Sent: Friday, April 08, 2011 10:08 AM To: [email protected] Subject: Re: [RDA-L] FRBR You will not find "Austen, Jane 1775-1817" as the 'main entry' on any AACR2 record for a movie version of Pride and Prejudice. - Yes, of course, that's exactly my point about FRBR/RDA Kathleen F. Lamantia, MLIS Technical Services Librarian Stark County District Library 715 Market Avenue North Canton, OH 44702 330-458-2723 [email protected] Inspiring Ideas Enriching Lives Creating Community The Stark County District Library is a winner of the National Medal for library service, is one of the best 100 libraries in the U.S. according to the HAPLR rating, and is a Library Journal 5 Star library. -----Original Message----- From: Jonathan Rochkind [mailto:[email protected]] Sent: Friday, April 08, 2011 11:02 AM To: [email protected] Subject: Re: [RDA-L] FRBR > Well, it seems to me that Pride and Prejudice is Jane Austen's conception (work) no matter what form (expression) > it takes, so I would answer your 2nd question, "is the creator the same?" with yes. As to valid alternatives, > that seems to me to be "cataloger's judgment," so we are left with a situation in which book and movie will > or will not be the same work depending on perception - and that's no way to run a railroad. Again, all I can say is that this is not the decision that AACR2 or historical anglo-american cataloging makes, and FRBR/RDA bases itself off of anglo-american cataloging tradition. You will not find "Austen, Jane 1775-1817" as the 'main entry' on any AACR2 record for a movie version of Pride and Prejudice. There are probably reasons that anglo-american cataloging does this, that people could talk about. It's a choice. You're right that we want to be consistent to 'run a railroad', even though some people might consider the movie version the same work and some people might not. So we have to make a choice. The purpose of the FRBR data model is to be explicit about our data modelling, so we can record our data in a way that software can have access to semantics to provide flexible interfaces to meet user needs. The Group 1 W-E-M-I set is NOT the only semantics in data modelled according to FRBR, and if the movie work is appropriately related to the original text work, interfaces can still choose to present that relationship to the user in various ways. If they were simply modelled as the same work, interfaces would be unable to make that choice, interfaces would HAVE to present them as "the same". That's another way to look at the "run a railroad issue" -- we need to model our data the same to share it, even though users have different needs in different contexts. So we should model it with maximum flexibility for eventual display, by modelling that work A is textual, work B is a movie, and work B is an adaptation or work A. That's more information than simply saying Expression A (movie) and Expression B (text) are "the same work".

