IQSS logo

IRC log for #dataverse, 2014-12-04

Connect via chat.dataverse.org to discuss Dataverse (dataverse.org, an open source web application for sharing, citing, analyzing, and preserving research data) with users and developers.

| Channels | #dataverse index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

All times shown according to UTC.

Time S Nick Message
01:04 axfelix joined #dataverse
02:54 axfelix joined #dataverse
03:17 garnett joined #dataverse
04:39 skay joined #dataverse
14:32 pdurbin shauna: I'm thinking that rather than a WelcomeBot I could just set up a cron job to query my database for new nicks on a regular basis and email me (or something) if someone new joins.
14:57 shauna pdurbin: how often do you check your email?  for me, the value of the bot is that it tells me (and Mark and Asheesh) right away if someone's there, so in the majority of cases we can respond right away.
14:57 shauna usually if the person leaves anyway at that point, there's nothing we can do since we don't have any other contact info.  Although the bot does tell people to email us and I'd say maybe 1-5% of the people it greets do that.
14:59 shauna Anyway, of course you can capture some of the functionality of the bot in other ways.  Up to you.  :)
16:27 pdurbin :)
16:28 pdurbin shauna: I'll keep thinking about it.
16:31 axfelix joined #dataverse
16:33 pdurbin who wants to talk about Search APIs?
16:33 pdurbin axfelix balo jeffspies_ JonathanNeal LyndsySimon mjturk shauna skay ^^
16:33 * LyndsySimon wakes up, blinks, and looks around.
16:34 pdurbin Search API Functional Requirements Document https://docs.google.com/document/d/1FfB4hX2FE-xVRzDpW9UcV7-FBN2vWd4cIpAbI_GtRWY/edit?usp=sharing
16:34 LyndsySimon Search isn't really an area where I have a ton of expertise, but API design is something I'm fairly passionate about.
16:34 * pdurbin is passionate about both :)
16:52 pdurbin skay: you are on it!
16:52 pdurbin thanks!
16:52 skay I blame orbitz -- I learned a lot about api stuff there
16:53 pdurbin thank you orbitz
16:57 skay pdurbin: for restricting size of responses via limiting fields -- the youtube api is an example of it in practice. and it's probably discussed in http://apigee.com/about/resources/ebooks/web-api-design but I cannot recall
16:58 skay pdurbin: and for pragmatism versus dogmatism you'll make choices about whether a client should use http headers for some things versus using query params.
16:58 skay pdurbin: query params are friendlier
16:58 skay pdurbin: makes it easier for a dev to do a sanity check in a browser
16:58 skay pdurbin: versus having to find some browser extension to make it easy to set http headers
16:58 skay or typing them all ont he commandline with curl
16:59 skay pdurbin: why yes, we did get in to some heated debates about pragmatism, why do you ask? ;)
17:00 skay pdurbin: I don't know how big your search respones get in general, so don't overthink how you want to control for payload size in ways such as using compression or also providing adapters to return bit-packed things
17:02 skay oh, I just saw your response about path to file versus path to landing page.
17:03 skay pdurbin: ugh, I wonder if there is a precedent for designing an action in an api that is equivalent to agreeing with a policy. if an api exchange can be valid, then maybe you could have something like:
17:03 * skay thinks, maybe go make this commend in the doc
17:10 skay pdurbin: I'm heading mentally back to work now. ttyl
17:24 mjturk pdurbin: hiya, sorry, for some reason that didn't highlight me
17:25 mjturk not sure i have much to contribute tho :)
17:30 JonathanNeal Search API's? Depends on the context
17:44 pdurbin JonathanNeal: we're designing one
17:44 pdurbin mjturk: no worries. good morning :)
17:44 mjturk pdurbin: you too :)
18:02 pdurbin LyndsySimon: does OSF have a Search API?
18:06 pdurbin or... what is everyone's favorite Search API?
18:07 pdurbin this might be a better question for #rest
18:10 axfelix joined #dataverse
18:30 skay I have love/hate relationships with search apis and have trouble answering hte question
18:30 axfelix joined #dataverse
18:31 skay I feel frustration with any api I use. e.g. I told you how the youtube api gives options for next page tokens and also has clients explictely specify which fields should get returned
18:31 pdurbin skay: you're off the hook, having helped so much already :)
18:31 skay so, it's an example of that in operation. but, I admit I seriously get pissed off at that api and their stuff in general
18:31 skay it seems clear as mud
18:31 skay I have to dig around to figure out what I want
18:32 skay I had to experiment with the api to see how to get a list of videos from a channel versus playlist versus whatnot
18:32 skay pdurbin: oh thanks. I'm relieved
18:32 skay pdurbin: derp. I realize I clicked on yoru doc and used my canonical identity. I thought I was using my plain old gmail one. no big deal
18:33 * pdurbin doesn't know the difference
19:18 axfelix joined #dataverse
19:21 garnett joined #dataverse
19:28 axfelix joined #dataverse
19:38 axfelix joined #dataverse
19:52 pdurbin Dataverse Project Receives New Sloan Grant to Expand API Integration to More Journals and Publishing Systems - https://groups.google.com/forum/#!topic/dataverse-community/GrcmcFNgchI
19:52 pdurbin axfelix: hooray!
19:56 mjturk congrats!
20:11 skay \o/
20:11 pdurbin :)
20:56 axfelix joined #dataverse
21:45 axfelix eleni told me! super exciting
21:45 pdurbin yep!
23:18 axfelix joined #dataverse
23:19 axfelix joined #dataverse
23:31 garnett joined #dataverse
23:39 pdurbin ah, and here's our blog post about it: A Bridge from Publishing Words to Publishing Data | Data Science - http://datascience.iq.harvard.edu/blog/bridge-publishing-words-publishing-data
23:42 pdurbin fightin' words about SWORD, almost

| Channels | #dataverse index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

Connect via chat.dataverse.org to discuss Dataverse (dataverse.org, an open source web application for sharing, citing, analyzing, and preserving research data) with users and developers.