Ticket #908 (closed issue: wontfix)

Opened 12 years ago

Last modified 11 years ago

Discovery ingest robustness given problem incoming metadata

Reported by: selatham Owned by: selatham
Priority: discussion Milestone: NDG2 Cleanup
Component: discovery Version:
Keywords: DiscoveryService Cc:

Description

Inconsistencies between the different metadata stores used in Discovery can cause problems. We cannot be assured that the given metadata will pass through all stages of ingest successfully. Therefore each record coming in should be treated transactionally. That is, every stage of the process must be successful for a given record before we allow them to be committed to the system. There are complications with this as records have to be added to the exist db before the next stage can occur. Exist does not support transactional working (unlike postgres). The alternative to trying to mend the current system is to re-design and have everything required for discovery queries in postgres. This vastly improves the logical robustness of the system. Probably improves performance too. The original xml can still be stored for retreiving as required.

Change History

comment:1 Changed 11 years ago by lawrence

  • Keywords DiscoveryService added
  • Component changed from DiscoveryService to discovery

Moved from DiscoveryService? component to discovery as part of NDG2 cleanup

comment:2 Changed 11 years ago by lawrence

  • Status changed from new to closed
  • Resolution set to wontfix

history given the new Calum code.

Note: See TracTickets for help on using tickets.