Opened 6 weeks ago

Closed 3 weeks ago

#2808 closed defect (fixed)

FIX - coverage's metadata does not show properly when ras namespace prefix is redefined

Reported by: Bang Pham Huu Owned by: Bang Pham Huu
Priority: major Milestone: 10.3
Component: petascope Version: 10.3
Keywords: Cc: Dimitar Misev, Mohit Basak
Complexity: Medium

Description

When updating a coverage's metadata with this content below:

                    <ras:axes xmlns:ras="http://www.rasdaman.org">
                        <ras:time>
                            <ras:areasOfValidity>
                                <ras:area start="2012-01-01T00:00:00.000Z" end="2017-12-31T23:59:59.999Z"/>
                                <ras:area start="2018-01-01T00:00:00.000Z" end="2018-12-31T23:59:59.999Z"/>
                                <ras:area start="2019-01-01T00:00:00.000Z" end="2019-12-31T23:59:59.999Z"/>
                                <ras:area start="2020-01-01T00:00:00.000Z" end="2020-12-31T23:59:59.999Z"/>
                                <ras:area start="2021-01-01T00:00:00.000Z" end="2021-12-31T23:59:59.999Z"/>
                                <ras:area start="2022-01-01T00:00:00.000Z" end="2024-12-31T23:59:59.999Z"/>
                            </ras:areasOfValidity>
                        </ras:time>
                    </ras:axes>                
                    <ras:dataProvider xmlns:ras="http://www.rasdaman.org">Copernicus</ras:dataProvider>              
                    <fic-md:fairicubeMetadata xmlns:fic-md="https://schemas.fairicube.eu/coveragemetadata" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:role="https://codelists.fairicube.eu/metadata/MetadataCatalogLink" xlink:title="LGN  metadata on the FAIRiCUBE Catalog" xlink:href="https://stacapi.eoxhub.fairicube.eu/collections/index/items/LGN"/>    

then the line <fic-md:fairicubeMetadata does not appear in coverage's updated metadata.

It only works if the metadata is like below:

<ras:axes>
                        <ras:time>
                            <ras:areasOfValidity>
                                <ras:area start="2012-01-01T00:00:00.000Z" end="2017-12-31T23:59:59.999Z"/>
                                <ras:area start="2018-01-01T00:00:00.000Z" end="2018-12-31T23:59:59.999Z"/>
                                <ras:area start="2019-01-01T00:00:00.000Z" end="2019-12-31T23:59:59.999Z"/>
                                <ras:area start="2020-01-01T00:00:00.000Z" end="2020-12-31T23:59:59.999Z"/>
                                <ras:area start="2021-01-01T00:00:00.000Z" end="2021-12-31T23:59:59.999Z"/>
                                <ras:area start="2022-01-01T00:00:00.000Z" end="2024-12-31T23:59:59.999Z"/>
                            </ras:areasOfValidity>
                        </ras:time>
                    </ras:axes>                      
                    <fic-md:fairicubeMetadata xmlns:fic-md="https://schemas.fairicube.eu/coveragemetadata" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:role="https://codelists.fairicube.eu/metadata/MetadataCatalogLink" xlink:title="LGN  metadata on the FAIRiCUBE Catalog" xlink:href="https://stacapi.eoxhub.fairicube.eu/collections/index/items/LGN"/>    

If it is an error, then petascope should be able to print the error.

Change History (1)

comment:1 by Bang Pham Huu, 3 weeks ago

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.