Initial version of a ui-scan module pushed to github/folio-org

The UI prototype has a "Check items out" button in the Users module, so wasn't sure if that was gonna be the access route. But maybe this UI is actually supposed to be triggered by the scanner. Anyway I made it a new stripes module and separate git project for now, so that it can be added to the main menu bar. Easy to change later.

The initial commit simply fetches a patron (by username) and displays the profile (no layout attempted)

Thought username would be easier for a demo than UUID and afaiu it's a simulation anyway.

and as discussed today, once the "Done" button is clicked, the client/UI should flip the state on all listed items to "checked out" (or whatever that state is called). It should ignore the patron/user id – this information does not need to be registered anywhere at this point. In the subsequent sprints we will include stories to modify this behavior of the client/UI to create and store a proper "loan" object that register both the patron identified and item identifier.

Correct Marc, Inventory storage is in the black box.

Thanks, Marc.

All right, wasn't entirely sure if not having node and npm would cause problem down the line with automated tests or something, so maybe good to note that – though some would probably figure that from the context.

Going forward I guess people would install the inventory module, right, meaning having Groovy and Gradle as mandatory dependencies will then be fine.

Inventory storage is a standard Java and Maven, RAML-module-builder based module, so it pretty much relies on exactly the same dependencies as the users module. It should be part of the install of mod-metadata that you did. I'm almost certain that the backend black box has inventory storage.

What you did for users should work exactly the same for inventory storage, you should be able to use the same (or different) database, admin role and config. There is no need to run setup-test-db.sh or setup-demo-db.sh for that.

The optional dependencies are pretty much Python (entirely optional, just makes unregistering managed modules from Okapi nicer), Node and NPM (entirely optional, only for linting the RAML and JSON.schema and for generating API docs), and SDKMAN (entirely optional, only for installing Groovy and Gradle). And Groovy and Gradle are only required for the inventory module.

I hope this helps.

Hugs,

Marc