Feature Request/Idea: Allow alternative dataset metadatablock views and edit forms via plugable components

Although you can configure custom metdatablocks (via the TSV file load) there is not much control over the display or input elements for that block besides external CVOCS for the JSF version of Dataverse.

The use-case that drives this request is the addition of a small geographical map near the coordinates display for our custom geo-location metadatablock. The visual feedback for the coordinates in the metadata will help in reducing erronous input. Even better would be to also have that map on the edit form, and thus possibly also allow the user to specify the coordinates directly on the map instead of typing numbers. For instance, by clicking on the map or positioning a marker.

Any open or closed issues related to this feature request?

• https://github.com/IQSS/dataverse-frontend/issues/580

No implementation files, tests, or entry points are named in the request. Start by reading the related dataverse-frontend issue #580 and tracing how custom metadata blocks are currently displayed and edited; done would require an agreed component design supporting alternative views and edit forms, including the geographic-map use case.