IQSS / dataverse

Open source research data repository software
http://dataverse.org
Other
878 stars 490 forks source link

Integrate Geographic Unit Field into Geographic Coverage Metadata Block #10502

Open Saixel opened 6 months ago

Saixel commented 6 months ago

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.

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

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 commented 3 months ago

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.