FR: Make custom metadata "requireable"

[madduck]

trafficstars

Would it be possible to make certain custom metadata required so that new documents cannot be approved/metadata-curated when these fields aren't filled?

It probably makes most sense to do this only based on the presence of a tag.

Use-case:

Or: invoices in general need a person to approve the invoice. I.e. when an invoice comes in (via IMAP or scanner, it gets tagged invoice. To be able to clear the "new" status, a person needs to be assigned for approval.

This will likely come in handy with workflows, too.

[madduck]

One benefit of making custom metadata required would be that I wouldn't need to always add the field to the metadata view before even being able to edit it.

[eikek]

Yes, that sounds useful. I think this should also be looked at in the context of the workflow #2272 issue. It goes a bit into the direction of "document types" (or not sure how other DMSs name it). It is not simple to implement, though.

[madduck]

Hey, thanks for your time replying to all my issues and comments.

Document type is surely a metadatum that would benefit from being required for all documents.

There's a huge overlap between this issue, and workflows, as there are overlaps with other issues, such as #542 (unique constraint) etc..

In many ways, I want to think that proper workflow support will make custom metadata unnecessary, so I think you're right in taking time to prioritise. On the other hand, working through the question of what it means for metadata to be required (and/or unique) now will mean we'll know more about it later, and can possibly reuse the code.