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
In order to reduce the number of extensions we need to maintain, data.gov developers want to move the server-side validation used by Inventory to dcat_usmetadata.
Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]
GIVEN [a contextual precondition]
[AND optionally another precondition]
WHEN [a triggering event] happens
THEN [a verifiable outcome]
[AND optionally another verifiable outcome]
[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]
Sketch
We should only move functionality we use. Hard validation should not apply to drafts, but we want to warn the user if a draft does not meet validation requirements.
The text was updated successfully, but these errors were encountered:
User Story
In order to reduce the number of extensions we need to maintain, data.gov developers want to move the server-side validation used by Inventory to dcat_usmetadata.
Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]
[AND optionally another precondition]
WHEN [a triggering event] happens
THEN [a verifiable outcome]
[AND optionally another verifiable outcome]
Background
ckanext-dcat_usmetadata has replaced the metadata form, formerly handled by USMetadata.
GSA/datagov-ckan-multi#422 (comment)
Security Considerations (required)
[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]
Sketch
We should only move functionality we use. Hard validation should not apply to drafts, but we want to warn the user if a draft does not meet validation requirements.
The text was updated successfully, but these errors were encountered: