Floating collection. Back end work.

Description

BACK END work:

The complete work with the UI as described in will be launched with the Sunflower Release.

Floating collection is defined as a group of items that are not housed permanently at a specific library, but are shelved at the library where they were most recently checked in. Floating collections are used to decrease transportation of items between libraries and to reduce manual handling, transit time, shipping expenses and/or traffic emissions.

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 for shelving.

If a book that is part of library A:s collection is checked out at library A, and then checked in at library B, it will not be returned to the shelves of library A, but instead, its new home is library B.

Current state:
Circulation in FOLIO does not support Floating Collections. Around 30% of Linköping University’s physical items are part of their floating collection. 65% of check outs come from items in the floating collection.

Problem:
If an item is checked in at a service point not assigned to the owning library location, the library can configure (at the collection or service point level) how the check in is handled: possibilities include automatically put in transit to owning library, set a temporary location, etc.

In scope:

  • Enable floating collections functionality for interested tenants.

  • Define floating collections for identified locations.

  • Functionality needs to work with check in/sorting machines to be useful, SIP2 work might be needed.

Out of scope:

  • Floating collection for consortia tenant (ECS)

Use case(s):
An item is checked in at a service point (manually or using a check-in machine).
When an item designated as floating located at Valla Library is checked in at Valla Library the item's library location doesn't change.
When an item designated as floating located at Valla Library is checked in at another library, such as the Norrköping Library, the system automatically changes the item's library, rather than putting the item in transit to the Valla Library. The item will now belong to the Norrköping Library until it is checked in at a different library.

Proposed solution/stories:

  • Settings page: Enable Floating Collection

  • Define Floating Collection by lowest location level, which in the records in Inventory will be reflected as the Holdings Permanent Location.

  • When item is returned by patron, to a different location as the Holdings permanent location, then the Item record is given a Item Temporary Location; which will be displayed in the Item effective location, and also searchable in Inventory Basic Search.

Links to additional info:

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

Priority

Fix versions

Development Team

Thor

Assignee

Solution Architect

Parent Field Value

None

Parent Status

None

Checklist

hide

Activity

Show:

Charlotte WhittFebruary 4, 2025 at 4:38 PM

- the Floating collection functionality is only visible if the environment varible is set to TRUE. So no need to have any Settings page - for now.

I doubt the current solution needs to be rewritten - when we get to do .

HkaplanianFebruary 4, 2025 at 2:15 PM

Some questions:

A large number of libraries are going to expect this to work with FOLIO’s consortia functionality. Will the settings page have a warning that this will not work in an ECS configuration?

I have not looked at the code, but someone will probably need to redesign and rewrite this feature to work with ECS since that was not taken into account. What will the impact be for libraries that have started using this feature? Are there plans to update this later for ECS?

The other option might be to build an “all new” version of this that works with ECS, so there will be 2 floating collection features for FOLIO?

Done

Details

Reporter

PO Rank

100

Analysis Estimate

Small < 3 days

Analysis Estimator

Front End Estimate

Out of scope

Front End Estimator

Back End Estimate

Medium < 5 days

Back End Estimator

Back-End Confidence factor

50%

Release

Ramsons (R2 2024)

Rank: FLO (MVP Sum 2020)

R4

Rank: 5Colleges (Full Jul 2021)

R5

Rank: Cornell (Full Sum 2021)

R5

Rank: Chalmers (Impl Aut 2019)

R2

Rank: GBV (MVP Sum 2020)

R4

Rank: hbz (TBD)

R4

Rank: Hungary (MVP End 2020)

R4

Rank: Linköping University (TBD)

R1

Rank: TAMU (MVP Jan 2021)

R5

Rank: Chicago (MVP Sum 2020)

R5

Rank: Leipzig (ERM Aut 2019)

R5

Rank: MO State (MVP June 2020)

R4

Rank: U of AL (MVP Oct 2020)

R5

Rank: Leipzig (Full TBD)

R1

Rank: Lehigh (MVP Summer 2020)

R4

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created October 30, 2024 at 7:35 PM
Updated February 27, 2025 at 1:16 PM
Resolved October 31, 2024 at 5:30 PM
TestRail: Cases
TestRail: Runs