ERGO-SPR-004-4CT

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Harvest twice the same EO GML document
2. Check the responses: new registry objects are inserted both the times
3.

What is the expected output? What do you see instead?
The expected output of the second harvest request is the update of the
registry objects inserted with the harvest previously carried out on the
same EO GML; instead, new registry objects (with different identifiers) are
created

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by mariaros...@gmail.com on 19 May 2009 at 3:20

[GoogleCodeExporter]

Original comment by mariaros...@gmail.com on 19 May 2009 at 3:25

• Changed title: _ERGO-SPR-003-4CT _

[GoogleCodeExporter]

Original comment by fanciu...@gmail.com on 19 May 2009 at 3:26

• Changed title: _ERGO-SPR-004-4CT _

[GoogleCodeExporter]

This is something to be talked about.

If you re-harvest a RIM object with the same ID then it will be updated. But I
couldn't find a reference on how to handle this for a re-harvested EOP as the 
spec
doesn't specify a binding between the EOP and the ID of the ExtrinsicObject.

You say that it is the expected output. Could you please point to a spec section
which describes this? I must have missed it.

Thanks

Original comment by cryptose...@gmail.com on 19 May 2009 at 4:33

[GoogleCodeExporter]

Hi,

I made a fix for it. Now the translator binds the xpath:
/eop:EarthObservation/gml:metaDataProperty/eop:EarthObservationMetaData/hma:iden
tifier
to
ExtrinsicObject/@id

Now re-harvesting EOP data updates the EO ExtrinsicObject and its related 
objects. 

Original comment by cryptose...@gmail.com on 20 May 2009 at 12:12

• Changed state: Fixed