Holdings Source: add to Accordion Administrative data in details, edit

Description

Overview

Similarly to instances, holdings need to have sources defined for them in order to differentiate where the holdings record came from and how it can be maintained.

Further information
Further information about the context of these changes can be found in the following front end issues:

Scope

  • Maintenance of the set of holdings sources

  • Assign a source to a holding

  • Searching instances where a holdings exists with a specified source

Stories:

  1. Story

    • Log into FOLIO Snapshot, go to Inventory

    • Go to any holdings record in, drill down to the Administrative accordion

    • When viewing the data elements in Detailed view

    • Then a new data element labelled Source is displaced to the right of the Holdings HRID, as shown in the UX mock up of the detailed view of the holdings record:

  2. Story

    • When creating a new holdings record in Inventory, and the holdings record is not relying on an underlying MFHD record in SRS

    • Then the value of the source data element is auto-populated by creating of the record with the value FOLIO, as shown in the UX mock up of the edit view of the holdings record:

  3. Story

    • When the source is FOLIO

    • Then all data elements in the holdings record are editable in Inventory

  4. Story

    • When the holdings record is being maintained with an underlying MARC record in the MFHD format

    • Then the value of the source element is MARC

Out of scope:

  1. Blocking changes to holdings when the holdings source is MARC (see )

Environment

None

Potential Workaround

None

Attachments

3

Checklist

hide

TestRail: Results

Activity

Show:

Cate Boerema September 21, 2020 at 8:38 AM

it's great to see this In review! I am guessing it won't be possible for to test this until the UI portion is complete. Given that, I am going to unblock the blocked UI issues and I think we can just close this one as done ("In review" is the state we use for something that needs manual testing).

+

Ann-Marie Breaux September 17, 2020 at 2:38 PM

Hi Yes, R1 = Iris release. Here's a screenshot of my last features for Honeysuckle and first features for Iris, showing the fix versions (remember these values only apply to UXPROD stories, so they use the fix version field in a different way from MOD/UI issues)

Marc Johnson September 17, 2020 at 2:12 PM

I think the MARC holdings work will end up in R2 instead of R1

Are R1 and R2 the new names for the first and second releases of 2021?

Ann-Marie Breaux September 17, 2020 at 1:54 PM

It's fine by me to make it optional for now as well. I think the MARC holdings work will end up in R2 instead of R1. Once the MARC holdings work happens, I imagine we can say that if the source = [blank] or FOLIO, then do not control the Inventory Holdings via the SRS MARC Holdings. If the source = MARC, then control the Inventory holdings via the underlying SRS MARC holdings.

Charlotte Whitt September 17, 2020 at 10:48 AM
Edited

and - re.

Could it be acceptable to make the source optional initially?

It's fine by me – if this simplify the work here and now, and we at a later time can make it required (if needed by Data Import).

Done

Details

Assignee

Reporter

Tester Assignee

Labels

Priority

Story Points

Sprint

Development Team

Prokopovych

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created July 24, 2020 at 3:08 PM
Updated October 6, 2022 at 7:10 AM
Resolved September 21, 2020 at 9:13 AM
TestRail: Cases
TestRail: Runs