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.

Sign up for GitHub

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

Jump to bottom

Add documentation about using Crick with Watson #165

Open
4 tasks
jmaupetit opened this issue Aug 3, 2017 · 3 comments
Open
4 tasks

Add documentation about using Crick with Watson #165

jmaupetit opened this issue Aug 3, 2017 · 3 comments
Labels
easy pick improvement

Comments

@jmaupetit
Copy link
Contributor

Purpose

We recently open-sourced Crick and there is only sparse documentation about how Watson & Crick talk to each other. Let's clarify this!

Proposal

We should work on:

  • Add basic documentation in the README.md
  • Improve the sync command documentation
  • Improve the backend section of docs/user-guide/configuration.md
  • Improve the overview section of docs/index.md
@3ynm
Copy link

3ynm commented Sep 4, 2017 •
edited
Loading

Yup! this is needed. I want to export watson data for creating my own view (not crick) and probably the sync command would help a lot, but I don't know how it works :(

Also, please try to not bloat the code of watson because of coupling other tools, "high-cohesion, low-coupling". Thanks for this SW :)

This was referenced Jan 26, 2019
Open
Open
Open
Open
@3ynm
Copy link

3ynm commented Aug 27, 2020

Apparently crick is a dead project? Still we could use this functionality to extract data, plz let us know how

@jmaupetit
Copy link
Contributor Author

Basically, the sync command performs a pull and then a push to a crick server. I invite you to read the code in the meantime:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
easy pick improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jmaupetit @3ynm