Versions Compared

Old Version 6

changes.mady.by.user Jana Freytag

Saved on

compared with

New Version Current

changes.mady.by.user Rameka Barnes

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

...

Cheryl Malmborg

Laurence Mini

mey

tpaige@umass.edu

Jana Freytag



Discussion Items

TimeItemWhoDescriptionGoals/Info/notes
2minAdministrivia

Jana Freytag

Upcoming National Holidays:

USA: Mon, 31st May

-- This meeting is cancelled

WOLFCon 21 lightning talks: 3rd June – See Programm

Announcements:

  • David Bottorff : Chicago shifts their implementation plans this summer from a full implementation to a ERM only Implementation

  • Erin Weller: Same for MSU - acquisitions and ERM going live in July but the rest, hoping for December

20MinDemo of UChicago's Pull List app

David Bottorff

Demo of UChicago's Pull List app (which creates unified pick list from ILS, Illiad, Relais, etc.) No hurry on this, but I know some folks were interested in seeing this as a possible model for something that could be developed on the FOLIO platform

David gave a demo of UChicago's Pull List app. It is set up by Library, includes Illiad, Relais, ILS, etc. 

Contact David or Tod Olson if interested or have additional questions about this.

30MinDiscussion of integration with online payment services

David Bottorff

Discussion of integration with online payment services

  • how many libraries currently offer online payment options? how many would like to do so?
  • what are libraries that offer online payment options doing now?
  • what would the priority be for FOLIO to integrate with online payment services?

Not many libraries reported currently having online payment systems.

Online payment system for Duke (Andrea): https://payments.library.duke.edu/

Online payment system TAMU (Rameka): https://library.tamu.edu/paymentinfo/

Jana will follow up with Holly to see what functionality FOLIO has for online payments. Will get Holly to come discuss with the group.

Meeting Outcomes

Functional Area

Product Owner

Planned Release (if known)

Decision Reached

Reasoning

Link to supporting materials

Comments

e.g. loans, fees/finesNamee.g. Q4 2018, Q1 2019Clearly stated decision
  • Because...
  • Because...
e.g. mock-up, JIRA issue