Minimal level cataloging is not yet clearly defined in RDA practice. For YUL processing, minimal level cataloging has been or can be applied to serial analytics as well as catalog management and other hidden collection projects, e.g.. where lack of language expertise or trained staff precludes full cataloging.
Minimal level cataloging is characterized by most, if not all, of the following:
At present, these guidelines are also limited to monographic print media; care should be taken to avoid cataloging individual serial issues as monographs or to confuse serial issues with volumes in monographic series. To the extent possible, these guidelines are consistent with RDA/PCC core cataloging.
For certain projects, designated monographs (usually but not always pamphlet-length) may be given minimal level cataloging if full cataloging copy is not available. In most cases, minimal level items are classed separately, even if they are part of a series. Otherwise, cataloging policies and procedures will be the same as those applied to serial analytics unless specifically noted in the instructions.
Serial analytics are usually brief pamphlet-length "volumes" of a monographic series. Serial analytics are cataloged as monographs ("books"). All of the volumes in the series are assigned the same call number. Unlike pamphlet projects, the classed-together number is generally LC classification. The volume number below the call number is used to differentiate the volumes on the shelf.
At YUL, serial analytics are by definition given minimal level cataloging unless fuller cataloging can be downloaded from OCLC. The decision to catalog the individual volumes of a monographic series at minimal level is made by the cataloger who set up the series, generally in consultation with public services. (By default, volumes of a monographic series normally receive full cataloging).
Serial analytics can be cataloged as monographs even if they are issues of a serial (i.e., they are issued on a regular basis with numeric and/or chronological designation), but there must be a decision recorded in Orbis (either in the authority record or the payment record) that the issues will be cataloged individually.
For minimal level project items not in the serial analytic workflow, it is first necessary to determine whether the resource to be cataloged is a monograph or a serial issue. If the item is a serial issue, it is out of scope. Serials are intended to be issued on a regular basis and usually combine a numeric and chronological designation, e.g. volume 1, no. 1, Jan. 2013, or sometimes only a chronological designation (spring 2014). Volumes issued annually (with only the year as the chronological designation) are also cataloged as serials. Do not confuse "theme issues" with monographs. As indicated by the name, these are issues of a serial on a particular topic, often with a particular title. In most cases, the issue will be a compilation of articles by different authors, but some theme issues may be, effectively, a single monograph either by a single author or by a group of collaborating authors. Note that serial analytics are generally of the latter type; if they are serial issues, each issue in the series is normally a monograph, not a "theme issue" compilation.
For decision and creation of series authority records for serial analytics, refer to Bibliographic Records for Monographic Series & Multipart Monographs on Standing Order: Cataloging Policies and Procedures. Part 3. Classed Together Analyzed (EL 7 Serial Analytics) and the Examples subsection.
Search Orbis for a bibliographic record. If a record is found, determine whether the record is for your item or is a second copy. If no Orbis record is found, search OCLC.
If a record is found in OCLC, verify that it is for your edition and that it was created by an English language cataloging agency. If the record was not created by an English language agency, generally do not export. Instead, create a new record from an RDA template following the instructions in part 3.
If the OCLC record is going to be used as the basis for variant edition cataloging, be sure to delete the 035 with the OCLC ID number and the 040 field.
If you download another library's institution record, be sure to delete the 035 with the OCLC ID number, but retain the 040 and the 079 fields even if the IR is not being used for variant edition cataloging.
Import the record into Orbis unless a duplicate window opens. Check with your supervisor if a duplicate window opens; do not complete the import until doing so.
Even if the call number on your item is local classification, retain the 050 field if there, since it may be used in the future for filtering and reports. If there is no 050 but there is a 090, re-tag it to 050 _4.
When the record is successfully imported, create a new MFHD. See guidelines at Part 5.
Open the template by clicking the New icon on the Voyager toolbar. Make sure you are using the RDA template (040 will have ‡e rda) and the template is for the book format (the Leader Type of Record is "a" and the Bibliographic Level is "m"). Change the template setting if a template for a serial or a non-print format opens.
In the Leader, change the Encoding Level from "5" to "7."
Since the 008 will be derived from what you enter in the MARC variable fields, put that part off until the variable fields have been completed.
020 (ISBN) Record the ISBN (International Standard Book Number) in field 020. Do not transcribe hyphens, include the qualifier for type of binding if it is printed with the ISBN on your item. If there is no ISBN present, you must delete the 020 field from the template before Voyager will allow the record to be saved.
Example:
|
020 |
‡a 9781607410812 (pbk.) |
Source of information. Take information for the 245 ‡a,‡b, and ‡c from the title page of the pamphlet. If there is no title page, use the cover. If this is not an option, check with your supervisor. Always take the ‡b information from the same source used for ‡a. If there is no statement of responsibility on the source used for the title, it can be taken from elsewhere on the item, but check with your supervisor.
Record the title in field 245 according to the following pattern-- note subfield coding, punctuation, and spacing. Use first indicator 1 if there is a 100 field; if there is no 100 field, use first indicator 0. Second indicator: number of spaces to skip if there is an initial article. Optionally, the unit can always use 0 and not transcribe the initial article.
Punctuation. 245 always ends with a period. If the statement ends with a bracket or a parenthesis, follow it with a period. If the statement ends with an abbreviation, do not add a second period.
| 245 | 1/0 | x | ‡a Title proper : ‡b Other title (i.e., rest of title) / ‡c Statement of responsibility. |
Transcribe in ‡a the title proper as it appears on the title page .
Transcribe in ‡b the other title information (such as subtitles, parallel titles, etc.) and precede it with a colon (:)
Transcribe author, editor, translator and corporate bodies as they appear on the title page in ‡c and precede with a slash (/).
Follow the capitalization style used on the title page. Optionally, use cataloging capitalization for some or for all items cataloged.
Unless you are familiar with the language, do not transcribe or supply diacritics. Policy on supplying diacritics can be determined by the nature of the project, linguistic expertise, and cataloging experience.
Example (in Orbis Thomas Gates is a see reference to Gates, Tom)
| 100 | 1 | ‡a Gates, Tom, ‡e author. | |
| 245 | 1 | 0 | ‡a Reclaiming the Transcendent : ‡b God in Process / ‡c Thomas Gates. |
Example. Diacritics in transcription are optional but could be mandatory for some projects when staff have expertise in the language. The source for parallel titles is not limited to the title page. The parallel title could be taken from, for example, the cover, even though the rest of the 245 is a transcription from the title page. As long as the parallel title is taken from somewhere in the book, it is not placed in brackets. A variant title field should be made for the parallel title (see below under 246).
| 100 | 1 | ‡a Đào, Huy Quyè̂n, ‡e author. | |
| 245 | 1 | 0 | ‡a Tượng gỗ Tây Nguyên = ‡b Wooden statues of Tay Nguyen / ‡c Đào Huy Quyền. |
Example (editor). This is not the same C. C. Liang established on the authority record. Optionally, the cataloging unit can differentiate this C. C. Liang from the established C. C. Liang with a qualifier, but it would need to be formulated by your supervisor even if no authority record is made.
| 245 | 0 | 0 | ‡a Challenge and summons / ‡c edited by C. C. Liang. |
| 700 | 1 | ‡a Liang, C. C. |
Example (two Other Titles, no 100, corporate name in 710). No authority record exists for the department. If "department" is not abbreviated on your item, do not abbreviate it in the access point.
| 245 | 0 | 0 | ‡a 8,000 FREE HOMESTEADS IN 1910 : ‡b Along the Lines of the Grand Trunk Pacific Railway in the Most Fertile Section of Western Canada : list of vacant lands, map and homestead regulations / ‡c Issued by General Passenger Department, Grand Trunk Pacific Railway Company. |
| 710 | 2 | ‡a Grand Trunk Pacific Railway Company. ‡b General Passenger Department. |
Generally transcribe the statement of responsibility as found without worrying about what titles, degrees, etc. to include or exclude.
| 100 | 1 | ‡a Paget, Henry Luke, ‡c Bishop of Chester, ‡d 1853-1937, ‡e author. | |
| 245 | 1 | 0 | ‡a Peace & happiness / ‡c by the Right Rev. H. L. Paget. |
In RDA the statement of responsibility is generally not abridged if there are more than 3 authors (the first or primary author is entered in 100 even if there are more than 3 authors). If the number of authors is very lengthy, it can be abridged using the method shown in the alternative example.
Example.
| 100 | 1 | ‡a Kroening, Karolin K., ‡d 1974- ‡e author. | |
| 245 | 1 | 0 | ‡a Analysis of Chemical Warfare Degradation Products / ‡c Karolin K. Kroening, Renee N. Easter, Douglas D. Richardson, Stuart A. Willison, Joseph A. Caruso. |
Alternative:
| 100 | 1 | ‡a Doll, Susan, ‡d 1954- ‡e author. | |
| 245 | 1 | 0 | ‡a All about Ohio / ‡c contributors, Susan Doll [and fifteen others]. |
If the statement identifies different functions, generally transcribe only the most significant statement (usually the first). If multiple functions are transcribed, separate different functions with a semicolon (with a space on either side).
Example. The statement of responsibility for the introduction is optional.
| 245 | 1 | 0 | ‡a Peace & happiness / ‡c by the Right Rev. H. L. Paget ; with an introduction by the Bishop of London. |
Make a variant access point for the title proper if there is a good chance someone would search under the variant.
Use first indicator 1 second indicator blank for all variant fields except parallel titles.
Use first indicator 3 second indicator 1 for parallel titles.
Do not use a period at the end of 246 (abbreviations excepted).
Example. In the previous 245 example, the title cannot be retrieved in Orbis if you leave out the comma, so make a variant access field for 8,000 without the comma. An apostrophe will have a similar effect, so a variant access field should be made if an apostrophe is part of the title proper.
The second 246 is probably less important than the first, but could be useful. Note that a 246 is not made for 1910, since users are unlikely to search under the spelled-out form of the date.
| 245 | 0 | 0 | ‡a 8,000 FREE HOMESTEADS IN 1910 : ‡b Along the Lines of the Grand Trunk Pacific Railway in the Most Fertile Section of Western Canada : list of vacant lands, map and homestead regulations / ‡c Issued by General Passenger Department, Grand Trunk Pacific Railway Company. |
| 246 | 1 | ‡a 8000 free homesteads in 1910 | |
| 246 | 1 | ‡a Eight thousand free homesteads in 1910 |
Example. Transcribe any typos as found on your title page in 245. If the typo occurs in the title proper, make a 246 with the title proper corrected. No 246 is necessary for typos in ‡b unless the title proper is very short (less than five words).
| 245 | 0 | 0 | ‡a Leve and be well. |
| 246 | 1 | ‡i Corrected title: ‡a Live and be well |
Example. If the title proper is in English and an ampersand has been used, make a 246 replacing the symbol with a word. For ampersands in other languages, and other symbols in the title proper, consult with your supervisor. Note that in the statement of responsibility, the second statement (in italics) is optional; the transcription can stop at Paget.
| 100 | 1 | ‡a Paget, Henry Luke, ‡c Bishop of Chester, ‡d 1853-1937, ‡e author. | |
| 245 | 1 | 0 | ‡a Peace & happiness / ‡c by the Right Rev. H. L. Paget. |
| 246 | 1 | ‡a Peace and happiness |
Example. 246 31 for parallel title.
| 100 | 1 | ‡a Đào, Huy Quyè̂n, ‡e author. | |
| 245 | 1 | 0 | ‡a Tượng gỗ Tây Nguyên = ‡b Wooden statues of Tay Nguyen / ‡c Đào Huy Quyền. |
| 246 | 3 | 1 | ‡a Wooden statues of Tay Nguyen |
Transcribe edition statements in 250 ‡a (both indicators are blank).
If the edition statement is expressed in different forms, use the form found on the title page (or wherever the title proper is taken from). If the edition statement does not appear on the title page, there is no order of preference for the other parts of the pamphlet; it can be from the cover, the verso of the title page, a page preceding or opposite the title page.
Transcribe edition statements as found; in RDA the cataloger does not supply abbreviations. If an abbreviation is used in the publication, transcribe it in that form.
Supplying diacritics and accents is optional.
Punctuation: same as 245: always end the statement with a period; if the statement ends with an abbreviation do not add a second period.
Example
Pamphlet title page: Fifth edition
| 250 | ‡a Fifth edition. |
Pamphlet. No statement on title page; statement on verso: Revised 2nd ed.
| 250 | ‡a 2nd ed. revised for RDA |
Pamphlet. No statement on title page. Cover: Updated
| 250 | ‡a Updated. |
Pamphlet title page: *** édition.
| 250 |
‡a *** édition. |
Pamphlet. No statement on title page. Cover: Corr. 2nd print.
| 250 | ‡a Corr. 2nd print. |
Take the place, publisher, and date of publication from the same source as the title proper, in most cases, then, the title page.
If the information is not on the title page, take it from elsewhere on the book, e.g. the verso or the cover. Sometimes this information is only on the last page of the publication, which is called the colophon.
Record the place of publication, the name of the publisher, and the date(s) of publication according to the following pattern:
| 264 | 1 | ‡a <Place of publication> : ‡b <Name of publisher>, ‡c <date of publication> |
The punctuation and subfield are provided in the template. If information is added in brackets, use separate pairs of brackets for each subfield. If the 264 field ends with a date, end the field with a period. If the 264 field ends with another mark of punctuation (bracket, parentheses, hyphen) do not add a period at the end of the field.
If there is more than one place of publication, transcribe the first named only. If there is more than one publisher, transcribe the first named only. Transcribe place and publisher name as you find it on the resource.
Transcribe the place of publication and the name of the publisher as they appear on your source. Transcribe any abbreviations if they appear, but do not convert any spelled-out word to an abbreviation. Use the capitalization as found and transcribe any errors as found. Do not add [sic] when transcribing an error found on the source.
If there is no place of publication found on the item, check with your supervisor and see if an inferred place of publication can be provided. If so, enter the inferred place of publication in brackets in 264 ‡a. If an inferred place of publication cannot be identified, then use [Place of publication not identified].
If there is no publisher named on the item, enter [publisher not identified] in ‡b.
Do not transcribe the name of the distributor or printer in ‡b. If there is no identifiable publisher and a distributor or printer are named, check with your supervisor.
If there is no publication date, and there is a copyright date, generally use the date named in the copyright in brackets, without the "c." Optionally, add a second 264 _4 with the copyright symbol and date in ‡c. In 264 _4, ‡a and ‡b are never used, and there is no period at the end of the field.
Lack of publication date is sometimes a problem with pamphlets and other hidden collections material. RDA options for recording dates of publication, distribution, etc. in the absence of an explicit publication date differ from the AACR2 options. The following table lists RDA options.
| Date information from item | 264 ‡c |
| 2014 | 2014. |
| c2011 | [2011] |
| recently published; received for cataloging in 2013 | [2013?] |
| title page has May 2002; no other dates on the item | May 2002. |
| refers to events that took place in 2001 and appears to have been published around that time | [approximately 2001] |
| published during the academic year 1985-1986 | [1985 or 1986] |
| ongoing multipart, part 1 published 1985, part 2 published 1986, other parts not yet published | 1985- |
| part 1 published 1970, part 2 published 1979, set is complete | 1970-1979. |
| published sometime in the 1970's | [between 1970 and 1979?] <do not use [197-]> |
| probably published in the early 20th century | [between 1900 and 1930?] |
| published in the 19th century | [between 1801 and 1900?] <do not use [19--?]> |
| a working paper based on a master's thesis; MA granted 1996 | [not before 1996] |
| a pamphlet predicting the collapse of the Soviet regime shortly before it collapsed | [not after 1989] |
Example. Title page: New York, Indianapolis, San Francisco, Toronto. New-Tech Inc. 1992
| 264 | 1 | ‡a New York : ‡b New-Tech Inc., ‡c 1992. |
Example. When transcribing the publisher name, include the entire hierarchy.
| 264 | 1 | ‡a [Yogyakarta] : ‡b Kerjasama Komunitas Penyair Lilin, Universitas Atma Jaya Yogyakarta [dan] Buku Litera Yogyakarta, ‡c 2013. |
Example. Transcribe the entire publisher statement. Although only one publisher is mandatory, if two publishers are connected grammatically, transcribe both in a single ‡b.
| 264 | 1 | ‡a New Delhi : ‡b Published by Indian National Trust for Art and Cultural Heritage and Aryan Books International, ‡c 2013. |
Example. No statement on title page, verso, cover or colophon. Author of pamphlet: Thomas Frost. On the page preceding the title page: ©2014 by Thomas Frost, 120 High St., New Haven, CT 06520. When supplying information in brackets, generally do not use abbreviations.
| 264 | 1 | ‡a [New Haven, Connecticut] : ‡b Thomas Frost, ‡c [2014] | |
| 264 | 4 | ‡c ©2014 <optional> |
Example. If the publication is a non-Gregorian date, transcribe it as found but provide the Gregorian date in brackets. Note that an inferred place of publication is not limited to a municipality. If the city is not known, the state or even the country is a possibility. This situation is more likely to occur in international collections projects.
| 264 | 1 | ‡a [California?] : ‡b [publisher not identified], ‡c 1392 [2013] |
Example. If the publisher cannot be identified, but the distributor or printer is given, a second 264 field is made with a distributor or printer second indicator. For this type of situation, consult with your supervisor. In this example, the place of publication and date of publication were given, but not the publisher name. However, the printer name (as well as the location and date of printing) were on the item and were transcribed in a second 264 field (note the different indicator for the printer 264).
| 264 | 1 | ‡a Guadalajara, Jal. : ‡b [publisher not identified], ‡c 2013. | |
| 264 | 3 | ‡a Guadalajara, Jalisco : ‡b Castro Impresores, ‡c 2013. |
Example. Use "place of publication not identified" as a last resort. In the following example, the 008 was coded for the Marshall Islands (xe), but 264 says the place is not identified.
| 264 | 1 | ‡a [Place of publication not identified] : ‡b [CreateSpace], ‡c [2013] |
264 would be better as:
| 264 | 1 | ‡a [Marshall Islands?] : ‡b [CreateSpace], ‡c [2013] |
Note that the subfields get separate sets of brackets.
300 ‡a is mandatory for all minimal level records. Record pages, leaves, or volumes as appropriate. Abbreviations should not be used. Only the primary extent pages or leaves are mandatory. Recording preliminary pages and inserted sequences is optional.
Examples.
Item has xii preliminary pages; the main pagination sequence is 36 pages.
| 300 | ‡a 36 pages |
Item consists of 30 numbered leaves (pages with printing on only one side):
| 300 | ‡a 30 leaves |
Item consists of ii numbered pages and 30 unnumbered pages.
| 300 | ‡a 1 volume (unpaged) |
Item consists of ii numbered pages and 30 unnumbered leaves.
| 300 | ‡a 1 volume (unfoliated) |
Item is 50 pages with 6 unnumbered leaves of plates (picture without text or a brief text label). Two groups of 3 leaves are inserted between pages 10-11 and pages 40-41:
| 300 |
‡a 50 pages |
Item has pagination in the following sequences: i-x, 1-13, 1-8, i-xx.
| 300 | ‡a 1 volume (various pagings) |
Item has 25 numbered pages, but roman numerals are used instead of Arabic numerals.
| 300 | ‡a xxv pages |
Item is 10 leaves but uses lower-case letters of the alphabet.
| 300 | ‡a a-j leaves |
Although unlikely in the case of serial analytics, some projects may have to deal with multipart monographs.
If the multipart set is complete, record the number of volumes. Note that volumes is not abbreviated.
| 300 | ‡a 2 volumes |
If the set is complete and the volumes are paged continuously, record the number of pages in parentheses.
| 300 | ‡a 2 volumes (1578 pages) |
If the set is incomplete, record only volumes:
| 300 | ‡a volumes |
300 ‡b-‡c are not used in serial analytic records. The subfields are optional for project work and can be determined at the beginning of the project.
300 ‡b. If used, limit terms to: illustrations, color illustrations, or illustrations (some color). Use of the terms "chiefly" or "all" in ‡b is not necessary and may not be RDA compliant. Do not abbreviate. For individual projects, more specific RDA authorized terms may be used if necessary.
300 ‡c. If used, follow these examples:
Height in centimeters, round up to the next whole centimeter. If the height is less than 10 cm, consult with your supervisor. No period after cm
| 300 | ‡a 15 pages : ‡b illustrations ; ‡c 25 cm |
Height x Width if the width is greater than or less than half the height.
| 300 | ‡a 17 pages ; ‡c 28 x 31 cm |
For unbound sheets, or unbound sheets in portfolios, boxes, or other containers, consult with your supervisor.
336-337-338. These RDA fields are provided in the template. If you catalog a sheet, you will need to change 338 to sheet. If you need to catalog a sheet or sheets, consult with your supervisor. Otherwise, leave the fields as is.
If the series appears on a separate page, transcribe the series title and the volume number (including the caption) from that page. Otherwise, take the series name from the title page, the verso of the title page, or the cover. Transcribe the series statement as found (using the same guidelines as applied to 245 ‡a).
Do not transcribe subtitles. Do not transcribe statements of responsibility unless the title is generic (if no series of responsibility appears with a generic title, do not supply one). If a statement of responsibility is transcribed, use a / as with 245 ‡c, but do not enter ‡c.
If a volume caption is not abbreviated on your source, do not abbreviate it; if a volume caption is abbreviated, transcribe the abbreviated form. If roman numerals are used, transcribe them as roman numerals. Do not add a period at the end of the field. Also transcribe the ISSN if there (the number should appear with the series: 4 digits-4 digits. Pattern and punctuation:
| 490 | 1 | ‡a <Series title proper>, ‡x <ISSN if there> ; ‡v <caption and volume number, if there> |
Search for the series title in ORBIS using the Staff Title search, and, if necessary, in LC Authorities, using Title Authority Headings search type. If you retrieve an authority record for the series, check field 644 for code t. If the code is "t," create an additional field 830. If it is code "n," make an 830 field but notify your supervisor about updating the authority record locally.
The 830 field is always the field in the record you are creating unless the record has an 856 or a 9xx field. In 830, use the title in the authority record 130 field exactly as found (the 130 will not begin with an article, unlike 490), and use the caption exactly as found in the authority record's 642 field (the caption will usually be abbreviated). End field 830 ‡v with a period. If there is no ‡v, end ‡a with a period. If there is an ISSN, record it in ‡x at the end of 830, with no period. Pattern and punctuation:
| 830 | 0 | ‡a <Series title proper> ; ‡v <caption & volume number if there>. ‡x ISSN |
If the series is not represented by an authority record, but the series has been used in a bibliographic record in 830 or 440, use the name and volume caption exactly as found in the bibliographic record 830. If there is no 830 but there is a 440 field, use the name exactly as found in 440 minus the initial article, but enter the series in 830, NOT 440. The Staff Title search does not retrieve 490 fields.
For serial analytics, there should be a series authority record in Orbis, with a 090 field, the classed-together number, and <PROV ANLYZ ONLY>. If none is found, or if the series authority record lacks a 090, check with your supervisor. For minimal level projects, if no series authority record or bibliographic record using the series is found, check with your supervisor.
Example. The 830 is determined by the series authority 130 field and differs significantly from the 490 field. In this example, the volume number includes the year. The authority record 642 only uses the decade and year (95-12), but bibliographic records in Orbis add the century beginning in 2000.
| 490 | 1 | ‡a Bank of Canada working paper ; ‡v 2005-39 | |
| 830 | 0 | ‡a Working paper (Bank of Canada) ; ‡v 2005-39. |
Example: ISSN and subseries. Note end punctuation in ‡v and ‡x. If both the main series and the subseries have volume numbering, check with your supervisor.
| 490 | 1 | ‡a Colección Eutopías. Documentos de trabajo, ‡x 0213246X ; ‡v 238 | |
| 830 | 0 | ‡a Colección Eutopías. ‡p Documentos de trabajo ; ‡v vol. 238. ‡x 0213-246X |
Example: generic title w/statement of responsibility. Note that in 490, there is no ‡c after the slash. The 830 ‡a is taken from the series authority 130.
| 490 | 1 | ‡a Working paper / National Centre for Development Studies, Australian National University ; ‡v no. 91/1 | |
| 830 | 0 | ‡a Working paper (Australian National University. National Centre for Development Studies) ; ‡v no. 91/1. |
Not all of 008 fields are required. The mandatory 008 fields are:
Date Examples
| 264 ‡c | Code | Date 1 | Date 2 |
| 2002 | s | 2002 | #### |
| [2002?] | s | 2002 | #### |
| [approximately 2002] | s | 2002 | #### |
| 1998- | m | 1998 | 9999 |
| 1998-2000 | m | 1998 | 2000 |
|
2013 reprint date; 1980 original date of publication |
r | 2013 | 1980 |
| [between 2002 and 2011] | q | 2002 | 2011 |
Reminder: in RDA cataloging, if there are multiple authors, the first named author is always entered in 100 1_. Exceptionally, if an author is not named first but appears prominently (extra large font size, for example), enter that author in 100. The other authors are entered in 700 1_.
Authors (100). Add ‡e author to the end of the field. Precede the delimiter with a comma unless the author date ends with a hyphen. Always enter a period after author. If the pamphlet is a bibliography, enter the compiler's name in 100 and add ‡e compiler.
Editors, Translators (700). Editors and translators are almost always entered in 700 rather than 100. If an editor is named on the title page, make a 700 for the name, especially if there is no author. Make a 700 for the translator if the work translated is in literature or the humanities (history, philosophy). Do not add a ‡e to editors, non-bibliography compilers, and other contributors who are not authors.
Corporate and Conference Names. For pamphlet length materials, neither corporate nor conference names are likely to need a 110 or 111. In the absence of an author, generally enter a corporate or conference name in 710 (corporate) or 711 (conference) if it is mentioned prominently on the title page.* Use first indicator 2 for corporate names unless ‡a is a jurisdiction (a place name), in which case use first indicator 1. For conference names always use first indicator 2. If a corporate name is entered in 710, do not use ‡e. For conference names (111), never use ‡e.
*If the pamphlet is a brief report attributed to a corporate body, enter it under 110 2/1 and add ‡e author.
If the item is a paper from a conference, make a 711 for the conference name if it has been established. A collection of papers or proceedings of a conference would have a 111 for the conference name, but pamphlet-length items are unlikely to be compilations of this kind.
Search for the correct form of the heading (personal, corporate, or conference) in ORBIS and, if necessary, in LCDB. If a personal name or a corporate name is not represented in ORBIS or in LCDB, use the form of the name as found on the item (last name first for personal names unless instructed otherwise). Include dates if the information is readily determined from the book.
If a conference name is not represented in ORBIS or in LCDB, do not record it in field 1xx or field 7xx. For project work, check with your supervisor with regard to formulating a 711 if a conference name is needed.
Examples:
Woolf, Virginia, ‡d 1882-1941 (as found in ORBIS)
| 100 | 1 | ‡a Woolf, Virginia, ‡d 1882-1941, ‡e author. |
Obama, Michelle, ‡d 1964- (as found in ORBIS). Because of the hyphen, no comma before ‡e.
| 100 | 1 | ‡a Obama, Michelle, ‡d 1964- ‡e author. |
Jean C. Gray (as found on the title page, but not found in ORBIS or in LCDB). Back cover: "born 1996"). The pamphlet is a bibliography for which Gray has sole responsibility.
| 100 | 1 | ‡a Gray, Jean C., ‡d 1996- ‡e compiler. |
Yale University. ‡b Library. (as found in ORBIS). A report on library renovations in 2014.
| 110 | 2 | ‡a Yale University. ‡b Library, ‡e author. |
Book has: AGEPE. Orbis has a reference from AGEPE to Côte d'Ivoire. ‡b Agence d'études et de promotion de l'emploi.
| 710 | 1 |
‡a Côte d'Ivoire. ‡b Agence d'études et de promotion de l'emploi. |
A paper from Actes de la 1re Journée d'études sur la Libye antique et médiévale, Sorbonne, France. Conference headings are hard to formulate correctly. Until recently, authority records were only made for the name of the conference, not for the individual conference; the cataloger had to formulate and supply the number, date, and location in the parentheses. Hopefully the need for these will be a rare occurrence. If a conference is needed as an access point, always check with your supervisor
| 711 | 2 |
‡a Journée d'études sur la Libye antique et médiévale ‡n (1st : ‡d 2010 : ‡c Paris, France) |
After completing the record, attempt to save the record by clicking on the sailboat icon labelled "Save to DB." The authority validation window will appear. Validate all of the headings that appear on the record (name and series) according to the Authority Control Workflow for Yale C&T Staff guidelines.
1. Serial analytics.
2. Project work. The project supervisor will determine the guidelines for call number assignments.
After cataloging, all minimal-level records should be exported to MARS, and will eventually be batch-exported to OCLC.