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

BIBFRAME June 2015

Subject:

Re: BIBFRAME Title Proposal

From:

Thomas Berger <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Sun, 14 Jun 2015 15:48:00 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (107 lines)

Am 14.06.2015 um 09:43 schrieb Shlomo Sanders:
> I get the feeling from this that a "VIAF" type repository for Works would be a good idea.
> In this way translations and transliterations can be handled by each country
> and yet have one common place for it all.

But as many (most, all?) National Libraries in their function of operators
of authority files have already decided long ago to implement the FRBR levels
"Work" and "Expression" by means of "authority records" this repository is
already building up /within/ VIAF... Additionally OCLC is performing its own
experiments of "FRBRizing WorldCat" (<
http://outgoing.typepad.com/outgoing/2014/04/frbrizing-worldcat.html >) and
results of this (IIRC mostly in form
of records for expressions) serve as input to VIAF in form of their "xR"
dataset.

So currently missing are bibframe elements (elements in the bibframe namespace
as well as statements typically deemed essential for bibframe works) in the RDF
"record views" of work or expression records like

https://viaf.org/viaf/249553408/rdf.xml

But the entities are already there.

viele Gruesse
Thomas Berger


> 
> Thanks,
> Shlomo
> 
> See the all new Developer Network<https://developers.exlibrisgroup.com/>
> Experience the all-new, singing and dancing interactive Primo brochure<http://www.exlibrispublications.com/primo/>.
> 
> From: Bibliographic Framework Transition Initiative Forum [mailto:[log in to unmask]] On Behalf Of Vitus Tang
> Sent: Saturday, June 13, 2015 02:26
> To: [log in to unmask]
> Subject: Re: [BIBFRAME] BIBFRAME Title Proposal
> 
> Sally,
> 
> It is good to know  that LC is converting its title and name/title authority records to bf:Work records. Thank you for that information. Supposed I am creating a work record for a translation. The record could contain two titles, one a uniform title constructed out of the work title of the original, and another one that is the title of the translation. For instance, a Japanese translation of John Steinbeck's Of mice and men:
> Uniform title: Of mice and men. Japanese
>              Translation title: Hatsuka nezumi to ningen
> Would they simply be two bf:WorkTitle in that work record, without further typing?
> 
> I'm not sure I fully understand why entities such as a bf:Person can be linked to an authority record but a bf:Work cannot. The function of a uniform title is as an "access point", just like "Steinbeck, John, 1902-1968" is the access point for the author (a bf:Person). If they serve the same function, shouldn't they have the same properties?
> 
> Thanks.
> 
> -- Vitus
> 
> 
> From: Bibliographic Framework Transition Initiative Forum [mailto:[log in to unmask]] On Behalf Of McCallum, Sally
> Sent: Friday, June 12, 2015 1:52 PM
> To: [log in to unmask]<mailto:[log in to unmask]>
> Subject: Re: [BIBFRAME] BIBFRAME Title Proposal
> 
> In BIBFRAME the uniform title is the name associated with a Work.  It is the WorkTitle.  There is no authority record for that title name.
> 
> In our work for the LC pilot we are currently converting our title and name/title authority records to make them into work records.  Then there will also be the need to merge in subjects, etc., etc.   We look forward to investigating this and using the results in the pilot.  Some of the questions we are trying to answer with this pilot include how well do they convert and are they usable as the base file after conversion.  New input, directly into BIBFRAME is easier to deal with as there these are born as works.  While new input is the focus of the pilot, we consider the base file an important component of the whole.
> 
> Does this help?
> 
> Sally
> 
> ***********************************
> Sally H. McCallum
> Chief, Network Development and MARC Standards Office
> Library of Congress, 101 Independence Ave., SE
> Washington, DC 20540  USA
> [log in to unmask]<mailto:[log in to unmask]>
> Tel: 1-202-707-5119 - Fax 1-202-707-0115
> ***********************************
> 
> From: Bibliographic Framework Transition Initiative Forum [mailto:[log in to unmask]] On Behalf Of Vitus Tang
> Sent: Friday, June 12, 2015 4:25 PM
> To: [log in to unmask]<mailto:[log in to unmask]>
> Subject: Re: [BIBFRAME] BIBFRAME Title Proposal
> 
> Ray,
> 
> How does the concept of a "uniform title" fit in here? For instance, the equivalent of a MARC 130, 240, or 830. For uniform titles, one would also need a mechanism for linking the title to an authority record, and currently the Title entity does not have a bf:hasAuthority property.
> 
> Thanks.
> 
> -- Vitus
> 
> Vitus Tang
> Head, Data & E-resources Control
> Metadata Department
> Stanford University Libraries
> [log in to unmask]<mailto:[log in to unmask]> - (650) 725-1153
> 
> 
> 
> From: Bibliographic Framework Transition Initiative Forum [mailto:[log in to unmask]] On Behalf Of Denenberg, Ray
> Sent: Friday, June 12, 2015 11:33 AM
> To: [log in to unmask]<mailto:[log in to unmask]>
> Subject: [BIBFRAME] BIBFRAME Title Proposal
> 
> 
> Attached, the first of several proposals mentioned in my earlier message.
> 
> Ray
> 

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