Custom Query (2152 matches)
Results (490 - 492 of 2152)
| Ticket | Resolution | Summary | Owner | Reporter | 
|---|---|---|---|---|
| #1114 | fixed | CLI for viewing search index of a package | dread | dread | 
| Description | To see what lexemes are generated for debug purposes. | |||
| #1116 | fixed | api search loses boolean q options | dread | dread | 
| Description | filter_by_openness and filter_by_downloadable options don't work when specified as URI parameters. (They do work in qjson parameters) | |||
| #1121 | wontfix | JSON extras appear in package edit form mangled | dread | |
| Description | It is possible to use the CKAN API to insert JSON format data into package extra values, but this data is displayed in the package edit form. Example: Package http://ckan.net/package/hbz_unioncatalog in the API the extra value as a list: "extras": {"publishingInstitution": ["http://lobid.org/organisation/DE-605", "http://lobid.org/organisation/DE-290"...
yet when you edit the package it loses all the quotes and brackets: http://ckan.net/package/edit/hbz_unioncatalog {{{http://lobid.org/organisation/DE-605http://lobid.org/organisation/DE-290... }}} so when you save the package, the list is mangled into a bad string. | |||

