Versions Compared

Old Version 2

changes.mady.by.user Kelly Drake

Saved on

compared with

New Version Current

changes.mady.by.user Martina Schildt

Saved on

Key

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

Date

Attendees

Goals

Discussion items

TimeItemWhoNotes
Announcements: Chicago is looking at Circ-only implementation, maybe for Round III.  Tod will start on a requirements list.40 min

Settings, reference data and finance show and tell, focused on each library (Simmons, Lehigh, Missouri St, Chalmers) for 10 minutes each

questions and discussion

Kelly Drake
  • Chalmers doesn't use finance at all in FOLIO
  • Lehigh has tested creating an order but still not sure what's working and what isn't, MSU also hasn't gotten very far
  • Kristen talked about the Finance settings for Simmons (based on Edelweiss):
    • using default list
    • using only two fund types (monographs & subscriptions)
    • using a fund spreadsheet now to figure out how their FOLIO fund structure should look (34 funds)
    • set up groups for tracking - these are created by each institution.  Groups don't have funds but show summaries of their associated funds
    • noting which funds can allow transfers to and from - they tested a transfer and it worked
    • won't be using vouchers so not setting up any external account info
  • Nobody else has tested these much
  • Questions about how encumbrances will work, more dev work on this expected in Fameflower & Goldenrod
  • Fund: lives over time over multiple fiscal years; budget is for a single FY
  • A feature that might be useful from some libraries (Simmons & MSU) would be to encumber against future budgets - due to their university accounting requirements
  • Funds/Allocations: everything will be in the default currency your institution selects (also controls fines & fees)
  • Simmons monograph order process: 
    • Preferred process is to create PO with bib stub, overlay with full MARC later (can't do that now)
    • Create PO; required fields (vendor, order type, acq unit)
    • Then create PO line, Simmons will put in inventory record in at time of order
    • Can create templates with pre-populated fields
    • Bill To/Ship To: not so important if vendor order imported but needed if actually sending out the order
    • Re-encumber: relates to ongoing orders
    • "Manual" - nobody sure what that means (ask Dennis next week)
    • Product ID: ISBN, etc.  OCLC# wouldn't go here because it's a record number
    • Updates & overlays will be worked on in Goldenrod
We'll look at orders more in-depth next week

Housekeeping

Kelly Drake

Assign notetaker: Tod Olson

New attendee: Robert Scheier from Holy Cross, in talks with EBSCO about moving to FOLIO. Welcome!


COVID-19 effects on FOLIO

Catching up on how sites are changing work for the pandemic, and how that may affect work on FOLIO.

For those who might have more time available as a result, what way can we help the project? 


App Interaction and Tenant cross-functionality

Martina Schildt

In consortial multi-tenant settings, there are different policies about what data tenants are allowed to see, share data. E.g. some might share patrons but not invoices. Or might be able to see orders at their partners. There are a number of use cases laid out in Permissions & restrictions in FOLIO.
There is a request for libraries in single tenant or shared data situations to document how data is partitioned or shared, either in your current system or as you see potentially in FOLIO. Please share any diagrams or documents in the Sample Data folder under Resource Management > App interaction. Deadline is March 20th.
Early implementing libraries are asked to talk through their setups in an App Interaction session for App Interaction to come up with a set of requirements to be shared with the TC.




Action items

  •