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:

Amanda Xu <[log in to unmask]>

Reply-To:

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

Date:

Sat, 14 Jan 2012 18:31:18 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (133 lines)

In the world of information being interwoven into streams of pulses with meta-info attached, representing its lowest and meaningful atomic level for application(s) or service(s) or segment of users, info on provenance of use becomes crucially important in web scale management as far as the following:

1) versioning, e.g. who did what, when, and why, and anything related to event and change management;

2) the role he/she played on the info vs. meta-info, e.g. creator, owner, reproducer, remixer, modifier, contributor as end user, commentator, editor, reviewer, etc. and anything meaning to origination control of the info itself;

3) authoritativeness in subject matter and CRUD (Create, Read, Update, Delete) operations to info itself, e.g. affiliations, associations, scholarly popularity, social proximity, professional ranking, participatory ranking, and anything meaningful to establish trust management;

4) authentication level and rubrics of contribution as meta-info vs. info itself, e.g. encoding level, types of work being done and level of contribution, e.g. authority control, bib control, holdings control, control of barcoded items (or features extracted) with RFID, QR code, category code, other statistical measurement code, etc. and anything meaningful for quality control of the meta-info;

5) constraints to use on info itself and meta-info respectively, e.g. conditions to link, reuse, update, remix or enhance with other media types, bundle or unbundle, slice or dice, reconfigure or distribute in types of multimodal interfaces, etc. and anything related to authorization or rights control;

6) accountability measures, governance, certification, contractual level agreement, and anything meaningful to proof control of info-itself and meta-info;

As far as I am concerned, the more open we are to allow end users' participation or machine creation of meta-info, the more tight control we need to establish for the management of changes, trust, quality, rights, and proof.  I believe we can leverage what has been done, adopted and worked successfully by Wikipedia, YouTube, Linkedin, etc. and their best practice in creating participatory culture for bibliographic control with touches of social, semantic and statistical means.

Sent from my iPad

On Jan 13, 2012, at 20:21, Karen Coyle <[log in to unmask]> wrote:

> I'm not sure that we can judge provenance on end-user needs of the usual stripe. I see provenance as a need for systems so that we don't produce a gawd-awful mess that doesn't serve users at all.
> 
> The main provenance need that I am aware of is that of managing updates to and interaction with data. Given that the world we are moving into will be more interactive than today's catalog, that the division between 'cataloger' and 'user' will be less strict because users will be able to do things with data, even adding or changing, then you need provenance as a way to identify library data on the Web. Changes in this environment will be of the form of adding another version of something, or linking some previously unlinked things together. Without provenance/versioning this results in gobbly-de gook.  In the Semantic Web sense, provenance goes hand-in-hand with versioning, and you do want to be able to know if you have the latest version of something. Provenance is what will make library data library data, and user data user data, and Roy's data Roy's data.
> 
> Or maybe we aren't talking about the same thing?
> 
> kc
> 
> Quoting Roy Tennant <[log in to unmask]>:
> 
>> Diane asks the question ³We want to do this well, don¹t we?² My reply would
>> be we should want to do it as well as is required to support real end-user
>> needs that are important to support. This is because we will clearly lack
>> the level of resourcing we enjoyed for much of the 80s and 90s, and even
>> into the 2000s. We must choose well where to put our resources or we will
>> regret it. Lacking any context, any cataloger will want to describe a
>> resource to within an inch of its life. But that isn¹t what we can afford to
>> do.
>> 
>> So I¹m suggesting we need to provide the end-user use cases where knowing
>> ³where it came from, when it was last updated, how it was created (human or
>> machine?)² is important and then we can go from there. This can be something
>> along the lines of ³without that information I can¹t provide the user with a
>> display from which they can make intelligent decisions about the resource
>> because of X and Y². But there must be something to justify all the work
>> besides our deep-seated (and laudible) desire to do things ³well².
>> Roy
>> 
>> 
>> On 1/11/12 1/11/12 € 12:18 PM, "Diane Hillmann" <[log in to unmask]>
>> wrote:
>> 
>>> Kevin:
>>> 
>>> I've sure been there, too, wishing there were good ways to figure out who did
>>> what in a MARC record!
>>> 
>>> I certainly disagree with Roy very strongly--provenance is one of the things
>>> we're really REALLY going to need as we move to an environment where we'll be
>>> managing data at the statement level collected from many places. This was the
>>> sort of thing I learned to do when I was working in the NSDL project, and for
>>> this librarian, it was a complete different way of looking at data aggregation
>>> (but pretty nifty, too). 
>>> 
>>> What I learned from that experience is that, when you're going to be doing
>>> something with this data (not just displaying it to people looking at
>>> catalogs), you need to know where it came from, when it was last updated, how
>>> it was created (human or machine?), etc. Management of data at the statement
>>> level (which for those of you attending ALA Midwinter, I'll be talking about
>>> at the Cataloging Norms IG, at 10:30-noon on Saturday) isn't rocket science,
>>> but it is quite different from the closed world of library data, and
>>> definitely requires provenance information to do well.
>>> 
>>> We want to do this well, don't we?
>>> 
>>> Diane
>>> 
>>> On Wed, Jan 11, 2012 at 2:35 PM, Kevin M Randall <[log in to unmask]> wrote:
>>>> Roy Tennant wrote:
>>>> 
>>>>> > In all of my 37 years working in libraries I've never
>>>>> > encountered a situation where it was necessary to know where the title
>>>>> > came from to do useful work with bibliographic data. In what situations is
>>>>> this
>>>>> > necessary, and why?
>>>> 
>>>> Okay, it looks like we've got two different meanings of "provenance" going on
>>>> in this thread.  I think Kelley McGrath started out talking about
>>>> "provenance" meaning WHO CREATED the metadata.  Because some of the message
>>>> talked about sources of data on the resource, this got morphed into a
>>>> discussion also about WHERE THE DATA APPEARED ON THE RESOURCE.
>>>> 
>>>> That being said, I think that *both* things are useful.  I would consider
>>>> myself quite blessed if I were able to say that I've never needed to have
>>>> this information through my entire career.  If we're talking about creator of
>>>> the metadata, that would be very, very useful in so many situations.  In a
>>>> MARC record, when there is more than one institution identified in the 040
>>>> field, there are many times I have needed to know, for example, which library
>>>> changed to serial from active to ceased, or which library added a note or
>>>> added entry--at the very least, so I could contact that library and determine
>>>> if something I have in hand is really the same thing as what the other
>>>> cataloger saw.  And if we're talking about where on the resource the data
>>>> appears, that is also helpful, especially with resources having the same or
>>>> similar titles, and/or bearing multiple publisher/issuing body names.
>>>> 
>>>> And in regard to the idea that we should "carry forward only what can be
>>>> justified by real requirements from real users", I would certainly hope that
>>>> we keep in mind that people who create, manipulate, and manage metadata ARE
>>>> "real users"!
>>>> 
>>>> Kevin M. Randall
>>>> Principal Serials Cataloger
>>>> Bibliographic Services Dept.
>>>> Northwestern University Library
>>>> 1970 Campus Drive
>>>> Evanston, IL  60208-2300
>>>> email: [log in to unmask]
>>>> phone: (847) 491-2939 <tel:%28847%29%20491-2939>
>>>> fax:   (847) 491-4345 <tel:%28847%29%20491-4345>
>>> 
>>> 
>> 
>> 
> 
> 
> 
> -- 
> 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

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