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  January 2012

BIBFRAME January 2012

Subject:

Re: Thoughts on provenance

From:

Karen Coyle <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Sun, 8 Jan 2012 20:14:01 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (65 lines)

Quoting Kelley McGrath <[log in to unmask]>:


>
> Three optional machine-comprehensible provenance elements attached  
> to every data element:
> 1) source of the data
> 2) the institution entering the data
> 3) date the data was input
>
> Perhaps something like the following for title proper:
> TitleProper: Citizen Kane
> DataSource: title frame
> DataInst: OrU
> DataDate: 2012-01-04

One possible answer is that we eliminate generalities like "title  
proper" that don't actually tell us much about title itself. "Title  
proper" is like "main entry" -- it tells you the role the title is  
playing in the record, not what the title actually is. We could have:

- title page title
- cover title
- title from jewel case insert

etc., if that information is important to capture, rather than calling  
one of them the "title proper" and essentially losing key information  
about the source of the title. In a situation where you want to  
display just one title you would have an algorithm in your display  
code that selects the one to display from a list: first title page,  
then cover, then supplied....

If you look at AACR/2 it's easy to see that the cataloger is selecting  
data elements to fit into certain display roles, and in that process  
losing the meaning of the data elements themselves. This is one of the  
difficulties in then transforming the current data into something that  
is based on the meaning of the data rather than its position in the  
record. Essentially the rule would be:

"say what it is, not where you want it to display"

And of course, notes about data elements are virtually useless in a  
data environment. The data elements themselves need to carry that  
information.

As for the dates or versions on a data element, and the entity that  
created the data, that is being considered by the W3C provenance  
working group.

http://www.w3.org/2011/prov/wiki/Main_Page

It might be interesting to offer some use cases from library  
cataloging as test cases for their work.

kc



-- 
Karen Coyle
[log in to unmask] http://kcoyle.net
ph: 1-510-540-7596
m: 1-510-435-8234
skype: kcoylenet

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

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