Custom Query (2152 matches)
Results (859 - 861 of 2152)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#956 | fixed | Add a resource group table. | kindly | kindly |
Description |
We need a way to group resources by various different factors. The most important of which is timeseries. The model will look like Package <o2m> resource_group <o2m> resource The use cases to this are outlined in this email. http://lists.okfn.org/pipermail/ckan-discuss/2011-February/000887.html |
|||
#957 | wontfix | new "kind " field added to resources | kindly | kindly |
Description |
The new field was outlined in http://lists.okfn.org/pipermail/ckan-discuss/2011-February/000887.html it says Can be "data", "metadata", "service", NULL. There is a need to do this for UKLP where some of the data associated with a package is metadata, some is data and some could be a service. |
|||
#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
|