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

Ability to Protect Fields from Being Overwritten by User Import

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Draft (View Workflow)
    • Priority: P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Template:
      UXPROD features
    • Epic Link:
    • Analysis Estimate:
      Medium < 5 days
    • Front End Estimate:
      XL < 15 days
    • Back End Estimate:
      Large < 10 days
    • Estimation Notes and Assumptions:
      Hide
      This estimation is largely dependent on the scope of the changes we make to the backend. I think a "Large" size is fitting if the change is primarily an additional field made to the required data stores to hold the change schema.

      Alternately, if we want a more comprehensive solution akin to mod-notes wherein we implement an actual module to track change permissions to schema, I think an XL designation would be more fitting.
      Show
      This estimation is largely dependent on the scope of the changes we make to the backend. I think a "Large" size is fitting if the change is primarily an additional field made to the required data stores to hold the change schema. Alternately, if we want a more comprehensive solution akin to mod-notes wherein we implement an actual module to track change permissions to schema, I think an XL designation would be more fitting.
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      89
    • Kiwi Planning Points (DO NOT CHANGE):
      21
    • PO Rank:
      54
    • Rank: Chalmers (Impl Aut 2019):
      R4
    • Rank: Chicago (MVP Sum 2020):
      R4
    • Rank: Cornell (Full Sum 2021):
      R3
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R4
    • Rank: FLO (MVP Sum 2020):
      R4
    • Rank: GBV (MVP Sum 2020):
      R2
    • Rank: Grand Valley (Full Sum 2021):
      R1
    • Rank: hbz (TBD):
      R2
    • Rank: Hungary (MVP End 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R4
    • Rank: Leipzig (Full TBD):
      R1
    • Rank: Mainz (Full TBD):
      R2
    • Rank: MO State (MVP June 2020):
      R1
    • Rank: St. Michael's College (Sum 2021):
      R2
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R4

      Description

      Support ability for staff to block a field(s) on a user record or the entire user record from being overwritten by a user import/data feed. This feature will support a library's need to temporarily prevent a user import/data feed or Folio logic from updating a field(s) on a user record.

      As a system administrator, I want to be able to designate what happens when a record is in the FOLIO database but does not come in the feed, depending what kind of feed it is.
      If the record in FOLIO was created via feed, the absence of the patron in a new feed should cause the record to be inactivated
      But, if a record in FOLIO was created by migration or in FOLIO itself, the feed will have no effect on it.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                pwanninger Patty Wanninger
                Reporter:
                cboerema Cate Boerema
                Analysis Estimator:
                Khalilah Gambrell Khalilah Gambrell
                Front End Estimator:
                Zak_Burke Zak_Burke
                Back End Estimator:
                Kurt Nordstrom Kurt Nordstrom
                Votes:
                0 Vote for this issue
                Watchers:
                14 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases