Map shelving order property for items

RCA Group

None

Description

Purpose

Allow for items (that have LC call numbers) to be sorted by shelving order (based upon call number and related fields)

Context

Refer to https://folio-org.atlassian.net/browse/UIIN-816#icft=UIIN-816 for how this field will be presented.

Scope

  1. Introduce a new property for the shelving order in the business logic representation of items (the definition should be read only)

  2. When this is provided by the storage API, map it to the

  3. It does not need to be mapped when provided by the client as the storage system always overwrites this property

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Marc JohnsonNovember 7, 2019 at 3:22 PM

As it was decided that derived properties should be done in storage modules, this story only involves propagating the new property from storage through the business logic module.

I will update the description of https://folio-org.atlassian.net/browse/MODINVSTOR-381#icft=MODINVSTOR-381 to clarify the scope.

Laura E DanielsOctober 22, 2019 at 4:41 PM

Agree that item-level sorting is the most important at this point.

Cate BoeremaOctober 22, 2019 at 3:48 PM

Thanks . I created https://folio-org.atlassian.net/browse/MODINV-168#icft=MODINV-168 for storing call number sort code for items. I assume item-level sorting is the most important at this point. should correct me if I'm mistaken.

I will ask the call number subgroup if they want to display the call number sort code on the item record (it seems like it would be useful from a testing perspective).

I will also ask them where they want to be able to sort by call number in FOLIO

Marc JohnsonOctober 22, 2019 at 2:43 PM
Edited

are the mod-inventory-storage stories in addition to the mod-inventory stories? So, for example, for normalized call number at the item level, would we need two stories

For the sortable call number on items, we will need two stories, if we are also intending to present this field on the UI

For holdings, we only need a story for mod-inventory-storage because there is no business logic pass through.

When we come to actually performing the sorting, we may need to clarify what field is actually being used. Is the sorting to be done in the inventory UI? If so, this presents a list of instances, which don't have a call number themselves.

Cate BoeremaOctober 22, 2019 at 9:35 AM

Would it be easier to create the story for displaying normalized call number on holdings? I assume we'll want to look at both holdings and item call number sorts.

how important is sorting holdings by call number? I thought most of the sorting would be done on items on pages like Loans.

If we are intending to do this for both the holdings record and items, we likely need two stories in mod-inventory-storage for storing the derived fields. And this work would need to be done before the presentation of them in the UI

are the mod-inventory-storage stories in addition to the mod-inventory stories? So, for example, for normalized call number at the item level, would we need two stories such as:

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Prokopovych

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created September 11, 2019 at 12:22 PM
Updated March 1, 2021 at 1:16 PM
Resolved March 1, 2021 at 1:16 PM
TestRail: Cases
TestRail: Runs

Flag notifications