2018-08-30 Resource Access Meeting Notes
Date
Aug 30, 2018
Attendees
@Andrea Loigman
@Emma Boettcher
@Joanne Leary
@Mark Canney
@Anya
@Sharon Wiles-Young
@Tania Hewes
@Wendy Wilcox
@Cheryl Malmborg
@Holly Mistlebauer
@David Bottorff
@Kimie Kester
@Rameka Barnes
@Cate Boerema (Deactivated)
@Darcy Branchini
@Jana Freytag
Discussion items
Time | Item | Who | Notes |
|---|---|---|---|
5 min | Housekeeping | @Andrea Loigman |
|
5 min | Staff/print slips | @Darcy Branchini |
|
15 min | Permissions for Loans | @Emma Boettcher |
|
45 min | Data elements review | @Emma Boettcher and @Cheryl Malmborg | vis-a-vis migration prep (to be continued Sept. 6) |
Notes
Tomorrow is first cross-SIG meeting about fast adds - requirements send an email to anya
Darcy - staff slips - if for v1 there was a second pop up print dialog box
alma printing is done via email -set up an email inbox server and third party software and automatically prints the email, not that slow at brandeis
cancel or confirm the checkin-confirming triggers the print dialog box
consensus is that this is not tolerable for v1
Darcy will talk with Brandeis about their option
Emma - permissions
what permissions have to be separated and distinguished?
ability to check in versus ability to check out - should be separate
view loan details but not view item details in inventory - no need to be separate, but opposite is not true - view item details but not loan details
check out - can they check in? can they renew? yes to both
renew - can they check in? can they renew? yes to both
view open loans can you check out, check in, renew?
Andrea-GDPR and need to separate actions (check out, check in, renew) with about a user (open loans, etc)
Wendy-a little confused by this approach, why not treat each permission granularly? Is this not more work than simply doing that?
Kate- we did go with this composite approach with User Management, but not necessarily
all in agreement that higher granularity is preferable to bundling
Cheryl and Emma - Data Migration
looking at each area like RA, how would data migrate from each system to FOLIO
what matches the loan JSON, where are the gaps?
would be helpful to have RA SIG folks or colleagues to review the document
Emma - are some of the gaps actually needed in the loan?
you would not want to propagate changes to a closed loan, and even some things (barcode, maybe location?) on open loans
David argues do not lock down location -need to move series, etc.
Thursday we will pick up where we left off with Emma