Custom Query (2152 matches)
Results (775 - 777 of 2152)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#2204 | fixed | [super] Related (Stuff) Extension | ross | rgrp |
Description |
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 NamingWhat do we call this extension?
Proposal"Related Stuff": Apps as in an application (website/service/tool) that uses this dataset (as in Apps and Ideas extension)
ImplementationNew table named Related with following structure || id (int) || type || title || description (markdown) || image_url || owner_id || url || created (timestamp)
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/{id}/related <- list
/dataset/{id}/related/{id} (optional) /dataset/{id} will have a Related tab (with bubble with count).
/related/{id}/edit AuthorizationAddition 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}
[x] Documentation. {0.25d} |
|||
#2223 | fixed | Switch to bootstrap from blueprint | zephod | rgrp |
Description |
Why?
|
|||
#2224 | wontfix | Simplify javascript and css dependencies and add minified version | rgrp | rgrp |
Description |
Compress everything for releases and add minified version to build (with switch to enable use of this?) |