1. BIBFLOW: An IMLS Project
Xiaoli Li
Co-head of Content Support Services
University of California Davis Library
Jan. 31, 2015

2. What Is the BIBFLOW Project?
Is a 2-year project of the UC Davis University Library and Zepheira, funded by Institute of Museum and Library Sciences (May 2014 – April 2016)
Its official title is “Reinventing Cataloging: Models for the Future of Library Operations”
Is a research project that will address questions like “What impact will adoption of BIBFRAME on technical services workflows in an academic library”?
BIBFLOW = BIBframe + workFLOW
One of the major deliverables is a that can help library community transition cataloging work to a linked data/BIBFRAME native ecosystem
Roadmap

3. How?

6. This complexity leads to the inevitable conclusion that Linked Data represents an evolutionary leap for libraries and not a simple migration.

7. Workflows and Use Cases
BIBFLOW’s focus is on developing a roadmap for migrating essential library work efforts (workflows) to a BIBFRAME / LOD ecosystem.  Library work involves daily engagement with a large collection of software systems, institutions, and vendors.  As such, moving to a LOD ecosystem is not simply a matter of understanding its impact on library data but also on these complex workflows.

8. Original Cataloging Workflow for Print Monographs
Melvyl (UC OPAC)
Aleph
Auth
Bib
Harvest (UCD OPAC)
yes
New Name Auth?
OCLC WorldCat
Vendor Service
Auth
Automated process (weekly done by Systems Dept)
yes
Auth Control
New Sub Heading?
Propose to LC
Bib
Create holdings record
Add/complete item record
Physical Processing Unit
Original Cataloging Workflow for Print Monographs

11. Use Case: Original Non-Rare Book Cataloging Using OCLC Connexion Client

12. 1

13. We need your feedback!
We invite comment on these workflows posted on our project blog:
Please let us know how these workflows compare to the workflows at your institution and also what workflows are missing. We will use your input to adjust our testing as the project progresses.

14. Assessment of Library Management System
To make the transition into LOD/BIBFRAME possible, library community needs a linked data oriented system

15. Key Findings about Kuali-OLE
OLE 1.0 (latest release at the time when we reviewed the product in 2014) is not cable of supporting LOD/BIBFRAME operations.
However,
OLE’s bibliographic database (DocumentStore) is robust, extensible, and capable in its current form of dealing with linked data. This is advantageous from a development perspective.
For more information, visit our project blog:

16. Based on identified workflows and the Kauli-OLE assessment, we were able to develop a preliminary LOD/BIBFRAME implementation model. This model allows for the gradual, phased shifting of library work efforts from a MARC to LOD/BIBFRAME ecosystem such that all workflows will function and communicate with each other synchronously regardless if they are LOD/BIBFRAME or MARC native.

17. What’s Next?
UC Davis and Zepheira will enhance BIBFRAME Scribe by adding external services and developing BIBFRAME profiles

18. MeSH
> Serials
> maps
> Authority?
> ??

19. What’s Next? (continued)
Program the Kauli-OLE product so UCD catalogers can use Scribe to create BIBFRAME description for various materials and store the data in a BIBFRAME-RDF triplestore.
Develop and test data transformation service/tools
Identify and connect an open source OPAC to the triplestore

20. Standard Kauli - OLE Implementation

21. Full BIB OLD/BIBFRAME Implementation

22. Native LOD/BIBFRAME Implementation

23. LMS Xiaoli’s Dream Triplestore Content from Web EAD METS RDA DDI ?
Holdings
Content from Web
Order
LMS
EAD
Triplestore
METS
RDA
CIRC
DDI ?
Vendors
OCLC
Publishers
Xiaoli’s Dream

24. We look forward to your feedback!
Thank you!
We look forward to your feedback!