. What is the current thinking around item status (Emma presents some use cases and options) . 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? . What workflows haven't we discussed still that may impact item status? . How should item status(es) display in inventory, codex etc. . Prioritize and discuss remaining workflows and decide how best to handle
revised: . Review status requirements . Differentiate status (e.g., available), flag (e.g., damaged), and dynamically computed information (e.g., overdue) - feasible? . Test models against use cases & workflows for acquisitions, lost items, in-transit items . Test models against the idea of custom statuses - what challenges do each present?
. Goal: have model to recommend to SIGs, understand model's impact on current designs, have heuristics to draw on in the future for what should be a status
Defining relationships between distinct bibliographic entities that are connected. Present solution on how to represent these records types in Inventory. Review examples on real life records from Chalmers and GBV/hbz.
"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?"
"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."
"- Update on current thinking regarding MARCCat integration (Charlotte and Ann-Marie) - Does this make sense to everyone? - What are the next steps in terms of requirements, design and development?"
"- Review, discuss, and detail JIRA tickets supporting Data Lake development and document additional considerations - https://issues.folio.org/secure/RapidBoard.jspa?rapidView=32&selectedIssue=UXPROD-331&quickFilter=110 - Establish expectations for data lake reporting (i.e., what types of reports do we expect the data lake to support or not support?) - Document important features for data lake/warehouse design. Establish timeframe for standing up a Data Lake test environment - Outline and document dependencies for meeting this target - Approach for comprehensive report repository, report templates."
Transportation will be provided from the 21c Hotel at 530 and 600 via a Coach Bus. OR If arriving via Uber or LYFT - Drop off is at Chapel Circle - once looking at the chapel, enter the building on the left - West Union, proceed downstairs to the Devils Krafthouse
WCAG 2.0 AA is the goal for Folio. This session will review the Accessibility backlog, discuss implementation, priority, and status. Outcome: Designers/Developers/POs have an understanding of the work required for v1.
"Follow on from the Item Status Requirements Discussion on Tuesday
Should status states / options be controlled vocabularies / reference records?
FOLIO has a few examples of states (item status, loan status, request status) and options (loan policy profile, period interval) which are currently represented as enumerations (or free-text), should these be converted to references to controlled sets of records?"
"Present current state of stripes CLI: what can it do, how it works, and debugging (MattJ). Identify features to improve dev experience, use in CI, and future UI bundle service. Promoting CLI as a resource for new devs (perhaps this is part of dev documentation topic). Upkeep: How to best maintain/test reference templates to ensure they don't go stale. Testing: How much responsibility should the CLI take on of testing apps/components? We have many documents now, some of them well maintained and others out of date. There are some gaps, but maybe more urgent is the problem of how to find what you need. Some kind of overall structure may be overdue."
"What is the scope of localisation in the backend:
Do validation and error messages need translating before returning to the client? Do states / options need translating before returning to the client (how might the affect queries etc)?
i18n feature list - https://issues.folio.org/secure/RapidBoard.jspa?rapidView=32&projectKey=UXPROD&quickFilter=106 "
"The UM SIG defined an import mechanism that will overwrite any field where there is new data in the import. That said, if the import is silent on a field, any data that may have been manually entered in FOLIO will be left untouched.
The RA SIG (1) doesn't fully understand how import is working and (2) based on what they do understand, they think this might not be enough. Specifically, they are looking for the ability to protect fields from being overwritten by the import feed if data has been modified by hand in FOLIO. This needs more discussion.
A specific use case that might require this kind of protection relates to fulfillment options. See UXPROD-241 for details.
Agenda: - How does user import currently work? - Will the current implementation suffice? Let's look at UXPROD-241 as a potential unsupported use case - What, if anything, needs to change vis-a-vis user import and when?"
As discussed in https://issues.folio.org/browse/STRIPES-521 the front-end team need to figure out how "helper modules" like Notes and Tags best fit into the Stripes architecture. At present, Notes is merely a "smart component", but there are generalisations to be had here and conventions to be established.
"Folio apps are developed by a wide array of talented developers and UI designers. Our apps serve a variety of workflows. How can we ensure consistency across all apps? Discussion will focus on UI inconsistencies and discuss if/how we can reconcile. Outcome: alignment on the definition of consistency and process to address inconsistency. With more apps, there is a need for governance on updates to stripes components and testing of those components to support a consistent and stable UX. Outcome: Overview of stripes components testing, discuss questions related to changes to existing components and creating new ones."
Present requirements as currently understood, design options. This will be the first time the RA SIG has an opportunity to see the design options created in the sub-group.
"Current Status of Automated Testing. Opportunity for development teams to meet and discuss successes and challenges. Outcome: alignment on automated testing effort Current Status of Performance Testing: Opportunity for various groups focused on performance to meet and discuss successes and challenges. Outcome: alignment on automated testing effort."
"We've made good progress in providing GraphQL access to some back-end resources, and in integrating use of those resources via GraphQL client code -- and we will be much further along with this by the time of WOLFcon. It will then be useful to discuss how best to generalise the code that's been written across modules.
Possible outcomes: * Ideas for what client-side library support we might want beyond what React-Apollo gives us. * A way of auto-generating GraphQL schemas, on the server side, from RAML and/or JSON Schema. * Maybe a way of conveying the relevant information to the client side so it can auto-configure."
"- 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 "
Members of the Community Outreach SIG will present the SIG’s mission, the new logo and branding, the development process and timeline for the new website, and highlight the current tools and resources available to the community. Feedback and questions welcome!
"Clarity on how best to link schema together, how to position schema, using shared resources. Improved tools for assessment and validation (raml-cop, raml-tester, ajv, prettier, RMB). Improved API docs. Discuss and reach agreement on the design of Folio Edge APIs: coarse-grain APIs intended for integration to 3rd party applications. Conform non-Okapi protocols, data formats and conventions. Includes system-level API Management: security; data caps; policies etc..."
There are some WOLFCon session Thursday morning but for those who do not need to be in any of the other sessions, we will meet in Gallery 5 and have mini-meetings.
Chicago's experience with mapping holdings and item data up against the Inventory metadata elements (Instance/holdings/item). Review the migration based on the alpha implementation and the already identified 'missing elements' to see if there are any additional elements that need to be addressed.
"- Intro to user requirements for anonymization (UXPROD-271, UXPROD-447) (Emma) - Review implementation proposal via JIRA issues (Vince) - https://issues.folio.org/secure/RapidBoard.jspa?rapidView=32&quickFilter=111 - Plan next steps: who, how and when to begin development"
"- What would it mean to implement a consortium within a single tenant? - What would be the pros and cons of implementing a consortium as a single tenant vs multi-tenant? - Do we want to prioritize the work needed to support single-tenant consortia? May depend on discussion below. - What would need to change to make that possible? Would we need to scope/put limiters on: -- Users -- Permissions (e.g. should people only be able to edit calendars associated with a given service point or location?) -- Settings scoping (notifications, print slips, controlled vocabs etc - go through Settings and discuss all) -- Inventory/catalog scoping -- Funds -- Payments -- Consortial borrowing (may need a separate meeting for this) -- Etc. - What else would need to be considered? Review roadmap (consortia tab) "- What would it mean to implement a consortium within a single tenant? - What would be the pros and cons of implementing a consortium as a single tenant vs multi-tenant? - Do we want to prioritize the work needed to support single-tenant consortia? May depend on discussion below. - What would need to change to make that possible? Would we need to scope/put limiters on: -- Users -- Permissions (e.g. should people only be able to edit calendars associated with a given service point or location?) -- Settings scoping (notifications, print slips, controlled vocabs etc - go through Settings and discuss all) -- Inventory/catalog scoping -- Funds -- Payments -- Consortial borrowing (may need a separate meeting for this) -- Etc. - What else would need to be considered? Review roadmap (consortia tab) ""- What would it mean to implement a consortium within a single tenant? - What would be the pros and cons of implementing a consortium as a single tenant vs multi-tenant? - Do we want to prioritize the work needed to support single-tenant consortia? May depend on discussion below. - What would need to change to make that possible? Would we need to scope/put limiters on: -- Users -- Permissions (e.g. should people only be able to edit calendars associated with a given service point or location?) -- Settings scoping (notifications, print slips, controlled vocabs etc - go through Settings and discuss all) -- Inventory/catalog scoping -- Funds -- Payments -- Consortial borrowing (may need a separate meeting for this) -- Etc. - What else would need to be considered? Review roadmap (consortia tab) "- What would it mean to implement a consortium within a single tenant? - What would be the pros and cons of implementing a consortium as a single tenant vs multi-tenant? - Do we want to prioritize the work needed to support single-tenant consortia? May depend on discussion below. - What would need to change to make that possible? Would we need to scope/put limiters on: -- Users -- Permissions (e.g. should people only be able to edit calendars associated with a given service point or location?) -- Settings scoping (notifications, print slips, controlled vocabs etc - go through Settings and discuss all) -- Inventory/catalog scoping -- Funds -- Payments -- Consortial borrowing (may need a separate meeting for this) -- Etc. - What else would need to be considered? Review roadmap (consortia tab) "- What would it mean to implement a consortium within a single tenant? - What would be the pros and cons of implementing a consortium as a single tenant vs multi-tenant? - Do we want to prioritize the work needed to support single-tenant consortia? May depend on discussion below. - What would need to change to make that possible? Would we need to scope/put limiters on: -- Users -- Permissions (e.g. should people only be able to edit calendars associated with a given service point or location?) -- Settings scoping (notifications, print slips, controlled vocabs etc - go through Settings and discuss all) -- Inventory/catalog scoping -- Funds -- Payments -- Consortial borrowing (may need a separate meeting for this) -- Etc. - What else would need to be considered? Review roadmap (consortia tab) "
10:30 - 11:00 State of the Community (Mike)11:00 - 12:00 OLE Marketing (Ginny/Patrick)12:00 - 1:00 LUNCH1:00 - 2:00 FOLIO Experience Review (Facilitated by Mike & Ginny) 2:00 - 3:30 Discussion re: Gap Analysis (Sharon/Kirstin?)3:30 - 5:00 OLE Futures (Facilitated by Mike & Ginny)
Referential integrity encompasses both entity relationships within a single storage domain (such as the relationships within inventory between instances, items and holdings) and entity relationships accross storage domains (such as between patrons and items in the loan domain). Propose tests for establishing data integrity, e.g., as part of a load process. Discuss and document requirements to support cross-domain reporting. Approach for comprehensive report repository, report templates