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

Ability to Protect Fields from Being Overwritten by User Import

    XMLWordPrintable

Details

    • Medium < 5 days
    • XL < 15 days
    • Large < 10 days
    • 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.
    • Prokopovych
    • 21
    • 54
    • R4
    • R4
    • R3
    • R1
    • R4
    • R4
    • R2
    • R1
    • R2
    • R1
    • R4
    • R1
    • R2
    • R1
    • R2
    • R1
    • 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

            is defined by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-530 Ability to override a field via Folio AND for it not to be overridden by data feed and rules/logic configured in Folio

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-531 Flag an entire user record as a potential exception

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-532 Set an expiration date for how long field or record should be protected

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-533 Allow user to add a reason why the field is protected

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-534 Need to track the fields that are protected

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-535 Store/Make the list of exceptions accessible in Folio

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-536 Need to a way for the list of overrides to be checked against the Folio user-import and user modules

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

            Task - A task that needs to be done. MODINVSTOR-119 generic way to mark records "protected"

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

            New Feature - New feature requests UXPROD-2320 Improvements to User loader - source of feed

            • TBD - To be determined
            • Draft

            New Feature - New feature requests UXPROD-2731 Improvements to User loader - additional match points

            • TBD - To be determined
            • Open

            New Feature - New feature requests UXPROD-2732 Improvements to User loader - protecting fields/overwriting

            • TBD - To be determined
            • Closed

            New Feature - New feature requests UXPROD-2734 Bulk APIs for Users module

            • TBD - To be determined
            • Open

            New Feature - New feature requests UXPROD-2873 Mod-user-import stabilization

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

            Page Loading...

            Page Loading...

            Activity

              People

                pwanninger Patty Wanninger
                cboerema Cate Boerema
                Khalilah Gambrell Khalilah Gambrell
                Zak_Burke Zak_Burke
                Kurt Nordstrom Kurt Nordstrom
                Votes:
                0 Vote for this issue
                Watchers:
                16 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases