Ticket #1015 (closed task: fixed)

Opened 12 years ago

Last modified 12 years ago

(DI-4-1) Problem with Discovery URLS in resultset

Reported by: sdonegan Owned by: sdonegan
Priority: blocker Milestone: NDG3
Component: discovery Version:
Keywords: ows_Server, discovery service Cc:


Spotted a problem wih the discovery service's resultset - links to further information are pointing at the wrong record - usually 1 out so probably an indexing issue. Need to sort the code in ows_server (models/ndgSearch.py). Response from backend seems ok, so problem here I think.

Change History

comment:1 Changed 12 years ago by sdonegan

  • Status changed from new to assigned

comment:2 Changed 12 years ago by sdonegan

  • Priority changed from critical to blocker
  • Type changed from defect to task

comment:3 Changed 12 years ago by sdonegan

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

Problem traced back to new postgres based backend - list docs in request presented to db did not match the order of the docs returned. Added new methods to match returned docset with doc ids using regexes and id's based on original filename. Also handles edp requests etc where requested format is "original". Tested on localhost and rolled out to proglue.

Note: See TracTickets for help on using tickets.