Ticket #349 (closed issue: fixed)

Opened 13 years ago

Last modified 12 years ago

[WG] BADC Update issues for live and development metadata content

Reported by: lawrence Owned by: selatham
Priority: blocker Milestone: Replace Metadata Gateway
Component: community Version:
Keywords: Cc:

Description (last modified by selatham) (diff)

1) How should we update moles content at the badc? On what system, and when will it go live?

2) When should OAI'd stuff go live ...

Change History

comment:1 Changed 13 years ago by selatham

  • Type changed from task to issue
  • Description modified (diff)

comment:2 Changed 13 years ago by selatham

  • Status changed from new to assigned

comment:3 Changed 13 years ago by selatham

  • Milestone changed from PostAlpha_review to ReFactored Discovery WebServices

comment:4 Changed 13 years ago by selatham

  • Summary changed from [WG] Update issues for live and development metadata content to [WG] BADC Update issues for live and development metadata content

1) We should update via the new BADC catalogue which then regularly produces MOLES XML. This MOLES XML gets put into a BADC eXist db for Browse and Discovery record production. 2)Discovery records are produced at regular intervals and placed in the BADC OAI provider.

Go live possibly in Nov (dependent on new BADC catalogue go-live).

comment:5 Changed 12 years ago by selatham

  • Priority changed from critical to blocker
  • Milestone changed from ReFactored_Discovery_WebServices to Replace Metadata Gateway

Pipeline parts are working, need stringing together in cron script. NOTE:There are content issues which will cause a number of rejections. They are being forwarded to BADC(Belinda/Anabelle?).

comment:6 Changed 12 years ago by selatham

  • Status changed from assigned to closed
  • Resolution set to fixed

Apart from the problems with xqueries timing out - the badc pipeline for producing moles (browse)and discovery metadata (for oai) is set. Therefore closing.

Note: See TracTickets for help on using tickets.