Changes made – worked smoothly.

Very helpful, thanks. I'll give this a shot.

@Mike Taylor

The inventory business logic interface is slightly stricter than the storage module (for example more properties are mandatory title, name on status, name on material type, name on location) and there are some additional properties. I believe the UI likely already complies with all of those additional validations.

The primary difference at the moment, is that the collection resources in inventory interface do not have a totalRecords property at the moment (I didn't get around to adding them, see https://folio-org.atlassian.net/browse/METADATA-29#icft=METADATA-29). I don't know if the UI uses those properties.

As far as I can tell, the item and instance collection resource API's are otherwise compatible apart from their root addresses.

I hope this helps with a little more clarity,

Hugs,

Marc

Can you please be more specific about what /inventory-storage APIs that I am currently using will not Just Work if I switch to invoking them on /inventory instead? All I get from your previous comment is a vague sense of impending doom 🙂

@Mike Taylor

I'm not sure about a strict superset. I believe they are currently very similar. This is likely to change in https://folio-org.atlassian.net/browse/DMOD-209#icft=DMOD-209, though it's possible that moving to the inventory module might mean the changes happening there are easier for the UI to handle.

Hugs,

Marc