2018-06-25 Resource Access Meeting Notes

Date

Jun 25, 2018

Attendees

• @Holly Mistlebauer

Goals

• Discuss Claims Returned workflow (continued from June 14, 2018)

Discussion items

Notes

 Khalilah: What fields in the user record should be protected when there is an import/data feed?

• Complete user record

• Patron address

• Email address

• Patron status

• User expiration date

• Patron group

  • Repeatable field w/ primary

• Barcode

• Fulfillment options

• Custom fields

  • Patron stat code – links patron to academic group (college major)

Can custom fields be searchable? Yes!

 Holly:

• According to transfer survey questions, need these abilities currently…

  • Transfer to bursar

  • Transfer to collections

  • Transfer to state (Germany)

  • Transfer to city (Germany)

  • We still need to finalize the transfer discussions, but it’s clear that we need to be able to identify that the fees/fines for an individual have been transferred to a specific place (e.g. Transferred Fully – Bursar, Transferred Partially – Collections).  We will produce an extract that can then be turned into the exact file needed by your institution—we can’t produce the exact extracts needed by each institution.

• According to tax/vat survey questions, no one collects vat or tax on fees/fines.  I will removed all references to tax/vat from the Manual Fees/Fines Table and Charge Manual Fees/Fines.  Alma had vat, which is why I added it—I thought that vat would be collected on things sold at a circ desk (e.g. thumb drives, blank disks).

• If we have the ability to waive a fee/fine at “go live”, can cancelling a fee/fine wait a quarter?

  • Cornell, Chicago, Lehigh could wait for up to a quarter for cancel.  Holly will update gap analysis.

  • Who requested the “Quick Paydown” feature?  Who would like to see it implemented?  No one at meeting claimed it.  Holly will email e-list.

Anya: Courses

Anya shared with us the progress her group has been making.  Her main goal was to see if they are going in the appropriate direction.  Overall, the group felt they were.  Some questions for clarification were discussed, including “item processing” statuses and how they fit with item statuses and request statuses.  We are not sure at this point how it all fits together.  Also not in their scope is how this fits with the discovery layer.  Also discussion about service desks and locations and their interactions.    It was agreed that there is still work to be done.  They will come back to the group when they have more to show us.

For supporting documentation:  https://folio-org.atlassian.net/wiki/pages/viewpage.action?pageId=2237280

Action items