Python plugins: return array of event objects

figshare / Total-Impact

Uncovering the invisible impacts of your research.

http://total-impact.org

Other

43 stars 4 forks source link

Python plugins: return array of event objects #12

Closed jasonpriem closed 13 years ago

jasonpriem commented 13 years ago

Python plugins should:

accept a JSON-serialized array of IDs (not just one, as is the case now)
return a JSON-serialized array of events, each of which looks like as described on the plugins wiki page

attn Python plugin authors: @cameronneylon @cdparra @hpiwowar

hpiwowar commented 13 years ago

The crossref plugin does this now. I'll try to get one other plugin to do it in the next day or two, and the rest shortly after.

hpiwowar commented 13 years ago

Shall we make the "url" dictionary value be a list rather than a single element? That way if papers have multiple url synonyms (doi lookup urls, landing pages, even shortened versions) they can all be included for searches.

jasonpriem commented 13 years ago

Yes, definitely, but I think that's an after-alpha issue...for now we're probably only dealing with CrossRef.

On 06/03/2011 12:36 PM, hpiwowar wrote:

Shall we make the "url" directory value be a list rather than a single element? That way if papers have multiple url synonyms (doi lookup urls, landing pages, even shortened versions) they can all be included for searches.

hpiwowar commented 13 years ago

that works. one thought is that we might want to define it as a list right now (that has a maximum of 1 element in current implementation), to avoid moving to a list in the future and breaking existing plugins. if it is easy. from the plugin side it is easy :)

jasonpriem commented 13 years ago

It is pretty easy, but I've got to leave for Paris in like 20hrs and I'm getting a little tight for time...how about we do it toward the end, if we have time?

On 06/03/2011 01:14 PM, hpiwowar wrote:

that works. one thought is that we might want to define it as a list right now (that has a maximum of 1 element in current implementation), to avoid moving to a list in the future and breaking existing plugins. if it is easy.

hpiwowar commented 13 years ago

ok :)

On Fri, Jun 3, 2011 at 10:19 AM, jasonpriem < reply@reply.github.com>wrote:

It is pretty easy, but I've got to leave for Paris in like 20hrs and I'm getting a little tight for time...how about we do it toward the end, if we have time?

On 06/03/2011 01:14 PM, hpiwowar wrote:

that works. one thought is that we might want to define it as a list right now (that has a maximum of 1 element in current implementation), to avoid moving to a list in the future and breaking existing plugins. if it is easy.

Reply to this email directly or view it on GitHub: https://github.com/mhahnel/Total-Impact/issues/12#comment_1298121

jasonpriem commented 13 years ago

creating URLs-as-lists as a separate issue