Ticket #325 (new enhancement) — at Version 5

Opened 4 years ago

Last modified 4 years ago

Event push notification

Reported by: dread Owned by: dread
Priority: critical Milestone: v1.1
Component: ckan Keywords:
Cc: Repository:
Theme:

Description (last modified by dread) (diff)

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.

Change History

comment:1 Changed 4 years ago by pudo

  • Description modified (diff)

comment:2 Changed 4 years ago by dread

  • Description modified (diff)

comment:3 Changed 4 years ago by dread

  • Description modified (diff)

comment:4 Changed 4 years ago by dread

  • Description modified (diff)

comment:5 Changed 4 years ago by dread

  • Description modified (diff)
Note: See TracTickets for help on using tickets.