FOLIO Sprint Review 54-55

  1. 0:00 Welcome; Core Team split into two groups: Core Platform and Core Functional
  2. 1:12 Core Platform Team Force membership update
  3. 2:00 Core Functional Force membership update
  4. 2:49 Stripes Force membership update
  5. 3:07 UNAM Team membership update
  6. 3:31 Q4 Release notes
  7. 4:37 Q1 2019 Release details
  8. 5:08 Definition of Done
  9. 10:23 teams’ sprint highlights slides
  10. 11:12 Acq-Orders demo
  11. 26:52 Folijet demo; file uploads, extensions
  12. 34:45 Stripes Force demo; UI filters
  13. 38:03 Vega demo; renewal overrides
  14. 44:31 UNAM demo; patron blocks
  15. 100:52 Core Functional Team demo; status views, notes
  16. 109:45 next sprints:
    1. Sprint 56 (January 28 – February 8)
    2. Sprint 57 (February 11 – February 22)
    3. 1:10:58 Plans for Coming Sprint(s)
    4. 1:10:19 Q4 QA Update – Bug Fest Week (1/7 – 1/11), Escaped Defects, UI Automated Testing, Performance slides


Principles in Action

Additional functionality: Once core functionality is established, improvements, and additional functionality can be explored and prioritized. 

As we start to see FOLIO coming to life, it’s natural to get excited about all the cool new things we can imagine: leveraging linked data, integrating with external systems, resource sharing, and more. Our principle regarding the importance of establishing core functionality reminds us to keep our eyes on the prize. Maintaining a manageable scope to the project is key to a successful implementation for early adopters. There will be time to innovate after go-live.

First Named release

Patrick Zinn, Director of Marketing, University Libraries at Texas A&M is the creator of the Bee logo for FOLIO. If you would like to know the history of the bee for FOLIO you can read this story posted by Patrick. “To bee or…Hey there is a Bee”. In the world of nature bees must be able to find plants and flowers to both pollantate and feed from in order to survive.  In the world of FOLIO we need librarians, developers, designers, and service providers to contribute to the community and to the project so that it matures into one of those products that is globally trusted and supported. The people that are active in the FOLIO community now can say, “we were there when….” One way to ensure the bees survival in nature is to plant wildflowers and when a FOLIO group started to think about what to start naming product releases the decision came easy, wildflowers are found everywhere and are needed for a health bee community. The very first named release is called Aster. All releases from now on will be named for wildflowers in ABC order.  If you would like to know what all was included in the Aster Release please click on the release notes.

Record Merge Working Group

The first meeting of the Five College record merge working group will be later in February.  This group will establish a charge based on some previous brainstorming. Some examples of the recommendations this working group has been asked to develop are:  What is the scope of records we want to include for de-duplication?

  • What local fields from each record needs to be included in a new record?
  • What record should be used as base for a new record?
  • What criteria should be used for matching?
  • Should this work be done in conjunction with another vendor? With EBSCO? In-House?

The members of the committee are Rebecca Henning (Amherst), Colin Van Alstine (Smith),  Jennifer Eustis (UMass), Sharon Domier (Five Colleges/UMass) and Steve Bischof (FIT)

How decisions are made: FIT Funnel

FIT Funnel for decision making
FIT Funnel for decision making

FIT has created a graphical representation — a funnel  — to help clarify roles and responsibilities and conceptualize decision-making. The funnel is specifically for the Five College beta testing and migration aspects of the project; we know that many staff are becoming involved with the open source FOLIO community and that is great! We are happy to encourage that as well. The funnel image outlines the responsibilities and expectations of staff participating in each part of the FC project and illustrates how recommendations, feedback, and decision-making will proceed.

Look for your local FIT member to be discussing the funnel at an upcoming institutional staff meeting.

FOLIO Sprint Review 52-53

  1. 0.00 Introduction/new team members
  2. 1:20 Q4 Release links, milestone dates
  3. 2:38 Q4 updates
  4. 5:13 File uploads demo
  5. 13:30 Acquisitions — vendor module enhancements
  6. 18:10 Password changes demo
  7. 28:30 Service points locations demo
  8. 37:45 User requests
  9. 39:00 Patron notices settings/templates
  10. 45:18 Inventory changes/additions
    1. Instance record
    2. Holdings record
    3. Item record
  11. 59:28 Stripes components storybook demo for UI modules — for developers
  12. 1:04:50 Hotkeys for users — shortcut keys demo
  13. 1:15:57 ERM demo
    1. license properties
    2. agreements
    3. eresources list
  14. 1:26:42 Sprint 54 — Three week sprint (December 24th-January 11th)
  15. 1:27:07 Q4 Release — January 14, 2019
  16. 1:27:18 Sprint 55 — Two week sprint (January 14 – January 25)
  17. 1:27:27 Plans for Coming Sprints

Aleph Advisory Group (AAG)

Successful system migrations include a preparation stage where data is cleaned. Correcting errors and aligning fields across the Five Colleges prior to moving to FOLIO will aide in a smooth data transfer. Further, clean data enables library staff to manage our resources so our patrons have an improved search and retrieval experience.

Aleph Advisory Group (AAG) is currently coordinating efforts across the Five Colleges to align bib/item formats, and to correct incorrectly assigned call number types.  We are also considering what data can be left behind (i.e. old patron records), This is a large effort that is starting to pick up steam! Do you have a suggestion for a data clean up project? Contact your local FIT or AAG representative.

Portugal Presentation

Kat Berry delivered a presentation at a FOLIO Day at the University of Lisbon, Portugal on November 30th. This FOLIO Day was very similar to the one we had at Hampshire College last October 2017. The presentation focused on how the Five Colleges made the decision to move to FOLIO and why we are adopting a single tenant model for our consortia.