datatogether/dataset_registries

Tracking the design and implementation of the metadata registries we will use to track rescued datasets

Data Together

Data Together empowers people to create a decentralized civic layer for the web, leveraging community, trust, and shared interest to steward data they care about.

Find out about who we are, what we do, and how to get involved at https://datatogether.org/)!

Organizational structure

We maintain pretty light governance but commit to an annual in-person meeting and quarterly calls:

Quarterly Calls

Quarterly calls are held four times annually, for everyone, but especially Data Together partners to sync up on ongoing projects, what is going on in their organizations, and more.

📅 Once per quarter
▶️ Call Playlist: youtube.com/playlist?list=PLtsP3g9LafVul1gCctMYGm9sz5FUWr5bu

Working Openly

We have developed guidelines for working as an open project, these are all contained in this repo:

• Volunteer Code of Conduct
• Contributing Guidelines
• Hosting Calls, Onboarding, and Project Guidelines

License

Data Together Documentation Materials are licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

dataset_registries's Issues

Still current?

Mostly empty and 8 months old. Do we want to invest in this repo?

Compare the Metadata that Different Groups have about the Datasets They have Rescued

In order to design a simple, practical, first-pass metadata format for tracking these datasets.

Information we will want the registries to keep track of:

• Which datasets have been downloaded
• Where they were downloaded from
• Who downloaded them
• Where they are available -- http links, ipfs links, dat links, etc
• If the download was vetted for authenticity. If so, then how it was vetted.
  • for example, thus far EDGI has only posted a fraction of the downloaded datasets on datarefuge.org because that CKAN instance only contains stuff that has been vetted using a documented process. We want the registries to show everything, including the stuff that was not vetted, but we want to be able to distinguish between vetted stuff and un-vetted stuff.

Note: a lot of datasets have been downloaded multiple times by different people. We need to represent "these are both versions of the same dataset" without losing info about where they are and who downloaded them.

ok to archive this repo?

Add README and Templates

Make sure this repo has the following files:

• Readme README.md
  • Repo Badges for: Github Project, Slack, License
  • 1-3 sentence description of repository contents
  • Getting Involved section
  • Development section
• License -- LICENSE
• Contributing Guidelines (minimal and pointing to org-wide) .github/CONTRIBUTING.md
• Issue Template -- .github/ISSUE_TEMPLATE.md skipping for now
• GitHub Description from 1-3 sentence readme blurb

This issue forms part of a project-wide meta-issue