2017-02-16 Resource Access Meeting Notes

Owned by Andrea Loigman
Last updated: Feb 16, 2017

Date

Attendees

Goals

  • Provide input to EBSCO and Index Data on Resource Access related needs/components for the first release of FOLIO

Discussion items

TimeItemWhoNotes
5minHousekeepingAndrea
  • note-taker
  • reminders - doc. reviews and sign-ups
55minFOLIO v.1Harry Kaplanian 

Notes:

 

2/16/17 Resource Access SIG Weekly Meeting Minutes


Email updates:


Cross module functions

Examples & User Stories of circulation / access services needing to do work in cataloging and acquisitions

https://docs.google.com/document/d/1M6MLGAUIHhRJTOLkekylY6WOeg8Di4RHkewc6q5Ic8w/edit?usp=sharing

 

Use cases for a workflow engine

Examples & User Stories of how a workflow engine would assist circulation / access services work

https://docs.google.com/document/d/1ljtk5VlEpAfz3kbWl-0p7Lll8exIgXOiOr6TpAC_PVA/edit?usp=sharing

 

These documents are also linked at the bottom of the wiki page at: https://folio-org.atlassian.net/wiki/display/RA/Circulation+components

 

 Meeting Attendees: Harry, Wendy Wilcox, Andrea Loigman, Cate Boerema, Charlotte Whitt, D. Bonner, David Larsen, Deb Lamb, Joanne Leary, Maria Grzeschniok, Mark Canney, Peter Murray, Rameka Barnes, Sharon Wiles-Young


FOLIO 2018 Release


https://docs.google.com/spreadsheets/d/1Yf81Xmfwj40gT_sd2AE5ZdiYeDmJp3W4No1X7fNOEYc/edit#gid=629121461


Provide override transaction capability.

  • Need override and permissioning capability in version 1.

  • Log the override (who did it)

  • Proxy status.  Is it a separate thing?  Don’t see how we could not have it in version 1.


Scan barcodes

  • Basic?  Obviously we need this functionality

  • Do we need RFID configuration? Library dependent.


Circulation statistics logging

  • At what point in time does this need to be severed statistics from the actual person that checked out the item?

  • Statistics should be stripped so personal identifiers should be removed.

  • Need to know everything about the transactions except the identifier.

  • Patron initiated scrubbing of transaction history?  Not necessary from day one.

  • This system should archive the data or provide a connection to a system that will.

  • Need to know who the person is at the time of the transaction (student statuses change all the time).  Preserve that status for that transaction in perpetuity.

  • Organizations using SSO


loan/return/renew/remove hold/in-house use

  • Reserve items -- do it all through APIs

  • Do we need a whole reserve system?

  • Loans and renewals queue up notices; needs to alter dates of notices; whole module of notification of notices that relate to loans and renewals

  • What needs an overdue notice, what needs a recall notice.  Timing is multiple times a day.  At the point that an item becomes available, do you want to notify the patron?  Do you want it delayed?  How long should it be delayed?  Overdue notices could be immediate.  The rest should be a scheduled process.  Log the fact that the notices are sent.

  • Tabler approach versus a batch approach.  Could be performance intensive to do an on-the-fly reading of loans.

  • Batch processes?  Most libraries would want to be able to add a delay because it takes awhile to shelve the materials.

  • Optional feature later is that some library systems have address this with a time delayed status.  “Check reshelving location.”  This is a reshelve item not a hold that would require a notice.


Place an item on reserve

  • Many libraries will use an external system

  • Must provide a connection

  • How soon could we get an external system to plug their system into Folio

  • Chicago will contract with Atlas to do this but we must have robust API’s

  • Change location, item type and status through API, we have all we need

  • The problem with Atlas’s functionality is that it is client based and not web-based

  • Will be reaching out to Atlas to determine

  • Database of record is in the reserve system; want to reflect changes in catalog

  • Need to do within FOLIO, need to be able to add a temporary location without removing the perm location.  Temp item type and temp item status and temp location.

  • Should be able to be done without a separate reserves module.

  • Needs to be above the line?  Is this true?  Temp item type and status must be above the line and integration with course system.  A separate reserve module could be later.

  • Do need a way to associate it with a course.  From day 1.  In the item record, need to be able to have a few fields to associate item with faculty member and a course.


Scheduling for fees and fines

  • Has to integrate with the calendar

  • 24 hour loan


Override and waive fines

  • Reduce a fine; waive it.  Not just deleting; need log

  • Permissioning is KEY

  • Chicago has complicated cash handling

  • Invoices and bills; payments for services and sales can be handled; ability to add a fee

  • Some defaults would be useful too; not just for dines


View and pay fines

  • Manage cash draw

  • Collapse fine information together (fine, payment inform; waive)

  • Sending to bursar?  Love to do automatically?

  • Review in SIG

  • Outward communication and internal function


Generating notices

  • SMS for notices?

  • Patron opt in

  • External vendors

  • Short term loans testing essential

  • System auto populate their calendars with due dates


NCIP

  • it will depend on which library goes first.  those are going to be the functions that will be first based on their other external stuff that Folio needs to integrate with

  • NCIP Is REQUIRED

  • Not convinced that a library cannot go live without NCIP

  • Single authentication is necessary


Printing slips

  • Prefer not spending much time on this


In transit

  • Seems straightforward


Holds and recalls

  • Required and we know that


Creating fines and refunds

  • Needs some reworking


Need to look at the below line items to vet if they are indeed NOT version 1 items.