You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the user enabled the coverage element in the settings (Settings->Workflow->Submission->Metadata->Coverage), then there are two inputs for the coverage element in the submission view, one created by OJS and one created by the geoOJS Plugin. But both store their data in the same database element ("coverage"). Besides the initial coverage input field is not able to show the stored data, stored by the geoOJS plugin, correctly(like shown in the screenshot).
So the initial coverage input field must be disabled when using the geoOJS plugin.
The text was updated successfully, but these errors were encountered:
tomniers
changed the title
remove duplicate coverage element in submission view
Remove duplicate coverage element in submission view
Nov 21, 2020
If the user enabled the coverage element in the settings (Settings->Workflow->Submission->Metadata->Coverage), then there are two inputs for the coverage element in the submission view, one created by OJS and one created by the geoOJS Plugin. But both store their data in the same database element ("coverage"). Besides the initial coverage input field is not able to show the stored data, stored by the geoOJS plugin, correctly(like shown in the screenshot).

So the initial coverage input field must be disabled when using the geoOJS plugin.
The text was updated successfully, but these errors were encountered: