{"action":"created","issue":{"url":"https://api.github.com/repos/sckott/traitdb/issues/1","repository_url":"https://api.github.com/repos/sckott/traitdb","labels_url":"https://api.github.com/repos/sckott/traitdb/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/sckott/traitdb/issues/1/comments","events_url":"https://api.github.com/repos/sckott/traitdb/issues/1/events","html_url":"https://github.com/sckott/traitdb/issues/1","id":191385496,"number":1,"title":"Feedback?","user":{"login":"sckott","id":577668,"avatar_url":"https://avatars.githubusercontent.com/u/577668?v=3","gravatar_id":"","url":"https://api.github.com/users/sckott","html_url":"https://github.com/sckott","followers_url":"https://api.github.com/users/sckott/followers","following_url":"https://api.github.com/users/sckott/following{/other_user}","gists_url":"https://api.github.com/users/sckott/gists{/gist_id}","starred_url":"https://api.github.com/users/sckott/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sckott/subscriptions","organizations_url":"https://api.github.com/users/sckott/orgs","repos_url":"https://api.github.com/users/sckott/repos","events_url":"https://api.github.com/users/sckott/events{/privacy}","received_events_url":"https://api.github.com/users/sckott/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":18,"created_at":"2016-11-23T21:39:32Z","updated_at":"2016-12-09T16:31:12Z","closed_at":null,"body":"rather than filling your inbox with another email, pinging you fine folks here:\r\n\r\n@ethanwhite @cboettig @dfalster @dlebauer @ibartomeus @wcornwell \r\n\r\nI'd love your feedback on this thing\r\n\r\n## What it is and why\r\n\r\nTrait data seems to be one of the most locked down bits of the data ecosystem. Datasets are out there but often in supplemental materials, etc. that are hard to discover. \r\n\r\nThis service aims to be primarily an REST API that can be searched for datasets based on \r\n\r\n* taxonomy\r\n* location\r\n* trait type\r\n* general search across all fields\r\n\r\nI got a Amazon research grant for $500 credits for https://github.com/sckott/gbids but it's not seeing much use as I thought it would get. So i'm trying to pivot to this idea, which i've been thinking about for some time. \r\n\r\nThere's description of the API at https://github.com/sckott/traitdb#api \r\n\r\n* Dataset metadata is gathered, and is at https://traits.party/datasets/\r\n* Individual dataset routes https://traits.party/datasets/z85a07642-9f49-408c-a16f-f71135d9450f give metadata for the single dataset\r\n* `/:datasetid/fields` https://traits.party/datasets/z85a07642-9f49-408c-a16f-f71135d9450f/fields/  gives the fields in the dataset\r\n* `/fetch` https://traits.party/datasets/z85a07642-9f49-408c-a16f-f71135d9450f/fetch retrieves the entire dataset from S3\r\n* the `/search` route (not running yet) searches across all datasets\r\n* the `/:datasetid/search` route (not running yet) searches in a given dataset\r\n\r\nBoth `/search` routes are based on Elaticsearch, and current plan has the entire datasets loaded into ES. I don't think this will scale for sure, so evaluating other options while still allowing searching datasets. The stuff returned from this route are the actual records (aka rows) of data from the datasets, so one can get just the records they want based on some search. \r\n\r\nThere's only 6 datasets in there now, as I evaluate what works and what doesn't, and get feedback for you :)\r\n\r\nI haven't yet cleaned up/standardized these but will be useful once done: \r\n\r\n* taxonomy\r\n* geolocation (lat/long, or similar)\r\n* place names\r\n* other things?\r\n\r\nThen we could allow search specifically on those elements instead of just a full text search across all. \r\n\r\nThere is no website for this yet, but could make one on top of the API, for users that prefer a GUI. \r\n\r\n## What do you think?\r\n\r\n* Do you think people will use this?\r\n* Any issues you see with licensing/etc? All Dryad datasets are CC0, and I've been using those so far. AFAIK supp. ESA jourjals datasets are CC licensed, so I think those are all fair game as well\r\n* Would it be better to not actually serve datasets, but only be a discovery service?  \r\n* If this was to narrow focus, what would be of the most benefit to the most people?\r\n* other things?\r\n"},"comment":{"url":"https://api.github.com/repos/sckott/traitdb/issues/comments/266057496","html_url":"https://github.com/sckott/traitdb/issues/1#issuecomment-266057496","issue_url":"https://api.github.com/repos/sckott/traitdb/issues/1","id":266057496,"user":{"login":"dlebauer","id":464871,"avatar_url":"https://avatars.githubusercontent.com/u/464871?v=3","gravatar_id":"","url":"https://api.github.com/users/dlebauer","html_url":"https://github.com/dlebauer","followers_url":"https://api.github.com/users/dlebauer/followers","following_url":"https://api.github.com/users/dlebauer/following{/other_user}","gists_url":"https://api.github.com/users/dlebauer/gists{/gist_id}","starred_url":"https://api.github.com/users/dlebauer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dlebauer/subscriptions","organizations_url":"https://api.github.com/users/dlebauer/orgs","repos_url":"https://api.github.com/users/dlebauer/repos","events_url":"https://api.github.com/users/dlebauer/events{/privacy}","received_events_url":"https://api.github.com/users/dlebauer/received_events","type":"User","site_admin":false},"created_at":"2016-12-09T16:31:12Z","updated_at":"2016-12-09T16:31:12Z","body":"@zachary-foster Although I am not working with species occurance / abundance data (I don't know if this is within scope for a 'trait' database but it seems that it could fit).\r\nSo we are coming from different perspectives but your comment \"observational studies vs experimental studies could be a useful distinction\" is an interesting question that could be discussed in a separate thread on schema design. And I am interested in the useful level of generalization.\r\n\r\nThe key issue here is that the definition of an 'observational' vs. 'experimental' and even the definition of the experimental design depends on the questions being asked. And the fact that there are almost as many experimental designs as there are studies means that there is some effort to harmonize data collected with different goals. A meta-analysist may have different questions than the original researcher and the original questions may not be relevant to the meta-analysis. Harmonization can include abstracting the experimental treatments into covariates that can be compared across studies."}}
{"actor":{"display_login":"dlebauer"}}