Thanks @Andrei Shumski if the BE won't allow a user to create one successfully for title POL let's leave it disabled. I will resolve this story as complete.

Hi @Dennis Bridges. For now Title for non-package POL is creating on BE side after creating POL. So there is no way for user to create Title manually (with or without disabled field Title). If try to create it you'll see an error message. Title for package POL does not create on BE. It's possible to create it only manually. User need to select package POL from plugin find-POL. If POL is package Title field becomes not disabled. Do we need to make it not disabled for any POL? But anyway user has no possibility to create it for non-package POL.

@Andrei Shumski Title field is restricted until I choose a POL. I see that the way the story is written that could be correct. However, could the restriction of package POL be removed so the user could create a title manually for any kind of POL? Essentially there is no need to restrict this to package POL but users will not likely create titles title POLs, so if removing the restriction would be difficult we can address it at a later date. Let me know what you think, I'm not sure if this was also done in the backend. Thanks!

Tested on Folio-testing, @Dennis Bridges, please review

Open

Hi @Dennis Bridges If a user is entering title information without using the look-up, could we have the Contributor and Product ID fields opened up to at least one row per item since those fields are required? Here's a mock of what I mean:

Open

Also the mock shows that the "Save & close" button is disabled until all required fields have values entered for them. I wrote up a bug about that behavior UIREC-47.