[GeoNetwork-devel] ISO 19139, profiles and and othe questions about the interaction withGeoNetwork

Well I was able to get the search working but I had to make an additional change to the iso19115.xsl file, I added a test to determine if there was no text node and in that event test for @value.

<xsl:template match=“*”>

<xsl:param name=“name” select=“name(.)”/>

<xsl:param name=“store” select=“‘false’”/>

<xsl:param name=“index” select=“‘true’”/>

<xsl:param name=“token” select=“‘false’”/>

<xsl:if test="string(.) = ‘’ ">

</xsl:if>

<xsl:if test="string(.) != ‘’ ">

</xsl:if>

</xsl:template>

I’ve said it before but XML is not my strong suit so please if there is someone that can make this a more appropriate patch please pipe up as I’d like to see this change made in a more reliable manner.

Cheers,

Michael Gannon.

-----Original Message-----
From: geonetwork-devel-bounces@lists.sourceforge.net [mailto:geonetwork-devel-bounces@lists.sourceforge.net] On Behalf Of Gannon Michael
Sent: Wednesday, 8 November 2006 4:52
To: geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] ISO 19139,profiles and and othe questions about the interaction withGeoNetwork

Hi list,

Following from your response to Johns question about adding search criteria for hierarchy level, I have added these two fragments into the lucene and iso19115 xsl’s.


Lucene.xsl:

<xsl:if test=“string(/request/hierarchy)!=‘’”>

</xsl:if>


iso19115.xsl:

<xsl:apply-templates select=“/Metadata/dqInfo/dqScope/scpLvl/ScopeCd/”>

<xsl:with-param name=“name” select=“‘hierarchy’”/>

<xsl:with-param name=“token” select=“‘true’”/>

</xsl:apply-templates>


The index field being generated from the indexing xsl is as follows:

It seems as though the value of the selected hierarchy level is stored in the metadata as an attribute of the /Metadata/dqInfo/dqScope/scpLvl/ScopeCd element.

My XML knowledge is not my strong suit, so shoot me down if I’m wrong, I think the problems are coming up because the value of hierarchy level is stored as an attribute value. Should the value be stored as an attribute value or as a text node of the element.

Cheers,

Michael Gannon.

PS. I’ve cut down the original email to prevent headaches :wink:

-----Original Message-----
From: geonetwork-devel-bounces@lists.sourceforge.net [mailto:geonetwork-devel-bounces@lists.sourceforge.net] On Behalf Of Andrea Carboni
Sent: Saturday, 4 November 2006 1:06
To: geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] ISO 19139,profiles and and othe questions about the interaction withGeoNetwork

Hi John,

I will try to answer to your questions.

……

-11-----------

yes it is. You have to change the indexing stylesheet (a short one) and to add

those fields to the web form (another simple stylesheet).

……

Cheers,

Andrea

Hi all,

As you may be aware my colleague Michael Gannon is investigating setting up

GeoNetwork as a prototype to manage our organisation’s ISO 19115 metadata.

We will probably use GeoNetwork as a prototype to enter, edit and store

metadata as well as get users to identify their requirements of a CSW.

As you know a while ago I mentioned about the ISO 19139 XSDs on this list and

thanks to Jeroen, Andrea and probably others, GeoNetwork now somehow handles

the ISO 19139 XML metadata format. I think that I also mentioned that the

ISO 19139 XML implementation doesn’t cater for all the ISO 19115 constraints

and code lists so ANZLIC - the Spatial Information Council (for Australia and

New Zealand) is cloning the ISO 19139 XSDs, adding Schematron to these cloned

XSDs and creating XML to represent the different ISO 19115 and ANZLIC code

lists. We are also adding XSDs and Schematron that allows for ISO 19119

metadata. That is, metadata for “services”. The XSDs were taken from the

eden web site mentioned in my previous emails but the Schematron, again

handles the constraints that the XSDs can’t implement.

Michael is using GeoNetwork 2.1.0 alpha-1 and has posted a couple of problems

that he has encountered to this list. I also have the following questions

which I hope you can answer to help us decide if we will use GeoNetwork for

our prototype. The question s are:

……

  1. Is it easy to configure GeoNetwork 2.1.0 alpha-1 advanced search

interface to search for other ISO 19115 elements such as, multiple

hierarchyLevelNames? For example, search for all metadata about “software”

or all metadata about “dataset” and “series”.

……

I thank you in advance for any answers to these questions that will help us

decide if we use GeoNetwork for out prototype CSW.

Thanks.

John


Using Tomcat but need to do more? Need to support web services, security?

Get stuff done quickly with pre-integrated technology to make your job easier

Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo

http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642


GeoNetwork-devel mailing list

GeoNetwork-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/geonetwork-devel

GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

Thanks Michael,

I will add your patch ASAP.

Cheers,
Andrea

Well I was able to get the search working but I had to make an additional
change to the iso19115.xsl file, I added a test to determine if there was no
text node and in that event test for @value.

      <!-- text element, by default indexed, not stored nor tokenized -->

      <xsl:template match="*">

            <xsl:param name="name" select="name(.)"/>

            <xsl:param name="store" select="'false'"/>

            <xsl:param name="index" select="'true'"/>

            <xsl:param name="token" select="'false'"/>

            <xsl:if test="string(.) = '' ">

                  <Field name="{$name}" string="{@value}" store="{$store}"
index="{$index}" token="{$token}"/>

            </xsl:if>

            <xsl:if test="string(.) != '' ">

                  <Field name="{$name}" string="{string(.)}" store="{$store}"
index="{$index}" token="{$token}"/>

            </xsl:if>

      </xsl:template>

I've said it before but XML is not my strong suit so please if there is
someone that can make this a more appropriate patch please pipe up as I'd
like to see this change made in a more reliable manner.

Cheers,

Michael Gannon.

-----Original Message-----
From: geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] On Behalf Of Gannon
Michael
Sent: Wednesday, 8 November 2006 4:52
To: geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] ISO 19139,profiles and and othe questions
about the interaction withGeoNetwork

Hi list,

Following from your response to Johns question about adding search criteria
for hierarchy level, I have added these two fragments into the lucene and
iso19115 xsl's.

-----------------

Lucene.xsl:

<xsl:if test="string(/request/hierarchy)!=''">

      <BooleanClause required="true" prohibited="false">

            <TermQuery fld="hierarchyLevelName" txt="{/request/hierarchy}"/>

      </BooleanClause>

</xsl:if>

-----------------

iso19115.xsl:

<xsl:apply-templates select="/Metadata/dqInfo/dqScope/scpLvl/ScopeCd/">

      <xsl:with-param name="name" select="'hierarchy'"/>

      <xsl:with-param name="token" select="'true'"/>

</xsl:apply-templates>

-----------------

The index field being generated from the indexing xsl is as follows:

<Field token="true" index="true" store="false" string="" name="hierarchy" />

It seems as though the value of the selected hierarchy level is stored in the
metadata as an attribute of the /Metadata/dqInfo/dqScope/scpLvl/ScopeCd
element.

My XML knowledge is not my strong suit, so shoot me down if I'm wrong, I
think the problems are coming up because the value of hierarchy level is
stored as an attribute value. Should the value be stored as an attribute
value or as a text node of the element.

Cheers,

Michael Gannon.

PS. I've cut down the original email to prevent headaches :wink:

-----Original Message-----
From: geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] On Behalf Of Andrea
Carboni
Sent: Saturday, 4 November 2006 1:06
To: geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] ISO 19139,profiles and and othe questions
about the interaction withGeoNetwork

Hi John,

I will try to answer to your questions.

......

-11-----------

yes it is. You have to change the indexing stylesheet (a short one) and to
add

those fields to the web form (another simple stylesheet).

......

Cheers,

Andrea

> Hi all,

>

> As you may be aware my colleague Michael Gannon is investigating setting up

> GeoNetwork as a prototype to manage our organisation's ISO 19115 metadata.

> We will probably use GeoNetwork as a prototype to enter, edit and store

> metadata as well as get users to identify their requirements of a CSW.

>

> As you know a while ago I mentioned about the ISO 19139 XSDs on this list
and

> thanks to Jeroen, Andrea and probably others, GeoNetwork now somehow
handles

> the ISO 19139 XML metadata format. I think that I also mentioned that the

> ISO 19139 XML implementation doesn't cater for all the ISO 19115
constraints

> and code lists so ANZLIC - the Spatial Information Council (for Australia
and

> New Zealand) is cloning the ISO 19139 XSDs, adding Schematron to these
cloned

> XSDs and creating XML to represent the different ISO 19115 and ANZLIC code

> lists. We are also adding XSDs and Schematron that allows for ISO 19119

> metadata. That is, metadata for "services". The XSDs were taken from the

> eden web site mentioned in my previous emails but the Schematron, again

> handles the constraints that the XSDs can't implement.

>

> Michael is using GeoNetwork 2.1.0 alpha-1 and has posted a couple of
problems

> that he has encountered to this list. I also have the following questions

> which I hope you can answer to help us decide if we will use GeoNetwork for

> our prototype. The question s are:

>

> ......

>

> 11. Is it easy to configure GeoNetwork 2.1.0 alpha-1 advanced search

> interface to search for other ISO 19115 elements such as, multiple

> hierarchyLevelNames? For example, search for all metadata about "software"

> or all metadata about "dataset" and "series".

>

> ......

>

> I thank you in advance for any answers to these questions that will help us

> decide if we use GeoNetwork for out prototype CSW.

>

> Thanks.

>

>

> John

-------------------------------------------------------------------------

Using Tomcat but need to do more? Need to support web services, security?

Get stuff done quickly with pre-integrated technology to make your job easier

Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo

http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

_______________________________________________

GeoNetwork-devel mailing list

GeoNetwork-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/geonetwork-devel

GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork