Custom Query (2152 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1003 - 1005 of 2152)

Ticket Resolution Summary Owner Reporter
#292 fixed PackageResources are created new on every package edit dread dread

Reported by dread, 4 years ago.

Description

When you edit a package, all of its resources are deleted and a fresh set created. This causes all history of them to be lost.

#1485 fixed Package/Group form extension mechanism so you can add forms for particular package_types kindly kindly

Reported by kindly, 2 years ago.

Description

We want to be able to change form depending on package type or group type.

This is dependent on a type field being added to the Package and the Group.

#108 fixed Package search in the REST API dread rgrp

Reported by rgrp, 5 years ago.

Description

Add package search facility in the rest api at /api/search

Queries can be provided as for the normal package search either by posting to that url or by performing a get with a query string.

E.g. .../api/search/package?q=xyz

Query parameters:

  • q is keyword string (searches name, title, tags by default)
    • split by words and ANDed
  • additional parameters for specific fields
  • qjson is alternative to q for Searching by specific fields (in addition to keyword string). Payload to json is a JSON-encoded dict which is a dictionary with a q field for free text (keywords) and additional key/value pairs for specific fields
    • if q and qjson specified ignore q and just process qjson value

Additional parameters in addition to query ("q" or "qjson") are:

  • limit
  • offset
  • fullinfo=0/1 - return full record for each result (default=0)
  • order_by=field_name
  • search_notes=0/1 (default 0) do we search notes field in a keyword search

Return value is json encoded dictionary with keys:

  • 'results': list of results
  • 'count': total number of results

Extras (for the future)

  • Prioritisation is not part of this ticket (requires fulltext support in DB or in external app such as Xapian)
Note: See TracQuery for help on using queries.