CKAN: Ticket #358: Resources in REST API

milestone deleted

rgrp — Tue, 27 Jul 2010 21:42:08 GMT

milestone v1.1 deleted

priority, type changed

dread — Wed, 06 Oct 2010 14:38:38 GMT

priority changed from critical to major
type changed from enhancement to defect

milestone set

pudo — Mon, 03 Jan 2011 11:21:15 GMT

milestone set to iati-4

owner changed; repo, theme set

kindly — Mon, 18 Apr 2011 10:18:15 GMT

owner changed from dread to rgrp
repo set to ckan
theme set to none

kindly — Mon, 18 Apr 2011 10:21:49 GMT

This ticket needs to have a more thorough spec which needs to include.

Examples of put/post requests to resources and if they are needed.
Dealing with resources that do not have a related packages in terms of authorization. Do they have a new action? how granular is the authorization? per resource? system level? etc.
The rules related to authorization for resources attached to packages. i.e you only get read permissions when the related package has read permissions? do they have their own rules?

dread — Mon, 18 Apr 2011 10:46:51 GMT

This ticket was designed only for reading resources, following an ongoing requirement from the Scraperwiki collaboration. Assume PUT/POST is out of scope.

I suggest dealing with resources that aren't attached to packages in an entirely new ticket or CEP, as the implications are wider than this aspect of the API.

type, description, milestone changed

rgrp — Mon, 18 Apr 2011 11:15:16 GMT

type changed from defect to enhancement
description modified (diff)
milestone changed from iati-4 to ckan-v1.5

status changed; resolution set

thejimmyg — Fri, 08 Jul 2011 12:39:42 GMT

status changed from new to closed
resolution set to duplicate

Merging with #922 go there for latest updates.