[super] Social sharing for datasets (and resources)

[rgrp]

Add a way to share datasets and see mentions of datasets on twitter (and elsewhere)

As a visitor I want to share a link to a dataset I have found. I also want to see how many others have shared this (or mentioned it).

• Sharing platform: simplest option is probably twitter but could generalize to e.g. sharethis system which supports, facebook, twitter etc etc.
  • Will need a config option for relevant API key e.g. ckan.sharethis.apikey
• Location: Put this at top of sidebar on dataset view (a better suggsetion?)
• Should show how many mentions / shares there are. (very important!)

Discussion

• (Tom and Ira and ...): do we really want this, versus e.g. proper follow extension?
• What about bringing conversation back in to CKAN. E.g. show all times this dataset (i.e. its url) was mentioned on twitter. If we do this I think this should be definite +1.
• Also, given our users, I think just doing twitter (identica) may be sufficient (how many people want to share links to datasets on facebook?)

[rgrp]

Unsure of importance. Probably fairly low but also fairly cheap to do. However, reckon we should defer of v1.6 given what else we have.

[toby]

We can supply the following to ShareThis?

• st_url Specifies URL (can be shortened URL) that you would like shared

• st_title Specifies title that you would like shared

• st_image Specifies link to image you would like displayed in the shared content

• st_summary Specifies summary text/description you wish to share

currently we just have the defaults but do we want to set these?

[toby]

config options:

• social.sharethis_api_key

• social.sharethis_style = horizontal | vertical | large | none

• social.sharethis_sites = googleplus twitter facebook email sharethis

Easy to add new sites we just need the ShareThis? name and a description Currently these are all site wide maybe add options for specific templates (via the template not config)

[toby]

style & sites can now be passed by individual templates

[toby]

The url issue wants resolving

when 1.7 released need to

• ensure setup.py setting are complete/correct

• publish to pypi

• check setup instructions work

[rgrp]

Just to check: I thought this was going into core. This really does not need to be an extension (it is so small ...)

[toby]

I've talked to David and we both feel that this should not be a part of core.