Conditionally Required Entries in Custom Metadata Blocks

Background

To ensure data quality and completeness, we need the ability to make certain fields in custom metadata blocks conditionally required based on user responses.

Issue

In the custom metadata blocks "Metadata about Data Sources" and "Metadata about Geospatial Files", we would like fields to appear as required only if "yes" is selected for the first question.

Feature Request

• Implement logic to conditionally require fields in custom metadata blocks based on previous field responses.
• Ensure that the fields are only marked as required if the condition is met.

Justification

This feature will help maintain metadata standards by ensuring that users provide all necessary information when certain conditions are met, thereby improving data quality and consistency.

Implementation Considerations

• Review the current implementation of metadata blocks and identify where conditional logic can be applied.
• Analyze the feasibility of implementing this feature and confirm with the team.
• Develop and test the necessary changes to the system to support conditionally required fields.
• Ensure that the changes are backward compatible and do not affect existing metadata entries.

Additional Context

This feature request is based on recurring issues where users do not provide additional metadata unless it is explicitly required. By making fields conditionally required, we can ensure that all relevant information is captured during the dataset creation process. Given that the viability of implementing this new feature is not yet confirmed, an initial analysis will be necessary to determine if it can be achieved and to plan the implementation accordingly.

Start by reviewing the current implementation of the custom metadata blocks “Metadata about Data Sources” and “Metadata about Geospatial Files,” including how field responses and required-state validation are handled. Confirm with the team whether conditional requirements are feasible and backward compatible; done should include an agreed implementation plan and tests for both condition states.