Humans do not tend to think in or easily remember UUIDs. At present in the location column of the packages table (and on the package view page) we are showing a UUID for the location of the package. This means a user needs to go to Enduro's Locations module, or to the Storage Service directly, to figure out what location name is associated with the storage location. This adds unnecessary steps for the user, that could easily be avoided by displaying the human-readable / assignable storage name. UUIDs should only be used as a fallback if no other label is available for display.
To Reproduce
Go to the Packages page in the Enduro UI
Ensure you have one or more AIPs that have completed processing and been stored
Look at the information in the Location column of the Packages table
Alternatively, click through to the Package details view page, and look at the Location box in the Summary area at the top of the page
Expected behavior
A human-readable name for the associated storage location is shown, instead of a UUID.
Describe the bug
Humans do not tend to think in or easily remember UUIDs. At present in the location column of the packages table (and on the package view page) we are showing a UUID for the location of the package. This means a user needs to go to Enduro's Locations module, or to the Storage Service directly, to figure out what location name is associated with the storage location. This adds unnecessary steps for the user, that could easily be avoided by displaying the human-readable / assignable storage name. UUIDs should only be used as a fallback if no other label is available for display.
To Reproduce
Expected behavior
A human-readable name for the associated storage location is shown, instead of a UUID.
Screenshots
Example from dev environment: