Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
In other words, ui-inventory currently use mod-inventory for the somewhat limited purposes of:
1) Mapping certain Item UUIDs to labels (loan type, location, material type) for the Item Detail View. 2) Resolving "effective location"
*: Not counting API access declared by components, but they would not add to the list I think.
Julian LadischJuly 27, 2018 at 7:43 AM
Closing this issue for now. Please reopen if there is a requirement that mod-inventory should also provide some of the source record APIs (which?) that already exists in mod-inventory-storage.
Marc JohnsonJuly 26, 2018 at 10:42 AM
@Julian Ladisch I concur, at this point there is limited value in replicating the source record endpoint in mod-inventory.
There might be value in the sourceRecordFormat being in the instance representation. However I think this is likely now sufficiently out of sync with the previous changes to storage, that the default UI does not use it.
@Niels Erik Nielsen Do you think there is value (at the moment) in that property being available in the business logic view of an instance (a quick look at UI inventory suggests that it uses instance-storage, and only items from the inventory interface)?
Right @Marc Johnson, this is the complete list of API access declared in ui-inventory itself*:
path: 'circulation/loans?query=(itemId==!{itemId}) sortby loanDate/sort.descending&limit=1', path: 'circulation/requests?query=(itemId==:{itemid}) sortby requestDate desc', path: 'holdings-storage/holdings', path: 'holdings-storage/holdings', path: 'holdings-storage/holdings/:{holdingsrecordid}', path: 'holdings-storage/holdings?query=(instanceId==:{id})', path: 'instance-storage/instances', path: 'instance-storage/instances/:{id}', path: 'inventory/items', path: 'inventory/items', path: 'inventory/items/:{itemid}', path: 'inventory/items?query=(holdingsRecordId==!{holdingsRecord.id})', path: 'loan-types', path: 'locations/%{permanentLocationQuery.id}', path: 'locations/%{temporaryLocationQuery.id}', path: 'material-types', path: 'platforms', path: 'users?query=(id==%{borrowerId.query})',In other words, ui-inventory currently use mod-inventory for the somewhat limited purposes of:
1) Mapping certain Item UUIDs to labels (loan type, location, material type) for the Item Detail View.
2) Resolving "effective location"
*: Not counting API access declared by components, but they would not add to the list I think.