Custom Query (2152 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1540 - 1542 of 2152)

Ticket Resolution Summary Owner Reporter
#325 fixed Event push notification dread dread

Reported by dread, 4 years ago.

Description

As a

CKAN client program

I want to

be notified when changes to the CKAN metadata occur.

Examples of use

  1. An external search engine needing to (re)index a package. (interest: Package)
  2. A front-end system that caches package info and wants to know when it changes, to keep in step. (interest: Package or Revision) See further details here: ticket:352 and previous iteration here: ticket:333.
  3. A system for automatically checking package URLs and resource URLs as they are put on the system. This could alert to bad URLs and automatically email feedback to (meta)data owners. (interest: PackageResource)
  4. Do some processing on resource (e.g. extract sample data for display) (interest: PackageResource)

Context

The current state of CKAN can be queried through the REST API, you can keep track of changes by reviewing the feeds, but there is no way to find out the instant something is changed, without costly polling.

Design

Split-off into two tickets:

  • Notification message - ticket:323
    • Which events to notify on
    • Message format
  • Interface for Notifier Service - ticket:322

Testing

To test notifications, Carrot / AMQP will be configured to use a native-Python Queue, instead of requiring RabbitMQ to be running on the machine.

#823 fixed Etags cache doesn't update when only non-core package fields changed. dread dread

Reported by dread, 3 years ago.

Description
  1. Create a package.
  2. Edit package and add a resource.
  3. View package in browser - no sign of the resource - ERROR.
  4. View package in API - resource is there.

Reason: hash doesn't change because package.revision only takes account of core fields.

#1022 fixed Error reporting in CKAN worker API pudo pudo

Reported by pudo, 3 years ago.

Description

Report on errors by any worker daemons, send them out via E-Mail

Note: See TracQuery for help on using queries.