1. Paul Moeller and Laura Wright
CU Boulder and FOLIO:
An Overview of Engagement and an Intro to Cataloging in FOLIO
Paul Moeller and Laura Wright

2. What is FOLIO? •The Future of Libraries is Open
•FOLIO is a collaboration of libraries, developers and vendors building an open source library services platform. It supports traditional resource management functionality and can be extended into other institutional areas. •

3. Some Partner Libraries
•Cornell
•Lehigh
•U. Chicago
•Texas A&M
•Five Colleges
•U. Alabama
•Fenway Library Organization
•Duke
•U. Glasgow
•SOAS London
•Sapienza
•U. Leipzig
•hbz
•GBV VZG
•Chalmers University of Technology

4. Open
GitHub
•All code for FOLIO is stored on GitHub. FOLIO offers a beginner’s guide to its repository on GitHub.
•dev.folio.org/source-code
Get the Code
•FOLIO’s code repository can be accessed on GitHub.
•repository.folio.org

5. Support
SirsiDynix
ByWater
EBSCO
Index Data

6. CU Boulder in FOLIO
•Became a partner in Open Library Environment (OLE) in 2017 •
•Voting member on OLE Board
•0.5 FTE developer committed by CU to project
•A member of CU staff to serve on the Product Council
•Product Council acts on behalf of the OLE Community and FOLIO partners to express and champion priorities in the development of the FOLIO Library Service Platform, and ensure the relevance and cohesiveness of the FOLIO project.
•Contribute efforts of other relevant staff as needed and available
•Why? Open, save $, improve marketplace, flexibility, cloud based service, build to suit…
•Commitment?

7. Special Interest Groups (SIGS)
SIGs are officially sanctioned by the FOLIO/OLE Product Council and provide forums for FOLIO participants to form consensus on FOLIO functionality through the creation of documents, reactions to prototypes, and code snippets. They allow users to exchange ideas, develop shared goals for the FOLIO project, and research and develop new interchange standards with widely used software.
•Metadata Management
•Laura Wright – Convener
•Accessibility
•Debbie Hamrick – Convener
•Resource Management
•Nicole Trujillo, Steve Brown, and others

8. Metadata Management in FOLIO
special thanks to:
Christie Thomas Head, Data Management Services, University of Chicago. Charlotte Whitt Senior Analyst, Product Owner, Index Data.
Lynn Whittenberger
Associate Head of Acquisitions & Discovery, North Carolina State University
and
other MM SIG members

9. Why FOLIO? cost/limitations of commercially available tools
micro-services, adaptability
moving beyond MARC
create solutions instead of workarounds
opportunity to examine our needs

10. Development begins with the user interface.
Working groups
Instances, Holdings, and Items
Advanced Searching
Analytics and Boundwiths
MARCcat
Working with format-specific bibliographic, holdings, and authority metadata.
UX-centered
Development begins with the user interface.
Working groups (cont.)
Container Records
Tags
ERM integration

11. “Inventory is the FOLIO app where bibliographic information from a variety of sources can be presented in a uniform, abstracted form for management of the collection regardless of the format or content rules used to describe a resource.”
(FOLIO Inventory: a working definition Metadata Management SIG)

12. Inventory Where users can manage and maintain local metadata
FUNCTION
DATA MODEL
INFRASTRUCTURE
Where users can manage and maintain local metadata
Influenced by BIBFRAME; introduces native FOLIO data format
Inventory is a hub for FOLIO and cataloging apps

13. Initial Data Modeli
Inspired by the BIBFRAME 2 conceptual model and the Dublin Core (DC) Elements
Model has evolved as we outline and review use cases and requirements

14. FOLIO’s current data model
Inventory
Import app
Container
FOLIO Apps
Export app
Instance
Generic Bibliographic Storage
Holdings
MARCCat App
Item

15. Container records Hierarchical (parent/child)
Collect other Inventory records together for management purposes
Container level metadata for describing a package, subscription, or membership
Records can be “in” more than one container

16. Questions so far?

17. Inventory in Action http://folio-snapshot-stable.aws.indexdata.com/

18. Demo Outline Searching Filtering, Faceting Results display
Instance record display / edit (local and source record)
Instance record creation (local)
Holdings creation / edit
Item record display / create / edit
Bound-with/analytic model
Paired field values

19. Paired/grouped values in Instance/Holdings/Item Records

20. Paired/grouped values in Instance/Holdings/Item Records

21. Questions?

22. Metadata Management environment
Data Import
MARCCat
Authority control
Order
eHoldings
ERM
Codex
Check out
Check in

23. MARCcat + BIBFRAME - exist side-by-side
Generic Bibliographic Storage
Inventory
MARCCat App
Container
FOLIO Apps
Instance
Generic BIBFRAME Storage
Holdings
BIBFRAME Editor App
Item
23

24. And more to come - multiple can exist side-by-side
Generic Bibliographic Storage
Inventory
MARCCat App
Container
FOLIO Apps
Instance
Generic EAD Storage
EAD Editor App
Generic BIBFRAME Storage
Holdings
BIBFRAME Editor App
Item
24

25. Questions?