Ticket #359 (closed defect: fixed)

Opened 13 years ago

Last modified 13 years ago

[M] COAPEC Moles content problem

Reported by: lawrence Owned by: selatham
Priority: blocker Milestone: ALPHA
Component: community Version:
Keywords: Cc: ko23

Description (last modified by lawrence) (diff)

I'll attach examples, but the bottom line is that moles content that is in there today for a coapec_obstn ... results in a stub-b which is mainly about metdesc2, which is probably why all the related stuff is buggered.

I don't konw for a fact this is a content problem, but I think it is, I'm assuming returnstubb.jar is fully functional for all the types ...

Attachments

coapec.obs.xml Download (101.3 KB) - added by lawrence 13 years ago.
This is the stub-b that is returned for COAPEC_Obstn
coapec-500yr.xml Download (85.2 KB) - added by lawrence 13 years ago.
This is the stub-b for the data entity

Change History

Changed 13 years ago by lawrence

This is the stub-b that is returned for COAPEC_Obstn

Changed 13 years ago by lawrence

This is the stub-b for the data entity

comment:1 Changed 13 years ago by lawrence

  • Description modified (diff)

I should have said you can use kevin's returnstubb.jar to see what you get,or my insecure.py repid/localid ...

comment:2 Changed 13 years ago by selatham

  • Status changed from new to assigned

metdesc2 did appear (erroneously) in the Obsstn record, but in the metadataDescriptionID/localIdentifier. You shouldn't be using this to get an Obstn stub-b. I will change the 'metdesc2' localid, but it shouldn't really matter what's in there (should it Kev?). Also noticed that the abstract text is wrong - so this could just be a complete red herring.

comment:3 Changed 13 years ago by selatham

  • Owner changed from selatham to lawrence
  • Status changed from assigned to new

Updated the obsstn record. I reckon it'll look OK now.

comment:4 Changed 13 years ago by lawrence

Still a problem with the abstract that's in the activity too ...

Also, I'm not yet sure whether it's a red herring because I don't understand why I'm not picking up the deployments etc ... I'll work on that next after

a bit of time on security ...

comment:5 Changed 13 years ago by lawrence

  • Owner changed from lawrence to selatham

comment:6 Changed 13 years ago by lawrence

comment:7 Changed 13 years ago by selatham

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

COAPEC Obsstn should OK now - as I siad earlier. Activity content was OK. Turns out to be a test id kicking about in Kev's code, which he's sorted out.

Note: See TracTickets for help on using tickets.