|
Current situation or problem:
A location can be marked as active or inactive. As of Kiwi, there are no additional workflows that depend on that status. (A pop-up modal can appear when assigning an inventory record to an inactive location, but that's it.)
For the purposes of managing locations, libraries would like to have more functionality driven by the active versus inactive field to facilitate collection management.
- A way to designate locations that are inactive but still have work happening, versus locations that are inactive and the associated records are essentially archived/deprecated
- Inactive but work happening - maybe a new location that things are being put into by tech services, but isn't "ready " for normal location workflows. Or, location being used for housing items during a library renovation.
- Archived/deprecated - an old collection, items completely withdrawn, but records need to be retained. E.g., this location should never be used anymore.
Some possible new functionality includes
- Allow a library the configuration option for extracts for discovery layers to say that only holdings and items at active locations should be extracted for discovery
- Allow a library the configuration option to say that for Inventory search, only holdings and items that are assigned to active locations are returned in search results
- Allow a library the option to say that a particular location should *never *have new holdings / items assigned to that location. (e.g., allow a PUT for the record, but not a POST).
- Allow a library the option to choose not to display inactive locations in location search filters
In scope
Out of scope
Use case(s)
- A library can have a collection that has been completely withdrawn - they don't circulate the items any more, they aren't adding new items to the collection. The records need to be retained, but they want to prevent new items from being accidentally added to it.
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?
- Completely withdrawn collections
- A location that's used as a holding / processing space - like during renovations
=======
Discussed at MM SIG on 2-17-2022. https://folio-org.atlassian.net/wiki/display/MM/Metadata+Management+SIG
- A way to designate locations that are inactive but still have work happening, versus locations that are inactive and the associated records are essentially archived/deprecated
- Inactive but work happening - maybe a new location that things are being put into by tech services, but isn't "ready " for normal location workflows. Or, location being used for housing items during a library renovation.
- Archived/deprecated - an old collection, items completely withdrawn, but records need to be retained. E.g., this location should never be used anymore.
|