Locations and Service Points (UXPROD-771)

[UXPROD-1562] Mark Service Point Inactive Created: 06/Mar/19  Updated: 15/Aug/23

Status: In Refinement
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Locations and Service Points

Type: New Feature Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Erin Nettifee
Resolution: Unresolved Votes: 0
Labels: round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by UITEN-204 If service point is inactive, prepend... Open
is defined by UITEN-205 Warn when making a service point inac... Open
is defined by UICAL-198 If associated service point is inacti... In Refinement
is defined by UITEN-206 Warn when making a service point inac... In Refinement
is defined by UITEN-207 Warn when making a service point inac... In Refinement
is defined by UITEN-208 Warn when making a service point inac... In Refinement
is defined by UIU-2539 If service point is inactive, prepend... In Refinement
Relates
relates to UITEN-212 Permission changes for service point ... Open
Potential Workaround: Cate Boerema: Have IT person delete via api endpoint (only if you are certain the service point has not been used anywhere)
Epic Link: Locations and Service Points
Kiwi Planning Points (DO NOT CHANGE): 2
PO Rank: 42
PO Ranking Note: 2020-10-04 - CB: Making my PO rank same as the calculated total rank for now.
2019-07-12: Keeping PO rank same as calculated rank (with potential minor adjustments to avoid having two features with same rank)
Rank: BNCF (MVP Feb 2020): R1
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R4
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R4
Rank: hbz (TBD): R4
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R4
Rank: MO State (MVP June 2020): R3
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R4

 Description   

Current situation or problem:

If a service point (SP) is no longer in use, we need a way to get it out of the various service point menus (e.g. on user and request records). Deleting SPs is challenging because of the various dependencies on records if the service point has been used for any loans, requests or fines. Instead, the path forward should be to mark a service point as "Inactive"

In scope

  • Append (Inactive) to beginning of the name of the Service point in the list of service points in Settings > Tenant ( UITEN-204 Open )
  • Add a field to service point form for active/inactive (maybe display between description and shelving lag time)
  • Warn if a FOLIO user is marking a service point inactive, but the service point has locations associated with it ( UITEN-205 Open )
  • calendars and future loans ( UICAL-198 In Refinement )
  • modifications to the service point API to expose the active/inactive value (backend ticket, to be written by development team)
  • Changes to the ui-servicepoints handler module so that inactive service points are

Out of scope

  • New permissions to make a service point inactive; if you can edit a service point, you can make it active or inactive. Given that

Use case(s)

  • A library closes a building, there is an organizational restructure, or they no longer have funding to keep a particular service point open
  • A service point needs to close temporarily due to pandemic response;
  • Closing a pickup location long-term (as opposed to just temporarily turning it off as a pick-up location)

Proposed solution/stories

Links to additional info

Questions

UI pieces needed

  • calendars and future loans ( UICAL-198 In Refinement )
    • all future due dates for a loan are calculated based on the calendar for the originating loan service point
    • so after a service point is deactivated, it still needs to be a visible calendar and still have dates visible in the UI, since you'd need to be able to continue to update the calendar until all of the associated loans to that service point are closed
  • fee/fines ( UIU-2539 In Refinement )
    • owners have associated service points
    • when a service point is deactivated, it should still remain attached to whatever fee-fine owner it was attached to - but label could have Inactive on it
    • libraries could then decide to remove the service point later on if desired (not sure what ramifications would be)
  • pickupLocation = yes ( UITEN-206 In Refinement )
    • Warn, but allow - wanted because you may be in scenario where you need to shut down quickly, then clean up after.
    • Libraries would need to check that no open requests were associated to the service point as a pickup location - so it's a documentation question
  • user preferred pickup location ( UITEN-207 In Refinement )
    • Warn, but allow
    • May need additional workflow to stop a request from being routed there for a new request? Or should an inactive service point immediately drop out of a pickup list?
  • Associated as a pickup location to a request (open or closed) ( UITEN-208 In Refinement )
    • Warn but allow - you may be in scenario where you need to shut down quickly then clean up after the fact
  • Assigned to a FOLIO staff user record
    • Warn, but allow

Questions

  • Given the logic checks that need to happen, is it better to add a field to the record and have a dropdown to choose active or inactive, or it is better to add a action menu option? (Similar to deletion)
  • If a service point is the primary service point to one or more active locations, what should happen when you want to make it inactive? 
  • If a service point is the primary service point to one or more inactive locations, what should happen when you want to make it inactive?
  • If a service point is configured to be a pickup location, should it be allowed to be made inactive, or should you be forced to make it not a pickup location first?
  • If a service point is associated to a user record for a FOLIO user (Service points accordion) what should happen when the service point is made inactive?
  • If a service point is associated to a user record for a FOLIO user as a preferred pickup location, what should happen when the service point is made inactive?
  • If a service point is associated as a pickup location to one or more open requests, what should happen when you want to make the service point inactive?
  • If a service point is associated as a pickup location to one or more closed requests, what should happen when you want to make the service point inactive?
  • If a FOLIO user is logged into an active FOLIO session at an active service point, and you make the service point inactive while the FOLIO user is logged in, what should happen?

Additional development

  • Users drop-downs changed so that you could only assign service points that are active to FOLIO users -
  • Users drop-downs changed so that you can only assign active service points as pickup locations - https://folio-org.atlassian.net/browse/UIU-2509
  • Changes to the ui-servicepoints handler module
  • Requests drop-downs change so that you aren't able to assign an inactive service point to an active request
  • NOT changing requests UI filter because you'd still want to be able to filter and find old requests

Discussion
Discussed at SIG Meeting 2019-01-17 and SIG Meeting 2-24-2022
Slide deck with discussion notes for 2-24-2022 - https://docs.google.com/presentation/d/1t1aYm16i0LeQ_qM9uVvgUZILtThmQwAnsi4K2dxdEwY/edit?usp=sharing


Generated at Fri Feb 09 00:16:35 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.