2019-04-15 Meeting notes

 What do we want to get out of the face-to-face (+Zoom) meeting?

FOLIO working meeting 2019 planning document

Notes from last week:

Some possible goals/topics for the meeting include:

• A round robin of updates from each implementer
• Sharing experiences with installation, testing, mapping, etc.
• Sharing experiences related to data clean up
• Brainstorming ideas for areas that the group can help support
• Identifying tools, documentation, or procedures we can develop
• Identifying tools that can be reused across institutions
• Following up on the feature prioritization/gap analysis
• Setting up a pipeline from the SIGs to the Implementation Group

Agenda items for FOLIO Working Meeting:

• How we use the tools we mention below
• Lessons learned from institutions who have migrated recently
  • E.g. how much historical information do we need in different areas, such as historical cost information or circulation history
    • In some (many?) cases could park historical data in a reference database, will refer to less and less as time goes on
  • Data cleanup, are there common themes? Things we wish we had cleaned up?
  • How do we document what we are doing for future people looking back trying to understand what we did?

• What is different for a FOLIO open source implementation vs a vendor created and maintained ILS

• Documentation/ training audit - going forward for FOLIO, going backwards into what has been done in the current systems
• Follow up on outcome of Gap Analysis
• Merging data from different systems during migration
• Change management
  • changing workflow, questioning current processes and helping people be comfortable with the change
  • How many current processes are really workarounds
  • manage process to change item types, loan policies
• This group is uniquely situated to have the holistic view of the implementation. Not much communication between the SIGs, this group may need to be the glue between them. How do we organize
  • Does the app-interaction group do this? They are more at the level of features and necessarly app interactions and limited to RM, MM, purchasing, not the higher-level coordination
  • There is a role for an implementer's sandbox where we can work collaboratively, agree on common parameters, test in a coordinated way and report issues in common. So we're not always reporting problems separately.
  • This would be the holistic workflow testing group (or coordinating group)
    • see also Getting Started for Testers
    • Can share workflows and different approaches
  • Build community of staff across institutions for testing and share experience.

Share what tools your institution is using

• Issue tracking software
• Testing suite
• Project management software
• Internal Communication (newsletters, sharing of documents and which documents are shared broadly)
• How your institution handles Project Management (PM Office? Specific PM leaders? How are decisions made?)