-
Notifications
You must be signed in to change notification settings - Fork 490
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
API development: read sensitive data and write privacy preserving metadata for OpenDP privacy tools #7158
Comments
Regarding writing privacy-preserving metadata, this doc describes several considerations: https://docs.google.com/document/d/1q0Upg3Pa5lP1Gq5TxEzm9BYtA5G8PaqAx7o4WfKPo4U/edit |
DP = Differentially Private DP-related APIs for Dataverse(1) API: Deposit DP Release Data
(1a) Origination/Provenance
(1b) Future consideration: Multiple ReleasesIn the next phase, multiple releases may be created for each Dataverse file. There should be provision to store data/files for each release. Example:
(1c) Future consideration: Building on Previous DDIsDiscuss whether DP DDIs should be “cumulative”, building on previous DP DDIs. In the (simplistic) example above:
An example of a “cumulative” Release 2, DP DDI would be:
(2) API: Retrieve DP Release Data
(3) API: Retrieve User Information
(4) API: Messaging
|
Closing in favor of this issue: |
New APIs are needed for using OpenDP to provide differentially private releases of metadata to Dataverse. First we need to define and finalize the APIs needed for the immediate minimum viable product under development for October. This issue is the placeholder to further define this need.
Currently anticipate OpenDP tool with read private metadata and dataset, and later write privacy-preserving (public) metadata in three formats (full form in JSON, reduced form in DDI schema in XML, and PDF/A file presenting a human readable summary report).
The text was updated successfully, but these errors were encountered: