Regarding the metadata curation checks intergration, there is still some development necessary (but I don't suspect too much) to allow configuring "global" checks that would apply on all submissions, regardless of having a community review or inclusion request.
The datamodel supports this, i.e. you can create a CheckConfig without specifying a community_id, but there are two missing parts at the moment:
- The ChecksComponent needs to take into account these global metadata check configs, and fetch and apply them throughout the record/draft lifecycle methods
- There's no dedicated UI page for having an overview of global checks that would run on the record. If you see the screenshot in the docs it's a tab on the community request.
So there's some design necessary to figure out 2., but we could also incrementally implement 1. since there will still be validation feedback on the deposit form.
See also original discussion on Discord
Regarding the metadata curation checks intergration, there is still some development necessary (but I don't suspect too much) to allow configuring "global" checks that would apply on all submissions, regardless of having a community review or inclusion request.
The datamodel supports this, i.e. you can create a
CheckConfigwithout specifying acommunity_id, but there are two missing parts at the moment:So there's some design necessary to figure out
2., but we could also incrementally implement1.since there will still be validation feedback on the deposit form.See also original discussion on Discord