Planet Cataloging

February 05, 2016

Resource Description & Access (RDA)

Top 10 RDA Blog Posts of 2015 on Resource Description & Access Cataloging

RDA Blog

This was the fourth year of RDA Blog on Resource Description and Access (RDA).  We hope that our posts have been both interesting and helpful to all librarians and catalogers. As 2015 comes to a close, I want to share our most read articles of the year.

Top 10 RDA Blog Posts of 2015 

  1. RDA Cataloging Rules for Pseudonyms with MARC 21 Examples
  2. International Standard Book Number (ISBN) - MARC to RDA Mapping
  3. RDA Cataloging Examples
  4. Articles, Books, Presentations on Resource Description and Access (RDA)
  5. Establishing Certain Entities in the Name or Subject Authority File : RDA Cataloging
  6. Libhub Initiative
  7. Corrected Titles Proper & Variant Titles : RDA vs AACR2 : Questions and Answers & Best Practices
  8. RDA Bibliography
  9. LC RDA Implementation of Relationship Designators in Bibliographic Records
  10. 33X fields do not necessarily mean RDA
Thank you for reading RDA Blog on Resource Description and Access (RDA)! Happy New Year, friends!

Resource Description and Access


by Salman Haider (noreply@blogger.com) at February 05, 2016 02:39 PM

Date of Publication Distribution Copyright in RDA & MARC 21 Field 264 Examples

Resource Description and Access RDA

Date of Publication, Distribution, and Copyright in Resource Description and Access (RDA) Cataloging Rules & MARC 264 Examples

Table of Contents:
  • Core Element
  • How Date of Publication is defined in RDA
  • Where the Rules are for Date of Publication in RDA
  • What are the Sources of Information for Date of Publication in RDA
  • How is Date of Publication Transcribed / Recorded in Resource Description and Access (RDA)
  • Dates of the Non-Gregorian or Julian Calendar; Dates in the Form of Chronogram
  • RDA Examples
  • What to do if the date on the resource is incorrect
  • Multipart Monographs, Serials, and Integrating Resources
  • Date of Publication not Identified in a Single-Part Resource
  • RDA Cataloging Examples of Dates
  • Supplying Dates (Date of Publication Not Identified in the Resource)
  • Importance of Supplying Probable Place and Date of Publication
  • Examples of Supplying Publication Data
  • Other RDA Examples of Dates
  • Date of Distribution
  • Where the Rules are for Date of Distribution in RDA
  • What are the Sources of Information for Date of Distribution in RDA
  • Recording Date of Distribution
  • Dates of the Non-Gregorian or Julian Calendar; Dates in the Form of Chronogram
  • Multipart Monographs, Serials, and Integrating Resources
  • Date of Distribution Not Identified in a Single-Part Resource
  • Copyright Date
  • Coreness for Copyright Date
  • Where the Rules are for Copyright Date in RDA
  • What are the Sources of Copyright Date in RDA
  • Recording Copyright Dates
  • Other RDA Blog posts on Publication, Distribution, and Copyright Date

Core Element: Date of publication is a Core Element; If the date of publication appears on the source of information in more than one calendar, only the date in the calendar preferred by the agency preparing the description is required.

How Date of Publication is defined in RDA: A date of publication is a date associated with the publication, release, or issuing of a resource.
The date of publication is the year in which the edition, revision, etc., described in the edition area was published. If there is no edition area, the date of the first publication of the edition to which the item belongs is considered the publication date.

Where the Rules are for Date of Publication in RDA: Look at instruction 2.8.6 in RDA Toolkit

What are the Sources of Information for Date of Publication in RDA: Take dates of publication from the following sources (in order of preference):

a) the same source as the title proper (see 2.3.2.2)

b) another source within the resource itself (see 2.2.2)

c) one of the other sources of information specified under 2.2.4.

How is Date of Publication Transcribed / Recorded in Resource Description and Access (RDA): Record the date of publication applying the basic 2.8.1 instructions on recording publication statements, using the form in which it appears on the source of information.

Example:
Source: Published in 2016
264  #1   ..., $c 2016.

Apply the guidelines on capitalization, punctuation, symbols, abbreviations, etc. given under 1.7.

Per LC-PCC PS 1.8.2 (First Alternative), transcribe roman numerals for publication dates; do not convert to Arabic. If the year appears only in Roman numerals, add the year in Arabic numerals, in brackets.

Example:
Source: MMXVI
264  #1   ..., $c MMXVI [2016]

Dates of the Non-Gregorian or Julian Calendar; Dates in the Form of Chronogram
  • LC-PCC PS 2.8.6.3: Add the corresponding date or dates of the Gregorian or Julian calendar if the date appearing in the resource is not of the Gregorian or Julian calendar.
Examples:

Source: 5630
264  #1   ..., $c 5630 [1869 or 1870]

Source: Heisei 1 
264  #1   ..., $c Heisei 1 [1989]

Source: anno 18
264  #1   ..., $c anno 18 [1939]

Source: Samvat 2000
264  #1   ..., $c Samvat 2000 [1943]

If the date as it appears on the resource is represented in different calendars, record the dates in the order indicated by the sequence, layout, or typography of the dates on the source of information.

Example:
Source: 4333 - 2000
264  #1   ..., $c 4333, 2000.

Resource Description and Access RDA

Question: What to do if the date on the resource is incorrect. Answer: If the date as it appears in the resource is known to be fictitious or incorrect, make a note giving the actual date

Example: Probable year of publication based on date range in which the publisher was active: Date of publication recorded as: [1969?]
  • LC-PCC PS 2.8.6.4: Record a supplied date in numerals instead of giving the chronogram. (A chronogram is a sentence or inscription in which specific letters, interpreted as numerals, stand for a particular date when rearranged). Indicate that the information was taken from a source outside the resource itself. Example: [1945]
    Multipart Monographs, Serials, and Integrating Resources

    RDA Rule 2.8.6.5 is for Multipart Monographs, Serials, and Integrating Resources

    If the first issue, part, or iteration of a multipart monograph, serial, or integrating resource is available, record the date of publication of that issue, part, or iteration, followed by a hyphen.
    Example: 1988-

    If publication of the resource has ceased or is complete and the first and last issues, parts, or iterations are available, record the dates of publication of those issues, parts, or iterations, separated by a hyphen.
    Example: 1968-1973

    If publication of the resource has ceased or is complete and the last issue, part, or iteration is available, but not the first, record the publication date of the last issue, part, or iteration, preceded by a hyphen.
    Example: -1977

    For an integrating resource, supply the date of the last update if it is considered to be important.
    Example: 1995–1998 [updated 1999] [First and last published iterations of an updating loose-leaf available; date of last update known]

    If the date of publication is the same for all issues, parts, or iterations, record only that date as the single date. Example: 1997

    If the first and/or last issue, part, or iteration is not available, supply an approximate date or dates.

    Example: [1998]- [Earliest issue available: v. 1, no. 3, July 1998]
    1997-[2000] [Last part not available but information about ending date known]
    [1988-1991] [First and last issues not available but information about beginning and ending dates known]

    If the date or dates cannot be approximated, do not record a date of publication.

    Date of Publication not Identified in a Single-Part Resource

    RDA Rule 2.8.6.6 is for Date of Publication not Identified in a Single-Part Resource

    If the date of publication is not identified in the single-part resource, supply the date or approximate date of publication. Apply the instructions in 1.9.2 on supplied dates (see p. 27).

    If an approximate date of publication for a single-part resource cannot reasonably be determined, record [date of publication not identified].

    But see the next page for important LC practice in such situations …………………
    Look at LC-PCC PS 2.8.6.6

    Supply a probable date of publication, if possible, using the guidelines below, rather than give “[date of publication not identified].”

    A. If an item lacking a publication date contains only a copyright date, apply the following in the order listed:

    1. Supply a date of publication that corresponds to the copyright date, in square brackets, if it seems reasonable to assume that date is a likely publication date.
    Example:
    Title page verso: Copyright ©2009
    Prefaced signed: June 2009
    Date of publication: not given

    Transcription: 264 #1 $a … $b … $c [2009]
    008/06: s
    008/07-10: 2009
    008/11-14: ####

    2. If the copyright date is for the year following the year in which the publication is received, supply a date of publication that corresponds to the copyright date.
    Example:
    Title page verso: ©2009
    Item received in: 2008
    Date of publication: not given

    Transcription: 264 #1 $a … $b … $c [2009]
    optionally: 264 #4 $c ©2009
    008/06: t
    008/07-10: 2009
    008/11-14: 2009

    B. If an item lacking a publication date contains a copyright date and a date of manufacture and the year is the same for both, supply a date of publication that corresponds to that date, in square brackets, if it seems reasonable to assume that date is a likely publication date.
    Example:
    Title page verso: ©1980//1980 printing
    Date of publication: not given

    Transcription: 264 #1 $a … $b … $c [1980]
    008/06: s
    008/07-10: 1980
    008/11-14: ####

    C. If an item lacking a publication date contains a copyright date and a date of manufacture and the years differ, supply a date of publication that corresponds to the copyright date, in square brackets, if it seems reasonable to assume that date is a likely publication date. A manufacture date may also be recorded as part of a manufacture statement if determined useful by the cataloger, or record it in MARC field 588 as a Note on issue, part, or iteration used as the basis for identification of a resource (2.20.13)
    Example:
    Title page verso: ©1978//Sixth Printing 1980
    Prefaced signed: June 1978
    Date of publication: not given

    Transcription: 264 #1 $a … $b … $c [1978]
    optionally: 264 #3 $a … $b … $c 1980.
    588 ## $a Description based on sixth printing, 1980.
    008/06: s
    008/07-10: 1978
    008/11-14: ####

    D. If an item contains only a date of distribution, apply the following in the order listed:
    1. Supply a date of publication that corresponds to the distribution date, in square brackets, if it seems reasonable to assume that date is a likely publication date. Also record a date of distribution as part of a distribution statement if determined useful by the cataloger.
    Example:
    Title page verso: Distributed 2008
    Bibliography includes citations to 2007 publications
    Date of publication: not given

    Transcription: 264 #1 $a London :$b Gay Mens Press, $c [2008]
    008/06: s
    008/07-10: 2008
    008/11-14: ####
    optionally: also give 264 #2 $a Chicago, IL : Distributed in North America by InBook/LPC Group, $c 2008

    2. If it does not seem reasonable to assume that the distribution date is a likely publication date, supply a date of publication, in square brackets, based on the information provided. Also record the distribution date as part of a distribution statement if determined useful by the cataloger.
    Example:
    Title page verso: Distributed in the USA in 1999
    Prefaced signed: London, January 1993
    Date of publication: not given

    Transcription: 264 #1 $a … :$b … $c [between 1993 and 1999]
    008/06: q
    008/07-10: 1993
    008/11-14: 1999

    E. If an item lacking a publication date contains only a date of manufacture, apply the following in the order listed:

    1. Supply a date of publication that corresponds to the manufacture date, in square brackets, if it seems reasonable to assume that date is a likely publication date. For books, this means that the item is assumed to be the first printing of the edition. Also record the manufacture date as part of a manufacture statement if determined useful by the cataloger.
    Example:
    Title page verso: First Printing 1980
    Date of publication: not given

    Transcription: 264 #1 $a … :$b … $c [1980]
    008/06: s
    008/07-10: 1980
    008/11-14: ####

    2. If the date of manufacture given implies that it is not likely the same as the date of publication, supply a date of publication, in square brackets, using the information provided. Also record the date of manufacture as part of a manufacture statement if determined useful by the cataloger, or record it in MARC field 588 as a Note on issue, part, or iteration used as the basis for identification of a resource.
    Example:
    Title page verso: 15th Impression 1980
    Date of publication: not given

    Transcription: 264 #1 $a … :$b … $c [not after 1980]
    optionally: 588 ## $a Description based on 15th impression, 1980.
    008/06: q
    008/07-10: uuuu
    008/11-14: 1980

    Supplying Dates (Date of Publication Not Identified in the Resource)
    RDA 1.9.2 shows examples of supplying dates

    Actual year known: 264 … $c [2010]

    Either one of two consecutive years: 264 … $c [2009 or 2010]

    Probable year: 264 … $c [2010?]

    Probable range of years: 264 … $c [between 2008 and 2010?]

    Earliest and/or latest possible date known:
    264 … $c [not before January 15, 2010]
    264 … $c [not before September 3, 1779]  - earliest date is known
    264 … $c [not after August 21, 1492]  - latest date is known
    264 …$c [between October 25, 1899 and February 25, 1900]  - both earliest and latest dates are known

    Importance of Supplying Probable Place and Date of Publication
    LC Policy strongly encourages you to supply a probable place of publication and a probable date of publication when this information is not on the resource. This helps with displays, and limits by place and date in OPACs. If you cannot supply this data, you will need to record Distribution data, and perhaps even Manufacture data.
    • Distribution elements are Core Elements ONLY if Publication data can not be identified. So you can save yourself the trouble of recording distribution data by supplying place and date of publication. And you can use distribution or manufacture information to help supply place and date of publication.
    As a last resort, if you have to give any distribution or manufacture information, give distribution information if present; if not, then give manufacture information. Be sure to give as complete a statement as possible.

    Examples of Supplying Publication Data

    Distribution statements are recorded in MARC field 264 #2. This need for a second MARC field is another reason why you are strongly encouraged to supply publication data if at all possible.

    These examples illustrate how supplying publication data is easier -- and perfectly acceptable:

    Example A:
    On source: ABC Publishers, 2009
    Distributed by Iverson Company, Seattle

    RDA: 264 #1 $a [Place of publication not identified] : $b ABC Publishers, $c 2009.
    264 #2 $a Seattle : $b distributed by Iverson Company, $c [2009]

    LC-Recommended: 264 #1 $a [Seattle?] : $b ABC Publishers, $c 2009.

    Example B:
    On source: On title page: Means Pub. Co., Omaha, Nebraska
    On title page verso: 2009 distribution

    RDA: 264 #1 $a Omaha, Nebraska : $b Means Pub. Co., $c [date of publication not identified]
    264 #2 $a [Place of distribution not identified]: $b [distributor not identified], $c 2009.

    LC-Recommended: 264 #1 $a Omaha, Nebraska : $b Means Pub. Co., $c [2009?]

    But sometimes distribution information must be provided when probable publisher information cannot be supplied:

    Example C:
    On jewel box: Published in 2010 in Providence; distributed in Boston and Ottawa by KL, Inc.

    RDA and LC: 264 #1 $a Providence : $b [publisher not identified], $c 2010.
    264 #2 $a Boston ; $a Ottawa : $b KL, Inc., $c [2010]

    OTHER RDA EXAMPLES OF DATES:

    Title page verso:
    First published, ALA Editions, 1955
    Reissued 1985 by Facet Publishing
    Reprint edition 2016 by Libraries Unlimited, New York
    264  #1   New York : $b Libraries Unlimited, $c 2016.

    Title page verso:
    First published in 1985  Sixth printing 1990
    264  #1  ..., $c1985.

    Title page date:  1996
    Title page verso:
    First printed, 1997
    264  #1  ...,$c 1996 [that is, 1997]

    Title page verso:
    First published in 1973
    Sixth printing 1975
    264  #1   ..., $c 1973.

    Title page verso: May 2016
    264  #1   ..., $c May 2016.

    Date of Distribution 
    Date of distribution is a Core Element for a resource in a published form if the date of publication is not identified.

    Where the Rules are for Date of Distribution in RDA: Look at instruction 2.9.6

    What are the Sources of Information for Date of Distribution in RDA: 
    Sources: Take dates of distribution from the following sources (in order of preference):
    a) the same source as the title proper (see 2.3.2.2)
    b) another source within the resource itself (see 2.2.2)
    c) one of the other sources of information specified under 2.2.4.

    For multipart monographs and serials, take the beginning and/or ending date of distribution from the first and/or last released issue or part, or from another source.

    For integrating resources, take the beginning and/or ending date of distribution from the first and/or last iteration, or from another source.

    Recording Date of Distribution
    If the date of distribution differs from the date of publication, record the date of distribution, if it is considered to be important, applying the basic instructions on recording distribution statements.

    Dates of the Non-Gregorian or Julian Calendar; Dates in the Form of Chronogram
    As with dates of publication, LC Policy Statements provide guidance in these situations.

    Multipart Monographs, Serials, and Integrating Resources
    RDA 2.8.6.5 provides guidance regarding dates in these situations.  The guidelines are similar to the guidelines for date of publication.

    Date of Distribution Not Identified in a Single-Part Resource
    • If the date of distribution is not identified in a single-part resource, supply the date or an approximate date of distribution. Apply the instructions on supplied dates given under 1.9.2. 
    • If an approximate date of distribution for a single-part resource cannot reasonably be determined, record [date of distribution not identified]. 
    • If the resource is in an unpublished form (e.g., a manuscript, a painting, a sculpture), record nothing in the date of distribution element.
    Copyright Date 

    CORENESS for LC: Give a copyright date for a single-part monograph if neither the date of publication nor the date of distribution is identified.  You are not required to record copyright dates for multipart monographs, serials, and integrating resources.
    A copyright date is a date associated with a claim of protection under copyright.

    Where the Rules are for Copyright Date in RDA:Look at instruction 2.11
      What are the Sources of Copyright Date in RDA: Take information on copyright dates from any source.

      Recording Copyright Dates
      Record copyright dates, applying the general guidelines on numbers given under 1.8.  Precede the date by the copyright symbol © or the phonogram symbol , or by “copyright” or “phonogram” if the symbol cannot be reproduced.  If the resource has multiple copyright dates that apply to various aspects (e.g., text, sound, graphics), record only the latest copyright date.

      Copyright date is recorded in MARC field 264, second indicator 4; $c is the only subfield used.

      Examples:
        264 #4 $c ©2002
      264 #4 $c ℗1983

      Source : Based on information from Library of CongressRDA Blog, OCLC and RDA Toolkit

      Author: Salman Haider
      Revised 2016-02-05 | Written 2016-02-04

      See also other RDA Blog posts on Publication, Distribution, and Copyright Date:
        
      Thanks all for your love, suggestions, testimonials, likes, +1, tweets and shares ....

      See also related posts in following RDA Blog Categories (Labels):

      by Salman Haider (noreply@blogger.com) at February 05, 2016 10:59 AM

      February 04, 2016

      Mod Librarian

      One Thing Thursday: How did the Most Beautiful Library in America get Demolished?

      One Thing Thursday: How did the Most Beautiful Library in America get Demolished?

      Here is one thing for this week:

      1. How did the most beautiful library in America get demolished?

      Also, dear friends and readers – I am a little burnt out on the five things a week format of this blog. I welcome suggestions for content and format alike. How about 10 things on the 10th – a monthly offering? Or 20 things on the 20th?

      Thanks for understanding while I take some time to sort out the best…

      View On WordPress

      February 04, 2016 12:45 PM

      Resource Description & Access (RDA)

      RDA - Production Publication Distribution Manufacture Date - MARC 264

      RDA - Production Publication Distribution Manufacture Date - MARC 264

      MARC field 264 (formerly known as the publication, distribution, field in AACR2) is the home for many different RDA elements.  MARC field 264 will replace field 260 so that each of the different types can be coded explicitly. We will talk about the following areas:

      • Production statement (2.7)
      • Publication statement (2.8)
      • Distribution statement (2.9)
      • Manufacture statement (2.10)
      • Copyright date (2.11)
      [Source: Library of Congress]

      Please note that relevant rules are available in RDA RULES-CHAPTER 2

      Some popular RDA Blog posts on PUBLICATION DISTRIBUTION ETC.MARC-260MARC-264, and DATE using guidelines from RDA RULES-CHAPTER 2 are following:
      Bookmark this RDA Blog post for important links to Resource Description and Access and AACR2 Cataloging Rules and Examples on PUBLICATION PRODUCTION MANUFACTURE DISTRIBUTION ETC.MARC-260MARC-264, and DATE applying guidelines from RDA RULES-CHAPTER 2 and LC-PCC PS.
        
      Thanks all for your love, suggestions, testimonials, likes, +1, tweets and shares ....

      See also related posts in following RDA Blog Categories (Labels):

      by Salman Haider (noreply@blogger.com) at February 04, 2016 10:23 AM

      February 03, 2016

      First Thus

      ACAT Latin America versus South America

      On 03/02/2016 13.36, Bughdana Hajjar wrote:
      > Dear autocatters,I received an email from our reference librarian asking about the difference in usage between latin America and South America?Would you help?Regards,
      See the LC Subject Heading manual H985 for Latin America http://www.loc.gov/aba/publications/FreeSHM/H0985.pdf “1. Latin America

      Assign the heading Latin America to works dealing collectively with the area and/or countries south of the Rio Grande, as well as all or parts of three or more of the regions that make up Latin America, that is, Mexico, Central America, South America, and the West Indies.

      Also assign Latin America as the collective geographic heading and subdivision for the Spanish-speaking countries of Latin America.”

      South America is the continent.

      FacebookTwitterGoogle+PinterestShare

      by James Weinheimer at February 03, 2016 01:12 PM

      January 31, 2016

      First Thus

      My First Attempt at Research: Looking It Up in Your Funk and Wagnall’s

      My First Attempt at Research:
      Looking It Up in Your Funk and Wagnall’s

      I want to recommend an excerpt from a highly enjoyable article in Harper’s Magazine by John Crowley, who is describing the Encyclopaedia Britannica and how he used it as a boy.

      Easy Chair — From the February 2016 issue

      Rule, Britannica By John Crowley

      […] I tried to learn about sex from the E.B. [i.e. Encyclopaedia Britannica] The daring I felt in even looking up the topic in secret filled me with a weird elation and, yes, a kind of heat. The article, though, was entirely devoted to sexual differentiation in various plants and animals, with elaborate tables of X and Y chromosomes. “Reproductive System, Anatomy of” featured an old “transverse section” of a sheep’s prostate and a diagram of a testicle revealing a worm’s nest of seminiferous tubules inside, a view I could not relate to my own or to anything else.

      This reminds me of my own boyhood encounters with encyclopedias. Life was different from what we know today and I believe it is difficult for many even to imagine how much things we take for granted have changed. One obvious instance is the use of the word “f**k,” which now can be found even in popular newspapers and magazines, and on the web it is almost everywhere. I still find it too uncomfortable to write it publicly, although I confess I do use it in speech. In its modern use, “f**k” has taken on some rather strange spellings and forms.NOTE

      In those days, the word was rarely used and almost never printed, except in adult publications that I couldn’t know about. You didn’t hear the word spoken on radio, TV, or in the movies. I remember coming across it only on, shall I say, special occasions.

      The major occasions I would see it was during our Sunday afternoon drives. The Sunday drive was the norm before air conditioning came into wide use and when we lived in the heat of New Mexico, my whole family looked forward to the Sunday afternoon drive. We could roll down all the car windows, my father would “open it up” on the highway, and we could all cool off. One invariable part of the drive was when my father would go through an underpass, located next to Escondida, New Mexico, the next town over.

      On the wall of the underpass was written the word “f**k,” and when we approached the underpass I would start to watch for it. My mother was completely appalled and wanted my father to go home a different way but I think he liked seeing it and he always drove through that underpass on the way home. But it is just as possible that he simply liked aggravating my mother and wanted to give his sons a thrill. Sometimes he would drive through so fast that I would miss the word and I would have to wait a whole week before I had the chance to see it again. I think he did that on purpose.

      The very first time I saw that word however is quite vivid in my memory. It happened when I was playing in the desert and went to play next to some railroad tracks. Someone had written F**K in capital letters on an old, dried-out trestle, using gum. I found it fascinating and when I got home, I told my mother what I had found and asked what it meant. She looked at me and said that if I EVER said that word again, she would wash my mouth out with soap. So, I never said it in front of her or any adult. To be honest, while the kids cussed constantly, I don’t remember that we used that word so much. The few times you did, you would whisper it and everyone would giggle.

      While you could hear lots of adults (including my father) on the street punctuating their speech with plenty of swear words like “shits” and “craps” and “goddamns,” you heard “f**k” very rarely in public. As a result, that particular word held a certain power that we don’t feel today.

      I remember that several times afterwards I returned to the railroad trestle to stare at that word as the gum slowly deteriorated in the sun.

      Yet, none of that lessened my curiosity in what the word itself meant, and the word led me into my very first foray into what I would later realize was genuine research. Just like John Crowley’s experience with the Britannica, I too was intensely interested in sex and wanted to know what all the fuss was about.

      The other boys seemed to know everything about it already and I had learned from experience that it was unwise to look too stupid in front of them. I had already learned that I couldn’t ask my mother. If I asked my brother, I knew he would never let me forget it and he would turn me into a laughing-stock with all of his friends, and I just couldn’t find it in myself to ask my dad. I never considered asking any of the girls I knew. At that time I considered girls a completely separate species. Teachers or librarians? They were hardly recognizable life forms.

      And yet, I knew there was an answer and I could even see it and hold it: the font of all knowledge was right in our own home. The Funk and Wagnall’s Encyclopedia. We didn’t have the Brittanica.

      Funk & Wagnall'sFrom http://www.amazon.com/Wagnalls-Standard-Reference-Encyclopedia-entire/dp/B000CF2BFK

      My parents got it through a promotion in one of the grocery stores where my father worked. You would sign up and every month or so you could buy a new volume. Our set had been complete for awhile, and I looked upon it as holding all the knowledge in the world. Therefore, the information I wanted had to be in there–the problem was, how could I find it? It was huge! There were 25 volumes!

      The only times I had used it before was to look up things I already knew, terms such as “dog” and “cat” where I enjoyed looking at all the different kinds of dogs and cats. This seemed to be a task that was altogether different. How should I start?

      I figured that you start by looking up something.

      But how? What?

      For younger people who may be reading this, they may be puzzled that I did not search the full text of the electronic version of the Funk and Wagnall’s Encyclopedia using a boolean search query. Or why I didn’t use the text and pictures on CD-ROM, DVD, a pen drive or any other hard drive. Or why I didn’t download it from the Internet Archive or Google Books or use a p2p file sharing program such as Bit Torrent. Or why I didn’t buy it for my Kindle, smart phone, tablet, smartWatch, Google Glasses or Oculus Rift. I didn’t do it because none of things existed. One other point may seem rather strange: the fact that I couldn’t do any of that did not bother me in the slightest because all of those things were beyond my imagination. Times are different now and if put in the same situation, I would find it intolerable.

      As I confronted that huge Funk and Wagnall’s, I started with the word I knew: f**k. Even before I began, I had serious reservations whether I would find it and this dampened my enthusiasm somewhat, but nevertheless, I thought it was worth a try.

      Sure enough, it wasn’t there. That word, that incredible word that everyone treated with such power and awe, turned out to be entirely worthless.

      So I turned to another word that I knew:

      Sex.

      That word, of course, was there but I was to be disappointed because what I found was hardly exciting. In fact, what I found was decidedly uninteresting, similar to what James Crowley found in the Harper’s article, and certainly not what I wanted. Like him, I too had felt daring and excited when I started, but this was a sad letdown. I wanted much more.

      At this point, I do not remember the exact trail of the terminology I followed; I only remember that it took some time. My method was: I would look up something that I thought would be interesting, discover it was uninteresting, but I would find words I did not know and I would look those up. Considering my actions from an adult, librarian vantage-point, I cannot question my method, since it appears I did everything right. I think that my diligence and endurance were actually praiseworthy.

      But none of that worked. Every word turned out to be a dead end. Every single one. I remember I gave up a couple of times but something would spur me on and I would once again begin to look for it…. always with no results. I believe there were a couple of reasons why I didn’t give up completely. One was, naturally, a young boy’s normal interest in such matters. But the other was that I knew the encyclopedia we owned held all the knowledge in the world–so the information I wanted absolutely HAD to be in there. Somewhere, it was right in front of me, in that shelf and a half of books!

      To say it was frustrating does not begin to describe how I felt. I remember considering whether I should start with volume 1 and slog my way through, but decided that was not an option. What could I do?

      There was a boy who was one of my best friends, and our families would have each other over for dinner occasionally. His family had a complete set of the Encyclopaedia Britannica and it was twice as big as our set of encyclopedias. I thought I could maybe find what I wanted there when we visited his house, but somehow it never worked out. It would be time for dinner, or my friend wanted to play, or everybody wanted to watch TV, and the TV turned out to be right next to the Encyclopaedia Brittanica, and I knew that if I picked out a volume somebody would ask what I was looking for.

      I couldn’t allow that to happen. Stuck again.

      Anyway, it took time to find what I wanted. I don’t remember how long it took but at the time it seemed forever. Looking back, it obviously took days if not weeks, but in the end I did find what I was looking for. It turned out I was right. The information really was there. It was under a word I had never heard of in my life: Coitus. I remember reading the text under that entry and thinking “Oh!”.

      Even in my early years however, I displayed a trait that could be considered as either good or bad, but it would continue to dog me throughout the years, and still dogs me to this very day: I couldn’t believe what I had read. As I considered what I had found under “coitus,” it seemed too outrageous to me and I wanted supporting evidence.

      Unfortunately, I was to discover that if finding the word “coitus” had been hard, then getting supporting evidence turned out to be impossible. I figured I had gotten everything I could out of that Funk and Wagnall’s that had tormented me for so long and I could safely ignore it, but ignoring the Funk and Wagnall’s meant I would have to look somewhere else. Where? It meant starting all over again, and I still couldn’t ask anybody. I figured that if I told someone my doubts and I was wrong, I would only make myself look more ridiculous than ever!

      From the very beginning of what was to be my very first research project, I had my suspicions that adults talked about “it” a lot but used some sort of secret language among themselves that was unknown to me. With this in mind, I began to pay much more attention to what adults said that I had dismissed previously–those times when the adults would laugh uproariously for reasons I couldn’t fathom, or when some adult would say something I didn’t understand, another would say “Wait a second,” make a motion toward me and then all the adults would look at me with strange looks on their faces. Earlier, I had simply dismissed all this as strange, adult stuff, but I began to listen in the hope of getting some of my supporting evidence.

      None of that worked very well and it turned out that instead of getting any genuine supporting evidence, I had to settle for what I would later learn was “preponderance of evidence,” which even back then I recognized as a much lower standard. From my own interpretations of what the adults were saying, I decided that the majority of the evidence seemed to lean more in favor of the coitus theory, as opposed to it.

      And there the matter lay until I grew older and I finally found the supporting evidence I needed.


      NOTE: (See for example A Glossary of 69 F**ks / by Rufus Lodge, Esquire Sep 2, 2014)

      FacebookTwitterGoogle+PinterestShare

      by James Weinheimer at January 31, 2016 02:47 PM

      January 28, 2016

      Mod Librarian

      5 Things Thursday: DAM, Women in Tech, Metadata,

      5 Things Thursday: DAM, Women in Tech, Metadata,

      Here are five things:

      1. Curious about the best digital asset management software?
      2. Read about an inspiring woman in tech: Alice Merchant.
      3. MedNexus is the place to go when you are feeling like a hypochondriac.
      4. Can a company like Target fail because of metadata?
      5. Smithsonian Libraries receives digitizing hidden special collections award.

      View On WordPress

      January 28, 2016 01:15 PM

      Resource Description & Access (RDA)

      Resource Description and Access (RDA) Traffic Stats

      Thanks all for your love, suggestions, testimonials, likes, +1, tweets and shares ....

      Please post your feedback and comments on RDA Blog Guest Book. Select remarks will be posted on RDA Blog Testimonials page.

      INTRODUCTION TO RDA BLOG:

      RDA Blog is a blog on Resource Description and Access (RDA), a new library cataloging standard that provides instructions and guidelines on formulating data for resource description and discovery, organized based on the Functional Requirements for Bibliographic Records (FRBR), intended for use by libraries and other cultural organizations replacing Anglo-American Cataloging Rules (AACR2). RDA Blog lists description and links to resources on Resource Description & Access (RDA). It is an attempt to bring together at one place all the useful and important information, rules, references, news, and links on Resource Description and AccessFRBRFRADFRSADMARC standardsAACR2BIBFRAME, and other items related to current developments and trends in library cataloging practice.

      Author: Salman Haider

      RDA BLOG HIGHLIGHTS AND TRAFFIC STATS

      RDA Blog HistoryRDA Blog is the first and oldest blog exclusively devoted to Resource Description and Access  (RDA). RDA Blog was created by Salman Haider, a Cataloging & Metadata Librarian Blogger & Online Social Media Expert from India. RDA Blog embarked on its journey to provide useful information about Resource Description and Access (RDA) in August 2011. It received good response from librarians, catalogers, and library professionals from all around the world. It is interesting to note that the first hundred thousand pageviews to RDA Blog came in 3 years, but it took just 8 months to reach another hundred thousand pageviews. At present it is viewed at a rate of fifteen to twenty thousand times per month. RDA Blog is widely followed in social media.
        RDA Blog also made it to the list of useful resources of following:

        by Salman Haider (noreply@blogger.com) at January 28, 2016 03:24 AM

        January 27, 2016

        OCLC Cataloging and Metadata News

        WorldCat Cataloging Partners: Prepare for Your Transition

        In this webinar, participants learned how OCLC is helping streamline cataloging workflows by integrating functionality from a number of different cataloging services into WorldShare Collection Manager.

        January 27, 2016 07:00 PM

        January 26, 2016

        mashcat « mashcat

        Upcoming webinars in early 2016

        We’re pleased to announce that several free webinars are scheduled for the first three months of 2016. Mark your calendars!

        Date/Time Speaker Title
        26 January 2016 (14:00-17:00 UTC / 09:00-12:00 EST) Owen Stephens
        Installing OpenRefine This webinar will be an opportunity for folks to see how OpenRefine can be installed and to get help doing so, and serves as preparation for the webinar in March.  There will also be folks at hand in the Mashcat Slack channel to assist.

        Recording / Slides (pptx)

        19 February 2016 (18:00-19:00 UTC / 13:00-14:00 EST) Terry Reese Evolving MarcEdit: Leveraging Semantic Data in MarcEdit. Library metadata is currently evolving — and whether you believe this evolution will lead to a fundamental change in how Libraries manage their data (as envisioned via BibFrame) or more of an incremental change (like RDA); one thing that is clear is the merging of traditional library data and semantic data.  Over the next hour, I’d like to talk about how this process is impacting how MarcEdit is being developed, and look at some of the ways that Libraries can not just begin to embed semantic data into their bibliographic records right now — but also begin to new services around semantic data sources to improve local workflows and processes. 14 March 2016 (16:00-17:30 UTC / 11:00-12:30 EST Owen Stephens (Meta)data tools: Working with OpenRefine OpenRefine is a powerful tool for analyzing, fixing, improving and enhancing data. In this session the basic functionality of OpenRefine will be introduced, demonstrating how it can be used to explore and fix data, with particular reference to the use of OpenRefine in the context of library data and metadata.

        The registration link for each webinar will be communicated in advance. Many thanks to Alison Hitchens and the University of Waterloo for offering up their Adobe Connect instance to host the webinars.

        by Galen Charlton at January 26, 2016 05:19 PM

        OCLC Cataloging and Metadata News

        WorldCat Cataloging Partners: Prepare for Your Transition

        In this webinar participants learned how OCLC is helping streamline cataloging workflows by integrating functionality from a number of different cataloging services into WorldShare Collection Manager.

        January 26, 2016 03:00 PM

        Terry's Worklog

        MarcEdit update Posted

        I’ve posted an update for all versions – changed noted here:

        The significant change was a shift in how the linked data processing works.  I’ve shifted from hard code to a rules file.  You can read about that here: http://blog.reeset.net/archives/1887

        If you need to download the file, you can get it from the automated update tool or from: http://marcedit.reeset.net/downloads.

        –tr

        by reeset at January 26, 2016 06:04 AM

        MarcEdit Linked Data–Rules file

        One of the changes in the current MarcEdit update is the introduction of a linked data rules file to help the program understand what data elements should be processed for automatic URL generation, and how that data should be treated.  The Rules file is found in the Configs directory and is called: linked_data_profile.xml

         

        image

        image

        The rules file is pretty straightforward.  At this point, I haven’t created a schema for it, but I will to make defining data easier.  Until then, I’ve added references in the header of the document to note fields and values. 

        Here’s a small snippet of the file:

        <?xml version=”1.0″ encoding=”UTF-8″?>
        <marcedit_linked_data_profile>
          <!–
            rules block:
                top level: field
                    Attributes:
                        type: authority, bibliographic, authority|bibliographic
                    tag (required):
                        Value: Field value
                        Description: field to process
                    subfield (required):
                        Value: Subfield codes
                        Description: subfields to use for matching
                    index (optional):
                        Values: subfield code or empty
                        Description: field that denotes index
                    atomize(optional):
                        Values: 1 or empty
                        Description: determines if field should be broken up for uri disambiguation
                    special_instructions (optional):
                        Values: name|subject|mixed
                        Description: special instructions to improve normalization for names and subjects. 
                    uri (required):
                        Values: subfield code to include a url
                        Description: Used to determine which subfield is used to embed a URI
                    vocab (optional):
                        Values (see supported vocabularies section)
                        Description: when no index is supplied, you can predefine a supported index
                       
                       
          Supported Vocabularies:
            Value: lcshac
            Description: LC Childrens Subjects
           
            Value: lcdgt
            Description: LC Demographic Terms
           
            Value: lcsh
            Description: LC Subjects
           
            Value: lctmg
            Description: TGM
           
            Value: aat
            Description: Getty Arts and Architecture Thesaurus
           
            Value: ulan
            Description: Getty ULAN
           
            Value: lcgft
            Description: LC Genre Forms
          
           Value: lcmpt
           Descirption: LC Medium Performance Thesaurus
          
           Value: naf
           Description: LC NACO Terms
          
           Value: naf_lcsh
           Description: lcsh/naf combined indexes.
          
           Value: mesh
           Description: MESH indexes
            –>
          <rules>
            <field type=”bibliographic”>
              <tag>100</tag>
              <subfields>abcdqnp</subfields>
              <uri>0</uri>
              <special_instructions>name</special_instructions>
            </field>
            <field type=”bibliographic”>
              <tag>110</tag>
              <subfields>abcdqnp</subfields>
              <uri>0</uri>
              <special_instructions>name</special_instructions>
            </field>
        </rules>
        </marcedit_linked_data_profile>

        The rules file is pretty straightforward.  You have a field where you define a type.  Acceptable values are: authority, bibliographic, authority|bibliographic.  This tells the tool which type of record the process rules apply to.  Second you define a tag, subfields to process when evaluating for linking, a uri field (this is the subfield used when outputting the URI, special instructions (if there are any), where the field is atomized (i.e., broken up so that you have one concept per URI), and vocab (to preset a default vocabulary for processing).  So for example, say a user wanted to atomize a field that currently isn’t defined as such – they would just find the processing block for the field and add: <atomize>1</atomized> into the block – and that’s it.

        The idea behind this rules file is to support the work of a PCC Task Force while they are testing embedding of URIs in MARC records.  By shifting from a compiled solution to a rules based solution, I can provide immediate feedback and it should make the process easier to customize and test. 

        An important note – these rules will change.  They are pretty well defined for bibliographic data, but authority data is still being worked out. 

        –tr

        by reeset at January 26, 2016 06:01 AM

        January 25, 2016

        Resource Description & Access (RDA)

        Subject Heading List : Glossary of Library & Information Science

        Glossary of Library & Information Science

        Subject Heading


        New Post on Librarianship Studies & Information Technology Blog provides a comprehensive definition of Subject Heading List

        This new encyclopedic entry in the “Glossary of Library & Information Science” of the Librarianship Studies & Information Technology Blog answers following questions?
        • What is Subject Heading List?
        • Where Subject Heading List is applied?
        • What is vocabulary control and why is it important?
        • How Subject Heading List assist library users and staff?
        • What are the alternatives to Subject Heading?
        • What are the popular Subject Heading Lists?
        Librarianship Studies & Information Technology Blog will be more focused on Information Access Through The Subject with special reference to the techniques of Library of Congress Classification (LCC) and Library of Congress Subject Headings (LCSH) by use of Classification & Shelflisting Manual (CSM), Subject Headings Manual (SHM), and Classification Web tool of Library of Congress. Librarianship Studies Blog will also highlight the history, development, and techniques of providing classification number using Dewey Decimal Classification (DDC).

        Librarianship Studies & Information Technology (LS & IT) Blog is envisioned as an Encyclopedia, Wikipedia, and Khan Academy of Library and Information Science; an authoritative source for consultation and reference for any library or information profession related issue and a treasure hub of knowledge on Library and Information Science.

        Follow Librarianship Studies & Information Technology in Social Media blog to be updated of new items and to start/comment on the discussions in the Google+ Community Librarianship Studies & Information Technology and Facebook Group Librarianship Studies & Information Technology.


        #RDABLOG #LIBRARIANSHIPSTUDIES #SUBJECTHEADING #LCSH

        by Salman Haider (noreply@blogger.com) at January 25, 2016 06:53 AM

        Subject Approach to Information in Libraries

        Information Access Through The Subject
        Information Access Through The Subject



        This new post of Librarianship Studies &amp; Information Technology Blog answers following questions:
        • What are the Subject Approach to Information in Libraries
        • How library users seek information on a particular subject?
        • How library materials are arranged on shelves and catalogs to be located by subject?
        • What is a subject?
        • What methods and tools catalogers use to show what a library or information center has on a particular subject?
        • What methods and tools catalogers use to show what a library or information center has on related subjects?
        • How classification schemes are used for subject approaches?
        • How subject headings are used for subject approaches?

        Source (Chapter 1): Information Access Through The Subject : An Annotated Bibliography / by Salman Haider. - Online : OpenThesis, 2015. (408 pages ; 23 cm.)
        Annotated bibliography titled Information Access Through The Subject covering Subject Indexing, Subject Cataloging, Classification, Artificial Intelligence, Expert Systems, and Subject Approaches in Bibliographic and Non Bibliographic Databases etc.



        #LIBRARIANSHIPSTUDIES #MLISTHESISONLINE

        by Salman Haider (noreply@blogger.com) at January 25, 2016 06:52 AM

        Library of Congress Subject Headings : Glossary of Library & Information Science

        LCSH Library of Congress Subject Headings
        Librarianship Studies & Information Technology



        New Post on Librarianship Studies & Information Technology Blog provides a comprehensive and most up-to-date description and definition of Library of Congress Subject Headings (LCSH)

        LCSH is a multidisciplinary vocabulary that includes headings in all subjects, from science to religion, to history, social science, education, literature, and philosophy. It also includes headings for geographic features, ethnic groups, historical events, building names, etc. Library of Congress Subject Headings (LCSH) is the most widely used subject vocabulary in the world. It is the model for many other vocabularies in English and other languages, and has been translated into numerous languages. The strongest aspect of LCSH is that it represents subject headings of the Library of Congress, the national library of United States, one of the richest of national libraries of the world ... … … (Visit link mentioned above to read complete article)

        This new encyclopedic entry in the “Glossary of Library & Information Science” of the Librarianship Studies & Information Technology Blog answers following questions?
        • What is Library of Congress Subject Headings?
        • What is scope of Library of Congress Subject Headings?
        • What is history Library of Congress Subject Headings?
        • How LCSH is produced?
        • Is LCSH a thesaurus?
        • Where LCSH is applied?
        • What is the cost of Library of Congress Subject Headings?
        • How LCSH applies a syndetic structure?
        • How LCSH is revised?
        • What are the different types of headings in LCSH?
        • How many headings are available in LCSH?
        • How present LCSH is different from the previous LCSH?
        • How to use in LCSH the names of persons and corporate bodies, jurisdictions and quasi-jurisdictional entities, and titles as subject headings?
        • Where can we get free LCSH?
        • What are the tools and resources for providing LCSH?
        • How to give LCSH in a bibliographic record according to international standards?

        Librarianship Studies & Information Technology Blog will be more focused on Information Access Through The Subject with special reference to the techniques of Library of Congress Classification (LCC) and Library of Congress Subject Headings (LCSH) by use of Classification & Shelflisting Manual (CSM), Subject Headings Manual (SHM), and Classification Web tool of Library of Congress. Librarianship Studies Blog will also highlight the history, development, and techniques of providing classification number using Dewey Decimal Classification (DDC).

        Librarianship Studies & Information Technology (LS & IT) Blog is envisioned as an Encyclopedia, Wikipedia, and Khan Academy of Library and Information Science; an authoritative source for consultation and reference for any library or information profession related issue and a treasure hub of knowledge on Library and Information Science.

        Follow Librarianship Studies & Information Technology blog in Social Media to be updated of new items and to start/comment on the discussions in the Google+ Community Librarianship Studies & Information Technology and Facebook Group Librarianship Studies & Information Technology.


        by Salman Haider (noreply@blogger.com) at January 25, 2016 06:41 AM

        Subject Heading : Glossary of Library & Information Science

        Subject Heading : Glossary of Library & Information Science

        http://librarianshipstudies.blogspot.com/2015/09/subject-heading-glossary-library.html
        New Post on Librarianship Studies & Information Technology Blog provides a comprehensive definition of Subject Heading.
        This new encyclopedic entry in the “Glossary of Library & Information Science” of the “Librarianship Studies & Information Technology” blog answers following questions?

        What is Subject Heading?
        What Subject Heading does?
        Where Subject Heading is applied?
        What is vocabulary control and why is it important?
        How Subject Heading assist library users and staff?
        What are the alternatives to Subject Heading?
        What are the popular Subject Heading Lists?
        Librarianship Studies & Information Technology Blog will be more focused on the techniques of Library of Congress Classification (LCC) and Library of Congress Subject Headings (LCSH) by use of Classification & Shelflisting Manual (CSM) and Subject Headings Manual (SHM) and Classification Web tool of Library of Congress, and Dewey Decimal Classification (DDC). Follow Librarianship Studies & Information Technology in Social Media blog to be updated of new items and start/comment on the discussions in the Google+ Community Librarianship Studies & Information Technology and Facebook Group Librarianship Studies & Information Technology.

        by Salman Haider (noreply@blogger.com) at January 25, 2016 06:26 AM

        January 24, 2016

        First Thus