Print

Print


Just to be clear, BIBFRAME no longer has bf:resourceRole in bf:Person, as shown in Adrian's example:

<http://d-nb.info/bf_temp/work_1034321757> 
... bf:associatedAgent [
        bf:hasGNDLink <http://d-nb.info/gnd/156605406> ;
        bf:label "Hehn-Kynast, Juliane" ;
        bf:resourceRole <http://id.loc.gov/vocabulary/relators/ill> ;
        a bf:Person
    ]

Taking the current transform of the DNB's demo data at http://bibframe.org/resources/sample-dnb/marcxml.xml and as transformed, http://bibframe.org/resources/sample-dnb/bibframe.xml

<bf:Work rdf:about="http://bibframe.org/resources/sample-dnb/010446591">
	<rdf:type rdf:resource="http://bibframe.org/vocab/Text"/>
	<relators:aut rdf:resource="http://bibframe.org/resources/sample-dnb/010446591organization9"/> 
....
</bf:Work>
....
<bf:Organization rdf:about="http://bibframe.org/resources/sample-dnb/010446591organization9">
	<bf:label>Verein Deutscher Ingenieure</bf:label>
	<bf:authorizedAccessPoint>Verein Deutscher Ingenieure</bf:authorizedAccessPoint>
	<bf:systemNumber rdf:resource="http://bibframe.org/resources/sample-dnb/010446591identifier15"/>
	<bf:hasAuthority rdf:resource="http://id.loc.gov/authorities/names/n79107696"/>
</bf:Organization>

In their 110, they have 2 systemIDs that can be converted to hasAuthority uris, 
<datafield ind1="2" ind2=" " tag="110">
	<subfield code="0">(DE-588)1012118-3</subfield>
	<subfield code="0">(DE-101)00406769X</subfield>
	<subfield code="a">Verein Deutscher Ingenieure</subfield>
	<subfield code="4">aut</subfield>
</datafield>
but the current transformation uses ID.loc.gov.

Nate


-----Original Message-----
From: Bibliographic Framework Transition Initiative Forum [mailto:[log in to unmask]] On Behalf Of Karen Coyle
Sent: Thursday, July 10, 2014 8:37 PM
To: [log in to unmask]
Subject: [BIBFRAME] The headings as strings assumption

Adrian Pohl has a very informative blog post about the use of identifiers in authorities, stimulated by his reading of Rob Sanderson's
document:
http://www.uebertext.org/2014/07/name-authority-files-linked-data.htm

The use of authorities to represent "preferred name" strings (as opposed to representing identified *entities* who have a preferred display form for human usage) appears to be an American anomaly - at least among the libraries he mentions.

One question we could ask ourselves, because we do have identifiers for the things described in authority records, is how feasible it would be to transform LC authorities to identify an entity  rather than a string. 
Is this a few tweaks, a total re-do, or something in between? My gut feeling is that it would be a behind-the-scenes change that wouldn't affect cataloger usage. Does anyone else see it that way?

I also wonder if we really must resign ourselves to using strings in our future data because "that's what's in the MARC records." There are authority control services that match the strings in bibliographic records to authority records in order to update the bibliographic data. 
That same process should be able to add authority identifiers to the bibliographic records for the same matches. In fact, there are vendors who will do this today. I'm sure that matching isn't 100%, but I suspect that having identifiers for name authorities in our bibliographic records is much less of an effort than converting our data and systems to BIBFRAME. It seems short-sighted not to begin this process today, before the death of MARC, rather than carrying the strings forward to a new bibliographic model.

kc

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