Open Source Library Services Platform LSP 37 th

Open Source Library Services Platform (LSP) 37 th ADLUG Meeting – Venice – 12 -14/09/2018 @FOLIO_LSP 1 | www. folio. org

EBSCO and others are funding the creation of an open source Library Services Platform (LSP): FOLIO will include full-featured ILS/LMS functionality and will be extensible to support add-on modules. 2 | www. folio. org

Our industry has witnessed a trend toward vendor consolidation, resulting in: • closed systems • less choice • less innovation • higher costs 3 | www. folio. org The FOLIO goal is open systems, more choice, more innovation, lower costs

Open Source means…. OPEN INNOVATION Open innovation means choice of vendors and applications 4 | www. folio. org MICROSERVICES ARCHITECTURE VIBRANT ECOSYSTEM Microservices architecture means easier to develop and innovate Vibrant ecosystem means many participants

FOLIO is a COMMUNITY of peers including: academic libraries, software vendors & others 5 | www. folio. org

FOLIO: The Engaged Community is Growing 6 | www. folio. org

FOLIO: The Engaged Community is Growing 7 | www. folio. org

Special Interest Groups (SIGs) • Accessibility • Internationalization Special Interest Groups (SIGs) provide forums for FOLIO participants with similar technology needs, geographic area, or topical interest • Metadata Management • Allow users to: • Consortia • Reporting − exchange ideas • Repositories − develop shared goals for the FOLIO project • Resource Access − research and develop new interchange standards with widely used software • Resource Management • Security • User Management 8 | www. folio. org

Core development team: Development Team 9 | www. folio. org • Index Data, Knowledge Integration, OLE and EBSCO Other development teams: • @Cult, Italy • Auburn University, USA • China Academic Library and Information System (CALIS), China • Frontside, USA • Instituto Brasileiro de Informação em Ciência e Tecnologia (IBICT), Brazil • QULTO, Hungary • Sirsi. Dynix, USA • Stacks, Canada • The University of the West Indies (UWI), Jamaica • Universidad Nacional Autónoma de México (UNAM), Mexico

FOLIO Development Languages Almost any modern language can be used perl: : mason Gateway/Backend Modules App & Connector Modules Frontend User Interface The core ecosystem is Java, vert. x, Java. Script and node. js, supporting the system modules and gateway. Building blocks for the App and connector modules can use a number of languages. FOLIO’s user interface is a template driven single page application built with React and Java. Script. 10 | www. folio. org

Modular Choose apps 11 | www. folio. org

Base Applications • Acquisitions • Cataloging (Metadata Management) • Circulation (Resource Access) • Electronic and Print Management (Resource Management) App • Knowledge base App • Migration Tools • OPAC Functionality • Resource Sharing 12 | www. folio. org

Extending into new areas • Content Management Systems • Data Mining App • Grant Management • Institutional Repositories App App • Learning Management Systems • Linked Data • Predictive Analytics • Research Data 13 | www. folio. org App

Platform of Choice • APIs throughout • Completely open • Anyone can build apps 14 | www. folio. org

Hosting by Libraries Any library may load and operate FOLIO code locally Completely free for the library, except for staff and hosting / server expenses 15 | www. folio. org

Supported Open Source Choices for hosting, services and support for FOLIO 16 | www. folio. org

FOLIO will be available under an APACHE 2 LICENSE the most permissive license 17 | www. folio. org

Software is rapidly taking shape V 1 Beta released July 2018 18 | www. folio. org

FOLIO Milestones | Timeline alpha release (resource manager) JANUARY 2018 FOLIO running in libraries JULY 2018 FOLIO V 1 release (beta) 19 | www. folio. org JANUARY 2019

Different ways to participate From staying informed to actual coding: • Forums • Meet-ups • Newsletters www. folio. org • Wiki • Special Interest Groups (SIGs) • And more 20 | www. folio. org

How WECAT fits in FOLIO 21 | www. folio. org

Porting of We. Cat The porting of We. Cat in FOLIO has required the Re-Think of the cataloguing module in order to be compliant and interact with all FOLIO Apps, above all INVENTORY. 22 | www. folio. org

What INVENTORY is ? INVENTORY is the FOLIO app where bibliographic information from a variety sources can be presented in a uniform, abstracted form for management of the collection. Inventory consists of four entities: • Instance • Holdings • Items • Packages Istance records may be derived from full bibliographic records (in MARC or other format) Instance records can also be in the native FOLIO format when full bibliographic description is not required. 23 | www. folio. org

What INVENTORY is not? Instance records are not full descriptive catalog records. Instance record editing is not the equivalent of full MARC (or other metadata format) editing. Source record editing occurs in MARCcat is the evolution of We. CAT. Records in Inventory interact with MARCcat. 24 | www. folio. org

How MARCcat and Inventory Fit Together in FOLIO Diagram to express the interaction between Inventory and MARCcat per V 1 25 | www. folio. org

Assumptions for v 1: • The only bibliographic formats are Codex (used for Codex Search App), Inventory (used for Inventory App), and MARC-21 (used for MARCcat). • Each Inventory instance record only can relate to one (1) [MARC] source record • In Inventory, users will have options to view the MARC record (generic bib storage) and edit the MARC record (in MARCcat app) • MARCcat bibliographic records, Generic bib storage, and any associated Inventory instance records will stay in sync automatically with regards to CRUD, with warning messages if needed. 26 | www. folio. org

Record in Inventory Button: Edit MARC Record -> link directly to the record in MARCcat in edit mode 27 | www. folio. org

@Cult operational goals All porting activities concern the: • Frontend side architecture: capture library-specific requirements, design models, (graphical) interfaces and workflows and validate the design with expert groups • Backend side architecture : implement fundamental set of library management functionality The Frontend and Backend sides interact with Metadata Management SIG 28 | www. folio. org

Metadata Management SIG The Metadata Management SIG (Special Interest Group) involves: • Librarians from different Libraries Institutions and Universities • Product owners (PO): is person responsible for working with SIG to determine what features will be in FOLIO. MARCcat PO is Tiziana Possemato • Developers: Core Development team (from Index Data, Ebsco, @Cult and so on. . . ) 29 | www. folio. org

What is Metadata Management SIG? The work of the Metadata Management is focused on the definition of the essential bibliographic management functions: • Creating, editing, suppressing, deleting, importing, exporting, replacing, overlaying, and reporting. • Considers metadata storage and harmonization between traditional library materials, knowledge bases, and other forms of information managed by libraries. • Defines core authority functions 30 | www. folio. org

Metadata Management SIG involvement gives librarians the opportunity to: • Re-Think It – everything we do, every step in the process • Have input on each aspect – design, workflow, functionality 31 | www. folio. org

Metadata Management SIG – subgroups Under Metadata Management SIG there are different subgroupes related to the specific apps: - Batch Loader subgroup - Inventory - MARCcat subgroup 32 | www. folio. org

MARCcat subgroup: SCOPE The MARCcat subgroup will work with developers to outline functional requirements for the FOLIO MARCcat application. Overall scope is to implement We. Cat cataloguing module into the FOLIO environment as the MARCcat app. 33 | www. folio. org

MARCcat Subgroup Resources Subgroup wiki page: https: //wiki. folio. org/display/MM/MARCcat+Subgroup Under Metadata Management SIG Attachments: meeting notes, use cases, wireframes, user stories Google Drive folder: https: //drive. google. com/drive/folders/17 m. Jz. I 0 k. Kch. YYZuc 19 j. Pdh. KGG 3 t. Cbj. ZOc Discuss: https: //discuss. folio. org/ Solicit feedback from larger community Slack channel: # marccat # inventory-and-marccat 34 | www. folio. org

Development process Product Owner, UX Designer, Developers and member of SIGs Feature UX Feature Requirements Feedback User Stories in issue. folio. org (collected by PO) Development Sprint Review (by Tech Team) SIG Demos (by PO) UAT* (by SIGs) *user acceptance testing 35 | www. folio. org

Questions? 36 | www. folio. org