Locations and Service Points (UXPROD-771)

[UXPROD-3561] Add "Inactive" to location FOLIO name when location is marked as inactive (filter functionality) Created: 14/Feb/22  Updated: 30/Nov/23

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

Type: New Feature Priority: TBD
Reporter: Erin Nettifee Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File a-inactive.png     PNG File b-inactive.png     PNG File c-inactive.png     PNG File screenshot-1.png    
Issue links:
Defines
is defined by UIIN-1967 If location is Inactive, prepend Inac... Open
is defined by STSMACOM-641 If location is inactive, prepend "Ina... In Refinement
Issue split
split to UXPROD-3807 Add "Inactive" to location FOLIO name... Closed
Relates
relates to UIIN-1290 Allow the selection of remote storage... Closed
relates to UXPROD-3526 Warn when assigning a course to an in... In Refinement
relates to UXPROD-3527 Warn when assigning a course reserve ... In Refinement
relates to UXPROD-3568 Additional functionality for Inactive... Draft
Epic Link: Locations and Service Points
Development Team: None
PO Rank: 0
Rank: Cornell (Full Sum 2021): R3

 Description   

Current situation or problem:

A location can be marked as active or inactive. Currently, there is only one workflow that is triggered if a location is inactive - when you are creating or editing a holding or item, when you choose an inactive location, you receive a warning message, but you are allowed to proceed.

It is not obvious when viewing a location in a filter that it is inactive - the pop-up is the only warning.

To facilitate cleaner workflows, we'd like for the following to happen when a location is inactive:

 

Filters (including edit view)

  • For the Instance pane, in the Effective location (item) filter, if a location appears in the facet list, pre-pend the name with "Inactive" ( UIIN-1967 Open )
  • For the Holdings and Items panes, in the Effective location (item) filter and Holdings permanent location filter, if a location appears in the facet list, pre-pend the name with "Inactive" ( UIIN-1967 Open )
  • When editing a holding, and editing a location value, and clicking the location filter to view the list of available locations, if a location is inactive, prepend "Inactive" to the location name ( STSMACOM-641 In Refinement )
  • When editing an item, and editing a location value, and clicking the location filter to view the list of available locations, if a location is inactive, prepend "Inactive" to the location name ( STSMACOM-641 In Refinement )
  • If a location is inactive, on any location search where a list of location appears, push the list of inactive locations to the bottom.

Viewing records - split to UXPROD-3807 Closed

The word "Inactive", wherever it appears, should be translatable to the session and/or tenant locale.

In scope

Out of scope

Use case(s)

Proposed solution/stories

Links to additional info

Questions

  • What use cases exist for allowing assignment to an inactive location, with warning?
  • What use cases exist for never allowing assignment to an inactive location?
    • When orders are attached to the record. You don't want the location to change after the fact.
  • Currently, inactive locations show up in filters in Inventory search. Should that continue?
  • Suppose we did not allow assignment of a record to an inactive location, and you have location X that has been active and assigned to multiple records, and you make location X inactive. If you then go into the record with location X and want to make changes to it, what is the desired behavior?
    • E.g., currently in FOLIO Inventory, when you edit a field on a record, it is sent back to FOLIO as a PUT request with the entire record. So editing a record with an inactive location results in an attempt to save the record with the inactive location even if that's not the field that's being edited.
  • Is it possible for a record with an inactive location to be managed such that a PUT is allowed, but a POST is not?

=======

Discussed at MM SIG on 2-17-2022. https://folio-org.atlassian.net/wiki/display/MM/Metadata+Management+SIG

2 desired pieces of functionality - this ticket and UXPROD-3568 Draft .



 Comments   
Comment by Erin Nettifee [ 22/Feb/22 ]

Kimie Kester prepped some options for consideration that I attached to this feature - (A, B, C) and I am asking the metadata management channel for any reactions.

Comment by Erin Nettifee [ 22/Mar/22 ]

The SIG opted for (B), but I am removing the suggested changes to the remote label, since I don't really think that needs to change and it's outside the scope of addressing the main issues with inactive locations that are part of this feature.

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