Science Score: 10.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
○codemeta.json file
-
○.zenodo.json file
-
○DOI references
-
○Academic publication links
-
✓Committers with academic emails
2 of 16 committers (12.5%) from academic institutions -
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (13.0%) to scientific vocabulary
Last synced: 10 months ago
·
JSON representation
Repository
you're invited to a data party!
Basic Info
- Host: GitHub
- Owner: andrew
- License: gpl-3.0
- Language: Go
- Default Branch: master
- Homepage: https://qri.io
- Size: 37.4 MB
Statistics
- Stars: 0
- Watchers: 2
- Forks: 5
- Open Issues: 0
- Releases: 0
Fork of qri-io/qri
Created over 7 years ago
· Last pushed over 6 years ago
https://github.com/andrew/qri/blob/master/
# [qri](http://qri.io) [](https://qri.io) [](http://godoc.org/github.com/qri-io/qri) [](./LICENSE) [](https://codecov.io/gh/qri-io/qri) [](https://circleci.com/gh/qri-io/qri)Qri Backend and CLI
a global dataset version control system (GDVCS) built on the distributed web## Welcome | Question | Answer | |--------|-------| | "I want to learn about Qri" | [Read the official documentation](https://qri.io/docs/) | | "I want to download Qri" | [Download Qri](https://qri.io/download) | | "I have a question" | [Create an issue](https://github.com/qri-io/qri/issues) and use the label 'question' | | "I found a bug" | [Create an issue](https://github.com/qri-io/qri/issues) and use the label 'bug' | | "I want to help build the Qri backend" | [Read the Contributing guides](https://github.com/qri-io/qri/blob/master/CONTRIBUTOR.md) | | "I want to build Qri from source" | [Build Qri from source](#build) __qri is a global dataset version control system (GDVCS) built on the distributed web__ Breaking that down: - **global** so that if *anyone, anywhere* has published work with the same or similar datasets, you can discover it. - Specific to **datasets** because data deserves purpose-built tools - **version control** to keep data in sync, attributing all changes to authors - On the **distributed web** to make *all* of the data published on qri simultaneously available, letting peers work on data together. If youre unfamiliar with *version control,* particularly the distributed kind, well you're probably viewing this document on [github](https://github.com/qri-io/qri) which is a version control system intended for code. Its underlying technology git popularized some magic sauce that has inspired a generation of programmers and popularized concepts at the heart of the distributed web. Qri is applying that family of concepts to four common data problems: 1. **Discovery** _Can I find data Im looking for?_ 2. **Trust** _Can I trust what Ive found?_ 3. **Friction** _Can I make this work with my other stuff?_ 4. **Sync** _How do I handle changes in data?_ Because qri is *global* and *content-addressed*, adding data to qri also checks the entire network to see if someone has added it before. Since qri is focused solely on datasets, it can provide meaningful search results. Every change on qri is associated with a peer, creating an audit-able trail you can use to quickly see what has changed and who has changed it. All datasets on qri are automatically described at the time of ingest using a flexible schema that makes data naturally inter-operate. Qri comes with tools to turn *all* datasets on the network into a JSON API with a single command. Finally, all changes in qri are tracked & synced. ## Packages Qri is comprised of many specialized packages. Below you will find a summary of each package. | Package | Go Docs | Go Report Card | Description | |---------|---------|----------------|-------------| | [`actions`](https://github.com/qri-io/qri/tree/master/actions) |[](https://godoc.org/github.com/qri-io/qri/actions) |
[](https://goreportcard.com/report/github.com/qri-io/qri) | functions that call to the repo to carry out tasks | | [`api`](https://github.com/qri-io/qri/tree/master/api) | [](https://godoc.org/github.com/qri-io/qri/api) | [](https://goreportcard.com/report/github.com/qri-io/qri) | user accessible layer, primarily made for communication with our frontend webapp | | [`cmd`](https://github.com/qri-io/qri/tree/master/cmd) | [](https://godoc.org/github.com/qri-io/qri/cmd) | [](https://goreportcard.com/report/github.com/qri-io/qri) | our command line interface | | [`config`](https://github.com/qri-io/qri/tree/master/config) | [](https://godoc.org/github.com/qri-io/qri/config) | [](https://goreportcard.com/report/github.com/qri-io/qri) | user configuration details, includes peer's profile | | [`lib`](https://github.com/qri-io/qri/tree/master/lib) | [](https://godoc.org/github.com/qri-io/qri/lib) | [](https://goreportcard.com/report/github.com/qri-io/qri) | takes arguments from the cmd and api layer and forms proper requests to call to the action layer | | [`p2p`](https://github.com/qri-io/qri/tree/master/p2p) | [](https://godoc.org/github.com/qri-io/qri/p2p) | [](https://goreportcard.com/report/github.com/qri-io/qri) | the peer to peer communication layer of qri | | [`repo`](https://github.com/qri-io/qri/tree/master/repo) | [](https://godoc.org/github.com/qri-io/qri/repo) | [](https://goreportcard.com/report/github.com/qri-io/qri) | the repository: saving, removing, and storing datasets, profiles, and the config | | [`dataset`](https://github.com/qri-io/dataset) | [](https://godoc.org/github.com/qri-io/dataset) | [](https://goreportcard.com/report/github.com/qri-io/dataset) | the blueprint for a dataset, the atoms that make up qri | | [`registry`](https://github.com/qri-io/registry) | [](https://godoc.org/github.com/qri-io/registry) | [](https://goreportcard.com/report/github.com/qri-io/registry) | the blueprint for a registry: the service that allows profiles to be unique and datasets to be searchable | | [`startf`](https://github.com/qri-io/startf) | [](https://godoc.org/github.com/qri-io/startf) | [](https://goreportcard.com/report/github.com/qri-io/startf) | brings starlark into qri to be used in transforms, adds qri specific functionality | | [`starlib`](https://github.com/qri-io/starlib) | [](https://godoc.org/github.com/qri-io/starlib) | [](https://goreportcard.com/report/github.com/qri-io/starlib) | the starlark standard library available for qri transform scripts | | [`qfs`](https://github.com/qri-io/qfs) | [](https://godoc.org/github.com/qri-io/qfs) | [](https://goreportcard.com/report/github.com/qri-io/qfs) | "qri file sytem" is Qri's file system abstraction for getting & storing data from different sources | | [`ioes`](https://github.com/qri-io/ioes) | [](https://godoc.org/github.com/qri-io/ioes) | [](https://goreportcard.com/report/github.com/qri-io/ioes) | package to handle in, out, and error streams: gives us better control of where we send output and errors | | [`dsdiff`](https://github.com/qri-io/dsdiff) | [](https://godoc.org/github.com/qri-io/dsdiff) | [](https://goreportcard.com/report/github.com/qri-io/dsdiff) | the dataset diffing package | | [`jsonschema`](https://github.com/qri-io/jsonschema) | [](https://godoc.org/github.com/qri-io/jsonschema) | [](https://goreportcard.com/report/github.com/qri-io/jsonschema) | used to describe the structure of a dataset, so we can validate datasets and determine dataset interop | ### Outside Libraries The following packages are not under Qri, but are important dependencies, so we display their latest versions for convenience. | Package | Version | |--------|-------| | `ipfs` | [](https://github.com/ipfs/go-ipfs/) | ### Building From Source To build qri you'll need the [go programming language](https://golang.org) on your machine. ```shell $ go get github.com/qri-io/qri $ cd $GOPATH/src/github.com/qri-io/qri $ make build $ go install ``` If you are building from source by cloning the repo, make sure to clone the repo to your go path: `$GOPATH/src/github.com/qri-io/qri`. The `make build` command will have a lot of output. That's good! Its means it's working :) It'll take a minute, but once everything's finished a new binary `qri` will appear in the `$GOPATH/bin` directory. You should be able to run: ```shell $ qri help ``` and see help output. ###### This documentation has been adapted from the [Cycle.js](https://github.com/cyclejs/cyclejs) documentation.
Owner
- Name: Andrew Nesbitt
- Login: andrew
- Kind: user
- Location: Bristol, UK
- Company: @ecosyste-ms and @octobox
- Website: https://nesbitt.io
- Twitter: teabass
- Repositories: 357
- Profile: https://github.com/andrew
Working on mapping the world of open source software @ecosyste-ms and empowering developers with @octobox
GitHub Events
Total
Last Year
Committers
Last synced: 10 months ago
Top Committers
| Name | Commits | |
|---|---|---|
| b5 | s****0@q****o | 610 |
| Kasey | k****a@g****m | 247 |
| Dustin Long | me@d****o | 123 |
| Thomas Osterbind | t****m@q****o | 25 |
| Brendan O'Brien | b****q@g****m | 23 |
| Thomas Osterbind | o****t@o****u | 17 |
| Adrian Lanzafame | a****2@g****m | 2 |
| Marcus Willock | c****m@g****m | 2 |
| Mat Kelly | m****1@g****m | 2 |
| Thomas Osterbind | o****t@u****m | 2 |
| Brett Waugh | b****2@g****m | 1 |
| Eben Pendleton | 4****p@u****m | 1 |
| Mat Kelly | m****y@c****u | 1 |
| Zack Mullaly | z****k@r****t | 1 |
| hexagon6 | h****6@f****i | 1 |
| il-dar | 3****r@u****m | 1 |
Committer Domains (Top 20 + Academic)
Issues and Pull Requests
Last synced: 10 months ago
All Time
- Total issues: 0
- Total pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Total issue authors: 0
- Total pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 0
- Pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Issue authors: 0
- Pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0