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

Bulk edit records

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Potential Workaround:
      Hide
      CW: This feature is ranked 'go-live' for all libraries except Chalmers. But Export (and re-import updated records) can be a workaround for the mvp.
      It seems better to use this workaround and take the time to develop something that is truly better, and long term solution.
      Show
      CW: This feature is ranked 'go-live' for all libraries except Chalmers. But Export (and re-import updated records) can be a workaround for the mvp. It seems better to use this workaround and take the time to develop something that is truly better, and long term solution.
    • Estimation Notes and Assumptions:
      Hide
      Assume we create a general bulk edit feature for searchandsort apps

      Assume doing the change 1x1 won't scale

      Needs new operation
      Show
      Assume we create a general bulk edit feature for searchandsort apps Assume doing the change 1x1 won't scale Needs new operation
    • Development Team:
      Firebird
    • Calculated Total Rank:
      150
    • Kiwi Planning Points (DO NOT CHANGE):
      280
    • PO Rank:
      112
    • Rank: BNCF (MVP Feb 2020):
      R1
    • Rank: Chalmers (Impl Aut 2019):
      R2
    • 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):
      R2
    • Rank: hbz (TBD):
      R1
    • Rank: Hungary (MVP End 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R1
    • Rank: Leipzig (Full TBD):
      R1
    • Rank: Leipzig (ERM Aut 2019):
      R1
    • Rank: MI State-Lib of MI (Sum 2021):
      R2
    • 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

      Ability to change one or more properties for each record in a list of records (e.g. Users, Items, Request) to a given value.

      This feature was initially discussed in the context of the Reserves sub-group, but it was decided that that group would rather have a Courses app than the ability to bulk edit locations. That said, when this is built, this is how the Reserves group thought it could work as follows:

      • Invoking the "batch edit" function displays a special batch-version of the CRUD-dialog for items
      • Values for …<below>..can be set as appropriate. Other values are left at their default value of "No change" - these will not be modified
      1. Location (Permanent, temporary) ability to (change, add, and remove),
      2. Item Type (Permanent, temporary) ability to (change, add, and remove),
      3. Loan Period (Permanent, temporary) ability to (change, add, and remove),
      4. Tags-ability to (change, add, and remove),
      5. ( also any of the COURSE information that is not in V1) -
      6. (ETC to be determined by other SIGs)
      • ANY changes made must be captured in item history to inculde
      1. Who - operator
      2. What - the actual change
      3. Where - level of service and tool ( batch, manual)
      4. When - date, time

      The list of items for a batch process may be created in different ways:

      • Scan a stack of item-IDs (e.g. barcodes) into a text-box,
      • Paste a list of item-IDs (e.g. barcodes) into a text-box
      • import a list of item-IDs (e.g. barcodes) from a text-file into the text box
      • Select items from a list of search results in FOLIO. (i.e. search items by shelfmark or tag etc. and then invoke the "batch change" function to modify all found or all selected items)

      IF ERRORS
      No changes are made to the record that presents an error - at the end of the process a list is provided of errored items to the the operator to manually change.
      E.g. List of 10 item is supplied 3 had errors but 7 did not so the 7 should have the changes auto-magically applied - and the 3 should be given to the operator to look into why there was an error but no changes should be applied to those 3.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                magdaz Magda Zacharska
                Reporter:
                cboerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                19 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases