Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-1241

BE: Analytical records; bound with - part 2: link multiple bibs to the same item

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Epic Link:
    • Analysis Estimate:
      Very Small (VS) < 1day
    • Back End Estimate:
      XXXL: 30-45 days
    • Confidence factor:
      Low
    • Development Team:
      Thor
    • Calculated Total Rank:
      146
    • PO Rank:
      136
    • PO Ranking Note:
      Aligned PO rank with Calculated Total rank.
    • Cap Plan Fix Version (DO NOT CHANGE):
      R2 2021
    • Rank: Chalmers (Impl Aut 2019):
      R4
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R1
    • Rank: FLO (MVP Sum 2020):
      R1
    • Rank: GBV (MVP Sum 2020):
      R1
    • Rank: Grand Valley (Full Sum 2021):
      R1
    • Rank: hbz (TBD):
      R1
    • Rank: Hungary (MVP End 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R1
    • Rank: Leipzig (Full TBD):
      R1
    • Rank: MO State (MVP June 2020):
      R2
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: Trinity College (Jun 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R1

      Description

      CW - 12/18/2020 + 5/24/2021: I have split the original feature UXPROD-1241 into three:

      1. UXPROD-1241 will cover the Backend work done by development team Thor in R1 2021, funded by GBV.
      2. UXPROD-2855 covers the front end work - display in the UI. This work can begin when UXPROD-1241 is done
      3. UXPROD-3080 covers the front end work - edit of bound with records
        The libraries ranking are kept in sync for all three features.

      Goal/Problem: Need to link multiple instance records to the same item.
      Need to identify (clarify) which elements will be displayed in instance detail record for circulation screens.

      Design document:
      https://wiki.folio.org/display/MM/Bound-with+data+model

      Cataloguing format of
      1) Analytical records (= analyzed separate bibliographic records for a work published as a collection) and
      2) bound with records (= bound-with monographs are instances of two or more independent works)

      Use cases: If one title in a bound-with is checked-out; all other titles bound-with need to be shown as checked out.
      As a user I need to see accurate availability at the title level
      As circulation staff I need to be able to see what materials are checked out and to what user
      Cataloging staff need to see which titles are bound together; if looking at one title, need to know which other titles are bound with it

      Analytic record needs to reflect circulation status of analyzed title

      Data elements needed? [feedback needed from RA]

      Related features:

      1. UXPROD-2855 FE: Display Bound with in the UI (Instance, holdings, item)
      2. UXPROD-3080 Edit. Bound with in the UI (Instance, holdings, item) - part 2: link multiple bibs to the same item

      MM-SIG working groups specifications: Slide deck - https://docs.google.com/presentation/d/1CXD7K_b6sN6f9ZdKW0qRIYA7PLcsjucPMbRtJun2mCU/edit#slide=id.p

      Old documents:
      Source: https://discuss.folio.org/t/multipart-monographs/1347

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                charlotte Charlotte Whitt
                Reporter:
                charlotte Charlotte Whitt
                Analysis Estimator:
                Charlotte Whitt Charlotte Whitt
                Back End Estimator:
                Marc Johnson Marc Johnson
                Votes:
                0 Vote for this issue
                Watchers:
                23 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases