Ticket #111 (closed issue: fixed)

Opened 15 years ago

Last modified 15 years ago

[M] Discovery ingestion in real time

Reported by: selatham Owned by: selatham
Priority: required Milestone: ALPHA
Component: discovery Version:
Keywords: Cc:

Description (last modified by selatham) (diff)

Creation of csml/updates of D etc … issues? Triggers (I’ve updated my OAI repository, harvest it now!) Can we exploit index updates? Polling versus triggering harvests etc … polling frequency.

(1) Each data provider needs to identify an appropriate polling frequency, and (2) there needs to be a web service which responds to a ping with a data provider name by polling that data provider's repository. Could be restful and follow the trackback formalism.

Change History

comment:1 Changed 15 years ago by selatham

  • Description modified (diff)

comment:2 Changed 15 years ago by spascoe

  • Summary changed from Dataset ingestion in real time to [M] Discovery ingestion in real time

comment:3 Changed 15 years ago by selatham

  • Cc lawrence rkl removed
  • Status changed from new to closed
  • Resolution set to fixed

(1) Polling frequency agreed by all as nightly. Implemented as such. (2) Ping mechanism still required (particularly by PML) for interim harvesting. This has turned into task #139.

Note: See TracTickets for help on using tickets.