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

Spike: Identify Existing Repositories that specialize in handling Sensitive Data #8737

Open
2 tasks
mreekie opened this issue May 24, 2022 · 3 comments
Open
2 tasks
Labels
NIH OTA DC Grant: The Harvard Dataverse repository: A generalist repository integrated with a Data Commons NIH OTA: 1.6.2 6 | 1.6.2 | Discovery phase to support DataTags | 10 prdOwnThis is an item synched from the produ... pm.GREI-d-1.6.2 NIH, yr1, aim6, task2: Discovery phase to support DataTag Type: Suggestion an idea

Comments

@mreekie
Copy link

mreekie commented May 24, 2022

This came up during the discussion of the integration with DP Creator as part of exploring short to medium term alternatives to support for dataverse storing higher classifications of sensitive data.

One of the options involves getting the data to DP creator from another data repository - one that specializes in the storage of sensitive data. We believe these exist. Let's identify them.

Definition of done:

  • Identify as many of these repositories as possible.
  • Identify the manner in which we would integrate with them
    • i.e. what protocol standards do they use for harvesting for example.

Context:

  • The idea is to find possibly if other repositories can do the data store.
  • Find out what standards they use for harvesting?

This is the scenario where DV stores the metadata and points to another repository where the data is stored at rest.

@mreekie mreekie added NIH OTA DC Grant: The Harvard Dataverse repository: A generalist repository integrated with a Data Commons pm.Len labels May 24, 2022
@mreekie
Copy link
Author

mreekie commented Sep 22, 2022

Next steps:

  • Take this to the community as well.
  • Use the community to build a list.
  • Or we could go back to datatags?
    • What could be done around data tags requirements under the hood?
    • Separate from this issue.

@stevenmce
Copy link

Hi Mike, ADA specialises in this, and have been working with the DP team on this. Feel free to contact me at the ADA_at_anu_dot_edu_dot_au to discuss. Regards, Steve

@mreekie mreekie added NIH OTA: 1.4.1 4 | 1.4.1 | Resolve OAI-PMH harvesting issues | 5 prdOwnThis is an item synched from the product ... bk2211 and removed NIH OTA: 1.4.1 4 | 1.4.1 | Resolve OAI-PMH harvesting issues | 5 prdOwnThis is an item synched from the product ... labels Oct 25, 2022
@mreekie mreekie added the NIH OTA: 1.6.2 6 | 1.6.2 | Discovery phase to support DataTags | 10 prdOwnThis is an item synched from the produ... label Nov 7, 2022
@mreekie
Copy link
Author

mreekie commented Nov 7, 2022

Moving into the 1.6.2 unordered backlog.
I'm not sure if this is part of this or the follow-up deliverable.

@mreekie mreekie removed the bk2211 label Jan 11, 2023
@mreekie mreekie removed the pm.Len label Feb 7, 2023
@mreekie mreekie added the pm.GREI-d-1.6.2 NIH, yr1, aim6, task2: Discovery phase to support DataTag label Mar 20, 2023
@pdurbin pdurbin added the Type: Suggestion an idea label Nov 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NIH OTA DC Grant: The Harvard Dataverse repository: A generalist repository integrated with a Data Commons NIH OTA: 1.6.2 6 | 1.6.2 | Discovery phase to support DataTags | 10 prdOwnThis is an item synched from the produ... pm.GREI-d-1.6.2 NIH, yr1, aim6, task2: Discovery phase to support DataTag Type: Suggestion an idea
Projects
None yet
Development

No branches or pull requests

3 participants