Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Modules needed

  • uiedge-usersuioai-inventorypmh
  • mod-inventoryoai-storage-modules
  • ui-bulk-edit
  • pmh
  • mod-datainventory-export workerstorage
  • mod-datasource-exportrecord-springstorage
  • okapi

Testing expectations 

  • Bulk edit user records
  • Bulk edit item records with the updates to locations and statues
  • Run multiple bulk edits concurrently
  • Run bulk edit while exporting:
    • circulation logs
    • bursar data
    • EDIFACT
    • eHoldings

Bulk edit testing setup

  •  Files with user barcodes (100, 1000, 2500,5000)
  •  Files with item barcodes (100, 1000, 10 000, 100 000)
  •  Files with holdings HRIDs (100, 1000, 10 000, 100 000)
  •  Users configured with following permissions:
    •   Bulk Edit: (CSV) Edit and Bulk Edit: (CSV) View - for user records testing
    •   Bulk Edit: In ppp Edit and Bulk Edit: In app View - for user item records testing
  •  JMeter tests repository: https://github.com/folio-org/folio-perf-test/tree/master/Folio-Test-Plans/bulk-edit

User records testing scenarios

  1. User status updates
    1. Upload file with user barcodes
    2. Click Start bulk edit option in Action menu and make following changes
      1. Set patron group to <value available on test environment>
      2. Set expiration date to  November 1, 2025
      3. Replace ".com" with ".org" in the  email box
    3. Confirm the changes
    4. Commit the changes
    5. Verify the changes are correct
    6. Download the file with updated records
    7. Download the file with errors (if applicable)
  2. Item records updates:
    1. Upload file with item barcodes 
    2. Click Start bulk edit option in Action menu and make following changes:
      1. Set Temporary location to Clear field
      2. Set Permanent location to < to the value available on test environment>
      3. Set Status to Unknown
      4. Set Temporary loan type to Clear field
      5. Set Permanent loan type to < to the value available on test environment>
    3. Confirm the changes
    4. Commit the changes
    5. Verify the changes are correct
    6. Download the file with updated records
    7. Download the file with errors (if applicable)
  3. Holdings records updates:
    1. Upload file with HRIDs
    2. Click Start bulk edit option in Action menu and make following changes:
      1. Set Temporary location to Clear field
      2. Set Permanent location to <to the value available on test environment>
    3. Confirm the changes
    4. Commit the changes
    5. Verify the changes are correct
    6. Download the file with updated records
    7. Download the file with errors (if applicable)

Concurrent and consecutive tests:

Each of the following scenarios to be tested separately. Scenarios are ordered by priority

Scenario 1. Run simultaneously bulk edits:

  • one job for 2500  user records
  • one job for 10k item records 

(If possible ramp up the number of records to 5k and 100k for users and items respectively)

Scenario 2.  Run simultaneously bulk edits:

  • one job for 2500  user records
  • one job for 10k holdings records 

(If possible ramp up the number of records to 5k and 100k for users and items respectively)

Scenario 3. Run consecutively four jobs editing 2500 user records

Scenario 4. Run consecutively four jobs editing 10k  item records

Scenario 5. Run simultaneously four jobs editing 2500 user records

Scenario 6. Run simultaneously four jobs editing 10k item records

Scenario 7. Run simultaneously four jobs editing 10k holdings records

  • Tenant level full harvest completes within less than 12 hours.
  • Multiple concurrent harvests complete successfully 
  • At least one full and two incremental harvests can run concurrently.
  • Incremental harvests run every four hours complete successfully
  • Incremental harvests do not affect CI/CO and Data Import operations.


Data volumes

  • Full harvest of eight million or records
  • Incremental harvest of: 
    • 100 000 records
    • 5 000 records
    • 20 000 records
    • 40 000 records
  • Data import -2 000 instances (to be confirmed)
  • CI/CO - TBD

Consortia requirements

  • Each harvest contains shared and local instances
  • Harvests started at the central tenant harvest across all tenant consecutively until all tenant are harvested
  • Harvest started at the member tenant level, harvest only this tenant's inventory

User records testing scenarios

  1. Full harvest:
    1. Record source SRS
    2. Record source= SRS and Inventory
  2. Incremental harvests (includes updates and additions for period specified by providing from" and "until" parameters)





Concurrent and consecutive tests:

Scenario 1.  Run simultaneously full harvest and incremental harvests

Scenario 2. Run incremental harvests every  four hours and start data import at the same time

Scenario 3.  Run incremental harvests every four hours, start data import, test CO/CI

Failover tests:

  1. Determine likelihood of failover
  2. Does tasks restart?
  3. Does other task pick up the jobs that were in progress?

User records - in app approach:

View file
nameuser-records-nolana.mp4
height250

Item records:

View file
nameitem-records-nolana.mp4
height250

Holdings records:

View filenameholdings-records-nolana.mp4height250