Based on the discussed supported features and config, update the RDM data model to support having a submission review request per each record version.
Currently, we store the review that corresponds to a record in the review field of the RDMParent record. We need to discuss the best thing to do here. We should keep backwards compatibility and minimise the complexity of a migration, so removing this existing review field is probably not a possibility. In any case, the migration should be as simple as possible and the current behaviour (reviews only for the first version) should be retained as the default option unless the instance/community configures it otherwise.
We will also need to modify the rdm_parents_community table which currently only allows for one request per record / community combo.
Maybe we should add a review field to RDMDraft (and correspondingly also to RDMRecord)? This is up for discussion.
Based on the discussed supported features and config, update the RDM data model to support having a submission review request per each record version.
Currently, we store the review that corresponds to a record in the
reviewfield of theRDMParentrecord. We need to discuss the best thing to do here. We should keep backwards compatibility and minimise the complexity of a migration, so removing this existingreviewfield is probably not a possibility. In any case, the migration should be as simple as possible and the current behaviour (reviews only for the first version) should be retained as the default option unless the instance/community configures it otherwise.We will also need to modify the
rdm_parents_communitytable which currently only allows for one request per record / community combo.Maybe we should add a
reviewfield toRDMDraft(and correspondingly also toRDMRecord)? This is up for discussion.