Add citations of papers citing our pkgs to our website

[sckott]

We're racking up a good number of citations now to our pkgs.

We should highlight these on our site.

We could do a single page for this, and on the pkgs page have a tooltip or similar that shows citations for each pkg?

[sckott]

see https://github.com/ropensci/docs_private/tree/master/ropensci_mentions for pdfs and other mentions

[karthik]

Great idea. Some ideas:

1. Perhaps at the bottom of tutorial pages since they are for individual packages.
2. Create a per package landing page (like CRAN) but cleaner and easier to evaluate (status, usage, activity etc).

I like the second idea and it would be a good next update to the way we do things.

[cboettig]

I really like the ropensci API thing Scott's been working on -- it seems like it would be nice to also aggregate this kind of thing (citation statistics for each package, or perhaps the DOI of each paper citing that package); along with the other stats we can already generate automatically or semi-automatically. With such a database / API in place, we could automatically populate the details in a per-package landing page (kinda like we have for the dashboard currently).

Maybe that's overkill and too much work, but long term I think having a centralized database we keep up-to-date and other things pull data from there is a nice way to go. Presumably it would also streamline the process of tabulating up metrics we need to report for grants, etc.

On Tue, Aug 11, 2015 at 9:38 AM Karthik Ram [email protected] wrote:

Great idea. Some ideas:

1. Perhaps at the bottom of tutorial pages since they are for individual packages.
2. Create a per package landing page (like CRAN) but cleaner and easier to evaluate (status, usage, activity etc).

I like the second idea and it would be a good next update to the way we do things.

— Reply to this email directly or view it on GitHub https://github.com/ropensci/roweb/issues/197#issuecomment-129960016.

http://carlboettiger.info

[sckott]

@karthik I also like the per pkg landing page (e.g., http://ropensci.org/pacakges/rfishbase) - do we want to be very deliberate about the styling for the page? or get something up quickly? i assume the former

@cboettig right, could easily put in the API, something like http://<ip>/<pkg name>/citations (e.g., http://<ip>/rfishbase/citations). The data that goes in: probably a CSL style citation, a DOI (if available), link to full text, any other useful info

[sckott]

we may want to consider blog posts too, perhaps a subset that are more interesting/etc.