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

Data Caveats and User Authorization #96

Open
joffreypeters opened this issue Aug 22, 2018 · 0 comments
Open

Data Caveats and User Authorization #96

joffreypeters opened this issue Aug 22, 2018 · 0 comments

Comments

@joffreypeters
Copy link
Contributor

Description
Some government data comes with caveats: for example FOUO or PROPIN which stand for "for official use only" and "proprietary information" respectively. This data should be handled differently in some circumstances, and in some cases should not be accessible by certain users. These data sources' caveats should be traced through the system and applied to final products where relevant. If possible and within the scope of this project, access should be restricted to unauthorized users.

Additional context
Classification and caveat markings are required in many government use contexts. For example, a data product which includes an FOUO data source, but for which all data sources are unclassified should be marked as (U//FOUO) or (UNCLASSIFIED//FOUO), so that users are aware of classification and caveats and can treat that data appropriately.

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

No branches or pull requests

2 participants