Dear FOLIO SIG members,


WOLFcon is coming up (May 7-11, in Durham, NC)!    You may be wondering if you or someone from your organization should be attending.  I wanted to send a quick note letting you know that, YES YOU SHOULD ATTEND if at all possible. 


Why?  WOLFcon is a unique opportunity for subject matter experts, designers and developers to meet face-to-face to work through the pressing issues related to v1 and beyond.   We have blocked time in the draft WOLFcon agenda (attached) by “theme” (e.g. RM SIG/Dev meeting or Cross-SIG/Dev meeting) and are currently in the process of collecting specific topic proposals for those theme blocks.  Some of the proposals we have received from SIG conveners, POs, dev leads and UX leads are listed below.  Each proposal has detailed agendas and target outcomes.  We mean business!  The WOLFcon planning committee will prioritize and assign the topics to theme blocks, doing our best to accommodate a wide variety of interests, while prioritizing hot issues and minimizing meeting conflicts.  We will do our best to design a productive agenda for all!


In addition to the working meetings, there will also be informative presentations and panels on topics such as Resource Sharing, Workflows and ERM/GOKb Update.


Of course we understand that time and budget considerations will factor heavily on attendance decisions.  That said, we wanted to make sure that you all understood the value of attendance.  Please reach out directly if you have any additional questions!


Best regards,


Cate Boerema


Cate Boerema

Principal Product Owner, FOLIO

EBSCO Information Services

Phone: +1 (978) 238-9334





TARGET OUTCOMES- Describe what you want to get out of this discussion.
(be specific, name presenters if applicable)

Item Status

- What item statuses have we defined for FOLIO so far? (PO (?): present item status overview spreadsheet)
- What should be considered when deciding whether something should be or impact an item status vs some other item flag or property? What are the functional implications we should take into account? (PO (?): present functional implications tab of item status spreadsheet)
- What workflows haven't we discussed still that may impact item status?
- Prioritize and discuss remaining workflows and decide how best to handle

Locations, Service Points and Implications

- Review plans for FOLIO locations and service points (Cate: present current designs and documentation)
- Discuss implications for these: where and how do they tie in: check out, check in, fees/fines, permissions, printing slips, item status etc. (Cate: present what we know and facilitate discussion)
- Should SP to locations relationship be 1:M or M:M?
- How do we associate a workstation, session etc with service points?

WeCat in FOLIO

- What is the current understanding of how FOLIO and WeCat will integrate (Charlotte: present diagram(s))
- Which FOLIO modules are required by WeCat (we refer to modules such as mod-permissions, mod-users, mod-inventory, mod-circulation)? Which of them are affected by WeCat?
- Does this make sense to everyone?
- What are next steps for moving this forward?

Resource Types, Format, Material Types

- Presentation of the joint MM+RA working group's recommendations based on categories that RDA has already developed (Content, Carrier, and Media Types) and a new fourth category called for Continuing items ('issuance')
- Does this fulfill the usecase in apps like Check out, Reporting, Codex Search

eResources in Inventory

Review plans for representation of eResources in Inventory - e.g. show order status, and maintain an item-record. Futher more discuss:
- batch load of electronic resources
- KB integration with Inventory; how to avoid duplication when managing holdings of eResources.

Help app

Review the design of the Help app - a cross functional app - see: (target outcomes to be described further)


As the project grow bigger, and more people gets involved, the more important gets the documentation. Here a list of some of the reference tools we have; some more updated than others: FOLIO Glossary of Terms, ERM Glossary, GitHub ... (more to be listed).

Acquisitions workflow walk-through

Let’s go through the process of ordering, receiving, paying for, managing budgets, etc., both individually and in batch. What is working well, and where are things not? Is the intersection between Acquisitions and Inventory working as anticipated?

ERM and E-Holdings

Discuss the intersection between e-holdings, acquisitions, and ERM. Review ERM data model and supported use cases. Review how KB integration can best support ERM functionality, both with KBs that maintain holdings externally and those that don't. Walk through use cases to ensure effort does not need to be duplicated in multiple places, and data can be migrated FOLIO while still maintaining relationships

How MARC cataloging/editing app and Inventory fit together

Understand 1) how instance, holdings, and item data get into inventory from various origins (loading massive migration data, batch MARC loads, individual record lookups in sources like OCLC, slim instances created based on work done in acq or circ apps), 2) how editing happens in inventory and WeCat, and how it varies depending on whether an inventory record is linked to an underlying MARC record or not. Go through examples and use cases, more practical than abstract.

Plans for post-MARC bibliographic data

Assuming we've got things organized well for MARC data by the time of WOLFcon, would it be worth discussing other bibliographic formats and brainstorming how we might see them interacting with Inventory and FOLIO? For example, what would be needed for FOLIO to ingest and work with metadata in Dublin Core or EAD format

Internationalization and Localization

Discuss and demonstrate translation efforts, as well as how FOLIO handles varying international requirements for dates, financials, so tha non-US FOLIO libraries understand how it can be localized to handle their special requirements

Authority records and FOLIO

Understand how FOLIO MARC cataloging, inventory, and codex will (or will not) interact with authority records for names, subjects. What if there are different authorized forms in different countries? What if a library has some local authority decisions that differ from national or international decisions?

Data migration process flow (whiteboard session)

Data mapping should be avoided, with preference for tools
ETL - we have large gaps, we have some transform tools for MARC, but need some for other data formats
We need a workflow for transforming data from our source systems to the the new FOLIO structure. This will be a change is data organization and data granularity.
Could be a 2- or 3-stage transformation workflow.
We will want to reuse where we can, but allow for customizations where needed.
Possibly a standardized staging database where data integrity and insertion of UUIDs can be handled. What does the ETL process look like in consortia?

Deployment and orchestration for production

One or two orchestration patterns that could be documented
Where can we standardize on common tools / encourage some standard tools?
Patterns for orchestration outside Okapi-managed deployment.

Data cleanup / Overview of data models

Install "hackathon"

Walkthrough of installation / architectural diagram presentation. Sharing experiences and tools.


Approach for comprehensive report repository, report templates

FOLIO Backlog & priorities
Secondary topic: cross-FOLIO apps/widgets

Better understanding of how development priorities are decided, especially across various functional areas. What is the impact of moving the backlog features into Jira? Is there a way to understand the overall priorities of the remaining FOLIO development work? How do libraries advocate for particular features, especially if they cross functional apps (like custom fields, change logs, bookmarks). Do we prehaps need a "universal (cross-app) feature" SIG? How do other dev groups know about useful little widgets that other dev groups have built, like the create/last update Stripes component used in instance/user? Can we create some sort of best practice to make cross-functional/helper/widget apps easier to install and more easily compatible with the main apps?


General discussion of tags in FOLIO, and work done on tags to date. While tags may not drive functionality, they will be essential for reporting. How will tags be used in the different apps? Let's walk through some use cases and examples.

Batch import app

FOLIO batch loading will not be app-specific. This session will attempt to answer the following questions:
- How will data be loaded into FOLIO?
- How will embedded MARC data be distributed into the Acquisitions and MM areas appropriately?
- How will objects in inventory be created?
- How will batch importing identify existing metadata and overlay and update it?