LISTSERV mailing list manager LISTSERV 16.0

Help for BIBFRAME Archives


BIBFRAME Archives

BIBFRAME Archives


BIBFRAME@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

BIBFRAME Home

BIBFRAME Home

BIBFRAME  August 2015

BIBFRAME August 2015

Subject:

Re: Proposal for treatment of series in BIBFRAME

From:

Karen Coyle <[log in to unmask]>

Reply-To:

Bibliographic Framework Transition Initiative Forum <[log in to unmask]>

Date:

Mon, 10 Aug 2015 16:27:22 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (54 lines)

On 8/10/15 12:54 PM, Kevin M Randall wrote:
> I'm quite baffled by the statement that RDA is not an identifier-based cataloging code.  RDA has "identifier" as the very first option for recording all relationships!

In RDA description identifiers are things that come with the resource. 
"Take information on identifiers for the person from any source." "Take 
identifiers for the manifestation from any source." These are elements 
of description that happen to be called "identifiers" but they aren't 
what I am talking about. They're defined as alphanumeric strings (e.g. 
any string) that are taken from the piece, recorded as part of the 
description, and generally are assigned outside of the library workflow 
(e.g. ISSNs ISBNs). This is an example of an identifier used to record a 
relationship:

For Example:
Library and Archives Canada control
number: 0062A7592E

There is no guidance on what is an actionable identifier, no 
relationship between the identifiers and the things they identify, no 
relationship between the identifier and information about the thing 
identified. Just saying "Use an identifier if there is one" is really 
useless without some sense of what you are identifying and how that fits 
into your model. I would call RDA's approach a nod to identifiers while 
still maintaining a text-based approach. It's like someone thought "Oh, 
we should be including identifiers as an option." And aside from those 
few sentences, the full remainder of RDA is about how to create text 
strings.

Maybe I made a mistake in not qualifying that for identifiers to be 
usable to establish relationships in a computer environment, they have 
to also follow the rules for machine-actionable identifiers, which the 
above is not. I'll say here now that when I speak of identifiers in the 
context of RDF, those identifiers follow the RDF standard and are 
machine-actionable in a web environment and using software that is RDF- 
and http://-identifier aware. The above identifier is a tiny bit better 
than the textual name of the organization, but there's really nothing 
you can do with it. This shows me that the developers of RDA did not 
understand what "identifier" means in the IT sense. In any case, what we 
have here is two different ducks: they both quack like a duck, but only 
one is a fully usable duck. The other one could be anything from a duck 
to a dog toy to a distraction in a bath tub.

OK, as you can tell I'm at the end of my tether. I just despair that 
we'll never bring library data in to the 20th century much less the 
21st. oooooof.

kc

-- 
Karen Coyle
[log in to unmask]  http://kcoyle.net
m: +1-510-435-8234
skype: kcoylenet/+1-510-984-3600

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
July 2011
June 2011

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager