-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Organization name and identifier consistency across dataset #28
Comments
In the case of same ID, my understanding is:
So, I think the first case is already checked. In the case of same name in the |
Sorry, I should have been clearer I was proposing a dataset level check rather than a compiled release level check. In the case of Bandung they don't use |
Aha, yes, consistent party name-ID pairs across contracting processes is a good check. |
This issue is also present in the UK FTS data, e.g.
|
In the Bandung data there are examples where the same identifier is used for different organization names and also examples where different identifiers are used for the same organization name, e.g.
It would be good to have checks for these issues in Pelican.
The text was updated successfully, but these errors were encountered: