[GeoNetwork-users] Ancilliary datasets [SEC=UNCLASSIFIED]

Hi Francois,

That sounds like great work I would definitely be interested in using it.

The reason I added the additional field was so I could find any record
related in a series of records i.e not just the nearest relative. This is a
type of recursive call.

We want to be able to notify programmatically when component datasets, in a
series, are updated.

Are you considering providing methods for calling the functionality you
described, or will it only be available manually?

Tony Hunter

GIS Professional - Asia Pacific (GISP - Asia Pacific)

Risk & Impact Analysis Group

Geospatial & Earth Monitoring Division

Geoscience Australia

GPO Box 378, Canberra, ACT 2601, Australia

( +61 2 62499362 Fax: +61 2 62499911

x Tony.Hunter@anonymised.com

Internet: http://www.ga.gov.au

-----Original Message-----
From: Francois-Xavier Prunayre
[mailto:francois-xavier.prunayre@anonymised.com]
Sent: Friday, 4 July 2008 5:58 PM
To: Oscar Gomez; Hunter Tony
Cc: geonetwork-users@lists.sourceforge.net
Subject: Re: [GeoNetwork-users] Ancilliary datasets [SEC=UNCLASSIFIED]

Hi Tony and Oscar,

On ven, 2008-07-04 at 09:49 +0200, Oscar Gomez wrote:

Hi Tony,

Thank you for the tip. For me that workaround you're implementing will

definitely work. I think it's the only way through.

we are also working on managing parent/child relationship in GeoNetwork.

What has been made so far:

* in the editor, added a popup to the parentIdentifier field in order

to do a search in the local catalogue and set the parentIdentifier to

the uuid of the selected record.

* in the metadata view, added an hyperlink to go to the metadata of the

parent (using the uuid)

* in the index, allow search on parentIdentifier in order to search for

child

* in the search results, added a button to search for child of each

records.

This is still under development but will be able to share this in the

comming weeks.

Tony, why did you add a column to the table ?

Ciao. Francois

Once you have implemented it at database level, do you have implemented

something at presentation level (I mean, on the web interface) for being

able to navigate from one metadata to his parent (or derived) dataset(s)?

Best Regards,

Oscar

*

*****************************************************************************
************************************************

*

*Oscar GOMEZ PRIETO*

*Joint Research Centre

European Commmission *

*Institute for Environment and Sustainability

Rural, Water and Ecosystem Resources Unit *

*Building 26A Office nº132 TP 262

Via Enrico Fermi 2749

I-21027, ISPRA(VA) Italy

Tel. **+39 - 03.32.78.38.24

E-mail: **oscar.gomez@anonymised.com* <oscar.gomez@anonymised.com>*

Unit Web site: **http://agrienv.jrc.it/* <blocked::http://agrienv.jrc.it/&gt;\*

***

*DISCLAIMER:** The views expressed are purely those of the writer and may

not in any circumstances

be regarded as stating an official position of the European Commission.*

*P** ** **Please consider the environment before printing this e-mail***

On Fri, Jul 4, 2008 at 9:34 AM, <Tony.Hunter@anonymised.com> wrote:

> Hi Oscar,

>

> I'm interested in doing the same type of operation.

> However the methods I'm using at the moment is by using parentIdentifier

as

> the link to a series of metadata records.

>

> This is a bit clunky and I'm implementing it at the database level by

> including a separate column in the metadata table called parent_id. I can

> then easily find all metadata records that are in the series.

>

> This is just a work around that hopefully will be addressed more

elegantly

> in

> the future.

>

> Tony Hunter

> GIS Professional - Asia Pacific (GISP - Asia Pacific)

> Risk & Impact Analysis Group

> Geospatial & Earth Monitoring Division

> Geoscience Australia

> GPO Box 378, Canberra, ACT 2601, Australia

> ( +61 2 62499362 Fax: +61 2 62499911

> x Tony.Hunter@anonymised.com

> Internet: http://www.ga.gov.au

>

>

>

> -----Original Message-----

> From: geonetwork-users-bounces@lists.sourceforge.net

> [mailto:geonetwork-users-bounces@lists.sourceforge.net] On Behalf Of

Oscar

> Gomez

> Sent: Friday, 4 July 2008 4:49 PM

> To: Hockaday John

> Cc: geonetwork-users@lists.sourceforge.net

> Subject: Re: [GeoNetwork-users] Ancilliary datasets [SEC=UNCLASSIFIED]

>

> Hi John,

>

> It's ok, I was just wondering whether it was possible or not.

>

> So thank you for your answer, it saved a lot of time of searching,

reading,

> and testing.

>

> Best,

>

> Oscar

>

> On Fri, Jul 4, 2008 at 1:51 AM, <John.Hockaday@anonymised.com> wrote:

>

> > Hi Oscar,

> >

> > Officially "no" but it looks like there is a need in the revised ISO

> 19115

> > metadata standard for something like "metadataFileIdentifier" in the

> > "LI_Source" that could have an "xlink" attribute to link to the full

> > metadata

> > record.

> >

> > Sorry I can't give you a "yes".

> >

> >

> > John

> >

> > > -----Original Message-----

> > > From: geonetwork-users-bounces@lists.sourceforge.net

> > > [mailto:geonetwork-users-bounces@lists.sourceforge.net] On

> > > Behalf Of Oscar Gomez

> > > Sent: Thursday, 3 July 2008 11:05 PM

> > > To: Geonetwork Users

> > > Subject: [GeoNetwork-users] Ancilliary datasets

> > >

> > >

> > > Hi!

> > >

> > > I have one question. With ISO19139, under lineage, you can

> > > specify that for

> > > creating a dataset, other datasets as "source" have been used.

> > >

> > > If the "source" metadata would already exist in GeoNetwork,

> > > is there any

> > > chance to point (and hyperlink) to the source dataset from the

current

> > > metadata? I would like to be able to "trace upstream" to the original

> > > datasets.

> > >

> > > Thanks in advance,

> > >

> > > Oscar

> > > European Commission, JRC

> > > --------------------------------------------------------------

> > > -----------

> > > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!

> > > Studies have shown that voting for your favorite open source project,

> > > along with a healthy diet, reduces your potential for chronic

lameness

> > > and boredom. Vote Now at http://www.sourceforge.net/community/cca08

> > > _______________________________________________

> > > 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

> > >

> >

> -------------------------------------------------------------------------

> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!

> Studies have shown that voting for your favorite open source project,

> along with a healthy diet, reduces your potential for chronic lameness

> and boredom. Vote Now at http://www.sourceforge.net/community/cca08

> _______________________________________________

> 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

>

--

Francois Xavier Prunayre

Camptocamp France SAS

Savoie Technolac, BP 352

73377 Le Bourget du Lac Cedex

Tel : + 33 (0)6 34 11 71 75

http://www.camptocamp.com

francois-xavier.prunayre@anonymised.com

Hi François,

Did you finally managed to include the parentIdentifier? Is it on the SVN
version?

By the way, is there any plan for adding a "version" element? I mean, if you
have for example a dataset (let's call it AM - administrative boundaries),
that is being updated over time, so you have different versions of the same
dataset, corresponding to different times (AM1990, AM1993, AM2001, AM2002,
...), is there any chance in GeoNetwork to have this relationship, so you
can navigate from version to version? I would call it "historical versions".

Thanks in advance,

Oscar

On Mon, Jul 7, 2008 at 3:04 AM, <Tony.Hunter@anonymised.com> wrote:

Hi Francois,

That sounds like great work I would definitely be interested in using it.

The reason I added the additional field was so I could find *any* record
related in a series of records i.e not just the nearest relative. This is a
type of recursive call.

We want to be able to notify programmatically when component datasets, in a
series, are updated.

Are you considering providing methods for calling the functionality you
described, or will it only be available manually?

Tony Hunter

GIS Professional – Asia Pacific (GISP - Asia Pacific)

Risk & Impact Analysis Group

Geospatial & Earth Monitoring Division

Geoscience Australia

GPO Box 378, Canberra, ACT 2601, Australia

( +61 2 62499362 Fax: +61 2 62499911

x Tony.Hunter@anonymised.com

Internet: http://www.ga.gov.au

-----Original Message-----
From: Francois-Xavier Prunayre [mailto:
francois-xavier.prunayre@anonymised.com]
Sent: Friday, 4 July 2008 5:58 PM
To: Oscar Gomez; Hunter Tony
Cc: geonetwork-users@lists.sourceforge.net
Subject: Re: [GeoNetwork-users] Ancilliary datasets [SEC=UNCLASSIFIED]

Hi Tony and Oscar,

On ven, 2008-07-04 at 09:49 +0200, Oscar Gomez wrote:

> Hi Tony,

>

> Thank you for the tip. For me that workaround you're implementing will

> definitely work. I think it's the only way through.

we are also working on managing parent/child relationship in GeoNetwork.

What has been made so far:

* in the editor, added a popup to the parentIdentifier field in order

to do a search in the local catalogue and set the parentIdentifier to

the uuid of the selected record.

* in the metadata view, added an hyperlink to go to the metadata of the

parent (using the uuid)

* in the index, allow search on parentIdentifier in order to search for

child

* in the search results, added a button to search for child of each

records.

This is still under development but will be able to share this in the

comming weeks.

Tony, why did you add a column to the table ?

Ciao. Francois

>

> Once you have implemented it at database level, do you have implemented

> something at presentation level (I mean, on the web interface) for being

> able to navigate from one metadata to his parent (or derived) dataset(s)?

>

> Best Regards,

>

> Oscar

>

>

> *

>
*****************************************************************************************************************************

> *

>

> *Oscar GOMEZ PRIETO*

>

> *Joint Research Centre

> European Commmission *

>

> *Institute for Environment and Sustainability

> Rural, Water and Ecosystem Resources Unit *

>

> *Building 26A Office nº132 TP 262

> Via Enrico Fermi 2749

> I-21027, ISPRA(VA) Italy

>

> Tel. **+39 - 03.32.78.38.24

> E-mail: **oscar.gomez@anonymised.com* <oscar.gomez@anonymised.com>*

> Unit Web site: **http://agrienv.jrc.it/* <blocked::
http://agrienv.jrc.it/&gt;\*

> ***

>

> *DISCLAIMER:** The views expressed are purely those of the writer and may

> not in any circumstances

> be regarded as stating an official position of the European Commission.*

>

> *P** ** **Please consider the environment before printing this e-mail***

>

>

>

> On Fri, Jul 4, 2008 at 9:34 AM, <Tony.Hunter@anonymised.com> wrote:

>

> > Hi Oscar,

> >

> > I'm interested in doing the same type of operation.

> > However the methods I'm using at the moment is by using
parentIdentifier as

> > the link to a series of metadata records.

> >

> > This is a bit clunky and I'm implementing it at the database level by

> > including a separate column in the metadata table called parent_id. I
can

> > then easily find all metadata records that are in the series.

> >

> > This is just a work around that hopefully will be addressed more
elegantly

> > in

> > the future.

> >

> > Tony Hunter

> > GIS Professional - Asia Pacific (GISP - Asia Pacific)

> > Risk & Impact Analysis Group

> > Geospatial & Earth Monitoring Division

> > Geoscience Australia

> > GPO Box 378, Canberra, ACT 2601, Australia

> > ( +61 2 62499362 Fax: +61 2 62499911

> > x Tony.Hunter@anonymised.com

> > Internet: http://www.ga.gov.au

> >

> >

> >

> > -----Original Message-----

> > From: geonetwork-users-bounces@lists.sourceforge.net

> > [mailto:geonetwork-users-bounces@lists.sourceforge.net] On Behalf Of
Oscar

> > Gomez

> > Sent: Friday, 4 July 2008 4:49 PM

> > To: Hockaday John

> > Cc: geonetwork-users@lists.sourceforge.net

> > Subject: Re: [GeoNetwork-users] Ancilliary datasets [SEC=UNCLASSIFIED]

> >

> > Hi John,

> >

> > It's ok, I was just wondering whether it was possible or not.

> >

> > So thank you for your answer, it saved a lot of time of searching,
reading,

> > and testing.

> >

> > Best,

> >

> > Oscar

> >

> > On Fri, Jul 4, 2008 at 1:51 AM, <John.Hockaday@anonymised.com> wrote:

> >

> > > Hi Oscar,

> > >

> > > Officially "no" but it looks like there is a need in the revised ISO

> > 19115

> > > metadata standard for something like "metadataFileIdentifier" in the

> > > "LI_Source" that could have an "xlink" attribute to link to the full

> > > metadata

> > > record.

> > >

> > > Sorry I can't give you a "yes".

> > >

> > >

> > > John

> > >

> > > > -----Original Message-----

> > > > From: geonetwork-users-bounces@lists.sourceforge.net

> > > > [mailto:geonetwork-users-bounces@lists.sourceforge.net] On

> > > > Behalf Of Oscar Gomez

> > > > Sent: Thursday, 3 July 2008 11:05 PM

> > > > To: Geonetwork Users

> > > > Subject: [GeoNetwork-users] Ancilliary datasets

> > > >

> > > >

> > > > Hi!

> > > >

> > > > I have one question. With ISO19139, under lineage, you can

> > > > specify that for

> > > > creating a dataset, other datasets as "source" have been used.

> > > >

> > > > If the "source" metadata would already exist in GeoNetwork,

> > > > is there any

> > > > chance to point (and hyperlink) to the source dataset from the
current

> > > > metadata? I would like to be able to "trace upstream" to the
original

> > > > datasets.

> > > >

> > > > Thanks in advance,

> > > >

> > > > Oscar

> > > > European Commission, JRC

> > > > --------------------------------------------------------------

> > > > -----------

> > > > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!

> > > > Studies have shown that voting for your favorite open source
project,

> > > > along with a healthy diet, reduces your potential for chronic
lameness

> > > > and boredom. Vote Now at
http://www.sourceforge.net/community/cca08

> > > > _______________________________________________

> > > > 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

> > > >

> > >

> >
-------------------------------------------------------------------------

> > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!

> > Studies have shown that voting for your favorite open source project,

> > along with a healthy diet, reduces your potential for chronic lameness

> > and boredom. Vote Now at http://www.sourceforge.net/community/cca08

> > _______________________________________________

> > 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

> >

>

>

>

--

Francois Xavier Prunayre

Camptocamp France SAS

Savoie Technolac, BP 352

73377 Le Bourget du Lac Cedex

Tel : + 33 (0)6 34 11 71 75

http://www.camptocamp.com

francois-xavier.prunayre@anonymised.com

Hi Oscar,

On mar, 2008-09-23 at 16:52 +0200, Oscar Gomez wrote:

Did you finally managed to include the parentIdentifier? Is it on the
SVN version?

I've some work done on parent/child relationship management (under test
this week) :
* popup to search for a parent in the editor
* button to display children in search results
* add parent/child relation info in lucene index

Stefano was working on that topic also, but not sure if he is still
working on that ?

The source code will be probably loaded in a sandbox in the coming
weeks. Then merge to trunk could be later as Simon does also lot of
stuff on the editor ... We've to investigate how to merge all these
changes first.

For your second type of relationship, how do you plan to create such a
link between datasets from different times ? using series ?

Ciao.

Francois

Dear François,

Thanks a lot for your answer. I would be very pleased if you could tell me
when it's available in the SVN.

Regarding the "time relationship", yes, series I think are ok. First I
thought it should be something similar to parent-child relationship, but in
fact is not, as the relationship is just grouping + precedence.

Best,

Oscar

On Tue, Sep 23, 2008 at 5:48 PM, Francois-Xavier Prunayre <
francois-xavier.prunayre@anonymised.com> wrote:

Hi Oscar,

On mar, 2008-09-23 at 16:52 +0200, Oscar Gomez wrote:
> Did you finally managed to include the parentIdentifier? Is it on the
> SVN version?
I've some work done on parent/child relationship management (under test
this week) :
* popup to search for a parent in the editor
* button to display children in search results
* add parent/child relation info in lucene index

Stefano was working on that topic also, but not sure if he is still
working on that ?

The source code will be probably loaded in a sandbox in the coming
weeks. Then merge to trunk could be later as Simon does also lot of
stuff on the editor ... We've to investigate how to merge all these
changes first.

For your second type of relationship, how do you plan to create such a
link between datasets from different times ? using series ?

Ciao.

Francois