Custom Query (2152 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:

Results (1210 - 1212 of 2152)

← 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 →
Ticket Resolution Summary Owner Reporter
#945 fixed [super] Richer resources - Resource Groups, new fields, improved UI kindly kindly

Reported by kindly, 3 years ago.
Description

Super ticket: #1032

This is a meta ticket for changes that are going to happen in resources.

  • New resource group table. #956
  • New kind field in resource. #957
  • UI for new kind field. #958
  • Resources in REST API ticket:358
  • Resources in WUI #1445
  • Make Resources first class entity. #922 (duplicate?)

Background on this change can be found at:

#954 fixed [super] API version 3 kindly rgrp

Reported by rgrp, 3 years ago.
Description

Child tickets:

  • #1107 Move package autocomplete from package controller and move to API
  • #1087 version and contact info api call

Move to a format that has a separate responseHeader and response.

A standard package response

{
  responseHeader: {
    status: 0,
  }    
  response: {package-dict}
}

On error: 

{
  responseHeader: {
    status: {err-code},
    error: 'message'
  }    
  response: none
}

A search query

Based directly on solr. 

{
  responseHeader: {
    status: 0,
  }    
  response: {
    numFound: 5,
    start: 0
    docs: [
    ]
  }
}

Issues

This is a breaking change for clients

References
#956 fixed Add a resource group table. kindly kindly

Reported by kindly, 3 years ago.
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

← 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 →
Note: See TracQuery for help on using queries.