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

A process is needed to periodically refresh the record against the source (Knowledge base)

    XMLWordPrintable

    Details

    • Template:
    • Epic Link:
    • Analysis Estimate:
      Small < 3 days
    • Front End Estimate:
      Large < 10 days
    • Back End Estimate:
      Large < 10 days
    • Confidence factor:
      Low
    • Estimation Notes and Assumptions:
      Hide
      Dependencies between the KB and Inventory; and the seamless push and pull of data between apps (FOLIO-1273) - there are som system design discussion to have here. How is this process for refresh to be scheduled? Will KB push this or will inventory pull it?
      Show
      Dependencies between the KB and Inventory; and the seamless push and pull of data between apps ( FOLIO-1273 ) - there are som system design discussion to have here. How is this process for refresh to be scheduled? Will KB push this or will inventory pull it?
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      49
    • Kiwi Planning Points (DO NOT CHANGE):
      1
    • PO Rank:
      62
    • PO Ranking Note:
      CW: PO rank aligned with Calculated Total rank.
    • Rank: BNCF (MVP Feb 2020):
      R1
    • Rank: Chalmers (Impl Aut 2019):
      R5
    • Rank: Chicago (MVP Sum 2020):
      R4
    • Rank: Cornell (Full Sum 2021):
      R4
    • Rank: Duke (Full Sum 2021):
      R4
    • Rank: 5Colleges (Full Jul 2021):
      R4
    • Rank: FLO (MVP Sum 2020):
      R4
    • Rank: GBV (MVP Sum 2020):
      R4
    • Rank: hbz (TBD):
      R1
    • Rank: Hungary (MVP End 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R4
    • Rank: Leipzig (Full TBD):
      R1
    • Rank: Leipzig (ERM Aut 2019):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R4
    • Rank: U of AL (MVP Oct 2020):
      R4

      Description

      Purpose: A process is needed to periodically refresh the record against the source (Knowledge base). Essentially, this is about defining how to keep update of eResources, which originate from the KB, and then have gotten a fuller description of the bibliographic record in Inventory (eResources in Inventory).

      Two use cases: updates to access information in holdings for selected titles (e.g., platform change, URL change) & updates to Instances – updates to Instances depends on first having ability to create Instances based on titles in KBs

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                charlotte Charlotte Whitt
                Reporter:
                cboerema Cate Boerema
                Analysis Estimator:
                Charlotte Whitt Charlotte Whitt
                Front End Estimator:
                Niels Erik Gilvad Nielsen Niels Erik Gilvad Nielsen
                Back End Estimator:
                Niels Erik Gilvad Nielsen Niels Erik Gilvad Nielsen
                Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases