2017-01-27 RM Notes

Attending:

• Kristin Martin (convener)
• D Ellen Bonner
• Former user (Deleted)
• Lynn Bailey
• Maria Grzeschniok
• Eric Hartnett
• Filip Jakobsen
• Marc Johnson
• Virginia Martin
• Kim Maxwell
• Peter McCracken
• Bill Verner
• Charlotte Whitt
• Kristen Wilson

Absent

• Martina Tumulla

Topic 1: Roadmap document

• Harry Kaplanian has been leading the effort to create a more detailed roadmap for the first release of FOLIO, due in 2018
• The roadmap draft can be seen here.
• Each tab attempts to list the necessary functionality for each major work area and note which items need to be in a v1 release.
• Harry is looking for a few members from each SIG to participate in a review call.
• RM reps will be Kristin M., Kristen W., Kim, and Peter.
• The group discussed a couple initial responses during the meeting:
  • Acquisitions, line 9, Create_Order API to receive new orders from Vendor: The group agreed that the ability to automate the creation of bib, order, and invoice records is essential for large libraries who already use this functionality to process approval programs and other high-volume programs.
  • Acquisitions, line 26, Order Transition Service: The group agreed that the ability to migrate open orders from a legacy system is also essential for implementation. Many libraries represented on the SIG have more than 10,000 open serial orders which cannot be migrated manually. 
• The review group will meet with Harry on Feb. 1

Topic 2: ER&L meeting

• Lynn is continuing to work with ER&L on logistics for the meeting.
• There are no to-dos for SIG members right now.

Topic 3: Updates from Filip

• Filip described his work as currently being in the thoughts/discussions/ideas stage. He is beginning to work on some sketches and prototypes, which should help the group find its direction.
• Filip has been meeting with Scott from Chicago about financial management.
• As his work progresses, he will begin reaching out to other SIG members for one-on-one conversations about the workflows and examples each person has shared.
• Initial thoughts about financial management:
  • The process will be fairly simple
  • Users will be able to see an overview of all funds or to interact with an individual fund
  • From each screen, they will be able to easily link into some reporting functionality that relates to the content they are currently looking at
• Initial thoughts about request functionality
  • Requests can come from a patron or staff member
  • Requests would tie into the knowledge base
  • There would be a dashboard with pending requests
  • Users can choose to place an order from the dashboard, select funds, choose tags, and then get an update on the status of the fund