In our organization, we have some resource templates that mark a number of fields as ‘required’. This adds some friction, as while we want those fields to be populated before publication, they may need some research, so it would be helpful if researchers could save ‘draft’ items to resume later.
I suppose what we really want is to have those properties optional while the item is still private, and only make them mandatory when the item is made public.
Is there any plug-in for such ‘conditional’ validations? Or perhaps it might make some sense for us to customize the native ‘required’ feature to behave like this?