Extend existing LocationMapping table to support CaiaSoft accession flow.
- LocationMapping table should contain 3 fields: remoteConfigurationId (ex configurationId, uuid, non-null value), originalLocationId (new field, uuid, non-null value), finalLocationId (ex folioLocationId).
- LocationMapping API should be extended to support new and renamed field.
- New API endpoint for returning all the originalLocationId (from inventory, non-remote locations) with corresponding finalLocationId should be implemented (if mapping doesn't exist "null" should be returned instead of finalLocationId)
CaiaSoft Business Workflows
- Schema is updated
- Sample data is added
- LocationMapping API is updated
- Unit tests are updated (if needed)