Custom Query (2152 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:

Results (331 - 333 of 2152)

← 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 →
Ticket Resolution Summary Owner Reporter
#478 fixed Unit test for "interface resource" in API johnbywater

Reported by johnbywater, 4 years ago.
Description

We don't want /api to be an HTML page, but rather provide information about the API in a JSON structure.

#479 fixed Suggest DGU presents database dumps through front end dread johnbywater
#480 fixed Catalogue service shall conform to specification thejimmyg johnbywater

Reported by johnbywater, 4 years ago.
Description

Common requirements for running CKAN behind a (e.g Wordpress or Drupal) front-end:

  1. Unrestricted total read-only access to catalogue API for general public (e.g. voluntary organisation).
    • monitored by API key
    • not monitored by API key
  2. Restricted total read-write access to catalogue API for authorized clients (e.g. front-end system, bulk upload clients).
    • restricted by CKAN access controller
    • restricted by HTTP Auth
    • restricted by IP address
  3. Restricted total read-write access to catalogue Web UI for authorized users (e.g. site admins).
    • restricted by CKAN access controller
    • restricted by HTTP Auth
  4. Restricted partial read-write access to catalogue Web UI for authorized users (e.g. group admins).
    • restricted by CKAN access controller
    • restricted by HTTP Auth

CKAN as a catalogue service

← 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 →
Note: See TracQuery for help on using queries.