Skip to content
This repository has been archived by the owner on Aug 3, 2022. It is now read-only.

Include level wherever possible #20

Open
nickevansuk opened this issue Jun 6, 2018 · 1 comment
Open

Include level wherever possible #20

nickevansuk opened this issue Jun 6, 2018 · 1 comment
Labels
rule: data quality warning
Projects
Validation Rules and Documentation

Comments

@nickevansuk
Copy link
Contributor

nickevansuk commented Jun 6, 2018 •
edited
Loading

Rule name

Include level wherever possible

Rule type

Data quality warning

Rule hint

Including level allows data users to present the correct activities to a relevant audience.

Associated proposal or model reference

Examples
@nickevansuk nickevansuk changed the title Missing details in the PostalAddress may result in the event not being listed in Google Reserve - Jun 6, 2018
@nickevansuk nickevansuk changed the title - Include level wherever possible Jun 6, 2018
@nickevansuk nickevansuk mentioned this issue Jun 6, 2018
Closed
@nickevansuk nickevansuk added this to To do in Validation Rules and Documentation via automation Jun 6, 2018
@nickevansuk nickevansuk moved this from To do to Waiting for consensus and specification update in Validation Rules and Documentation Jun 6, 2018
@petewalker petewalker mentioned this issue Jul 11, 2018
Closed
@ldodds
Copy link
Contributor

ldodds commented Jul 17, 2018

Seems reasonable to promote level to recommended from optional

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
rule: data quality warning
Projects
Validation Rules and Documentation
  
Waiting for consensus and specificati...
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ldodds @nickevansuk