2022-02-24 Resource Access Meeting Notes


Date


Zoom

https://zoom.us/j/337279319 (pw: folio-lsp)

Attendees

Thomas Trutt 

(OLD ACCOUNT) Erin Nettifee 

Brooks Travis 

Martina Tumulla 

Sharon Wiles-Young 

julie.bickle 

Dwayne Swigert 

Christine Tobias 

Andy Horbal 

David Bottorff 

Laszlo Jakusovszky 

Natalia Umaña 

Mark Canney 

Cornelia Awenius 

Nicole Daly 

Erin Weller 

Laurence Mini 

Cheryl Malmborg 

Pamela Pfeiffer 

Karen White 

Robert Scheier 

Heather MacFarlane (Deactivated) 

Kimie Kester 

Joanne Leary 

Molly Driscoll 

mey 

tpaige@umass.edu 

Kara Hart 

Jana Freytag 

Discussion Items

TimeItemWhoDescriptionGoals/Info/notes
2minAdministrivia

PC-Update:

  • New recording storage
    • recordings.openlibraryfoundation.org
    • For how long do we want to keep the meetings?
    • Keep the Recordings longer and make special recordings (like the presentation on permissions better available)
    • Jana will set up a page in our wiki space to provide better access to our recordings and make them searchable
30MinMaking service points inactive(OLD ACCOUNT) Erin Nettifee 

Discuss  UXPROD-1562 - Getting issue details... STATUS  







Meeting Notes


  1. Making service points inactive
    1. Look at what SP are
    2. Deletion via UI Call
    3. Q: Under what scenarios would you imagine deactivating a service point, and then reactivating it in the future?

      1. extremes: closed Building, Staffing issues,
      2. Andy in Chat: We have one inactive service point right now which we might reactivate in the future. (space issues in the sp)

      3. Christine in Chat: When we close/retire a branch location. Or if temporarily close a branch library/service point due to pandemic protocols. Or God forbid, a disaster occurs and the library is no longer open (i.e., fire, flood, etc.)
      4. Thomas in Chat: suspension of services; for use contactless pickup
      5. Brooks in Chat: “Virtual” service points, as well.
      6. Discovery layer: turning off the Pick up location (permanently or temporarly)
      7. for staff to select it as a preferred pick up 
    4. Scenarios: Permission for deactivating a sp but nothing else?
      1. protect the crud permission but not
      2. Thomas: i kind of like the action menu idea better, but activate/deactivate instead of delete

    5. Assigned to an Active Location:
      1. Thomas, David, Christine,  in Chat: Option 1
      2. Thomas in Chat: could we do option one but add a dialog asking what service point the locations should be change to..??

        1. context: catalogouging work flows
    6. pickupLocation = yes?
      1. Renovation: What if staff are working in the space?
      2. How much time would you have to know that a sp would be deactivated
      3. Option1: becomes nicer including bulk edit of requests
      4. Option2: would allow to stop requests comming in
      5. For stopping request comming in by switching pickup location:
      6. result: Option 2 would be preferred
    7. Associated to a user as apreferred pickup location
      1. Option 3(proposed by Brooks): On this next one, I would allow without warning, and just have Requests and any patron-facing interfaces ignore the preference if the location is inactive
    8. Associates as a pickup location to a request
      1. Brooks in Chat: I think it has to be #2 Same as turning off pickupLocation=Yes
      2. What about closed request? let them stay
      3. Brooks in Chat: Again, it would be great if we could bulk update the requests via the UI at that point
    9. Associated to a FOLIO staff user record
      1. Option 2:
      2. Andy Horbal in Chat:  Have we talked about what, if anything, happens to the name of the service point when it is inactivated?

      3. Brooks Travis in Chat: Warn but allow, and update the front-end to ignore those SPs in service point assignment/selection.

      4. Andy in Chat: Under our improvised solution, the service point appears as INACTIVE Service Point A on the User record, which actually works pretty well.
    10. Anything else?:
      1. Joanne: What happens to fee/fines logic ex.: what happens to a book if the location associated with a fee/fine owner is deactivated?
      2. Cheryl: Calendar is also associated with location - What happens with this connection?
      3. Brooks in Chat: I would argue for updating the circulation back-ends to deny transactions from inactive service points

      4. Brooks in Chat: All future due dates are calculated based on the originating service point calendar - Renewals, recalls, etc.
  2. Unable to Place Recalls via Instance Hold Endpoint (/circulation/requests/instances) When Item is Checked out with a Fixed Due Date Schedule -- CIRC-1449

    1. Please be aware of this and that it is a
    2. Brooks: My biggest question to the group is how widespread do we think the use of fixed due date schedules is where the institution also allows patron-initiated recalls.

    3. Regarding: rolling loan periods with a fixed due date schedules
    4. How critical is it?
      1. Andrea: Would affect Duke but implementing the invisible Permissions is acceptable
      2. Others agree - Andy in Chat summarized it: it's never an IDEAL solution, but so far I think it has always turned out to be one that gets the job done.