LISTSERV mailing list manager LISTSERV 16.0

Help for BIBFRAME Archives


BIBFRAME Archives

BIBFRAME Archives


[email protected]


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, 15 Jan 2012 07:10:06 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (77 lines)

Quoting "J. McRee Elrod" <[log in to unmask]>:

> Roy Tennant questioned the utlility of:
>
>
>> - title page title
>> - cover title
>> - title from jewel case insert
>
> The absence of such information can result in duplicate records for
> the same resource, or the assumption that the same resource was issued
> under different titles.

We know that different libraries have different capabilities, so we  
can probably agree that some library metadata won't make these  
distinctions. One of the advantages of the data management technology  
of the Semantic Web is that your system can have a hierarchy of  
metadata:

title (broadest)
   - narrower: title page title
   - narrower: cover title

Some libraries can use the specific terms, some can use the broader  
term, and yet those different selections can be used together because  
the terms are linked. With this technology a search on "title" can  
retrieve the narrower terms as well - or not, as you wish.

Obviously if some libraries use less precise information matching and  
de-duplicating can also be less precise. However, the totality of the  
information that you have, meaning some information from different  
sources, can be used to make sense of things. So if MOST libraries  
have stated that the title page title is "Title X" then you can assume  
that an undifferentiated title "Title X" is a title page title. It's  
not a 100% kind of match any more, but a more nuanced match (that  
Simon probably has the correct terms for!). The Open Library used a  
version of this in their determination of Works by using the  
information from records that did have uniform titles to bring in  
records for the same manifestation but that had not included the  
uniform title.

kc

>
> I approve of the new MARC field 588 for source, since the information
> is of more utility for the cataloguer than the end user, and need not
> be an early note.  I think 588 should be used for all source of title
> notes, not just those from outside the resource.
>
> The division of similar information is a flaw in MARC, e.g.: 506 and
> 540 should be adjacent or two subfields of the same field; noncast
> credits for video recordings of motion pictures should be together in
> 508, not divided, with some in 245/$c; physical information should not
> be as widely divided as 300 and 538; and now source of title should
> not be divided between 500 and 588.
>
> I hope any new coding system will have like with like, a basic
> principle of classification which should be extended to coding.
>
> Please don't tell me display need not reflect coding.  Why create the
> additional work for ourselves of changing element order?
>
>
>    __       __   J. McRee (Mac) Elrod ([log in to unmask])
>   {__  |   /     Special Libraries Cataloguing   HTTP://www.slc.bc.ca/
>   ___} |__ \__________________________________________________________
>



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

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
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