1. Getting Open Source Up and Running: OLE and FOLIO
@FOLIO_LSP
Getting Open Source Up and Running:
OLE and FOLIO
Paula Sullenger, Associate Dean for Information Resources
Texas A&M University
Sharon Wiles-Young, Director for Library Access Services
Lehigh University

2. Lehigh In Production with OLE:
SWY - Chicago Lehigh and SOAS came up on OLE summer of UX/UI -

3. Lehigh University: Open Source Possibilities
SWY - OIM oracle identity management data mapped into the patron/user record interfaced with University systems

4. OLE lessons learned Off shore developers model not ideal
Disadvantages Advantages
Off shore developers model not ideal
ERM development could not continue because of technology middleware developed by Kuali
Excited by possibilities for workflows and middleware not flexible
UX/UI design not a priority
Consulting and working with Librarians incredibly important and new collaborations developed
Librarians learned new skill sets and software
Librarians doing more with data - CIRC and ILL
Coding and working with apps and APIs
SWY -

5. Lehigh University: Open Source
SWY - So why would Lehigh do this all over again?
NCIP
toolkit

6. The (Present &) Future of (Texas A&M) Libraries is Open
blacklight
VIVO
Library of Congress
Chronam
PS - Why would Texas A&M join in? - We have to get off Voyager soon - wanted to go open source first
We know it’s not free, not even cheap
OAKTrust & OAKFund
Internet Archive
BookReader

7. FOLIO Structure and communications
Host for FOLIO
Home for three existing open source projects:
Open Library Environment
GOKb
VuFind
SWY - FOLIO ; Administrative home, all the licenses including Apache 2 , tools - wiki and listservs , now home for other open source projects and this can build even more partnerships in the FOLIO project.

8. FOLIO Structure and communications
Stakeholders- Tripartite - OLE, EBSCO, Index Data
OLE Board
OLE Steering Committee
Product Council - guides the functional development of the FOLIO Library Services Platform and manages scope without impeding development
AGILE DEVELOPMENT
FOLIO ; WEEKLY and Overview of project and Communicates the roadmap, responsible for coordinating new developer groups and work with SIGS, identify gaps, outreach and encourage others to get involved if interested,Wiki has all the minutes and agendas of Sigs and other groups, Important to resource SIGs, understand the SIG progress address new SIGs and
AGILE Development- very important to keep development cycle going- make sure SIGs are responding to PO and UI/UX needs and that SIGs get to respond to new code development of functionality

9. FOLIO is a COMMUNITY of peers including: academic libraries, OLE Partners, Index Data, EBSCO & others

10. FOLIO: The Engaged Community is Growing
Domestic

11. FOLIO: The Engaged Community is Growing
PS- Int’l interest very high - especially interested in future possibilities - Hungary, Australia

12. OLE resources
SWY - Show Librarian involvement; partnership and collaboration -- Also non-OLE participation - Harvard, MIT, NC State,

13. FOLIO Platform : Library Service Platform
Innovative open source LSP
that enables logical, seamless, efficient and effective workflows for library staff that will lead to improved services for our
communities and institutions.
SWY - Platform testing

14. Evolution to FOLIO: Functional requirements to Roadmap
PS - As soon as FOLIO was conceived, a group formed to think out the functional requirements; combined with German FR, came up with this document; Roadmap followed - v1, then future enhancements; Formed SIGs to flesh out the first four primary functional areas - RM, RA, MM, UM? Put out call for volunteers from the OLE member libraries - others joined in also

15. Special Interest Groups (SIGs)
Metadata Management
Resource Access
Resource Management
User Management
Consortia
Internationalization
Forum Facilitators
Reporting
Security
Accessibility
PS Highlight the non-OLE participants from Harvard, NCSU, ZBW, Nat’l Libr of Scotland,
Consortia - University System of Maryland & Affiliated Institutions (USMAI) Library Consortium, input from OhioLINK, Colorado Alliance have participated in some meetings and informed discussion

16. PS - UX is primary - SIG members and UX designer spend weeks on a topic - UX designer comes back with conceptual drawings - Coding doesn’t begin until concept approved - working demo comes back for feedback

17. Development Milestones
PS Create, Read, Update, Delete

18. Development Milestones - cont

19. Discuss list - participation
PS - developer teams -- questions

20. Innovations: UX/UI Prototype ux.folio.org
SWY - comparison Here is the modern UX/UI layout with navigation and icons which you will see in more detail from others today-- Filip put out for comment on discuss and gets feedback
so we were ready...

21. Development work in FOLIO:
DEMO
Development work in FOLIO:
Users
Instances
Items
Check in and Check out
Requests
e-holdings

22. Current work Order screen mockup Print/electronic journal mockup
Print book

23. Innovations

24. FOLIO Codex Introduction
PS -
Kristen Wilson?

25. FOLIO Codex IntroductionPS

26. FOLIO Codex IntroductionPS

27. FOLIO Codex IntroductionPS

28. FOLIO Codex IntroductionPS
Codex metadata elements

29. FOLIO Codex
A normalization and virtualization layer that allows for FOLIO to integrate metadata about various resources regardless of format, encoding, or storage location.
FOLIO is schema-agnostic (MARC, MODS, Dublin Core, ETD, PBCore, Darwin Core…)
Native metadata from format-specific editing apps or from external sources
Codex metadata derived from Native metadata
Format & Schema agnostic - Codex is not a database, on-the-fly with each query
PS - Codex vs. DC- Codex not a schema - the native schemas may come and go or change; write a new crosswalk for each
Codex in an interface - everyone involved in FOLIO can code against it

30. FOLIO Codex Model
Initial version in Orange; future development in Blue
“Package” as a container
“Item/Holding” still under development

31. Innovations Inventory Fund Mgmt Future consortia/collaboration
Hook to university systems (ID mgmt)
External KB linking

32. Different ways to participate
From staying informed to actual coding, and everything in between:
Forums
Meet-ups
Newsletters
Wiki
Special Interest Groups (SIGs)
FOLIO Forums recordings:

33. Different ways to participate
(working platform for SIGs and Product Council)
(Need active participation from librarians)
(Very technical)
(User interface concepts)
(working code)

34. Future: Next Generation of Digital Learning Environments
Malcolm Brown LMS systems one size fits all approach is dead end; interoperability standards use of apps, take advantage of connectors no recommendation on vendor, no prescribed components and local applications distant online learning
Megan Oakleaf and Malcolm Brown - Academic Library and the Promise of NGDLE- Lehigh have a new assessment officer looking at GPA data and how do libraries help meet with this officer? One example of Dean of Students identifying students needed more attention writing papers are refered to the library.

35. Catalyst article about Koha
Koha plus FOLIO: A solution for connected Library Services
“Most academic institutions will have both a library system and a learning management system. It would be great if these systems could talk to each other.”
Applications- Link Moodle and Koha
Check out course reserves
Course reserve materials-
Push other relevant resources to Moodle course
Institutional wide reports - report sharing

36. Development team
Core development team: Index Data, Knowledge Integration, OLE and EBSCO
Collaboration through open tools: issue tracker, wiki, forums, Slack, GitHub
Biweekly check-ins and coordination: “lightweight agile”
Open to anyone but time and effort is needed to enjoy/contribute
Other Development Groups:
Auburn University
Universidad Nacional Autónoma de México (UNAM)
The University of the West Indies (UWI)
China Academic Library and Information System (CALIS)
Instituto Brasileiro de Informação em Ciência e Tecnologia (IBICT)
Vendors (e.g. QULTO, Frontside, Stacks, SirsiDynix)
PS - Jeremy Last year Dublin ; August - 47 in Montreal F2F - 3x per year

37. THANK YOU Paula Sullenger | Assoc. Dean, Texas A&M
Sharon Wiles-Young | Director, Access Services, Lehigh
@FOLIO_LSP