Spike: How to handle cross-app UUIDs in sample data

Our sample data contains references to records in other apps (e.g. material-types, locations, instanceId, itemId, etc.). We need to figure out how to address this problem.

Questions to be answered:

• There is some uncertainty about whether the UUIDs for the reference/sample data in other apps is static, or changes each time it's loaded. Discussing with the inventory team is probably a good place to start.
• Assuming we can get to the point where these UUIDs are static/hardcoded, how do we handle maintenance? i.e. if one of these UUIDs changes for some reason, how do we know?
  Is there some process that can be agreed upon? Ideally we'd be able to catch this prior to discovering the problem during testing on a deployed system (e.g. folio-testing/etc.)

Acceptance Criteria:

• The questions above are answered and documented (here or on confluence)
• Follow-on stories have been created as necessary to implement processes or changes. (including against other projects if needed)

Timebox: 3 day(s)