Skip to content

Add, Update Item Bulk

Notes

  1. The upload format will initially be fixed and in the future allow for user definition of columns, etc..
  2. The upload will have a reasonable limit on the number of rows. In the future, the limit will increase once asynchronous execution and notification to the user is implemented.
  3. The Upload will have special “Action” and “ArdaId” columns.
    1. The Action column instructs the system of what to do with the item: NEW, UPDATE, UPDATE-OVERRIDE, DRAFT, DRAFT-OVERRIDE, DELETE, IGNORE
    1. NEW: Will create a new item (subject to uniqueness constraints)
    2. UPDATE will update and publish the item if there is no active draft, fail otherwise
    3. UPDATE-OVERRIDE will update and publish the item discarding any pre-existing drafts.
    4. DRAFT will update and leave a draft if there is no active draft, otherwise fail.
    5. DRAFT-OVERRIDE will update and discard any pre-existing draft. Leaves the item in Draft state.
    6. DELETE will mark the Item as deleted or retired and discard any pre-existing drafts.
    7. IGNORE will skip the UPDATE
    2. The ArdaId column is required for UPDATE, UPDATE-OVERRIDE, UPDATE-DELETE or DELETE and must contain the ID that is obtained by downloading the list of items first. This ID is generated by the Arda system, and it uniquely identifies the item to update to avoid errors.
    3. The upload is not “atomic” across all rows but on a row-by-row basis. The result for the user will be a count of successful operations and a list of errors for each row that failed to process.

Steps

  1. User goes to the List Items page and selects “bulk change” or similar.
  2. The user will upload a CSV (future extended formats) with one item per row with a predefined format.
  3. The system will perform initial validation of the file and inform the user of any errors to be corrected, or to ignore any rows with errors.
  4. The system will confirm the operations to perform to the user (e.g. 123 UPDATES, 33 NEW, 22 DELETES)
  5. The system will proceed with the Updates. The user will be blocked from interacting with the system from the browser session while this takes place. (In the future this will be made asynchronous)
  6. The system will inform the user of success or issues with individual rows. (possibly on a separate list tab)

Scenario

uml diagram

Copyright: © Arda Systems 2025, All rights reserved

Comments