Skip to content

LIBDRUM-909. Provide separate umdDescribe/mhheaDescribe form configs#272

Merged
dsteelma-umd merged 2 commits intodrum-mainfrom
feature/LIBDRUM-909
Apr 20, 2026
Merged

LIBDRUM-909. Provide separate umdDescribe/mhheaDescribe form configs#272
dsteelma-umd merged 2 commits intodrum-mainfrom
feature/LIBDRUM-909

Conversation

@dsteelma-umd
Copy link
Copy Markdown

Fixes validation error display rendering by creating a separate "mhheaDescribe" form for use with
Minority Health and Health Equity Archive submisions, modeled on the the standard "umdDescribe" form.

This eliminates the need for a separate "Submission Type" panel from both forms. Having this separate panel appears to be the source of the error validation display issue.

The "umdDescribe" and "mhheaDescribe" forms are commented with "custom" and "common" sections. The "custom" section in "umdDescribe" handles the dynamic display of the "Equitable Access" field when specific document types are selected. The "custom" section in "mhheaDescribe" does not have this functionality, as it is not needed.

The "common" sections of both forms should remain in sync -- updates to one should be (manually) replicated in the other. There is no way to enforce this, other than through mentioning it in the documentation.

https://umd-dit.atlassian.net/browse/LIBDRUM-909

Fixes validation error display rendering by creating a separate
"mhheaDescribe" form for use with
Minority Health and Health Equity Archive submisions, modeled on the
the standard "umdDescribe" form.

This eliminates the need for a separate "Submission Type" panel from
both forms. Having this separate panel appears to be the source of the
error validation display issue.

The "umdDescribe" and "mhheaDescribe" forms are commented with "custom"
and "common" sections. The "custom" section in "umdDescribe" handles the
dynamic display of the "Equitable Access" field when specific document
types are selected. The "custom" section in "mhheaDescribe" does not
have this functionality, as it is not needed.

The "common" sections of both forms should remain in sync -- updates
to one should be (manually) replicated in the other. There is no way to
enforce this, other than through mentioning it in the documentation.

https://umd-dit.atlassian.net/browse/LIBDRUM-909
Updated the "DrumSubmissionForms.md" and "DrumTestPlan.md" documents
to reflect the changes made in this issue.

https://umd-dit.atlassian.net/browse/LIBDRUM-909
@dsteelma-umd dsteelma-umd merged commit 594caf0 into drum-main Apr 20, 2026
11 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant