Submit for review: When a user selects this option, a message should indicate the dataset will be reviewed and published

[sbarbosadataverse]

This issue is being updated 4/17/26:

For HDV root utilizing submit for review and for collections utilizing submit for review, add some additional messaging so users can understand the feature:

1. The first case is what is submitted for review. It should be clear to users that the dataset will be reviewed and published:
   This dataset is being submitted for review and publishing. If PUBLISHING is not your intended workflow, do not submit this for review and contact support."

The next set of message is acknowledging a set of terms before submitting for review. Terms were initially added here:
IQSS/dataverse-pm#521

But publishing is not the proper place for collections and spaces that use "submit for review."
Additional messaging on submit for review should be:

1. My submission has been fully anonymized (required for all human subjects' datasets)
2. My submission does not violate any known copyright laws
3. I understand that I am liable for any and all violations of the Harvard Repository Terms of Use (link to terms): https://support.dataverse.harvard.edu/harvard-dataverse-general-terms-use

[pdurbin]

• add a new database setting for "submit for review" messaging (update: see note about naming below). The related setting is :PublishDatasetDisclaimerText, added in Add acknowledgment before publishing #12051
• add messaging to "submit for review" popup
• add checkbox (just like the "publish" version)
• make text red, like "publish"

[scolapasta]

Once thing we need to consider is the name of the setting, as this message will (likely) also be used for self publish (so we don't have to have two settings for the same message. So the name should not specifically be tied to "submit for review"

[scolapasta]

maybe the setting can be called something like PrePublishDatasetDisclaimerText since it will be used it multiple cases.

[stevenwinship]

Is the PrePublishDatasetDisclaimerText also replacing the existing PublishDatasetDisclaimerText? I can see how the two should stay separate so the wording can be different if needed. @sbarbosadataverse mentioned a possibility of the wording being different for journals. Is that part of this issue?

[pdurbin]

@stevenwinship no, the idea is to add a new database setting. I just added "new" above for clarity. Thanks.