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

Service to dump bibliographic information #33

Open
jar398 opened this issue Mar 20, 2013 · 4 comments
Open

Service to dump bibliographic information #33

jar398 opened this issue Mar 20, 2013 · 4 comments

Comments

@jar398
Copy link
Member

jar398 commented Mar 20, 2013

For a variety of purposes it would be useful to have a service that does the following query:

select id, doi, treebase_id, citation from study

returning the result in any conveniently machine-readable syntax, such as JSON.

@pmidford
Copy link
Contributor

I can take this. So you want all the studies (no where clause?)

@jar398
Copy link
Member Author

jar398 commented Mar 21, 2013

On Wed, Mar 20, 2013 at 8:01 PM, Peter Midford [email protected]:

I can take this. So you want all the studies (no where clause?)

Yes, all the studies.

Actually I think it should include all the columns, speculatively, so I
don't have to go back and update the service later if I find I need
something else. As a CSV it's only on the order of 100K, so why not - it
probably won't grow more than 10x, and this service won't be called all
that often.

Thanks
Jonathan

Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-15211788
.

@jar398
Copy link
Member Author

jar398 commented Mar 22, 2013

This looks almost the same as #34 (which is closed)

@pmidford
Copy link
Contributor

It appears that github generates a new issue when you create a pull request (there are other closed issues for previous pull requests). So to be precise, issue 34 is the request to merge the fix for issue 33. This doesn't seem like desirable behavior, maybe there's a way to use pull requests without generating new issues (or at least the option to link back to previous issues).

-Peter

On Mar 22, 2013, at 4:12 PM, Jonathan A Rees [email protected] wrote:

This looks almost the same as #34 (which is closed)


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants