Integrate Geographic Unit Field into Geographic Coverage Metadata Block

[Saixel]

Background

To streamline the metadata entry process and improve the logical grouping of related geographic information, there is a need to integrate the "Geographic Unit" field into the "Geographic Coverage" metadata block in the CAFE project's Dataverse instance.

Feature Request

Reorganize the "Geographic Coverage" metadata block to include the "Geographic Unit" field as a part of it.

• Assess whether the current metadata structure allows for this integration without compromising the functionality and usability of the metadata entry interface.
• If direct integration poses challenges, explore alternative solutions that would allow for a seamless user experience while maintaining the logical grouping of geographic metadata fields.
• Integrate the "Geographic Unit" field into the "Geographic Coverage" block as an intrinsic part of the new entry creation process. Currently, users can add new entries for both "Geographic Coverage" and "Geographic Unit" using a plus button; however, these entries are independent of each other. The update should allow that with each new "Geographic Coverage" entry, a corresponding "Geographic Unit" field is included, ensuring associated geographic information remains linked and is coherently grouped within the user interface.

Justification

This change aims to enhance the intuitiveness of the metadata entry process by consolidating related geographic fields, thereby reducing confusion and potential errors during data submission. It also seeks to ensure that all relevant geographic metadata is considered and entered at the same point in the dataset creation process.

Implementation Considerations

• Review the current metadata model to understand the dependencies and constraints associated with the "Geographic Coverage" and "Geographic Unit" fields.
• Collaborate with technical and user experience teams to design a solution that either integrates these fields or improves their alignment and interactivity within the dataset creation workflow.
• Ensure that any changes maintain or enhance the overall metadata quality and adhere to best practices in data management.

Additional Context

This request comes as part of ongoing efforts to tailor the Dataverse environment to better meet the specific needs of the CAFE project, focusing on enhancing user satisfaction and data quality.

[Saixel]

After identifying the problem and separating it into two distinct issues, we have extensively debated the modifications needed for the "Geographic Unit" and "Geographic Coverage" fields. Given that these fields are part of a core metadata block and not a custom one, modifying their structure poses significant challenges.

We have proposed creating the same metadata fields within our custom "Geospatial" metadata block, which we already use, and using them there instead of in the general block. However, this change is not particularly urgent, so we have decided to deprioritize or pause this issue until we have addressed other more pressing tasks.

It should be evaluated with the rest of the team and the community whether the initially proposed change in the Unit and Coverage fields is something that could make sense and we would want to implement, or if, when the time comes, we proceed with the option to work on this in a custom block as mentioned.