CKAN: Ticket Query

#2315: Change Cookie expiry

dread — Fri, 20 Apr 2012 10:57:29 GMT

Change login cookie from a default expiry of 50 years to 2 years. You can also uncheck a 'remember me' checkbox on the login form for the cookie to just last the session.

Background conversation on ckan-dev:

DR: I wonder if anyone objects to the expiry of the login cookie to be changed from 50 years to 2 years? 50 years might be appropriate for thedatahub.org, but for government sites it seems (to me) to be too lax.

Toby: is this the repoze.who cookie? If so that seems sensible to me.

Rufus: Definitely agree. I would also like to see introduction of a standard "remember me" checkbox (set to true by default). At the moment a login lasts forever (until you logout) automatically.

#2325: Format alphabet pager (tags page) for bootstrap

dread — Wed, 25 Apr 2012 15:01:50 GMT

Also need to fix bug where 'Other' is never highlighted.

#2285: Data Previewer / Viewer v3 : Embedding! - /resource/../embed

icmurray — Thu, 12 Apr 2012 11:40:10 GMT

Allow a user to embed the data viewer in their webpage.

[x] Embedding widget [1d]

[x] The embed page [1-2d]

[x] Documentation and Announce [0.5d]

Depends upon:

[x] Recline improvements ?d

All the above, plus user stories are fleshed out in [1]

[1] http://ckan.okfnpad.org/feature-2283-data-viewer-v3?

#2307: Merge 1.6.1 into master

icmurray — Mon, 16 Apr 2012 15:50:02 GMT

There are a number of features developed against 1.6.1 that need to be merged into master.

#2308: Merge facet html snippets in the multi-lingual branch

icmurray — Mon, 16 Apr 2012 15:52:09 GMT

Seanh and icmurray both touched on the html snippets in facets.html. So there's a merge issue. icmurray to merge changes in the multi-lingual branch prior to merging into master.

#2269: EC ODP review and server setup

johnglover — Mon, 02 Apr 2012 13:42:57 GMT

code review with D.R. for ckanext-ecportal
merge and test all multilingual code
fix server issues: routing, Git access to CKAN repository

Bugs to fix:

~~rename groups to publishers~~
~~update home page layout (recent updates along side publishers)~~
~~don't add 'en' to main menu links if english~~
~~resource edit page, fix missing images~~
~~change dataset 'settings' to 'edit'~~
~~translate 'published by' drop-down list~~
~~fix JS on 'add a dataset page'~~
~~prepopulate 'published_by' when clicking 'add a dataset' from group~~
~~chosen broken (dataset edit) if in different language~~

#2306: Updates to metadata model

johnglover — Mon, 16 Apr 2012 14:54:46 GMT

Finalised metadata model requires several changes to our existing model:

new extra: alternative title
new extra: identifier
new extra: interop level
new extra: version description
new extra: dataset status
dataset type: change to fixed vocab
resource types: prefix with documentation/distribution/etc for clarity, add new resource types
rename update frequency to accrual periodicity
add new fixed vocab field: language coverage
resources: missing issued date - add as new core field called 'created'

Also add functional tests for full metadata model.

#2327: Upgrade solr schema to version 1.4

kindly — Wed, 25 Apr 2012 17:29:33 GMT

Add Ascii folding filter to text fields.
Add capacity field for public, private access.
Add title_string so you can sort alphabetically on title.
Fields related to analytics, access and view counts.
Add data_dict field for the whole package_dict.

Actual implementation of data_dict adding will be added later.

#2292: Group edit form no longer allows for adding of multiple datasets at once

rgrp — Sat, 14 Apr 2012 19:23:08 GMT

Can only add one dataset at a time now (not sure when this broke but was working ~2-3m ago).

Assigning to seanh for review and estimation. I'd rate this as quite annoying but not absolutely critical (hence assigned priority).

#2204: [super] Related (Stuff) Extension

rgrp — Sun, 04 Mar 2012 12:09:52 GMT

This is a reworking of the existing apps extension.

Initial proposal at http://wiki.ckan.org/Proposals#Apps_in_CKAN and http://wiki.ckan.org/Proposals#References.2FLinks_in_CKAN

Naming

What do we call this extension?

related
- RP best IMO but perhaps too close to separate relationships concept?
relatedstuff
links
references

Proposal

"Related Stuff": Apps as in an application (website/service/tool) that uses this dataset (as in Apps and Ideas extension)

This case seems a general example of wanting to link some external thing to a dataset (e.g. this policy paper refs this dataset, this application uses this dataset, this visualization is built on this dataset cf http://lists.okfn.org/pipermail/ckan-discuss/2011-August/001607.html)

Implementation

New table named Related with following structure

|| id (int) || type || title || description (markdown) || image_url || owner_id || url || created (timestamp)

type = Idea | App | API | Visualization | Post | Paper | News Article
- Suggest we make this a ckan.ini config option (comma separated ...?)
  - Do we want the possibility of different templates for different types of Related objects?

image: ?? Depends where we store images. Simplest option would be to change to image_url and leave it to users to have already uploaded an image somewhere. If not we need to support image uploading and storage. See #1692 (add image attribute to datasets and groups) for more discussion, once implemented the URL here can be an internal url.

owner_id = user_id or creating user (see authorization below)

Related2Dataset (note that related_id, dataset_id tuple should be unique). This allows for m2m connections. If a given related item is only with one dataset this could be simplified. May contain status so dataset owner can turn this on/off.

|| id || dataset_id || related_id || status

status should be used to allow for a dataset owner (for dataset_id) to de-activate the relationship between the dataset and the related.

Url

/dataset/{dataset-name}/related/{related-item-id}/{related-item-title-stringified}
- If a reference item could exist in its own right (and perhaps refer to multiple datasets then it should get its own url at e.g. /related/{id}
/dataset/{dataset-name}/related/add => Modal dialog on related tab so we can use API to create them.

/dataset/{id}/related <- list

use image_url for small icon etc, title description (shortened?)
Click through to full related item (optional)
dataset owner is shown show / hide button ... (or on /dataset/{id}/related/{id} )
related owner sees an edit button / icon (pops up modal)

/dataset/{id}/related/{id} (optional)

/dataset/{id} will have a Related tab (with bubble with count).

Drop down with Add Related -> Pop-up modal and save via API

(Not used: /related/add with dataset prefilled ... )

/related/{id}/edit

Authorization

Addition of related item be considered orthogonal to datasets (and hence with separate authorization i.e. i can add the info that site X uses dataset Y without needing permission to edit dataset Y).

Thus any logged in user could add a Related item. We set the owner of the related item to creating user and going forward only that user or a sysadmin can update or delete.

NB: we could have a system where datasets owners have to approve related items before they show up next to their dataset. This would add substantial complexity so I propose we leave out of phase 1.

Tasks and estimates {7.5d}

[x] Model + Migration for Related table. {0.75d}

[x] Controller for Related (or relevant sections in Package controller). {0.75d}

[x] Routing setup. {0.25d}

[x] Schema for related. {0.5d}

[x] Logic layer actions. {1.0d}

[x] Auth (default + publisher). {0.5d}

[x] Templates + Dataset changes (new tab etc). {1.0d}

[x] JS Application for adding Related objects in a modal. {1.0d}

[x] Testing. {0.75d}

[x] Dataset owner disabling of Related (via M2M table). {0.5d}

Updated to allow author of related to delete as well

[x] Documentation. {0.25d}

#2239: EC ODP RDF/N3 templates

ross — Mon, 19 Mar 2012 15:08:23 GMT

Implement the EC/ODP template for RDF to match the requested schemas.

Using the previous work on allowing for templatised RDF representations we should implement the proposed schema for EC/ODP.

We also agreed to allow upload of RDF as an extra (raised to top level in package schema) which will instead be used for the RDF template. On insertion extra CKAN triples will be added... initially this is just owl:sameAs although we're awaiting EC/ODP agreement on which triples we should add to show the CKAN link.

#2255: Organizations (Privacy + Ownership)

ross — Thu, 22 Mar 2012 11:53:38 GMT

[x] The publisher_form extension and the 'publisher' component of the system will be renamed to organizations to both make its functionality clear, and to differentiate it from the publish auth profile.

Ownership of datasets is important and this ticket will enforce membership for a dataset to a single individual organization. The workflow for adding a dataset to a publisher/organization will stay the same but there will be no mechanism for adding existing datasets to an organization from within the organization forms.

[x] New datasets can be created from the organization form, in which case the organization will be set in the dataset form dropdown (with privacy set to private - see below)

[x] Datasets created from direct access to /dataset/new will have a drop down showing all of the organizations available to the current user.

[x] When editing a dataset the organization can only be changed if the current user is the admin of the current organization, and only then to one of the organizations available to the current user.

Only Organization admin can see the edit Organization form.

[x] Privacy will be enforced by changing the dataset form to have a public/private switch next to the organization drop-down which will be set as the capacity with which the dataset is added to an Organization. Private means visible only within the Organization, and should be the default.

[x] Search will be affected as the public/private status of a dataset will need to be added to the schema

[x] Only public datasets showing in site search, and private showing in organization dataset search (if user is within the organization).

[x] Make sure resources are restricted in visibility if the parent dataset is private

[x] Documentation should be updated to reflect these changes.

[x] Verify, then add, then re-add to documentation.

A User joins or creates an Organization

If creator of the Organization User becomes administrator of the Organization otherwise they become a Member.

~~Creation of new Organization must be approved by a System Administrator~~

New Members must be approved by the Organization Administrator

#2280: Move ecportal to organizations, add history template

johnglover — Wed, 04 Apr 2012 15:07:09 GMT

#2303: Move ECPortal rdf dump paster

ross — Mon, 16 Apr 2012 13:24:52 GMT

Move ECPortal rdf dump paster command into core so that it can be run on thedatahub for virtuoso install.

#2274: Review multilingual branch with kindly, merge into master

seanh — Mon, 02 Apr 2012 14:10:04 GMT

#2299: Set Slovakas default language on data.gov.sk

seanh — Mon, 16 Apr 2012 12:25:12 GMT

#2300: Write initial docs for multilingual branch

seanh — Mon, 16 Apr 2012 12:26:03 GMT

#2318: Bug with Portugese translation and Javascript

rgrp — Sat, 21 Apr 2012 18:44:49 GMT

If you switch to Portugese and try to add a resource on dataset edit it will fail. This is because there is a string translation in js_strings.html that has quotes in it. When this is inserted into the file this causes a js exception which then prevents any further js processing.

Specifically:

CKAN.Strings.youHaveUnsavedChanges = "Você tem alterações não salvas. Certifique-se de ter clicado "Salvar Alterações" abaixo antes de sair desta página.";
Uncaught SyntaxError: Unexpected identifier

To fix is simple i imagine: need to escape " correctly in js_strings.html (or translations used).

I have temporarily patched this live in order to allow the hackday here to continue.

#1370: [super] Social sharing for datasets (and resources)

rgrp — Fri, 30 Sep 2011 22:44:46 GMT

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?)

#2311: disqus - improvements

toby — Mon, 16 Apr 2012 17:54:13 GMT

get working on TDH

look at removing stream filters

#2316: add resource status api to see the state of celely tasks

kindly — Sat, 21 Apr 2012 13:47:17 GMT

add resource_status_show action function to see the state of celery tasks.

Need to get information from both out task status table and the celery_taskmeta table.