opengov-opendata/ckanext-discourse

CKAN + Discourse

ckanext-discourse's Issues

properly encode SEO markup so discourse onebox shows extended characters properly

Opengraph markup should encode chars like single quote, etc.

Make discourse.ckan_category parameter smarter

Right now, its only the HTML fragment needed to pull the Discourse JSON of a category, which is then appended to discourse.url to get the fully qualified URL of the category json, e.g.

discourse.url = https://talk.beta.nyc/
discourse.ckan_category = c/data/community-data.json

https://talk.beta.nyc/c/data/community-data.json

It should just be the human-readable name of the category, i.e.

discourse.url = https://talk.beta.nyc/
discourse.ckan_category = Community Data

cc @amercader

Optimized CKAN Oneboxing

Something similar to the way Discourse oneboxes GitHub links, e.g.

For CKAN, maybe metadata like organization, group, maintainer, etc. can be included in the onebox.

This needs to be implemented on https://github.com/discourse/onebox

CORS-like issue, blocks posting topic to discourse

I have followed the instructions on the readme, and currently, I have the Discourse iframe being partly loaded on CKAN. It says 'loading discussion' with my Discourse site logo displayed, then there's a 10 second pause, the message changes to say 'error embedding'.
And the following error appears in Chrome dev console:
Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://discourse-site') does not match the recipient window's origin ('https://ckan-site').

Note that I have SSL enabled on both CKAN and Discourse.

Add Debug setting

preventing ckanext-discourse from actually creating a discourse topic in the associated discourse instance. Instead, it will just display debug data in the iframe.

This should help avoid spam in the associated discourse instance when troubleshooting discourse integration.

Add ckanext-pages support

So users can also create topics on custom pages.

To indicate that a custom page should allow Discourse commenting, the CKAN administrator adds the following snippet (e.g. ">>DISCOURSE<<"??? ) to the markdown text of the page.

Group/organization blacklist

Create a blacklist that ckanext-discourse will ignore. This is good for testing and for excluding datasets where discourse commenting is not required.

ckan discourse extension example

Hi Team,
Can you provide any example for ckan-discourse extension. I have setup a discourse server and installed ckan extension on ckan server. But I not able to see any changes on my ckan server. I want to know how does the commenting look like and what issue can be for me not able to see the comments on my ckan server

Automatically set discourse.topic_suffix using CKAN site title

No need to manually specify it in the CKAN ini file.

Any chance you could share some screenshots?

It would be really helpful to see how the integration between the two apps looks for the end user. How is the forum topic linked from data set?
How is the data set linked from the forum?

Cheers!

Groups and Organization Comments were not being displayed properly

The associated templates need to be tweaked to pass the full_url to ckanext-discourse.

Add comment count to Popular Datasets and Recently Updated homepage widgets

As is done on the internal pages (group, org, package lists).

Do not attempt to create topics for private datasets

Otherwise, ckanext-discourse will fail to create the topic properly in the associated Discourse instance.

Right now, when a private dataset is created in CKAN, the created Discourse topic links to the CKAN login screen, since Discourse is attempting to authenticate access to the private dataset.

KeyError with discourse

CKAN 2.41
psql (PostgreSQL) 9.1.19
Standard source deployment

I recieve the following error after running $python setup.py

[Sun Nov 22 22:35:14 2015] [error] Traceback (most recent call last):
[Sun Nov 22 22:35:14 2015] [error] File "/usr/lib/python2.7/site.py", line 157, in addpackage
[Sun Nov 22 22:35:14 2015] [error] exec line
[Sun Nov 22 22:35:14 2015] [error] File "", line 1, in
[Sun Nov 22 22:35:14 2015] [error] KeyError: 'ckanext'
[Sun Nov 22 22:35:14 2015] [error]
[Sun Nov 22 22:35:14 2015] [error] Remainder of file ignored

Add handling for private datasets

Discussions on private datasets should be supported. While datasets are being reviewed internally, it can be argued that internal folks need to have a place to have those discussions before a dataset release.

This could be done by creating a separate private Discourse category to which private dataset discussions are posted.

An added bonus of this approach is that once a dataset is released, a separate topic post-release is created to which the private discussions pre-release can link to.

Check if discourse.ckan_category exist during plugin configuration

Right now, it only checks if the parameter is not empty.

Allow secure private comments on private datasets

Using a separate private discourse category. See #20 for details.

Auto-notify dataset maintainer of discourse topic creation/replies

Create Discourse plugin to optimize CKAN embedded topics

Right now, the generic embed logic creates a topic that is not that detailed.

It'd be better if the topic description is a Onebox embed of the CKAN page.

Open source ckanext-discourse

after adding additional documentation, testing and cleaning up the code