Custom Query (2152 matches)
Results (409 - 411 of 2152)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#824 | fixed | 'Getdata' moved out of CKAN | dread | dread |
Description |
Data importers should use API instead of object model directly:
|
|||
#825 | fixed | Document fabric tool | dread | dread |
#826 | fixed | Resource 'extra' fields | kindly | dread |
Description |
There are a number of extra properties we want to store in a resource:
i.e. this is a much needed enhancement Need to be able to read/write these values in web interface and API. (At some point we may wish to have custom form widgets for these new fields in the resource table, but let's leave this for the future.) ImplementationI suggest these are arbitrary key/value pairs, just like package extras, reusing PackageExtra? code as much as possible. (Other much more radical alternative is to move model to RDF.) |
Note: See TracQuery
for help on using queries.