2019-08-14 User Management Meeting Notes

Meeting URL

https://zoom.us/j/488543197

Date

14 Aug 2019

Attendees

• Michelle Suranofsky
• (OLD ACCOUNT) Erin Nettifee
• patty.wanninger
• Kelly Drake
• Maura Byrne
• Todd Wallwork
• Uschi Klute
• Jana Freytag

Goals

Discussion items

Note taker - Erin

• First agenda item - what can we see in the MVP?
• Second agenda item - searching on umlauts / diacritics
• Third agenda item - deleting users.

=====

MVP - the report is coming out today. It is incumbent upon the project to visualize this for people. While MVP is being worked on, implementers are also doing exercise to visualize.

Patty says that the report should provide a list of current UXPRODs with quarter placement.

Example - Patty in Alabama talking about using scripts to do user load versus Banner integration. Bulk Loader has been used by Texas A&M, Alabama

On data migration wiki site — there's info on what was developed. A spreadsheet for testing is there - with a users tab - see who did what and what they used and how long it ook.

Patty - group talking about delta - how often do we load users? 

Could this be wrapped into the question about deletion?

First question - how does users support deletion right now?

Todd - we don't have the ability to do deletion user by user.

Patty - can we discuss how patron purges work?

Erin described how it works at Duke. Uschi described how it works at her institutions. Define script based on patron type, activity level, dependencies - then a test purge and review log file - and then do a real purge.

Patty - so can we write one feature — one story that would include purge script, and then one that would include deleting through the UI. Seems like there is consensus there.

A script that could handle deleting one patron would be an acceptable workaround for the GUI feature.

So - Patty - what about a constant loader? Something that would send updates when they happened. 

Michelle - Lehigh has an OLE webservice piece that does a database transaction.

So - Patty - is the API feature on FOLIO compliant to accept updates this way?

Patty - next week we are in Sweden to do rigorous bug testing and implement ERM for Chalmers.

Patty will follow up with questions about bulk loading — FOLIO should be able to support scripting – but we seem to be missing the U in the CRUD.

Patty - what happens when someone drops from a file?

Erin - describes at Duke

Todd - date comparison - we look at update of IDM file - you don't have a current update date, if that doesn't update then Voyager doesn't let you do anything. But they have a problem because self-check machines look at expiration date, not the way Voyager does it. 

Also Voyager doesn't allow bulk deletion of barcodes until patron is deleted.

Maura - one of the things they need at UChicago is the ability to override.

Erin - there is a Jira in there.

Jana - but if you make it inactive from the drop down, and expiration date is in future, it reverts to active. Is this a bug?

Jana and Patty- so what exactly does active / inactive do? 

Erin - there's no documentation unless there is something in Jira.

Patty - so what is the point of using inactive with an expiration date in the future?

• Uschi - example of patron losing a library card, and inactivating until card is found.

Patty - would people ever bulk load inactive users? 

Jana - yes, we will as part of the initial data migration.

Jana - maybe we should start a list of what we want. Jana will start a list in the wiki that people can add to. (here is the list: Active and Inactive Status)

Referenced resources

Custom fields presentation