CASE: Selected devotional songs of a Kannada saint poet; with Hindi and English translations.
Monday, June 17, 2013
TIP OF THE DAY
Whenever we recode an AACR2 NAR to RDA, we should also re-evaluate the
record (especially the heading) to see if anything needs to be revised.
Order of subfields k and l in Preferred Titles
QUESTION: What is order
of subfields k and l in preferred titles.
For example …$t Plays. $k Selections. $l Hindi.
ANSWER: Under RDA it has been determined that $k Selections is an attribute of a work and language ($l) is an attribute of an expression. So $k must preceed $l
[Answer provided by Ana Lupe Cristán]
For example …$t Plays. $k Selections. $l Hindi.
ANSWER: Under RDA it has been determined that $k Selections is an attribute of a work and language ($l) is an attribute of an expression. So $k must preceed $l
[Answer provided by Ana Lupe Cristán]
<<<----->>>>
EXAMPLE: For selected plays of a Panjabi author, translated into Hindi:
[240]-10 ‡a Plays. ‡k Selections. ‡l Hindi.
Publication Date and Copyright Date
If the record has both the publication and copyright dates, then the
008/06 should be "t" and the 008/11-14 should have the copyright
date. See LC-PCC PS 2.8.6.6 for examples.
LC-PCC PS for 2.8.6.6 -- DATE OF PUBLICATION NOT IDENTIFIED IN THE RESOURCE
DtSt Type of Date/Publication Status (OCLC MARC BIBLIOGRAPHIC)
LC-PCC PS for 2.8.6.6 -- DATE OF PUBLICATION NOT IDENTIFIED IN THE RESOURCE
<<<<<---------->>>>>
| t | Publication date and copyright date. The item has a
publication, release or production date and a copyright date. Date 1 is
the year of publication, release, or production; Date 2, the year of
copyright. Treat deposit dates (preceded by D.L.) as copyright dates.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Saturday, June 8, 2013
RDA 2.4.1 Serials' editor
Exception
Serials. Record a statement of responsibility identifying an editor of a serial only if the name of the editor is considered to be an important means of identifying the serial (e.g., if a particular person edited the serial for all or most of its existence; if the person's name is likely to be better known than the title of the serial).
Serials. Record a statement of responsibility identifying an editor of a serial only if the name of the editor is considered to be an important means of identifying the serial (e.g., if a particular person edited the serial for all or most of its existence; if the person's name is likely to be better known than the title of the serial).
Identifying Original and Translation in same resource
QUESTION:
700 02 ‡a Ugrādityācārya, ‡d 8th/9th century. ‡t Kalyāṇakāraka.
700 02 ‡a Ugrādityācārya, ‡d 8th/9th century. ‡t Kalyāṇakāraka. ‡l Hindi.
However, in this case, the 1st 700 would really result in the same N/T string as the 100/245 combo. So is it still required?
ANSWER:
This is in regards to 2011352604, which contains both the original text in Sanskrit and the Hindi translation. In AACR2, we would have had a 240 of Kalyāṇakāraka. $l Hindi & Sanskrit. In RDA, we would not have a 240. Instead, in theory, we would give 2 700s (as in the Mail Carrier example from the class materials):
700 02 ‡a Ugrādityācārya, ‡d 8th/9th century. ‡t Kalyāṇakāraka.
700 02 ‡a Ugrādityācārya, ‡d 8th/9th century. ‡t Kalyāṇakāraka. ‡l Hindi.
However, in this case, the 1st 700 would really result in the same N/T string as the 100/245 combo. So is it still required?
ANSWER:
Yes, two 700 name/title analytics. In some cases the preferred title may be the same as the 245 title proper, but in man other cases it won't be. We just thought it would always be easier to say "make the analytics" than to say "sometimes you do, and sometimes you don’t". So it may be redundant in some cases.
(Reproduction of suggestions of experts on RDA)
Revisions to CSM due to RDA
The Classification and Shelflisting Manual (CSM) contains the policies on assigning LC classification numbers and LC book numbers (i.e., shelflisting). Originally written in the 1980s and last updated in 2010, the CSM reflects the AACR2 environment.
The U.S. national libraries’ decision to implement Resource Description and Access (RDA) led the Policy and Standards Division (PSD) to review the CSM and determine which instruction sheets needed to be revised to reflect RDA instructions. Generally, the text was updated to ensure consistency with past classification and shelflisting practice, and new examples were chosen.
Specialists in PSD also took this opportunity to reevaluate some long-standing practices both to simplify them and to make them more sustainable in today’s linked, global, environment.
The priority was to first revise the instruction sheets that are most heavily affected by the implementation of RDA. Those sheets are now provided as PDFs on the ABA website at http://www.loc.gov/catdir/cpso/csm_instruction_sheets.html. PSD will also post additional instruction sheets there as the revisions are completed.
PSD is planning staff briefings on the policy changes, the times and dates of which will be announced in the coming days.
The brief descriptions of significant policy changes provided below are intended for guidance only. The full instruction sheets should be consulted for instructions and examples.
F 175 Editions The instructions for classifying simultaneously published editions were clarified.
F 632 Literary Authors Individual literary authors born before 1925 and anonymous literary works published before 1925 must now be printed in the schedule (i.e., numbers must be proposed for them). The cutoff dates had been 1870 and 1899, respectively. A section was added to clarify the classification of criticism and commentaries about an individual author’s works.
F 633 Literary Authors: Subarrangement of Works Compilations are no longer classified either as collections or as separate works based on whether the author is still living. Instead, the assignment of an RDA conventional collective title is now the sole determinant. The caption Selections, which is used frequently in the literary author tables, will be revised to Selections. Extracts. Passages in order to clarify the distinction between Selected works and Selections.
F 634 Literary Collections The treatment of a literary collection versus a collection in which one of the works is predominant was clarified.
G 140 Dates The examples of date formats were updated to reflect RDA instructions. Policy on the use of work letters was revised. New editions of works entered under corporate body should be assigned work letters beginning with b if necessary, to distinguish between editions published in the same year. This change makes the policy for corporate bodies consistent with the policy for works entered under a personal name or title. [The instruction to use the workmark a for serials was not changed.]
G 150 Translations Several languages were added to the Translation Table. Polyglot was redefined to mean that there are two or more translations present within a resource (previously, three translations were necessary). The Cuttering practice for translations in which the language is not listed in the Translation Table was revised. Instead of repurposing a Cutter extension in the Table, the language should be assigned a unique Cutter extension.
(Source: PSD-LC)
The U.S. national libraries’ decision to implement Resource Description and Access (RDA) led the Policy and Standards Division (PSD) to review the CSM and determine which instruction sheets needed to be revised to reflect RDA instructions. Generally, the text was updated to ensure consistency with past classification and shelflisting practice, and new examples were chosen.
Specialists in PSD also took this opportunity to reevaluate some long-standing practices both to simplify them and to make them more sustainable in today’s linked, global, environment.
The priority was to first revise the instruction sheets that are most heavily affected by the implementation of RDA. Those sheets are now provided as PDFs on the ABA website at http://www.loc.gov/catdir/cpso/csm_instruction_sheets.html. PSD will also post additional instruction sheets there as the revisions are completed.
PSD is planning staff briefings on the policy changes, the times and dates of which will be announced in the coming days.
The brief descriptions of significant policy changes provided below are intended for guidance only. The full instruction sheets should be consulted for instructions and examples.
F 175 Editions The instructions for classifying simultaneously published editions were clarified.
F 632 Literary Authors Individual literary authors born before 1925 and anonymous literary works published before 1925 must now be printed in the schedule (i.e., numbers must be proposed for them). The cutoff dates had been 1870 and 1899, respectively. A section was added to clarify the classification of criticism and commentaries about an individual author’s works.
F 633 Literary Authors: Subarrangement of Works Compilations are no longer classified either as collections or as separate works based on whether the author is still living. Instead, the assignment of an RDA conventional collective title is now the sole determinant. The caption Selections, which is used frequently in the literary author tables, will be revised to Selections. Extracts. Passages in order to clarify the distinction between Selected works and Selections.
F 634 Literary Collections The treatment of a literary collection versus a collection in which one of the works is predominant was clarified.
G 140 Dates The examples of date formats were updated to reflect RDA instructions. Policy on the use of work letters was revised. New editions of works entered under corporate body should be assigned work letters beginning with b if necessary, to distinguish between editions published in the same year. This change makes the policy for corporate bodies consistent with the policy for works entered under a personal name or title. [The instruction to use the workmark a for serials was not changed.]
G 150 Translations Several languages were added to the Translation Table. Polyglot was redefined to mean that there are two or more translations present within a resource (previously, three translations were necessary). The Cuttering practice for translations in which the language is not listed in the Translation Table was revised. Instead of repurposing a Cutter extension in the Table, the language should be assigned a unique Cutter extension.
(Source: PSD-LC)
LCSH revisions due to RDA Phase 2 revisions
The RDA Phase 2 changes to the name authority file were completed on March 27, 2013, so the Library of Congress’ Policy and Standards Division will now begin to update LCSH authority records. PSD expects to complete the project by the end of April 2013.
Personal, corporate, and conference names, as well as titles and geographic headings (MARC 21 fields 100, 110, 111, 130, and 151), that are established in the name authority file and are also printed in LCSH are eligible for revision. Phrase headings and subdivisions that are based on names or titles (e.g., Food in the Koran; Future life—Koranic teaching) will also be revised as necessary.
This is a large project that must be undertaken in a systematic manner in order to find all of the affected records. LC catalogers and SACO participants are therefore requested to refrain from making proposals to update headings until after PSD announces the completion of the project.
At this time, PSD is not planning a wholesale revision to those LC subject headings that include abbreviations that are not permitted in RDA, which chiefly appear in a subfield $y (e.g., Egypt—History—Early Dynastic Period, ca. 3100-ca. 2686 B.C.).
(Source: PSD, LC)
RDA Policies for Library of Congress
LC policies for a few topics recently discussed by the ABA Management Team. These policies either confirm that the interim policies LC staff have been following are still in place, or note where policies will be different in the post-March period.
The topics covered are:
Policy 1: RDA Acceptable Authority Records after March 31, 2013
Policy 2: Monographs Imported from OCLC (including copy cataloging)
Policy 3: CIP Verification
Policy 4: Working with Existing Serial Records
Policy 5: Added Volumes for Multipart Monographs
Policy 6: Manual Hybridization of AACR2 Records with RDA Elements
All staff involved with creating and updating LC/NACO authority records should pay particular attention to Policy 1 on the treatment of authority records. Policies 2-6 are primarily applicable to ABA and other processing units choosing to follow them.
These policies are also posted at http://www.loc.gov/aba/rda/pdf/rda-policies-for-lc.pdf
Phase 2 Changes to the LC/NACO Authority FileAlso note that the Phase 2 changes to the LC/NACO authority file were completed this week-- 371,942 records were updated as part of this process. Should you encounter one of these revised headings in your normal work, please use the new authorized form in your bibliographic record. A similar automated change is being planned for updating headings in bibliographic records, but until this process is complete, headings will be out of synchronization between the authority record and bibliographic records. Until the automated changes to bibliographic records are complete, it is not necessary to perform bibliographic file maintenance on existing bibliographic records, nor report the discrepancies to PSD.
Questions on these policies may be sent to LChelp4RDA@loc.gov
Acronyms as variants in RDA NARs
QUESTION:
Would the same rules for qualifying a corporate body apply to both the heading and the variants? For example, would this be appropriate under RDA:
110 2_ Progressive Artists Group (Jaipur, India)
410 2_ PAG (Jaipur, India)
We would never qualified "PAG" under AACR2 when it's used as a variant form. When it's used as a heading, of course, then we would qualify. What about in RDA?
ANSWER:
We had a very specific LCRI practice that basically forbade the adding of qualifiers to many kinds of references, we got rid of those restrictions on variants because they represented an exception that wasn't really important and only caused confusion. 11.13.2.1 tells you that you can add the same additions to variants as to authorized access points.
For personal names see RDA Rule 9.19.2.1
(Reproduction of Question and Answer from experts from LC)
Revised LC-PCC Policy for Fuller form of name (9.19.1.4, option)
From: Program for Cooperative Cataloging [mailto:PCCLIST@LISTSERV.LOC.GOV] On Behalf Of Reser, Dave
Sent: Thursday, February 21, 2013 5:23 PM
To: PCCLIST@LISTSERV.LOC.GOV
Subject: [PCCLIST] Revised LC-PCC Policy for Fuller form of name (9.19.1.4, option)
Dear PCC members--
Training documentation will be updated to reflect the change in policy.
Thanks, Becky Culbertson (PCC SCS chair) and Dave Reser (LC PSD)
Sent: Thursday, February 21, 2013 5:23 PM
To: PCCLIST@LISTSERV.LOC.GOV
Subject: [PCCLIST] Revised LC-PCC Policy for Fuller form of name (9.19.1.4, option)
Dear PCC members--
The policy related to the optional use of the RDA element "Fuller form of name" in authorized access points for persons (RDA 9.19.1.4, option) has been the subject of debate by more than one PCC Task Group, the PCC Policy Committee, and listservs such as PCCLIST. LC and PCC have agreed to a new shared policy for this instruction (a change from the previous LC policy). Because of the high level of interest in this topic, and the postponement of the February release of the RDA Toolkit where it would have been published (http://www.rdatoolkit.org/blog/517 ), we have taken the exceptional step of mounting the revised policy so that it may be applied immediately by catalogers. Until it is published in the Toolkit, the policy will reside in the Section "Preliminary Publication of LC-PCC PS" at http://www.loc.gov/aba/rda/lcps_access.html (the revised policy is also included below).
Thanks, Becky Culbertson (PCC SCS chair) and Dave Reser (LC PSD)
LC‐PCC PS for 9.19.1.4, Option (Fuller form of name)
New Authority Records
LC practice/PCC practice for Optional addition: 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 (see RDA 9.19.1.4).
Existing Authority Records
LC practice/PCC practice for Optional addition: 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.
<<<<--------->>>>
9.19.1.4 Fuller Form of
Name
Add a fuller form of the person’s name (see 9.5
) if needed
to distinguish one access point from another. Make this addition when the
person’s date of birth or date of death is not available (see 9.19.1.3).
) if needed
to distinguish one access point from another. Make this addition when the
person’s date of birth or date of death is not available (see 9.19.1.3).
EXAMPLE
Johnson, A. W. (Alva William)
Johnson, A. W. (Anthony W.)
Johnson, Carol (Carol Sue)
Johnson, Carol (Carol W.)
S. W. (Simon Wilson)
S. W. (Susanna
Warren)
Optional Addition 
Cataloger's Desktop Now Contains Six RDA-Related Resources
Library of Congress
News from CDS
Cataloger's Desktop Now Contains Six RDA-Related Resources
Another RDA-related resource has been added to Cataloger's Desktop. The new resource, RDA training resources, is maintained by the CILIP-BL Committee on RDA and provides links to RDA training from Cambridge University Library, CILIP Cataloguing & Indexing Group, the Australian Committee on Cataloguing, rdacake (RDA CAnadian Knowledge Exchange), Die Deutsche Nationalbibliothek, National Library of New Zealand, and several U.S. contributors.
The following is the current list of RDA-Related resources in Cataloger's Desktop:
* RDA: Information and Resources in Preparation for RDA (LC)
* RDA: LC Documentation for the RDA Test
* RDA: Resource Description and Access (subscription resource that requires a separate subscription to RDA Toolkit)
* RDA-L (JSC)
* RDA Training Resources (CILIP-BL)
* RDA Vocabularies (Open Metadata Registry)
Tuesday, June 4, 2013
Conference Names as Subordinate Bodies
In RDA the instructions for subordinate bodies (11.2.2.14) are the same as in AACR2.
Type 3 – Name that is general in nature
•Annual Meeting; Macadamia Nut Association
•110 2# $a Macadamia Nut Association. $b Annual Meeting
Type 6 – Name that includes the entre name of the higher body
•Annual Meeting of the International Whaling Commission
•110 2# $a International Whaling Commission. $b Annual Meeting
[Source: Library of Congress RDA Training materials]
Monday, June 3, 2013
Choosing the Preferred Name in Conferences, Seminars, Workshops, etc
l RDA 11.2.2.2
Sources of Information:
“Determine the preferred name for a corporate body from the following sources (in order of preference):
a) the preferred sources of information (see 2.2.2) in resources associated with the corporate body
b) other formal statements appearing in resources associated with the corporate body
c) other sources (including reference sources)”
l RDA 11.2.2.5
Different Forms of the Same Name:
“If different forms of a corporate body's name appear in resources associated with the body, apply the general instructions given below. When appropriate, apply the special instructions given under 11.2.2.5.1–11.2.2.5.4 as well.”
l RDA 11.2.2.5
Different Forms of the Same Name:
Order of preference:
• Form appearing in preferred sources of information
• Form presented formally on preferred source, if more than one
• Most commonly found form
• Brief form that would differentiate the body
l RDA 11.2.2.5.1
Variant Spellings :
“If variant spellings of the name appear in resources associated with the body, choose the form found in the first resource received.”
l RDA 11.2.2.5.2
More Than One Language Form of the Name:
Order of preference:
• Form in the official language of the body.
l LCPS: If there is more than one official language and one of these is English, choose the form in English
• Form in language used predominantly in resources
• Form that is presented first in the first resource received
[Source: Library of Congress RDA Training materials]
Conferences, meetings, exhibitions, fairs and festivals
These events now have the same rules
l RDA 11.2.2.11
Number or Year of Convocation of a Conference, Etc.:
“Omit from the name of a conference, congress, meeting, exhibition, fair, festival, etc. […] indications of its number, or year or years of convocation, etc.”
l No instruction to remove an indication of frequency (Annual, Biennial, etc.)
<<<<----------------->>>>
Examples:
l Omit year of convocation:
• CAV (Conference)
l NOT
• CAV ’91
l Retain indication of frequency (Annual, Biennial, etc.):
• Annual Conference on Fishing
l NOT
• Conference on Fishing [with “Annual” omitted]
[Source: Library of Congress RDA Training materials]
Named Conferences
Under RDA a conference name need not contain a word that denotes a conference, to be considered named
LCRI 21.1.B1 has no equivalent in RDA or in the LC-PCC PS
<<<<----------------->>>>
A named conference need only fulfill these RDA definitions
l RDA 8.1.2
Person, Family, and Corporate Body:
“The term corporate body refers to an organization or group of persons and/or organizations that is identified by a particular name and that acts, or may act, as a unit.”
l RDA 8.1.3
Name:
“The term name refers to a word, character, or group of words and/or characters by which a person, family, or corporate body is known.”
<<<<----------------->>>>
l Conference names eligible for use as an authorized access point (111 or 711)
• Freedom & Faith
• Digital Library Futures: User Perspectives and Institutional Strategies
l Considered unnamed under AACR2, but named under RDA
l May not convey the idea of a corporate body (conference)
<<<<----------------->>>>
Additions to names
l RDA 11.7.1.4
Names Not Conveying the Idea of a Corporate Body:
“If the preferred name for the body does not convey the idea of a corporate body, record a suitable designation in the language preferred by the agency creating the data.”
l Examples:
• Freedom & Faith (Conference) (1984 : Saint Charles, Ill.)
• Digital Library Futures: User Perspectives and Institutional Strategies (Conference) (2009 : Milan, Italy)
See also LC-PCC PS for 11.7.1.4
l Initialisms and Acronyms
• “If the name chosen for the authorized access point for a corporate body is an initialism or acronym written in all capital letters (with or without periods between them), add a qualifier to the name.”
l Example:
CICA (Conference) (2011 : Hangzhou, China)
[Source: Library of Congress RDA Training Materials]
Thursday, May 30, 2013
Monday, May 27, 2013
Thursday, May 23, 2013
Copy Cataloging in RDA documentation -- Library of Congress
Instructions for copycat in RDA>>
Copy Cataloging Using RDA
- Instructor Manual (May 2013) [Word : 6.30 MB]
- Exercise Answers (May 2013) [Word : 6.17 MB]
Tuesday, May 21, 2013
Single Portfolio or Case
For a resource consisting of one or more sheets, etc., housed in a single portfolio or case, record the extent as 1 portfolio or 1 case, as appropriate.
For cases consisting of two or more volumes, see 3.4.5.16.
.Monday, May 20, 2013
Field 040 Subfield Order in Serial RDA Records
The correct 040 subfield order for CONSER RDA serials in OCLC is: $a $b $e $c $d
Example:
040 DLC ǂb eng ǂe rda ǂc DLC ǂd OCLCQ ǂd CLU ǂd DLC
040 DLC ǂb eng ǂe rda ǂc DLC ǂd OCLCQ ǂd CLU ǂd DLC
Using Wikipedia in Authority Work
PSD, Library of Congress guidelines on Using Wikipedia in Authority Work
 |
| (click picture to enlarge) |
Saturday, May 11, 2013
RECORDING SCRIPTS IN RDA
LC-PCC PS for 7.13.2
SCRIPT
CORE ELEMENT FOR LC/PCC
Script is a core element for LC if a language is commonly written in more than one script, and if the resource is in a script other than the primary one for the language.
[2012-05]
LC-PCC PS for 7.13.2.3
RECORDING SCRIPTS
Form of Script Name
LC practice/PCC practice: Use the English language names of scripts found at: 〈http://www.unicode.org/iso15924/iso15924-en.html
〉. Generally do not include the parenthetical information found in the list when recording the script name.
〉. Generally do not include the parenthetical information found in the list when recording the script name.
If a resource is in a language that is commonly written in more than one script, name both the language and the script.
Applicability
LC practice/PCC practice: If the resource is in a script other than the primary one for the language, name both the language and the script in the language note (MARC field 546).
).
EXAMPLE
| 546 ## | $a Panjabi. |
For a publication using the Gurmukhi script
but
| 546 ## |
$a Panjabi $b Devanagari.
|
For a publication using the Devanagari script
| 546 ## | $a Sindhi. |
For a publication using the Persian script
but
| 546 ## |
$a Sindhi $b Gurmukhi.
|
For a publication using the Gurmukhi script
| 546 ## | $a Azerbaijani. |
For a publication using the Latin script
but
| 546 ## |
$a Azerbaijani $b Arabic.
|
For a publication using the Arabic script
| 546 ## |
$a Azerbaijani $b Cyrillic.
|
For a publication using the Cyrillic script
| 546 ## | $a Church Slavic. |
For a publication using the Cyrillic script
but
| 546 ## | $a Church Slavic $b Glagolitic. |
For a publication using the Glagolitic script
For complex notes involving multiple languages and scripts, see Policy Statement 7.13.2.4.
.
[2012-04]
LC-PCC PS for 7.13.2.4
Details of Scripts
LC practice/PCC practice: When recording complex notes involving multiple languages, record information about both the language and script in $a (Language note) of MARC field 546 (language and script in same subfield because $a is not repeatable).
(language and script in same subfield because $a is not repeatable).
EXAMPLE
| 546 ## | $a Kazakh, Uighur (Cyrillic), and Chagatai (Cyrillic and Arabic script). |
EXAMPLE
| 546 ## | Sanskrit (Latin and Devanagari) and English. |
[2012-04]
Wednesday, April 3, 2013
Authorized Access Point Representing an Expression
6.27.3 Authorized Access Point Representing an Expression (see this LC-PCC PS for Translations and Langugae editions)
(see this LC-PCC PS for Translations and Langugae editions)
Construct an access point representing a particular expression of a work or a part or parts of a work by combining (in this order):
EXAMPLE
Goncourt, Edmond de, 1822–1896. Frères Zemganno. English
Resource described: The Zemganno brothers / by Edmond de Goncourt. An English translation of a French novel
Pushkin, Aleksandr Sergeevich, 1799–1837. Evgeniĭ Onegin. English (Beck)
Resource described: Eugene Onegin / Alexander Pushkin ; translator, Tom Beck
Kolloidnyĭ zhurnal. English
Resource described: Colloid journal of the Russian Academy of Sciences. An English translation of a Russian serial
Piave, Francesco Maria, 1810–1876. Ernani. Spanish
Resource described: Ernani : drama lírico en cuatro actos / de F. Piave ; música de G. Verdi ; versión castellana de M. Capdepón. A Spanish translation of Piave’s libretto
Brunhoff, Jean de, 1899–1937. Babar en famille. English. Spoken word
Resource described: Babar and his children. An audio recording of an English translation of the children’s story
Wilde, Oscar, 1854–1900. Works. 2000
Resource described: The complete works of Oscar Wilde / general editors, Russell Jackson and Ian Small. — Oxford ; New York : Oxford University Press, 2000– . Other expressions of Wilde’s complete works have been published in other years
Shakespeare, William, 1564–1616. Works. 2003. Yale University Press
Resource described: The annotated Shakespeare. — New Haven : Yale University Press, ©2003–. An expression of Shakespeare’s complete works; another expression with title Nelson Thornes Shakespeare also began in 2003
Langland, William, 1330?–1400? Piers Plowman (C-text)
Resource described: Piers Plowman / by William Langland ; an edition of the C-text by Derek Pearsall. Langland’s work Piers Plowman exists in different versions designated as A-text, B-text, C-text, etc.
Nutcracker (Choreographic work : Baryshnikov)
Resource described: The nutcracker. A recording of a performance of the American Ballet Theatre and Mikhail Baryshnikov production of the ballet The nutcracker; choreography by Baryshnikov
Subscribe to:
Posts (Atom)