Ticket #664 (closed defect: fixed)

Opened 14 years ago

Last modified 14 years ago

[M] Discovery 'list index out of range' problem

Reported by: selatham Owned by: ko23
Priority: required Milestone: Replace Metadata Gateway
Component: discovery Version:
Keywords: WS-Discovery2 MDIP Cc:


Search on 'NEXTmap', get nextmap record  http://glue.badc.rl.ac.uk/discovery?textTarget=All&searchString=NEXTMap&advanced=0

Click on more, get "Unable to show document, reason was [list index out of range]"

Change History

comment:1 Changed 14 years ago by lawrence

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

This is an xquery problem as well. I propose to fix the viewing, and then hand the ticket to Kev. Meanwhile:

 This link points to the original: see the nasty parameter content.

And  This link points to the converted one: lots of empty parameter descriptions (which is what is breaking the html view) ... I intend to make the view support empty parameter things (since viewing original difs might have this problem), but think we should fix the xquery to handle this as well.

Has this come via MOLES yet? If so, then we should address the content problem too! If not, let's just treat it as a pathological example that our code should handle.

comment:2 Changed 14 years ago by lawrence

  • Owner changed from lawrence to ko23

OK, my code won't break with this (changeset:2332), it's now Kev's problem. Having said that, I still think the original record is using parameters where topic keywords would be better. Someone should look at this record and decide what it should it look like.

comment:3 Changed 14 years ago by selatham

The neodc content is not coming via MOLES yet. So it's a pathological example to handle.

comment:4 Changed 14 years ago by selatham

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

We now have blank GCMD science valids being filled with 'unknown'. This fixes the technical problem. May want to deal with unknown appearing in GUI later, but will close for now.

Note: See TracTickets for help on using tickets.