Skip to content
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

Find a new way of storing non-sanction adverse info #334

Open
pudo opened this issue Jul 27, 2023 · 3 comments
Open

Find a new way of storing non-sanction adverse info #334

pudo opened this issue Jul 27, 2023 · 3 comments
Labels

Comments

@pudo
Copy link
Member

pudo commented Jul 27, 2023

We have a few data sources where we use the Sanction schema to describe non-sanction adverse information, such as a procurement debarment, a criminal record or a regulatory penalty. We should have a new schema type - of which Sanction is maybe a sub-type - for those sorts of facts.

@pudo pudo added the schema label Jul 27, 2023
@brrttwrks
Copy link

I've been facing this a bit and agree, that some form of 'fine' 'rebuke' 'penalty' or more broadly 'assessment', but in most cases (due to our work) negative assessment/judgement/resolution ... I feel we are in thesaurus territory.

@brawer
Copy link
Contributor

brawer commented Aug 18, 2023

What is the next step to make this happen?

@pudo
Copy link
Member Author

pudo commented Aug 19, 2023

I guess we just need a name, and figure out if we want Sanction to be a sub-type of it. Perhaps it also helps to clarify what's really broken about this. In my mind, it's the fact that while we use the term "this company got sanctioned for defrauding the World Bank" it's a different meaning of "sanction" than the US gov coming down on them. The broadest thing is Punishment, I guess.

We'll also have to think about a migration story here, allowing our data re-users to adopt the new schema before we remove the old.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants