RDA & BIBFRAME: Status Report · RDA: Resource Description and Access (integrating resource, 2010- ) ISBD (consolidated edition, 2011; complete revision process started in 2018) Encoding

RDA & BIBFRAME:

Status Report

Charlene Chou

University of Washington Libraries

at

The Open University of Hong Kong

January 16th, 2019

Agenda

Goals

Focus on its impact on catalogers rather than

detailed concepts

What role will we play?

Part one: RDA Updates

RDA 3R Project

CEAL best practices & discussions

Part two: BIBFRAME updates

Testing at the University of Washington

LC pilot two

OCLC testing

2

My RDA Experiences & 3R Schedules

Fall 2010: as one of RDA testers at Columbia University

CEAL RDA training workshop & best practices:

Lead Trainer: 2012 to present

CEAL CTP Subcommittee on RDA, Chair, 2014-2017

CEAL Committee on Technical Processing, Chair, 2016-2020

ALA CC:DA 3R Test Group member, August 2018-present

RDA 3R project schedules

2016: some wording changes start such as agent replacing

person, family or corporate body

April 2017: original RDA Toolkit content frozen

June 13, 2018: Beta toolkit publicly released; the most recent

release was on Oct. 9, 2018

April 2019: stabilize the English text

Add policy statements and translations to beta site

Late 2019?: the new Toolkit becomes official

3

Part One

RDA Updates

4

Acknowledgements

Some slides include content

from RSC presentation website:

Kathy Glennan, Evolution of the RDA

Toolkit and Its Impact on Catalogers

Kate James, RDA 3R Project, March

2018

RDA Workshop, at ALA, June 2018

5

Transformation in Cataloging Glennan, K.:

Conceptual models

IFLA Functional Requirements models (FRBR, FRAD, FRSAD) replaced by IFLA Library Reference Model (IFLA LRM, 2017)

Descriptive/content standards

RDA: Resource Description and Access (integrating resource, 2010- )

ISBD (consolidated edition, 2011; complete revision process started in 2018)

Encoding standards

MARC 21 (ongoing development)

Significant additions made in response to RDA, 2008-2011)

Data models

BIBFRAME (ongoing development)

Introduction of LCGFT, LCMPT, LCDGT, FAST

My concerns:

DH (Digital Humanities) & DS (Digital Scholarship) developments &

projects

6

Kathy Glennan: Evolution of the RDA Toolkit and Its Impact on Catalogers

IFLA LRM Framework for the analysis of non-administrative metadata

relating to library resources

High-level, enhanced entity-relationship model

Consolidation and update of existing IFLA conceptual models

FRBR: Functional Requirements for Bibliographic Records (1998; amended 2009)

FRAD: Functional Requirements for Authority Data (2008, amended 2013)

FRSAD: Functional Requirements for Subject Authority Data (2010)

Applying LRM

Cataloging code implementations

Must respect the basic structure of the entities and relationships among them

May add expansions within the basic framework (specialized attributes, specific subclasses, refinements of relationships, etc.) May focus only on WEMI attributes and relationships, omitting the others

May use either literals (strings) or URIs/IRIs (things) to represent attributes

In the latter case, these really become relationships

RDA (beta Toolkit) is the first implementation of LRM

With expansions

7


Scope of RDA

RDA: Resource Description and Access is a package of data

elements, guidelines, and instructions for creating library and

cultural heritage metadata that are well-formed according to

international models

Focused on “things” of bibliographic interest

A refinement of IFLA LRM

Elements fulfill one or more LRM user tasks

Other information is out of scope

Administrative metadata

Rights metadata

Subject access beyond RDA entities

8


3R (RDA Toolkit Restructure and

Redesign) Project

Goals

Implement IFLA LRM entities

New: Agent, Collective agent, Nomen, Place, Timespan

Revised: Person

Retain current RDA elements unless they conflict with LRM

Redundant elements will be removed after sometime after

3R

Unstructured description of an element (e.g., type of recording)

preferred over old “details of” approach (e.g., details of type of

recording)

Generalize the instructions

Offer more flexibility in choosing how to record a piece of

information

Develop a new approach to relationship designators

9


3R (RDA Toolkit Restructure and

Redesign) Project

Goals, continued

Promote even greater international adoption of RDA

Original Toolkit available in 8 languages

RDA vocabularies (in whole or in part) available in 18

languages now

Better position RDA for use in linked data applications

Improve the Toolkit interface and address long-standing

problems

Restructure the underlying data

Provide efficient and reliable work processes and tools

for RDA editors and translators

10


11


RDA Elements

Specific aspects, characteristics, attributes, or

relationships used to describe an entity • Each element

has its own page in RDA, with the following structure

Elements over 1700

12


RDA Attributes, Relationships

Attributes

Same scope as LRM

Relationships

Same scope as LRM

Represented as elements – no longer

“relationship designators”

Includes inverses

Relationship matrix – 13 x 13 categories

Browse all entities and relationships in a two-

level hierarchy (domain & range) that places all of the RDA relationships in context

13


RDA Guidance Chapters 14


Changes with 3R Project 15

Changes with 3R Project

16


Changes with 3R Project

17


18


Aggregate Manifestations 19


An Aggregate Manifestation 20


In Real Life …

21


22

Diachronic Works

New Element—Extension Plan 23


Diachronic Works

Concept applies to more than just serials

Includes multipart monographs that are not complete when first

published

The complete poetical works / Lord Byron ; edited by Jerome J. McGann: 7 volumes, 1980-1993

But not all multipart monographs are diachronic o The winning of the

West / by Theodore Roosevelt: 4 volumes, [2004]

24


Challenges with Serials 25


Challenges with Serials 26


Application Profiles 27


Toolkit Navigation: Current and New

Current

Contains “general guidelines” chapters and instructions throughout

Instructions organized by section then chapter

Table of contents expands

Link to another instruction or policy statement replaces current instruction

New

Will contain general

guidance section

separate from entities

Instructions organized by

entity

Entity view diagram

expands to show

elements

Preview pane allows

viewing current instruction

and related instructions or

PS

28

Kate James: RDA 3R Project at CEAL conference

Attributes and Relationships

Current

Attributes and relationships are elements

Attributes and relationships in separate chapters

Identifier for Item (2.20)

Item relationships in chapters 17, 22, and 28

New

Attributes and relationships are elements

Attributes and relationships together

Item: identifier for item

Item: manifestation exemplified

29


Attributes as Relationships

When one entity is recorded as an attribute of another,

there is a relationship

Associated institution is a current example

New entities blur line between attributes and relationships

even more

Amy Tan has date of birth 1952

Amy Tan has related timespan of person 1952

30


Relationship Designators as

Elements

Current

Creator (Chapter 19)

relationship designators

(I.2.1)

instructions for relationship

designators in Chapter 18

Instructions for use in Chapters 18, 24, and 29

Part of the relationship element

New

Work: creator

Related elements:

artist, author,

cartographer,

composer, etc.

General guidance and

instructions at each element

It is the relationship element

31


Verbalized Labels from RDA

Registry

In RDA Registry, all elements have verbalized labels

that provide clues for domain and range entities

You can make a simple sentence with the labels, e.g.,

ALA has member Carla Hayden

32


Relationship Designator:

composer

Work to Agent:

Nihon kyo sokyoku

Composer: Ifukube, Akira, 1914–2006

Reciprocal relationship: Agent to Work

Ifukube, Akira, 1914–2006

Composer of: Nihon kyo so kyoku

33

Current Chapter 18 does not allow for unstructured description of relationships between works and agents, but if it did, you could say, “Nihon kyosokyoku has composer Akira

Ifukube.”


Registry Label: has

composer

Work to Agent:

Nihon kyo sokyoku

Has composer: Ifukube, Akira, 1914–2006

Nihon kyo so kyoku has composer Ifukube, Akira, 1914–2006

Reciprocal relationship: Agent to Work

Ifukube, Akira, 1914–2006

Is composer of: Nihon kyosokyoku

Ifukube, Akira, 1914–2006 is composer of Nihon kyo so kyoku

34


Example Changes

4 different types of examples

Basic Set

Resembles current examples

Recording Methods

Shows the same data recorded in different ways

View as Relationship

diagram

View in Context

A set of data elements for an entity

35


Basic Set Examples:

Relationships

Godzilla, King of the Monsters is an adaptation of the work Gojira

Recording method: unstructured description

http://id.loc.gov/authorities/names/no201302

1406 http://www.rdaregistry.info/Elements/w/#P10013


Recording method: IRI

[and others…]

36





http://www.rdaregistry.info/Elements/w/#P10013

http://www.rdaregistry.info/Elements/w/#P10013




View as Relationship

Example--Draft 37

Example resembles a visualization of an RDF triple. Both

entities and the relationship designator can be represented

with IRIs.


View in Context Example:

Work

creator: Christo, 1935–

creator: Jeanne-Claude

preferred title of work: The gates

form of work: Installation

date of work: 1979

38

Hopefully we will be able to show from which element you viewed

this example. Here the blue text is showing that you were looking at

“form of work.”


CEAL Best Practices

What’s missing in RDA for CJK Materials?

39

Ideas, proposals, and discussions

CJK RDA Full-record Examples

CJK Numerals

Presentation slides

Survey report

CJK relationship designators

CJK serials: title changes (CONSER CJK funnel)

CJK NACO best practices (NACO CJK funnel)

CJK pseudonyms

CJK subject headings, demographic and genre terms

(SACO CJK funnel)

Example: Zhiqing proposal

Buddhism resources

40

http://rdaandcjkworkshop.pbworks.com/w/file/123763518/CTP_RDA_Examples_Group_Full-record Examples_Feb.2017.docx



http://rdaandcjkworkshop.pbworks.com/w/file/116145293/2017_workshop_CJK Numerals.pptx

http://rdaandcjkworkshop.pbworks.com/w/file/116145293/2017_workshop_CJK Numerals.pptx

http://rdaandcjkworkshop.pbworks.com/w/file/116064309/CJK_numerals_surevy_report.pdf

http://rdaandcjkworkshop.pbworks.com/w/file/116064309/CJK_numerals_surevy_report.pdf

CJK Relationship Designators

Background:

CJK-specific issues not covered by the RDA Toolkit, Appendix I

as well as the PCC Training Manual for Applying Relationship

Designators in Bibliographic Records

Issues to discuss

Type 1: Mixed roles

Type 2: Synonyms

Type 3: Not exactly equivalent to terms in the Appendix I

Type 4: Different role depending on context and languages

Type 5: Not in the Appendix I

Next steps--recommendations

Appendix

41

http://access.rdatoolkit.org/rdaappi_rdai-15.html

http://www.loc.gov/aba/pcc/sct/documents/rel-desig-guide-bib.pdf



Type 1: Terms in mixed roles

Example 1: 编著 (bian zhu )

Options:

1. $e author, $e editor

2. $e author, $e compiler

3. $e author

4. $e compiler

Example 2:纂修 (zuan xiu)

Options:

1. $e compiler

2. $e compiler, $e sponsoring body

3. $e sponsoring body

42

Type 1: Terms in mixed roles (2)

Example 3: 編述 (bian shu)

Options:

$e compiler

$e editor

$e author, $e compiler

$e author, $e editor

Example 4: 繪著 (hui zhu)

Option 1: $e author, $e artist (for graphic novels specifically)

Option 2: $e author, $e illustrator (depending on the types of resources)

Others?

Recommendation: cataloger’s judgment with caution in context

43

Type 2: Synonyms: the list of multiple terms

Example 1: film producer for Chinese films

Terms: 制作, 攝製, 監制 (监制), 總製作人, 製作人, 制片人, 總制片人 (总制片人)

Example 2: compiler for older materials

Terms: 輯(辑), 纂, 編纂, 輯逸(辑佚)

Example 3: author

Terms: 著, 作, 著作, 執筆, 撰, 學, 文, 共著者, 作者, 原作, 執筆, 著者

Recommendation: the spreadsheet of grouping these

terms would be an effective tool for catalogers

44

Type 3: Terms may not have the exactly same meanings defined in the Appendix I

Example 1: 編譯 (bian yi)

Options:

$e editor, $e translator. (if involved translation from one language to

another language)

$e compiler (likely for a reference book, or compiling and making older

text in modern terms)

$e compiler, $e translator.

Example 2: using $e writer of added commentary, $e writer of

supplementary textual content, $e editor, or $e compiler for the

following categories of terms?

Revisions: 校訂, 校閱, 修訂/改訂, 增訂/增廣, 補闕

Criticisms: 批評, 考證, 辨異, 校對

Annotations & commentaries: 箋注, 音譯, 索隱, 解

45

Type 3: Terms may not have the exactly same

meanings defined in the Appendix I (2)

4. Cross-role or same role?

点校 (emend with punctuation)

$e editor (without writing commentary?)

$e compiler

校點 (criticism with punctuation)

$e writer of added commentary

$e editor

$e compiler

Recommendations:

These terms need to study in depth by a group of experts.

Some of them may be candidates to propose new terms.

46

Type 4: Terms may indicate different roles depending on context and languages

Example: 藏版 (keeper of the printing blocks)

The Japanese rare books guidelines (DCGPM)—publisher

The Chinese rare books guidelines (CGCRB) to Romanize

If some cases, publisher or printer

In some cases, keeper of the printing blocks

How about reprints to be cataloged in RDA?

keeper of the printing blocks (candidate for a new term?)

Recommendations:

Follow the rare books guidelines for its language respectively

For Chinese rare books (before 1795), follow CGCRB to Romanize.

Cataloger’s judgment with caution in context

47

Type 5: Terms are not in the Appendix I

Examples

藏版: (keeper of the printing blocks) when it’s not either publisher or

printer for Chinese ancient books

抄/鈔 (manuscript copier/scribe)

“transcriber” in Appendix I is “ … for writing down or notating unwritten or unnotated content, or by changing it from one system of notation to another.”

Propose a new term for manuscript copier or scribe?

音譯 (phonetic study): transliterator?

Recommendation: propose new terms

48

Next steps

Recommendations

for you to consider

49

Recommendations for next steps

Establish a working group to create a guideline to be used for CJK

community including our colleagues in Asia.

For missing terms, CEAL members are highly encouraged to

propose new terms to be added to the Appendix I.

Provide the file of CJK relationship designators at the RDA Toolkit

as the supplement to the Appendix I.

We need your votes and suggestions for the

next steps!

50

Appendix

Spreadsheet of CJK relationship designators for print (updated

3/18/2016)

Spreadsheet of CJK relationship designators for AV materials

(March, 2015)

51

http://rdaandcjkworkshop.pbworks.com/w/file/106329528/CJK_Relationship_Designators-_tentative_table_for_discussion_rev.xlsx



http://rdaandcjkworkshop.pbworks.com/w/file/93995933/CJK_Relationship_Designators_tentative_table_AV.xlsx

http://rdaandcjkworkshop.pbworks.com/w/file/93995933/CJK_Relationship_Designators_tentative_table_AV.xlsx

Part Two BIBFRAME Updates

52

Agenda

Linked data

BIBFRAME Updates

University of Washington Libraries

BIBFRAME 1.0: testing from 2014-2015

BIBFRAME 2.0: PCC Mellon project in 2019

LC Pilot two: testing for non-Roman scripts

CEAL conference in March 2018

ALA conference in June 2018

Other issues

OCLC

53

Linked Data: Testing & Review

Back-end

Data structure and concepts behind linked data

Bibframe Review Group

Review converted MARC data in BF (legacy data):

Outcome: UW comments to LC (125 issues)

Skills: BF vocabulary, BF in Turtle, FRBR, etc.

Mapping (RDA core to Bibframe):

Outcome: UW proposals on series and carrier

details

Testing on input forms for native RDA cataloging:

RIMMF, LC Bibframe Editor, UW RDA input form

Study: Bibframe, RDF/XML, RDA/RDF, Schema, etc.

CONTENTdm production pilot

Skill sets:

Functional knowledge of RDF (Resource

Description Framework), RDF triples (subject-

predicate-object), Ontologies/schema.org,

RDA/RDF, Bibframe, etc.

RDA/FRBR/RDA Registry

Impact on the workflow of technical services

Linked Data Working Group

Responding to ExLibris (ILS) development, adding

members from ITS, Acquisitions, etc., the plan for training

Front-end

WWW ontology

BBC (British Broadcasting Co.)

BBC Sports Ontology

The band “The Specials”—links to related news articles

Europeana collections

Explore 52,034,342 artworks, books … across Europe

Auto-suggestions based on RDF

DPLA (Digital Public Library of America)

Explore 11,645,532 items

Discovery

ILS/library portals (e.g. BL)

Web, e.g. Google Scholar

Multilingual searching on the Web

54

http://bibframe.org/vocab/

http://www.rdaregistry.info/rimmf/

http://www.rdaregistry.info/rimmf/

http://bibframe.org/tools/




http://www.lib.washington.edu/msd/pubcat/ld/input-form

http://www.rdaregistry.info/

http://www.bbc.co.uk/ontologies/sport

http://www.bbc.co.uk/ontologies/sport

http://www.europeana.eu/portal/

http://dp.la/

http://dp.la/

55

FRBR: graphical representation in 2010

RIMMF

tested in

2016

Reflection: Can we be software-enabled specialists who can gather, subset, normalize,

and enrich piles of records for a specific audience or purpose? Roy Tennant, LJ, 2006

Reflection: What can library communities contribute to the development of

semantic web in WWW?

1. Environmental scan: Semantic Web/Linked Data development in WWW

1. Web 1.0 (users only retrieve info) to Web 2.0 (users contribute)

2. Web 3.0—”Semantic Web”, Berners-Lee, Scientific American, May 2001

• Aims at converting the current web, dominated by unstructured and

semi-structured documents into a “web of data”.

• Tim Berners-Lee: the past was document sharing, the future is data

sharing. A URL should point to the data. Anyone accessing the URL

should get data back. Relationships in the data should point to

additional URLs with data.

• WWW Consortium (W3C)

• Building the Web of Data

56

https://www.w3.org/

https://www.w3.org/2013/data/

Summaries & References Panchyshyn, Roman.

Skill sets for Technical Staff, 2015 1. Skill sets:

1. Competency in RDA

2. Batch processing

3. Scripting languages

4. Bibframe

5. Linked data

6. Other metadata schemas

7. Identity management

8. Project management

9. Other skills

2. Positioning:

As leaders for quality metadata

3. Action plan—creative training plans

4. Stay on the edge:

Monitor for new trends or services

Take on leadership roles, e.g. BF testing, RDA/XML

5. Invest in staff success

6. 21st century technical services: takeaways

Quality service: leadership ad well-trained staff

Ability to adapt and meet new challenges

References Semantic Web

An introduction to Tim Berners-Lee’s Semantic Web.

Tim Berners-Lee

Semantic Web Stack

Linked Data at the University of Washington

Naun, Kovari and Folsom. LTS and Linked Data: a positon paper, December 16, 2015.

Deng, Shi. FRBR : Why do you need to know, 2010 OCLC CJK Users Group Meeting.

Tennant, Roy. Library Journal, Apr. 15, 2006.

57

https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&ved=0ahUKEwijtoDDn9LLAhUI52MKHfm8CXgQFggoMAI&url=http://connect.ala.org/node/242294&usg=AFQjCNESEGoE4u851a9yAOE0Q6F0Nu-8iQ&bvm=bv.117218890,d.cGc&cad=rja

https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&ved=0ahUKEwijtoDDn9LLAhUI52MKHfm8CXgQFggoMAI&url=http://connect.ala.org/node/242294&usg=AFQjCNESEGoE4u851a9yAOE0Q6F0Nu-8iQ&bvm=bv.117218890,d.cGc&cad=rja

https://en.wikipedia.org/wiki/Semantic_WebWeb_3.0

https://en.wikipedia.org/wiki/Tim_Berners-Lee



https://en.wikipedia.org/wiki/Semantic_Web_Stack

http://www.lib.washington.edu/msd/pubcat/ld

http://www.lib.washington.edu/msd/pubcat/ld

https://ecommons.cornell.edu/bitstream/handle/1813/41481/LTS_linked_data_position_paper.pdf?sequence=3&isAllowed=y

https://ecommons.cornell.edu/bitstream/handle/1813/41481/LTS_linked_data_position_paper.pdf?sequence=3&isAllowed=y

BIBFRAME Testing at University of

Washington Libraries

1.0: UW testing from 2014-2015

More than 100 comments sent to LC for

improvement

Some of them are CJK examples

2.0: one of participating libraries of PCC Mellon

Grant project to catalog in BIBFRAME

58

BIBFRAME Issues List: related to CJK examples #119 (UW): 020 $q should be retained for display purposes

#174 (UW): 041 gives non-existent language code for Chinese (zho)

#228 (UW): bf:titleStatement should have parallel non-roman script

#224 (UW): 245 $b non-roman should be in bf:subtitle

#201 (UW): bf:responsibilityStatement should retain brackets; not converted for Maps format; only parallel script not romanization; not converted for book w/o non-roman script

#225 (UW): 246 $i with non-roman not given

#178 (UW): 250 repeatability--$3 and parallel scripts

#227 (UW): providerStatement should have parallel non-roman script

#226 (UW): 264 $b with non-roman and multiple publishers duplicates non-roman script

#177 (UW): 505 lacks parallel non-roman script

#116 (UW): 650, @en assigned to foreign language terms

#232 (UW): 650 _7 $2 sk should have non-roman strings with dashes and w/o $2

#157 (UW): 8XX authorized access point should be from 8XX not 490

#162 (UW): language qualifiers on parallel script fields seem wrong (multiple examples)

#173 (UW): non-roman fields missing for related Work entry, e.g. original of translation

#179 (UW): multiparts should not generate multiple instances, for each vol.

#231 (UW): Non-roman forms are not authorized access points

Some CJK examples

Only in romanized form

<http://example.org/99131426860001452agent14> a bf:Agent ; bf:label "Ino ,

Kanori," .

bf:titleStatement "Taiwan ta cha ri ji"

Wrong language encoding "伊能嘉矩, 1867-1925"@zh-hani ;

<http://example.org/99131426860001452title6> a bf:Title ; bf:titleValue "Ino

Kanori no Taiwan tosa nikki.", "伊能嘉矩の臺湾踏柤日記."@zh-hani .

bf:providerDate "2014-", "2014-"@zh ;

Missing $q in 020 ISBN bf:isbn10 <http://isbn.example.org/986213349X> ;

bf:isbn13 <http://isbn.example.org/9789862133491> ;

providerStatement should have parallel non-roman script

bf:providerStatement "Taibei Shi : Guo jia tu shu guan : Da kuai wen hua, 2012." ;

264 $b with non-roman and multiple publishers duplicates non-roman script

bf:publication [ a bf:Provider ;

bf:providerDate "2012",

"二零一二."@zh ;

bf:providerName [ a bf:Organization ;

bf:label "Da kuai wen hua",

"國家圖書館 :"@zh,

"大塊文化"@zh ] ],

[ a bf:Provider ;

bf:providerDate "2012",

"二零一二."@zh ;

bf:providerName [ a bf:Organization ;

bf:label "Guo jia tu shu guan ",

"國家圖書館 :"@zh,

"大塊文化"@zh ] ;

bf:providerPlace [ a bf:Place ;

bf:label "Taibei Shi ",

"臺北市 :"@zh ] ] ;

Some CJK examples (2)

RDA/RDF vs. BIBFRAME

RDA/RDF is stronger in

Series

Notes

Technical details of a resource

Inverse properties (e.g.

animator/animatorOf)

BIBFRAME is stronger in

Administrative metadata

Identifiers

Subject headings

Holdings information

Support for both transcription

(literals) and URIs

Joe Kiegel's presentation at UW on 2/19/2015

Both RDA/RDF and BIBFRAME are able to represent

library information as linked data

Both schemas originate in libraries and must be

adopted widely by non-library users in order to

succeed

As Linked Data


RDA/RDF lacks a number of features of a carrier, e.g.

administrative metadata

BIBFRAME is currently not capable of carrying constrained RDA

without significant loss in information about classes

While neither fully works today, a combination of the two is more

successful

As Carriers


LC Updates

LC report at ALA Annual in June 2018

LC report on non-Roman scripts at CEAL

conference in March 2018

65

LC Report at ALA: Moving from MARC to BIBFRAME at LC

Revised BIBFRAME 2.0 data model and updated

vocabulary

http://www.loc.gov/bibframe

New MARC-to-BIBFRAME data conversion

specifications and conversion programs

https://github.com/lcnetdev/marc2bibframe2

Updated BIBFRAME record editor profiles

Infrastructure improvements at the Library of Congress

Additional servers

Updates to database software and triple store (MarkLogic)

66

67

Open Issues The MARC-to-BIBFRAME conversion creates “stubs” for works in

MARC 7xx tags; need a follow up process to unite these stub descriptions with full work descriptions

Merging drops the 7xx headings from the work descriptions; illustrators, editors, etc., on subsequent editions are ignored

Load sequence and system control numbers impact merging

http://...e2014431926 (work created in BIBFRAME editor)

http://...c018228499 (work created during MARC conversion)

Need editing profiles for many types of workflows and materials; not fully defined yet

Need ability to add a property/class “on the fly” while editing descriptions

Descriptions that are retrieved from the BIBFRAME database, edited, and returned to the database need to be fully linked with existing descriptions

Need the ability to “clone” a description – retrieve an existing Work or Instance, create a new description and save to the database with a new identifier

Need to accept multiple data serialization schemes (XML, JSON, RDF)

68

What’s Next?

Continue to evaluate and adjust matching and merging

in the BIBFRAME database and reload data as needed

Ingest CIP and ONIX data

Load Casalini RDF data

Offer download of LC’s BIBFRAME file for others to explore

Now available

http://www.loc.gov/bibframe/implementation/

Continue to improve editor

Mapping from BIBFRAME to MARC

69



Pilot Phase 1

BIBFRAME Editor

Creating BF bib record by opening the template

for monographs.

The template was then divided in three areas

RDA Work Elements

RDA Expression Elements

RDA Manifestation / BibFrame Instance

Elements

70

LC Pilot 2 for non-Roman scripts Phase 2:

A larger group and working closely with the developers

The records created for the Pilot Phase 2 will not be used for production purposes and that participant catalogers will still need to create data in BIBFRAME and a MARC record in ILS Voyager. They will catalog first in BIBFRAME and then in ILS Voyager.

Access points in Romanized form and Original script in description fields

LC: The non-Roman script should be primary in BIBFRAME and Romanization secondary. Perhaps Romanization beyond the title is not necessary. It may not be a standard ALA Romanization in any case. There should be a way to code which Romanization scheme it is.

Workflow management

The BibFrame Editor is a work in progress, evolving constantly to respond to the input of the participants.

One issue being addressed is how to avoid creating a duplicate record when a participant update a record.

The developers were able to migrate some nineteen million records from the LC Database to the BibFrame Database, but the BibFrame Database that I use is not a database of record

Areas to improve:

In the look up windows, we might be able to see the variant forms in a name authority description ; and for subject more prompting from the system to complete the field while editing it. One area where I have not totally digested on how to proceed is with the compilations, now called aggregates. I have not totally mastered how to input the information in the BibFrame Editor as I know to do it in the LC Database with MARC fields

71

OCLC Research BIBFRAME

2.0 Converter Analysis

Process

11 million records containing LCCNs from the OCLC

Research copy of WordCat

OCLC Research WorldCat includes additional identifiers

All formats included in the set

Converted selected records to MARCXML

MARCXML sent through LC BIBFRAME 2.0 converter

72



Analysis

Work IDs are very important

Useful at the beginning of the process

OCLC clustering adds them to OCLC Research WorldCat

URIs are very important

Several blank nodes without them

Blank nodes = non-interoperable

Converter contains BIBFRAME item descriptions

But we were only using bibliographic records

This left gaps in the data

OCLC Research updates to the converter

Populate 758 field with Work/cluster IDs

Modified to look for $0 and $1

Preferred URIs for VIAF and FAST

73

Cornell Work ID Project





Future experimentation

Look at indexing possibilities/goals/requirements

URI clean-up and population to existing MARC

records to reduce the number of blank nodes

Continue working with the Library of Congress

With multiple extensions to and variations of

BIBFRAME emerging, OCLC is thinking broadly

as we build capabilities that support the complex landscape

77

Thank you 78

Documents

RDA & BIBFRAME: Status Report · RDA: Resource Description and Access (integrating resource, 2010- ) ISBD (consolidated edition, 2011; complete revision process started in 2018) Encoding