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

FE: Display Bound with in the UI (Instance, holdings, item)

    XMLWordPrintable

Details

    • Very Small (VS) < 1day
    • Large < 10 days
    • Low
    • Prokopovych
    • 61
    • 131
    • Aligned PO rank with Calculated Total rank.
    • R4
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R2
    • R2
    • R1
    • R1
    • 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. Edit of bound with records
        • UXPROD-3080 Covers work the Sif development team (funded by GBV) will do. Scope: Nolana
        • UXPROD-3640 Covers work the Sif development team (funded by GBV) will do. Scope: Orchid

      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.

      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-1241 Back End work - BE: Analytical records; bound with - part 2: link multiple bibs to the same item
      2. UXPROD-3080 Prokopovych. Edit. Analytical records; bound with - part 2: link multiple bibs to the same item
      3. UXPROD-3640 Sif. Edit. Analytical records; bound with - 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

            blocks

            New Feature - New feature requests UXPROD-3080 Edit - first iteration. Analytical records; bound with - part 2: link multiple bibs to the same item

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-3640 Edit and delete - second iteration. Analytical records; bound with - part 2: link multiple bibs to the same item

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            has to be done before

            Task - A task that needs to be done. MODDATAIMP-529 Check schema updates for Inventory holdings and items

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Task - A task that needs to be done. MODDATAIMP-530 Update a bound-with instance, holdings, item to doublecheck

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open
            is blocked by

            New Feature - New feature requests UXPROD-1241 BE: Analytical records; bound with - part 2: link multiple bibs to the same item

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            is defined by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVSTOR-757 Add sample data for bound-with

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-1518 Item. Bound with. Display text bound with in top of Item record

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-1521 Item. Bound with. Add accordion at bottom of item record for linked instance information

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-1522 Item. Bound with. Display bound with icon in the item list (in the top of the instance record)

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-1523 Item. Bound with. Top heading with Instance, Holdings short description

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-1524 Result list. Bound with. Instance in the MCL list is marked with bound with icon

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-1533 Holdings accordion. Item detail list. Some items are a bound with, other items are not

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            relates to

            Task - A task that needs to be done. UIIN-327 Representation of analytics and bound with records. Design and technical decisions, part 2

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Closed

            Task - A task that needs to be done. UX-172 UX. Representation of analytics and bound with records in Inventory

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UXPROD-135 Analytical records; bound width - linking multiple instance records to a single holdings records (and the reverse, multiple holdings to a single instance record), part one

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-23 Requests: Search and Select Item on Request Screen

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open

            New Feature - New feature requests UXPROD-3174 Analyze Folijet support work for Inventory Bound-with feature (Data Import)

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Blocked
            mentioned in

            Page Loading...

            Page Loading...

            Page Loading...

            Activity

              People

                charlotte Charlotte Whitt
                charlotte Charlotte Whitt
                Charlotte Whitt Charlotte Whitt
                Votes:
                0 Vote for this issue
                Watchers:
                25 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases