Consortia (Cross Tenant) (UXPROD-794)

[UXPROD-816] If item is returned at non-owning library location, library can configure (at the collection or service point level) how the return is handled: possibilities include automatically put in transit to owning library, set a temporary location, etc. Created: 05/Jun/18  Updated: 13/Mar/23

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Consortia (Cross Tenant)

Type: New Feature Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: suppress-from-capplan
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Requires
is required by UXPROD-795 Patrons can borrow/request/hold/recal... Open
Epic Link: Consortia (Cross Tenant)
Development Team: None
Kiwi Planning Points (DO NOT CHANGE): 20
Rank: Chalmers (Impl Aut 2019): R2
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R5
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R5
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R4
Rank: hbz (TBD): R4
Rank: Hungary (MVP End 2020): R4
Rank: Lehigh (MVP Summer 2020): R4
Rank: Leipzig (Full TBD): R1
Rank: Leipzig (ERM Aut 2019): R5
Rank: Linköping University (TBD): R1
Rank: MO State (MVP June 2020): R4
Rank: TAMU (MVP Jan 2021): R5
Rank: U of AL (MVP Oct 2020): R5

 Description   

Description:
If item is returned at non-owning library location, library can configure (at the collection or service point level) how the return is handled: possibilities include automatically put in transit to owning library, set a temporary location, etc.

Notes:
in transit is critical functionality, floating/temp locations less, choosing is low priority.

 

Keywords: Floating collections, floating collection

****************

New text - TBD with Linköping:

Description:
A floating collection is a group of items that are not housed permanently at a specific library, but belong to whichever library has most recently checked in the the item. Using a floating collection will reduce transit time or shipping expenses if sites do not want to move these materials between libraries. Typical examples of floating collections include paperbacks and videos.
For an item that is part of a floating collection, the item's library is changed whenever the item is checked in at a different library. The item belongs to whichever library last checked it in.
Floating collection is defined by libraries which are part of the single tenant / consortia tenant?

Current state:
Circulation in FOLIO does not support Floating Collections

Problem:
If item is returned at non-owning library location, library can configure (at the collection or service point level) how the return is handled: possibilities include automatically put in transit to owning library, set a temporary location, etc.

In scope:

Out of scope:

Use case(s):
As a circulation staff at the circ desk,
I can check in an item designated as floating at library of Valla UB. The item's library location doesn't change as long as the item is only checked out and returned to the Valla UB.
The first time the item is returned to another library, such as the Norrköbing UB, the system automatically changes the item's library, rather than putting the item in transit to the Valla UB.
The item will now belong to the Norrköbing UB until the next time it is returned to a different library.

Note: If the item needs to go to a specific library to fill a hold, the hold takes precedence over the floating collection setting, and the item is routed to fill the hold.

Proposed solution/stories:
Settings page: Enable Floating Collection
Set Floating Collection on all level of locations (to be inherited)?
Set Floating collection on material types
Set Floating collection on item level?

Links to additional info:
Sirsi: FAQs: Handling Floating Collections (byu.edu)

Slidedeck (WIP): https://docs.google.com/presentation/d/1YwEdifzpjN8Z7_eDSqvKDgiQWtDPTkEZh0o3rddJgbw/edit#slide=id.p



 Comments   
Comment by Theodor Tolstoy (One-Group.se) [ 23/Feb/21 ]

Kelly Drake I added a keyword here because this Jira did not show up when searching for floating collections

Comment by Kelly Drake [ 23/Feb/21 ]

Thanks Theodor Tolstoy (One-Group.se) - is work being planned on floating collections?

Comment by Theodor Tolstoy (One-Group.se) [ 23/Feb/21 ]

I have no idea Kelly Drake . I know many libraries interested in FOLIO that heavily rely on it. Looking at the ranking does not make it seem to happen very soon

Comment by Eva Sejmyr [ 26/Apr/21 ]

This is our definition of floating collections:
When a book, which is a part of a floating collection is checked in, it will not be prompted for transit to the owning library but stay at the library/branch where it was checked in. So if a book that is part of library A:s collection is checked out at library A, and then returned to library B, it will not be returned to the shelves of library A, but instead, its new home is library B.  Is this what you mean by UXPROD-816 Open ?

We have used floating collections for many years for sustainability reasons. It helps us reduce transport emissions and unnecessary handling for staff.

We need to be able to specify which material types and/or locations are part of the floating collections.

Comment by Jana Freytag [ 03/Mar/23 ]

This feature might relate to https://folio-org.atlassian.net/browse/UXPROD-2877 ´Refuse check-in if item is not at primary service point for home location` and some German libraries yould be very interested in this.

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