CKAN: Ticket Query

#2941: Add follower support back into CKAN 2.0

johnmartin — Tue, 25 Sep 2012 14:51:10 GMT

Add the views and functionality of following users and groups into 2.0

#3008: Add tests for dashboard activity stream auth

seanh — Tue, 30 Oct 2012 12:41:00 GMT

We need to test that only logged in users can see their own dashboard activity streams, and they can only see their own dashboard activity streams not those of other users.

#2918: Can't remove users from organizations

ross — Wed, 12 Sep 2012 13:12:52 GMT

When you remove someone, without adding them, the text box at the bottom (which should probably autocomplete) is empty, and this causes problems on the server.

Ideally when you add a user (select from the autocomplete) it would add another row to the table, defaulting the user to editor and setting the names to user{{X}}name and user{{X}}capacity where X is $('tr').size()

#2940: Edit different resources from edit dataset pag

johnmartin — Tue, 25 Sep 2012 13:46:52 GMT

We need a nice way to be able to get to editing the different resources that are associated to a dataset.

#2954: Flickering on resource view when changing between views

johnmartin — Wed, 03 Oct 2012 12:55:16 GMT

From the google doc: When I move between grid, graph and map view mode (or click on filters) the whole data explorer flickers (jumps up & down slightly) for a few moments before settling. This is happening on all resources for me and when you initially open launch the page: http://demo.ckan.org/dataset/afghanistan-election-data/resource/f6331f99-51f6-44d9-95b9-b20f3b74f360. Only in Chrome, working fine in Firefox.

#3004: ImportError: No module named polib

seanh — Mon, 22 Oct 2012 12:09:50 GMT

This is happening whenever people try to run paster commands. polib should only be needed for the check-po-files command don't import otherwise.

#2935: Make recline work with new datastore

kindly — Wed, 19 Sep 2012 08:14:19 GMT

#3009: On-site notification of new dashboard activity

seanh — Tue, 30 Oct 2012 16:49:22 GMT

We want a "bubble" with a number in it to appear in the top-right of the site next to your user name when you're logged in, telling you how many new activity stream items you have in your dashboard activity stream.

There's a github issue for this here:

https://github.com/okfn/ckanext-pdeu/issues/11

#2955: Recline should be updated

dominik — Wed, 03 Oct 2012 13:22:14 GMT

#2916: User management in orgs needs autocomplete

ross — Wed, 12 Sep 2012 12:09:52 GMT

The user management in organizations ( http://localhost:5000/organization/users/NAME ) should autocomplete names in the dropdown box so that only valid usernames are added to the table.

#2950: paster command to minify javascript and css

icmurray — Mon, 01 Oct 2012 19:06:16 GMT

With the latest template, css and js changes in 2.0, there are a number of things that need preparation prior to a production deployment. One of these is:

the fanstatic_resources defined in ckan/lib/fanstatic_resources.py (bottom of module) should be prepared, and minified.

This ticket is to:

provide a paster command which when run will generate the minified javascript as css files.
stop the auto-minification of files when CKAN starts up.
remove reference to the minified files in the .gitignore file.
add instruction to the release process to run this command, and check-in the minified files to the repo.

## Background

Currently, minification works seamlessly without the need for any preparation when CKAN is started in a development setup. But on a production site, the webserver will (almost certainly) not have write-access to the directories that will contain the minified files. And so the minification will fail, and the site will end up serving the un-minified media, or even *old* minified media.

One way around this would be to allow webserver write access to the directory its serving out of. But this is not generally considered good practice.

Another method would be to distribute the minified files with CKAN. This ticket describes how to do this without causing a lot of noise in the commit history of the repo.

The auto-minifcation occurs when importing ckan/lib/fanstatic_resources.py.

## Changing the process slightly

The reason for moving away from auto-minifying files at start-up, to minifying files when running a paster command is:

we should be distributing the minified files when we make a release (as we do with translation files). This makes it easier to install CKAN from source.

if we distribute the minified files, then they need to be checked-in to the repo.

if they are auto-minified, whenever small changes are made, then this will create a lot of noise in the repo. It will be clearer to have the minified-files generated manually as part of the release process. (Or whever we make a deployment internally).

#3022: setup_template_variables method of IDatasetForm never called

amercader — Thu, 22 Nov 2012 16:45:43 GMT

On the package controller the package_type is not passed to the lookup function, so the setup_template_variables defined on the extensions is never called

#3015: Dropdowns don't work without JavaScript

johnmartin — Tue, 13 Nov 2012 11:19:13 GMT

Essentially the default bootstrap dropdowns don't work properly without JavaScript? which is a little bit of an issue with JS not working.

#2980: Add new groups and organizations functionality into legacy templates

seanh — Mon, 15 Oct 2012 10:44:43 GMT

From Toby: add the functionality to legacy templates

#2879: Datasets (Package) should have a 'public' field

ross — Mon, 20 Aug 2012 12:39:49 GMT

The Package model should have a boolean field added to it describing its visibility beyond that supplied via auth.

The related permission for viewing packages where public is set to False would be package.view (show, whatever), and *never* visible for unauthenticated users.

#2880: Datasets (Package) should have owners

ross — Mon, 20 Aug 2012 12:42:15 GMT

Each dataset should have an explicit owner that is an organisation. This is the organisation that owns the dataset* and will be used for specifying who can move a dataset out of the default organisation.

This should probably be a foreign key link from dataset to organisation (or rather group).

Currently this won't necessarily be the organisation that the dataset is a member of, but it is likely that this will be the case initially (at least until someone moves it to another organisation).

#2549: Merge organization logic into groups

ross — Mon, 18 Jun 2012 11:03:41 GMT

Requirements

Merge the organizations plugin into the core groups functionality. Most of this is templating and a small number of changes to the group controller.

Investigate the possibility of removing the Membership model and using FKs.

Interface

This is likely to consist of:

Updating the templates in templates/group/

Configuring whether we want to constrain datasets to a single group (as per organizations)

Implementing the separate user management (add users to group).

Checking the publisher auth to not necessarily rely on group type = 'organization'

Making sure that the changes still work with publisher auth.

User Stories

None

Tasks

[ ] Code

[ ] Configuration

[ ] Model/Migration?

[ ] Fix templates

[ ] Documentation

Estimates

#2878: Roles and Permissions for Organisations

ross — Mon, 20 Aug 2012 12:37:46 GMT

As part of merging Organisations into core, it is necessary that we clarify the capacity field with which the users/datasets are added as members to the group 'subclass'.

Rather than the capacity being an opaque string that implies auth but doesn't clearly specify it, we will use role names where roles are defined in the database - with a clearly defined set of standard roles. The Role table is expected to have simply a string name/representation and acts as a container for permissions.

Each permission is a string of the form object.action (such as package.add, group.delete) of which several are expected to be associated with a role. This means the permission table will contain a string and a reference to the role.

This work will require UI changes to the screens allowing users to be added to a group/organisation so that the list of available roles is available to add those users.

[x] Model for Role and Permission

[ ] Logic layer changes for managing roles/permissions etc.

[ ] Determine default roles, perhaps just admin/editor/viewer

[ ] Fix the auth layer to use the permissions/roles - may be better implemented as another ticket.