Validate Item Record

Tested in http://folio-testing.aws.indexdata.com/ version: item-storage 3.0 - by using Chrome.
Labels, error messages and mandatory fields - all looks good

@Jakub Skoczen, do you think we already have what we need to ensure that imported data is valid (for user data) or should we get in a story for that?

I don't know what the back-end guys have planned, exactly. But my expectation would be that the Ingest service will validate the records according to some set of criteria, which may or may not be the same as those we use for manual user-record creation; and that records that fail that validation will be discarded and a report generated.

As always, the back-end tells the real truth about what may and may not be stored, both for bulk import and for manual user creation. Client-side validation, whether done with or without reference to server-provided facilities, is only a convenience – like client-side permission checking.

@Cate Boerema @Mike Taylor

When I suggested that the validation was performed on the client (the UI), I was referring only to the per-field validation in the users UI module (which I thought had been done by a request to the server), rather than validation for a user in general. I believe there is record validation in the users module. Apologies for any confusion caused by the distinction.

So there is validation in the import (or in something the import uses)? I was reading the earlier comments and concluding that the validation was all in the UI and thinking the import would, then, bypass the validation. I may have misunderstood.