Changes between Version 8 and Version 9 of Software/MSI/ConfigurationTriton


Ignore:
Timestamp:
20/11/09 10:31:52 (10 years ago)
Author:
sdonegan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Software/MSI/ConfigurationTriton

    v8 v9  
    149149== Main Discovery Ingest Configuration & Notes == 
    150150 
     151The ingest system takes records from either the OAI Provider or from an ATOM XML feed.  Currently, the OAI provider is configured to harvest records from all providers (including CEDA centres) but the actual ingest is activated on all BUT the CEDA centres.  Ingestion of CEDA records is conducted via the atom feed.  Note that the oai info editor service uses the same code base via an egg (`oai_document_ingester`) - ingests via the info editor kick off the same processes as the standard nightly ingest activated from a cronjob.  CEDA centres DO NOT APPEAR in the oai_info editor and are not in the nightly ingest do (due to the regular atom feed updates).  The withdrawal of the ceda datacentre_config files from the oai_document_ingester directory ensures there is no conflict between the standard oai xml ingest and the atom feed ingest. 
     152 
     153Example command for activating a feed ingest: `../../bin/python2.5.1 feeddocumentingester.py -vd http://bora.badc.rl.ac.uk:8080/exist/atom/content/db/DIF interval=3600 eXistDBHostname=bora.badc.rl.ac.uk eXistPortNo=8080 dataCentrePoll=neodc ingestFromDate=1990-01-01` ('''NOTE''': these should be run in the background and the interval set to ~ 4 times a day.  Use a cronjob script to check if process is running) 
     154 
    151155== Discovery Service API configuration & Notes == 
    152156