[GeoNetwork-users] Link to a feature catalogue question

Jose_Garcia · November 15, 2011, 10:07pm

Hi

The relation between a dataset metadata and a feature catalogue record is
stored in the relation table of the database.

Is there any reason to store this way instead of storing in
MD_Metadata/contentInfo/MD_FeatureCatalogueDescription/featureCatalogueCitation/CI_Citation
?

Thanks and regards,
Jose García

andrew_walsh · November 16, 2011, 2:47am

Hi Jose,

Not sure about reason why GN developers have designed feature
catalogue links this way. You might check with Francois
about this, I seem to remember he did some work on the relations
table. Just guessing, presumably there is an ISO19110 record in
the same geonetwork instance which is related through an id/uuid to the
ISO19115 metadata record (dataset) ?

Another way you mention is to use the
MD_Metadata/contentInfo/MD_FeatureCatalogueDescription/featureCatalogueCitation/CI_Citation

We had discussed this way last year as part of ideas for the AODN data portal.
The idea was that there were 'featureType' metadata records (hierarchy level of "featureType" )
with a citation and URLlink ( http://aodn.org.au/featureCatalog/fc?ftype=CTD ) to a central AODN
feature catalogue and the particular feature type i.e CTD

The attached test metadata record (hypothetical) has a hierarchy level of "featureType" and
describing an ocean observation feature type "CTD".

Evert,

We mentioned features (ISO19110) just the other day at GN
workshop so I thought you might be interested in this question.
How had you implemented ISO19110?

Regards,

Andrew

----- Original Message ----- From: "jose garcia" <josegar74@anonymised.com>
To: <geonetwork-users@lists.sourceforge.net>
Sent: Wednesday, November 16, 2011 10:46 AM
Subject: [GeoNetwork-users] Link to a feature catalogue question

Hi

The relation between a dataset metadata and a feature catalogue record is
stored in the relation table of the database.

Is there any reason to store this way instead of storing in
MD_Metadata/contentInfo/MD_FeatureCatalogueDescription/featureCatalogueCitation/CI_Citation
?

Thanks and regards,
Jose García
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

(attachments)

iso19139fc.xml (39.8 KB)

Jose_Garcia · November 16, 2011, 8:45am

Hi Andrew

Thanks for response. Now relation is only keep in the database outside of
metadata xml (unless i miss it).

Storing the relation at metadata level like in MD_Metadata/contentInfo/MD_**
FeatureCatalogueDescription/**featureCatalogueCitation/CI_**Citation I
think is a better option, so for example can be possible to add a CSW
queriable to retrieved linked metadata to a feature catalogue. Now seem not
possible in actual implementation.

Will check with Francois.

Regards,
Jose García

On Wed, Nov 16, 2011 at 3:47 AM, andrew walsh <awalsh@anonymised.com> wrote:

Hi Jose,

Not sure about reason why GN developers have designed feature
catalogue links this way. You might check with Francois
about this, I seem to remember he did some work on the relations
table. Just guessing, presumably there is an ISO19110 record in
the same geonetwork instance which is related through an id/uuid to the
ISO19115 metadata record (dataset) ?

Another way you mention is to use the
MD_Metadata/contentInfo/MD_**FeatureCatalogueDescription/**
featureCatalogueCitation/CI_**Citation

We had discussed this way last year as part of ideas for the AODN data
portal.
The idea was that there were 'featureType' metadata records (hierarchy
level of "featureType" )
with a citation and URLlink ( http://aodn.org.au/**
featureCatalog/fc?ftype=CTD<http://aodn.org.au/featureCatalog/fc?ftype=CTD>\) to a central AODN
feature catalogue and the particular feature type i.e CTD

The attached test metadata record (hypothetical) has a hierarchy level of
"featureType" and
describing an ocean observation feature type "CTD".

Evert,

We mentioned features (ISO19110) just the other day at GN
workshop so I thought you might be interested in this question.
How had you implemented ISO19110?

Regards,

Andrew

----- Original Message ----- From: "jose garcia" <josegar74@anonymised.com>
To: <geonetwork-users@anonymised.com**sourceforge.net<geonetwork-users@anonymised.comourceforge.net>
>
Sent: Wednesday, November 16, 2011 10:46 AM
Subject: [GeoNetwork-users] Link to a feature catalogue question

Hi

The relation between a dataset metadata and a feature catalogue record is
stored in the relation table of the database.

Is there any reason to store this way instead of storing in
MD_Metadata/contentInfo/MD_**FeatureCatalogueDescription/**
featureCatalogueCitation/CI_**Citation
?

Thanks and regards,
Jose García
------------------------------**------------------------------**
------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-**sfdev2dev1 <http://p.sf.net/sfu/rsa-sfdev2dev1>
______________________________**_________________
GeoNetwork-users mailing list
GeoNetwork-users@anonymised.com**sourceforge.net<GeoNetwork-users@anonymised.comeforge.net>
https://lists.sourceforge.net/**lists/listinfo/geonetwork-**users<https://lists.sourceforge.net/lists/listinfo/geonetwork-users>
GeoNetwork OpenSource is maintained at http://sourceforge.net/**
projects/geonetwork <http://sourceforge.net/projects/geonetwork>

Francois_Prunayre · November 20, 2011, 5:26pm

Hi Jose, some inputs on that topic

2011/11/16 jose garcia <josegar74@anonymised.com>:

Hi Andrew

Thanks for response. Now relation is only keep in the database outside of
metadata xml (unless i miss it).

Storing the relation at metadata level like in MD_Metadata/contentInfo/MD_**
FeatureCatalogueDescription/**featureCatalogueCitation/CI_**Citation I
think is a better option,

Why not, but how do you write the relation ?

There are many ways to make links in ISO19139:
* gco:CharacterString (eg. parentIdentifier)
* @uuiref (eg. service)
* xlink:href (eg. keywords in thesaurus)
* gmx:Anchor (not supported in GeoNetwork for the time being)

Here is some comments on different options :

Option 1 : Custom relation table (supported for linking iso19110 record)

Option 2 : Use @uuidref for linking feature catalogue and sources

<gmd:contentInfo>
              <gmd:MD_FeatureCatalogueDescription>
                      <gmd:includedWithDataset>
                              <gco:Boolean>false</gco:Boolean>
                      </gmd:includedWithDataset>
                      <gmd:featureCatalogueCitation
uuidref="92f84de3-1ff9-438b-bd89-9d89ec0bddfd"/>
              </gmd:MD_FeatureCatalogueDescription>
</gmd:contentInfo>

Main issue is that the type of the element pointed by the uuiref may
be different than the type of the element. For example :
gmd:featureCatalogueCitation is a CI_Citation but the uuidref points
to MD_Metadata (For GeoNetwork the metadata = the datasets or
services, but we could have aggregates)
srv:operatesOn is a MD_DataIdentification but the uuidref points to MD_Metadata.

This option is also supported in trunk for linking feature catalogue
or source (See #616).

Option 3 : Use xlink:href

<gmd:contentInfo>
              <gmd:MD_FeatureCatalogueDescription>
                      <gmd:includedWithDataset>
                              <gco:Boolean>false</gco:Boolean>
                      </gmd:includedWithDataset>
                      <gmd:featureCatalogueCitation
xlink:href="http://you.org/uuid?abcdef#someElementIds"/>
              </gmd:MD_FeatureCatalogueDescription>
</gmd:contentInfo>

Main issue is that xlink:hrefs are resolved by GeoNetwork (ie. the
xlink is resolved and the document is inserted in the metadata record
- so XLinks are supposed to point to XML fragments). This default
behavior could be changed but there is no real specification on how to
link element using XLinks (extra xlink:* attributes could be used to
define the resolution mechanism maybe).

Option 4 : Use gmx:Anchor

<gmd:contentInfo>
       <gmd:MD_FeatureCatalogueDescription>
               <gmd:includedWithDataset>
                       <gco:Boolean>false</gco:Boolean>
               </gmd:includedWithDataset>
               <gmd:featureCatalogueCitation>
                       <CI_Citation>
                               <title>
                                       <gmx:Anchor xlink:href="URL du
feature Catalogue">Le titre du feature Catalogue</gmx:Anchor>
                               </title>
Is the gmx:Anchor supposed to point to an HTML page, XML page ? In
that case you also need to create the CI_Citation element and all its
mandatory fields and duplicate some info (eg. title).

So option 1 and 2 are currently supported in trunk but not sure if
there is any other / more ISO compliant method to create that type of
link. Maybe next version of ISO will help on that ?

Cheers.

Francois

so for example can be possible to add a CSW
queriable to retrieved linked metadata to a feature catalogue. Now seem not
possible in actual implementation.

Will check with Francois.

Regards,
Jose García

On Wed, Nov 16, 2011 at 3:47 AM, andrew walsh <awalsh@anonymised.com> wrote:

Hi Jose,

Not sure about reason why GN developers have designed feature
catalogue links this way. You might check with Francois
about this, I seem to remember he did some work on the relations
table. Just guessing, presumably there is an ISO19110 record in
the same geonetwork instance which is related through an id/uuid to the
ISO19115 metadata record (dataset) ?

Another way you mention is to use the
MD_Metadata/contentInfo/MD_**FeatureCatalogueDescription/**
featureCatalogueCitation/CI_**Citation

We had discussed this way last year as part of ideas for the AODN data
portal.
The idea was that there were 'featureType' metadata records (hierarchy
level of "featureType" )
with a citation and URLlink ( http://aodn.org.au/**
featureCatalog/fc?ftype=CTD<http://aodn.org.au/featureCatalog/fc?ftype=CTD>\) to a central AODN
feature catalogue and the particular feature type i.e CTD

The attached test metadata record (hypothetical) has a hierarchy level of
"featureType" and
describing an ocean observation feature type "CTD".

Evert,

We mentioned features (ISO19110) just the other day at GN
workshop so I thought you might be interested in this question.
How had you implemented ISO19110?

Regards,

Andrew

----- Original Message ----- From: "jose garcia" <josegar74@anonymised.com>
To: <geonetwork-users@anonymised.com**sourceforge.net<geonetwork-users@anonymised.comsourceforge.net>
>
Sent: Wednesday, November 16, 2011 10:46 AM
Subject: [GeoNetwork-users] Link to a feature catalogue question

Hi

The relation between a dataset metadata and a feature catalogue record is
stored in the relation table of the database.

Is there any reason to store this way instead of storing in
MD_Metadata/contentInfo/MD_**FeatureCatalogueDescription/**
featureCatalogueCitation/CI_**Citation
?

Thanks and regards,
Jose García
------------------------------**------------------------------**
------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-**sfdev2dev1 <http://p.sf.net/sfu/rsa-sfdev2dev1>
______________________________**_________________
GeoNetwork-users mailing list
GeoNetwork-users@anonymised.com**sourceforge.net<GeoNetwork-users@anonymised.comceforge.net>
https://lists.sourceforge.net/**lists/listinfo/geonetwork-**users<https://lists.sourceforge.net/lists/listinfo/geonetwork-users>
GeoNetwork OpenSource is maintained at http://sourceforge.net/**
projects/geonetwork <http://sourceforge.net/projects/geonetwork>

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

Jose_Garcia · November 21, 2011, 7:59am

Hi Francois

Responses inline.

Regards,
Jose García

On Sun, Nov 20, 2011 at 6:26 PM, Francois Prunayre <fx.prunayre@anonymised.com>wrote:

Hi Jose, some inputs on that topic

2011/11/16 jose garcia <josegar74@anonymised.com>:
> Hi Andrew
>
> Thanks for response. Now relation is only keep in the database outside of
> metadata xml (unless i miss it).
>
> Storing the relation at metadata level like in
MD_Metadata/contentInfo/MD_**
> FeatureCatalogueDescription/**featureCatalogueCitation/CI_**Citation I
> think is a better option,
Why not, but how do you write the relation ?

See
https://geo-ide.noaa.gov/wiki/index.php?title=ISO_19110_(Feature_Catalog)

There are many ways to make links in ISO19139:
* gco:CharacterString (eg. parentIdentifier)
* @uuiref (eg. service)
* xlink:href (eg. keywords in thesaurus)
* gmx:Anchor (not supported in GeoNetwork for the time being)

Here is some comments on different options :

Option 1 : Custom relation table (supported for linking iso19110 record)

Option 2 : Use @uuidref for linking feature catalogue and sources

<gmd:contentInfo>
             <gmd:MD_FeatureCatalogueDescription>
                     <gmd:includedWithDataset>
                             <gco:Boolean>false</gco:Boolean>
                     </gmd:includedWithDataset>
                     <gmd:featureCatalogueCitation
uuidref="92f84de3-1ff9-438b-bd89-9d89ec0bddfd"/>
             </gmd:MD_FeatureCatalogueDescription>
</gmd:contentInfo>

Main issue is that the type of the element pointed by the uuiref may
be different than the type of the element. For example :
gmd:featureCatalogueCitation is a CI_Citation but the uuidref points
to MD_Metadata (For GeoNetwork the metadata = the datasets or
services, but we could have aggregates)
srv:operatesOn is a MD_DataIdentification but the uuidref points to
MD_Metadata.

This option is also supported in trunk for linking feature catalogue
or source (See #616).

Will take a look, didn't know about this. Thanks.

Option 3 : Use xlink:href

<gmd:contentInfo>
             <gmd:MD_FeatureCatalogueDescription>
                     <gmd:includedWithDataset>
                             <gco:Boolean>false</gco:Boolean>
                     </gmd:includedWithDataset>
                     <gmd:featureCatalogueCitation
xlink:href="http://you.org/uuid?abcdef#someElementIds"/>
             </gmd:MD_FeatureCatalogueDescription>
</gmd:contentInfo>

Main issue is that xlink:hrefs are resolved by GeoNetwork (ie. the
xlink is resolved and the document is inserted in the metadata record
- so XLinks are supposed to point to XML fragments). This default
behavior could be changed but there is no real specification on how to
link element using XLinks (extra xlink:* attributes could be used to
define the resolution mechanism maybe).

Option 4 : Use gmx:Anchor

<gmd:contentInfo>
      <gmd:MD_FeatureCatalogueDescription>
              <gmd:includedWithDataset>
                      <gco:Boolean>false</gco:Boolean>
              </gmd:includedWithDataset>
              <gmd:featureCatalogueCitation>
                      <CI_Citation>
                              <title>
                                      <gmx:Anchor xlink:href="URL du
feature Catalogue">Le titre du feature Catalogue</gmx:Anchor>
                              </title>
Is the gmx:Anchor supposed to point to an HTML page, XML page ? In
that case you also need to create the CI_Citation element and all its
mandatory fields and duplicate some info (eg. title).

So option 1 and 2 are currently supported in trunk but not sure if
there is any other / more ISO compliant method to create that type of
link. Maybe next version of ISO will help on that ?

Cheers.

Francois

> so for example can be possible to add a CSW
> queriable to retrieved linked metadata to a feature catalogue. Now seem
not
> possible in actual implementation.
>
> Will check with Francois.
>
> Regards,
> Jose García
>
> On Wed, Nov 16, 2011 at 3:47 AM, andrew walsh <awalsh@anonymised.com>
wrote:
>
>> Hi Jose,
>>
>> Not sure about reason why GN developers have designed feature
>> catalogue links this way. You might check with Francois
>> about this, I seem to remember he did some work on the relations
>> table. Just guessing, presumably there is an ISO19110 record in
>> the same geonetwork instance which is related through an id/uuid to the
>> ISO19115 metadata record (dataset) ?
>>
>> Another way you mention is to use the
>> MD_Metadata/contentInfo/MD_**FeatureCatalogueDescription/**
>> featureCatalogueCitation/CI_**Citation
>>
>> We had discussed this way last year as part of ideas for the AODN data
>> portal.
>> The idea was that there were 'featureType' metadata records (hierarchy
>> level of "featureType" )
>> with a citation and URLlink ( http://aodn.org.au/**
>> featureCatalog/fc?ftype=CTD<
http://aodn.org.au/featureCatalog/fc?ftype=CTD>\) to a central AODN
>> feature catalogue and the particular feature type i.e CTD
>>
>> The attached test metadata record (hypothetical) has a hierarchy level
of
>> "featureType" and
>> describing an ocean observation feature type "CTD".
>>
>> Evert,
>>
>> We mentioned features (ISO19110) just the other day at GN
>> workshop so I thought you might be interested in this question.
>> How had you implemented ISO19110?
>>
>>
>> Regards,
>>
>> Andrew
>>
>> ----- Original Message ----- From: "jose garcia" <josegar74@anonymised.com>
>> To: <geonetwork-users@anonymised.com**sourceforge.net<
geonetwork-users@lists.sourceforge.net>
>> >
>> Sent: Wednesday, November 16, 2011 10:46 AM
>> Subject: [GeoNetwork-users] Link to a feature catalogue question
>>
>>
>> Hi
>>>
>>> The relation between a dataset metadata and a feature catalogue record
is
>>> stored in the relation table of the database.
>>>
>>> Is there any reason to store this way instead of storing in
>>> MD_Metadata/contentInfo/MD_**FeatureCatalogueDescription/**
>>> featureCatalogueCitation/CI_**Citation
>>> ?
>>>
>>> Thanks and regards,
>>> Jose García
>>> ------------------------------**------------------------------**
>>> ------------------
>>> RSA(R) Conference 2012
>>> Save $700 by Nov 18
>>> Register now
>>> http://p.sf.net/sfu/rsa-**sfdev2dev1 <
http://p.sf.net/sfu/rsa-sfdev2dev1>
>>> ______________________________**_________________
>>> GeoNetwork-users mailing list
>>> GeoNetwork-users@anonymised.com**sourceforge.net<
GeoNetwork-users@lists.sourceforge.net>
>>> https://lists.sourceforge.net/**lists/listinfo/geonetwork-**users<
https://lists.sourceforge.net/lists/listinfo/geonetwork-users>
>>> GeoNetwork OpenSource is maintained at http://sourceforge.net/**
>>> projects/geonetwork <http://sourceforge.net/projects/geonetwork>
>>>
>>>
>>>
>>>
>
------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> GeoNetwork-users mailing list
> GeoNetwork-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork
>

andrew_walsh · November 21, 2011, 11:06pm

Hi Jose and Francois,

Thanks for your inputs, seems as usual with a big standard
like ISO19115 there is more than one way to approach this.
However the NOAA wiki link gives some guidance with an example, thanks
got that link, Jose.

Seems that the feature catalog could be
an external resource or an internal one that Geonetwork
manages. I hadn't looked at any ISO19110/Feature Catalog
functions in Geonetwork yet, will take a look.

Regards,

Andrew

----- Original Message ----- From: jose garcia
To: Francois Prunayre
Cc: andrew walsh ; geonetwork-users@lists.sourceforge.net
Sent: Monday, November 21, 2011 6:59 PM
Subject: Re: [GeoNetwork-users] Link to a feature catalogue question

Hi Francois

Responses inline.

Regards,
Jose García

On Sun, Nov 20, 2011 at 6:26 PM, Francois Prunayre <fx.prunayre@anonymised.com> wrote:

Hi Jose, some inputs on that topic

2011/11/16 jose garcia <josegar74@anonymised.com>:

Hi Andrew

Thanks for response. Now relation is only keep in the database outside of
metadata xml (unless i miss it).

Storing the relation at metadata level like in MD_Metadata/contentInfo/MD_**
FeatureCatalogueDescription/**featureCatalogueCitation/CI_**Citation I

think is a better option,

Why not, but how do you write the relation ?

See https://geo-ide.noaa.gov/wiki/index.php?title=ISO_19110_(Feature_Catalog)

There are many ways to make links in ISO19139:
* gco:CharacterString (eg. parentIdentifier)
* @uuiref (eg. service)
* xlink:href (eg. keywords in thesaurus)
* gmx:Anchor (not supported in GeoNetwork for the time being)

Here is some comments on different options :

Option 1 : Custom relation table (supported for linking iso19110 record)

Option 2 : Use @uuidref for linking feature catalogue and sources

<gmd:contentInfo>
             <gmd:MD_FeatureCatalogueDescription>
                     <gmd:includedWithDataset>
                             <gco:Boolean>false</gco:Boolean>
                     </gmd:includedWithDataset>
                     <gmd:featureCatalogueCitation
uuidref="92f84de3-1ff9-438b-bd89-9d89ec0bddfd"/>
             </gmd:MD_FeatureCatalogueDescription>
</gmd:contentInfo>

Main issue is that the type of the element pointed by the uuiref may
be different than the type of the element. For example :
gmd:featureCatalogueCitation is a CI_Citation but the uuidref points
to MD_Metadata (For GeoNetwork the metadata = the datasets or
services, but we could have aggregates)
srv:operatesOn is a MD_DataIdentification but the uuidref points to MD_Metadata.

This option is also supported in trunk for linking feature catalogue
or source (See #616).

Will take a look, didn't know about this. Thanks.

Option 3 : Use xlink:href

<gmd:contentInfo>
             <gmd:MD_FeatureCatalogueDescription>
                     <gmd:includedWithDataset>
                             <gco:Boolean>false</gco:Boolean>
                     </gmd:includedWithDataset>
                     <gmd:featureCatalogueCitation
xlink:href="http://you.org/uuid?abcdef#someElementIds"/>
             </gmd:MD_FeatureCatalogueDescription>
</gmd:contentInfo>

Main issue is that xlink:hrefs are resolved by GeoNetwork (ie. the
xlink is resolved and the document is inserted in the metadata record
- so XLinks are supposed to point to XML fragments). This default
behavior could be changed but there is no real specification on how to
link element using XLinks (extra xlink:* attributes could be used to
define the resolution mechanism maybe).

Option 4 : Use gmx:Anchor

<gmd:contentInfo>
      <gmd:MD_FeatureCatalogueDescription>
              <gmd:includedWithDataset>
                      <gco:Boolean>false</gco:Boolean>
              </gmd:includedWithDataset>
              <gmd:featureCatalogueCitation>
                      <CI_Citation>
                              <title>
                                      <gmx:Anchor xlink:href="URL du
feature Catalogue">Le titre du feature Catalogue</gmx:Anchor>
                              </title>
Is the gmx:Anchor supposed to point to an HTML page, XML page ? In
that case you also need to create the CI_Citation element and all its
mandatory fields and duplicate some info (eg. title).

So option 1 and 2 are currently supported in trunk but not sure if
there is any other / more ISO compliant method to create that type of
link. Maybe next version of ISO will help on that ?

Cheers.

Francois

so for example can be possible to add a CSW
queriable to retrieved linked metadata to a feature catalogue. Now seem not
possible in actual implementation.

Will check with Francois.

Regards,
Jose García

On Wed, Nov 16, 2011 at 3:47 AM, andrew walsh <awalsh@anonymised.com> wrote:

Hi Jose,

Not sure about reason why GN developers have designed feature
catalogue links this way. You might check with Francois
about this, I seem to remember he did some work on the relations
table. Just guessing, presumably there is an ISO19110 record in
the same geonetwork instance which is related through an id/uuid to the
ISO19115 metadata record (dataset) ?

Another way you mention is to use the

MD_Metadata/contentInfo/MD_**FeatureCatalogueDescription/**
featureCatalogueCitation/CI_**Citation

We had discussed this way last year as part of ideas for the AODN data
portal.
The idea was that there were 'featureType' metadata records (hierarchy
level of "featureType" )

with a citation and URLlink ( http://aodn.org.au/**
featureCatalog/fc?ftype=CTD<http://aodn.org.au/featureCatalog/fc?ftype=CTD>\) to a central AODN

feature catalogue and the particular feature type i.e CTD

The attached test metadata record (hypothetical) has a hierarchy level of
"featureType" and
describing an ocean observation feature type "CTD".

Evert,

We mentioned features (ISO19110) just the other day at GN
workshop so I thought you might be interested in this question.
How had you implemented ISO19110?

Regards,

Andrew

----- Original Message ----- From: "jose garcia" <josegar74@anonymised.com>

To: <geonetwork-users@anonymised.com**sourceforge.net<geonetwork-users@anonymised.comceforge.net>

>
Sent: Wednesday, November 16, 2011 10:46 AM
Subject: [GeoNetwork-users] Link to a feature catalogue question

Hi

The relation between a dataset metadata and a feature catalogue record is
stored in the relation table of the database.

Is there any reason to store this way instead of storing in

MD_Metadata/contentInfo/MD_**FeatureCatalogueDescription/**
featureCatalogueCitation/CI_**Citation

?

Thanks and regards,
Jose García

------------------------------**------------------------------**

------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now

http://p.sf.net/sfu/rsa-**sfdev2dev1 <http://p.sf.net/sfu/rsa-sfdev2dev1>
______________________________**_________________
GeoNetwork-users mailing list
GeoNetwork-users@anonymised.com**sourceforge.net<GeoNetwork-users@anonymised.comceforge.net>
https://lists.sourceforge.net/**lists/listinfo/geonetwork-**users<https://lists.sourceforge.net/lists/listinfo/geonetwork-users>
GeoNetwork OpenSource is maintained at http://sourceforge.net/**
projects/geonetwork <http://sourceforge.net/projects/geonetwork>

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork