Print

Print


Stephen,
 
Thanks.  So the solution is to simply add 667 notes to each NAR to eliminate future confusion and reassign the bib errors.
 
That is also what I was getting at, that the 37X fields permit linking that 5xx would not.
 
Chris

From: Program for Cooperative Cataloging [[log in to unmask]] On Behalf Of Stephen Hearn [[log in to unmask]]
Sent: Wednesday, May 25, 2016 12:22 PM
To: [log in to unmask]
Subject: Re: [PCCLIST] Bad metadata

I'm not sure what to say about coding a name authority as 008/14=b (no main/added entry use).  DCM has instructions for when to code 008/15=b (no subject use), but is silent about 008/14.  There are cases where the coding of 008/14 is a bit paradoxical. Tale headings established in LCNAF, e.g., "Cinderella," carry an instruction:

DESCRIPTIVE USAGE: Heading for the basic story, not to be used as an authorized access point in bibliographic records without language of expression added, e.g., Cinderella. English. ...

but 008/14 is coded "a" despite the instruction.  Compare this practice with the practice for obsolete place names like Ceylon.  Ceylon's name authority is marked 008/15=b with a 667 blocking subject use, but all the name headings built on Ceylon, e.g., "Ceylon. $b Archaeological Department," are coded 008/15=a.  

We're still advised not to make 5XX references for LCSH terms in LCNAF authorities; e.g., the DCM has instructions for 500, 510, 511, 530, and 551, but not 550.  My understanding has been that only LCNAF AAPs could go into 551, and that the concern is that LCSH and LCNAF are separately maintained authority files for which cross-file references could be a maintenance problem. However, the same restriction is not applied to 370.  The DCM includes instructions for citing authorized LCSH non-jurisdictional places in 370 fields, so "370 $f Chesapeake and Ohio Canal (Md. and Washington, D.C.) $2 lcsh" should be OK as a way to cite an associated place.  

Stephen

On Wed, May 25, 2016 at 9:39 AM, Chris Baer <[log in to unmask]> wrote:

Stephen,

 

It appears my original response to your comments did not go through.

 

This proposed canal company could never have been an author (1xx), lacking any organization or power to act, but is legitimately a subject (6xx) of the Chesapeake and Ohio Canal Convention that proposed it.  Since this is almost certainly the only place it would ever appear, should be it coded subject use only?  Also, it might be best to add 667 notes to the both the Potomac Company and Potomac Canal Company records to prevent further confusion.

 

Incidentally, under RDA, does it make sense to link the corporate name with the geographic name of the canal itself?  The link is pretty obvious in this case, but there were many state canals operated by statewide boards whose names did not match those of the canals, while their reports contain some of the best information.  I raised this point during NACO training decades ago, but was told it was verboten under the old rules.

 

This still leaves the question of how to unlock the misattributed bib records.

 

Chris Baer

 

 

 

 

From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Stephen Hearn
Sent: Wednesday, May 25, 2016 9:59 AM


To: [log in to unmask]
Subject: Re: [PCCLIST] Bad metadata

 

John Hostage is correct. LC-PCC PS 11.2.2.5 does not call for adding a (Proposed) qualifier to a proposed corporate body name. My mistake. Thanks for the correction.

 

The PS does allow for establishing the names of proposed bodies and does not call for removing them if the body itself is never established, so it does not instruct us to delete the Potomac Canal Company authority.

 

RDA 11.13.1.7, Other Designation, does include an optional provision to "Include such a designation if it assists in the understanding of the nature or purpose of the body." The option has no LC-PCC PS. The Proposed Bodies LC-PCC PS is arguably about whether to establish such entities, not about how to name them. Would this option under 11.13.1.7 allow the use of (Proposed) in a case like Potomac Canal Company to assist "in understanding the nature or purpose of the body"?

 

Stephen

 

On Tue, May 24, 2016 at 4:43 PM, John Hostage <[log in to unmask]> wrote:

I think the meaning of PS 11.2.2.5 is not to use the qualifier (Proposed), in contrast to prior practice.  Instead, just establish the name as found.

 

------------------------------------------

John Hostage

Senior Continuing Resources Cataloger

Harvard Library--Information and Technical Services

Langdell Hall 194

Harvard Law School Library

Cambridge, MA 02138

[log in to unmask]

+(1)(617) 495-3974 (voice)

+(1)(617) 496-4409 (fax)
ISNI 0000 0000 4028 0917

 

From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Stephen Hearn
Sent: Tuesday, May 24, 2016 14:36
To: [log in to unmask]
Subject: Re: [PCCLIST] Bad metadata

 

Would this be a case where applying the qualifier (Proposed)--Potomac Canal Company (Proposed)--could resolve the issue without leaving someone who finds a reference to the proposed but never realized entity at a loss?  Cf. LC-PCC PS 11.2.2.5.  If so, would "Potomac Canal Company (Proposed)" be established separately or considered a variant name for the Chesapeake and Ohio Canal Company?  It's not clear to me how much continuity there was between the two.

 

Stephen

 

Stephen

 

On Tue, May 24, 2016 at 12:49 PM, Chris Baer <[log in to unmask]> wrote:

I have enhanced and corrected the NARs for two related companies, the Patowmack/Potomac Company (n 50057652) and the Chesapeake and Ohio Canal Company (n 50057654), both of which contained significantly false information, specifically a false intermediary, the Potomac Canal Company (n 50057653).

 

On the Potomac Company, I deleted the fifth 670, which is the source of some of the false information.  This underlines the previous point I was trying to make about putting too much trust in online sources not subject to peer review or adequately sourced.  The source is a half-baked misunderstanding of original material.  The “Washington Canal” was not part of the Potomac Company but a separate canal that ran down the middle of what is now the Mall and branched south to the old Navy Yard.  The canal segments built by the Potomac Company were the Little Falls Canal, the Great Falls Canal, the Seneca Falls Canal and so on.  There are two reasonably definitive works on the subject, one by Sanderlin (1947) should have been available.  I also added 670s from the charters, which specify dates, jurisdictions and powers.

 

On the Chesapeake and Ohio Canal Company, I did something of the same, adding data from Sanderlin to show how the project was wound up and conveyed to the National Park Service.  More importantly, I have corrected the predecessor/successor relationship.

 

This brings us to the false intermediary, the Potomac Canal Company.  A Potomac Canal Company was indeed chartered by Virginia on February 22, 1823, but it required the assent of Maryland, which was not given.  The closest analogy is that the company was stillborn, that is, like a stillborn infant, it existed but was born without life and could not act.  In the next year, a new charter was passed for the Chesapeake and Ohio Canal Company to which both states gave the necessary assent, and it acquired life and the ability to act.  The Potomac Company transferred its property and went out of business four years later, so for a period, both existed.  The relationship between the Potomac Canal Company and the Chesapeake and Oho Canal Company is that of two successive siblings, one of which is born dead and the second who lives.  Only in the most metaphorical of senses can the first be considered an earlier version of the second.

 

So what to do about n 50057653?  It is a real entity, not merely a misnomer for the Potomac Company or the Chesapeake and Ohio Canal Company.  At the same time, it will only appear in the text of its charter in the Virginia session laws and as a name within certain other texts.  The best thing would be to delete it after making sure it is decoupled from its supposed “earlier” and “later” names.

 

Here is what happened.  A less than knowledgeable cataloger at LC misinterpreted a somewhat imprecise text and breathed life into a dead letter.  Then other catalogers incorrectly assumed that this body incapable of acting was the author of something that should have been properly credited to the Potomac Company.  Then OCLC locked everything so it cannot be changed.  The result, bad metadata that gives the appearance of having the librarians’ seal of approval.

 

So there is the simple practical question of how this can be fixed, specifically, how can the erroneous authorship be corrected and how can n 50057653 be properly deleted.  I should also point out that this was a very simple one-to-one relationship.  The mess in some of the complex ones is even worse, and the more webs that are woven, the harder it will be to untangle them.

 

Ted is right.  I am not a cataloger.  I am a historian and curator and have worn other hats in the past.  I work with researchers daily, which I am expected to do, and that means trying to explain things in depth and answer specific questions. I do research almost daily in everything from 18th century manuscripts to online data bases.  I almost never interact with catalogers.  Everyone in our department is a historian of one kind or another.  If the above insistence on accuracy seem over-legalistic to some, that is because providing precise information to lawyers from authoritative documents is part of my job.  For those who have no experience at it, archival description is not at all like cataloging.  It is more like writing an interpretive historical essay and then an index to a mass of material that doesn’t come prepackaged and whose order is determined by how and for what it was created.  It requires research, subject-matter knowledge, and detective skills.  I got to be the data-base policeman because our department is the largest by volume and use and went to automated description first.

 

So is bad metadata created by people acting in haste well outside their zone of expertise a problem or not??  It’s a lot harder to clean up the messes afterwards, especially now that OCLC uses its algorithms to put things in lockdown.

 

For us, this sort of thing is junk, and given that it falls in one of our areas of specialization, it has no place in our catalog, no more than a scrupulous historian would transmit self-serving fabrications or urban legends as fact or an art museum curator perpetuate a false attribution.  We are expected to know better.  If it is good enough for the library community, perhaps we should part company.  If we are expected to accept it, it seems to me like being forced to shout “Long live Big Brother.”  Sorry, but accuracy calls for it.

 

Chris Baer

Assistant Curator

Manuscripts & Archives

Hagley Museum and Library

 

P.S.  I agree wholeheartedly that going to some sort of numerical coding is the best solution, as it would allow different institutions with different clienteles to use the term best geared to their specific needs.  I just wonder how to get from here to there.  Obviously, currently active authors, publishers, researchers, etc. can be expected to create registries going forward, but what about things like this, or people whose work is proprietary and meant for archives only, or the random bits from the past that suddenly fall into the bibliographic universe from afar like the coke bottle or whatever it was in “The gods must be crazy?”  Note also that this does NOT solve the problems of bad metadata such as falsely-drawn, fudged or imprecise relationships or attributes.

 

 



 

--

Stephen Hearn, Metadata Strategist

Data Management & Access, University Libraries

University of Minnesota

160 Wilson Library

309 19th Avenue South

Minneapolis, MN 55455

ORCID:  0000-0002-3590-1242



 

--

Stephen Hearn, Metadata Strategist

Data Management & Access, University Libraries

University of Minnesota

160 Wilson Library

309 19th Avenue South

Minneapolis, MN 55455

ORCID:  0000-0002-3590-1242




--
Stephen Hearn, Metadata Strategist
Data Management & Access, University Libraries
University of Minnesota
160 Wilson Library
309 19th Avenue South
Minneapolis, MN 55455
Ph: 612-625-2328
Fx: 612-625-3428
ORCID:  0000-0002-3590-1242