Custom Query (2152 matches)
Results (1864 - 1866 of 2152)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#2226 | fixed | [super] Refactor and improve documentation (v1.7) | rgrp | rgrp |
Description |
Documentation is key to the success of projects! Move material into main docs from wiki
Create a User GuideBasic step-by-step on getting started with CKAN (See start on set of slides here e.g. http://blog.thedatahub.org/2012/03/02/tutorial-publish-data-with-the-datahub/)
Break into sectionsSuggest something like: # General * Intro * Conceptual Overview * What CKAN helps you do (http://ckan.org/) * FAQ ? (or point to the wiki) # For Administrators * Installation and Setup * Configuration options * Customization - Theming etc * Authorization and Workflows * Storage # For Users (Publishers, Data Wranglers, etc etc) * Walkthrough of publishing a dataset * Storage * API (see Developers section) # CKAN Developers * Domain Model * API * Extensions * i18n CKAN Developers * Buildbot |
|||
#1094 | duplicate | [super] Refactor the Auth System | thejimmyg | thejimmyg |
Description |
Here are some proposed changes related to CKAN's authorization system - they aren't very big, but should provide for some forthcoming use cases including #787. Two man reasons for the changes are:
The first two changes revolve around the is_authorized method, which is called by the logic layer to ask whether a particular user (e.g. Bob) is allowed to do a certain action (e.g. edit) on a certain object (e.g. Package).
which *overrides* the current call with its own implementation (note: in previous discussions we have considered allowing a chain of plugins, no longer!) Reason: authorization can be completely delegated to another system (or partially)
but for action=create_package, the object supplied is System, and for action=edit the object supplied is the package. Instead action should always be the string name of a function in the logic layer and object should always be the object passed to that function. This means our auth system is based around the actual actions we are performing (rather than a model them) and with the actual data that forms the action (rather than a related object). You never need a System object in this model.
Although this sounds a bit radical we already have auth extensions. Read-only CKAN Web UI(Additional requirement from #764) Whilse using CKAN web interface, you are not tempted to edit stuff:
|
|||
#961 | fixed | [super] Refactoring of forms, validation and model synchronization | kindly | rgrp |
Description |
This is a meta-ticket to hold all of the work on refactoring forms, validation and model-synchronization in CKAN. ckan-dev thread: http://lists.okfn.org/pipermail/ckan-dev/2011-January/000180.html The IssueFrom #926: The current formalchemy setup conflates view, controller and model code in a way that makes it hard to debug and customise. From http://lists.okfn.org/pipermail/ckan-dev/2011-January/000181.html: ... FormAlchemy, in retrospect, was probably a mistake as it merges too much model/validation/form generation into one thing. At least 3 functions involved [in this area]:
Related Tickets
|