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
{{ message }}
This repository has been archived by the owner on Jul 15, 2021. It is now read-only.
Is your feature request related to a problem? Please describe.
Currently when a user provides a metadata URL to an existing record, this wil prevent ARGG from creating a duplicate record. However, it does not deactivate the metadata fields from the form. Although these will be ignored, it may cause confusion for users as well as cost them time filling out unnecessary fields.
Describe the solution you'd like
When a user provides a URL for an existing metadata record, deactivate any fields that are specific to creating a new draft metadata record. For example, the 'Access' section of the submission form would no longer need to be filled out.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is your feature request related to a problem? Please describe.
Currently when a user provides a metadata URL to an existing record, this wil prevent ARGG from creating a duplicate record. However, it does not deactivate the metadata fields from the form. Although these will be ignored, it may cause confusion for users as well as cost them time filling out unnecessary fields.
Describe the solution you'd like
When a user provides a URL for an existing metadata record, deactivate any fields that are specific to creating a new draft metadata record. For example, the 'Access' section of the submission form would no longer need to be filled out.
The text was updated successfully, but these errors were encountered: