[GeoNetwork-users] Advanced search for time extent in 2.4.1

Stephen_M_Richard · November 25, 2009, 8:48pm

My understanding is that

MD_Metadata / DateStamp indicates the date the metadata was created (NAP says created or updated, ISO, INSPIRE, ANZLIC just say created). The utility is to indicate to harvesters if the *metadata record* has changed since last harvest. Under this reading, any update to the md record recreates it (i.e. I like the NAP reading); otherwise it's not very useful.

I'm guessing the other date you're talking about is MD_DataIdentification/citation/CI_Citation/date, which is the date of most recent update to the resource that is described (not the same as the metadata record).

Of course there's always the question of which when the normal user will expect that AdvancedSearch actually refers to--
--Update date for metadata record (probably not)
--Date of currentness for the resource (maybe)
--Temporal extent that the resource content describes (maybe)

The last one is MD_DataIdentification/extent/EX_Extent/temporalElement/EX_TemporalExtent....

One problem that needs to be fixed is for the AdvancedSearch UI to clarify which when is 'When?'.

steve

Hi,

Maybe someone on the users list can help me with this:

When I'm entering a date in the Advanced Search "When?" section (in GeoNetwork 2.4.1) the following information is queried (in ISO19139 records):

"Identification Info / Metadata / Date stamp"

As far as I unstand the value of this is set automatically on creation of a record.

In my opinion it would be _very_ useful to query the value of the following entry instead:

"Identification Info / Date"

This would allow to search for updated records as well.

It looked like in the trunk version of GeoNetwork, the search has been already altered to search this field, by I may be mistaken.

Also the help says:

"The WHEN? section gives you the possibility to restrict your search in terms of temporal extent, indicating a specific range of time referred to the data creation or publication date"

It's a bit confusing to me. How are you using this search feature?

Cheers,
Michael

-- Michael Stegherr, Computer Scientist CSIRO Exploration and Mining | Phone 08 6436 8572 AARC, 26 Dick Perry Av, Kensington WA 6151, Australia

--
Stephen M. Richard
Section Chief, Geoinformatics
Arizona Geological Survey
416 W. Congress St., #100
Tucson, Arizona, 85701 USA

Phone: Office: (520) 209-4127
Reception: (520) 770-3500 FAX: (520) 770-3505

email: steve.richard@anonymised.com

Hockaday_John · November 26, 2009, 5:28am

On Thursday, 26 November 2009 7:48 AM Stephen M Richard wrote:

My understanding is that

MD_Metadata / DateStamp indicates the date the metadata was
created (NAP says created or updated, ISO, INSPIRE, ANZLIC
just say created).

The ISO 19115 definition is the "date that the metadata was created". Under the rules for profiles this can't be changed to "created or modified". I haven't read the NAP but if this definition is changed then they should call the element something else.

The utility is to indicate to harvesters
if the *metadata record* has changed since last harvest.
Under this reading, any update to the md record recreates it
(i.e. I like the NAP reading); otherwise it's not very useful.

I agree that knowing the "lastUpdateDate" would be very useful. That is why Australia and other nations have suggested that there be another last updated metadata date.

I'm guessing the other date you're talking about is
MD_DataIdentification/citation/CI_Citation/date, which is the
date of most recent update to the resource that is described
(not the same as the metadata record).

Of course there's always the question of which when the
normal user will expect that AdvancedSearch actually refers to--
--Update date for metadata record (probably not)
--Date of currentness for the resource (maybe)
--Temporal extent that the resource content describes (maybe)

We should be able to index all of them and provide that choice to the designer of the interface. If they have reasons to exclude any of the date searches then they should removed from the interface.

This should apply to most fields within ISO 19115 and other profiles. This process will allow all search capabilities being integrated for any type of profile if that profile contains those elements. All that is needed is the web interface includes those search terms that the users of that interface wish to see.

Thanks.

John

The last one is
MD_DataIdentification/extent/EX_Extent/temporalElement/EX_Temp
oralExtent....

One problem that needs to be fixed is for the AdvancedSearch
UI to clarify which when is 'When?'.

steve

> Hi,
>
> Maybe someone on the users list can help me with this:
>
> When I'm entering a date in the Advanced Search "When?"
section (in GeoNetwork 2.4.1) the following information is
queried (in ISO19139 records):
>
> "Identification Info / Metadata / Date stamp"
>
> As far as I unstand the value of this is set automatically
on creation of a record.
>
> In my opinion it would be _very_ useful to query the value
of the following entry instead:
>
> "Identification Info / Date"
>
> This would allow to search for updated records as well.
>
> It looked like in the trunk version of GeoNetwork, the
search has been already altered to search this field, by I
may be mistaken.
>
> Also the help says:
>
> "The WHEN? section gives you the possibility to restrict
your search in terms of temporal extent, indicating a
specific range of time referred to the data creation or
publication date"
>
> It's a bit confusing to me. How are you using this search feature?
>
> Cheers,
> Michael
>
> -- Michael Stegherr, Computer Scientist CSIRO Exploration
and Mining |
> Phone 08 6436 8572 AARC, 26 Dick Perry Av, Kensington WA
6151, Australia

--
Stephen M. Richard
Section Chief, Geoinformatics
Arizona Geological Survey
416 W. Congress St., #100
Tucson, Arizona, 85701 USA

Phone:
Office: (520) 209-4127
Reception: (520) 770-3500
FAX: (520) 770-3505

email: steve.richard@anonymised.com

--------------------------------------------------------------
----------------
Let Crystal Reports handle the reporting - Free Crystal
Reports 2008 30-Day
trial. Simplify your report design, integration and
deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
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 26, 2009, 6:12am

Hi GN users,

A while back I did a summary of the various date fields in the ISO19115 and in the
GN database. The following might be useful:

Below is a summary of the different kinds of date fields in both XML and
Geonetwork db.

***DateStamp****

Its the "creation date" according to ISO.
MD_Metadata.dateStamp
It is automatically set when the user creates a new record
from a template is not editable with the Geonetwork editor.

*****Citation Date(s)******

e.g Identification->CI_Citation->Date
There can be 1 or many of these in the metadata depending on the number of documents cited
in the metadata. Its basically the document/dataset publication date. It's fully editable

******Begin Date and End Date*******

These are in the temporal element section . Its editable on all the profiles.

*****Revision Date*****

This is special extended element, its only in the Australian MCP profile (BlueNet version of GN).
Its not editable but is automatically updated when you edit a MCP record. This extended field
is very useful, (maybe other profiles could utilise it). The only date field
which is similar is the 'changeDate' described below, but this date is only
stored in the geonetwork db.

***createDate and changeDate***** (Note - not in XML instances- in Geonetwork db only)

Within geonetwork's database table (Metadata) there is a
'createDate' and a 'changeDate'. The createDate is stored when the record
is created an the changeDate updated whenever the record is edited.
The changeDate is utilised by the harvesting function in geonetwork
and also lets you sort queries by change date, a very handy function.

It seems also that the createDate and changeDate are stored in the MEF
file when you do an export from Geonetwork (they are stored in the info.xml file within the MEF file).
So you should get persistance on these dates if you export/import when
you add data to your geonetwork site.

Andrew

----- Original Message ----- From: <John.Hockaday@anonymised.com>
To: <steve.richard@anonymised.com>; <geonetwork-users@lists.sourceforge.net>
Sent: Thursday, November 26, 2009 4:28 PM
Subject: Re: [GeoNetwork-users] Advanced search for time extent in 2.4.1 [SEC=UNCLASSIFIED]

On Thursday, 26 November 2009 7:48 AM Stephen M Richard wrote:

My understanding is that

MD_Metadata / DateStamp indicates the date the metadata was
created (NAP says created or updated, ISO, INSPIRE, ANZLIC
just say created).

The ISO 19115 definition is the "date that the metadata was created". Under the rules for profiles this can't be changed to "created or modified". I haven't read the NAP but if this definition is changed then they should call the element something else.

The utility is to indicate to harvesters
if the *metadata record* has changed since last harvest.
Under this reading, any update to the md record recreates it
(i.e. I like the NAP reading); otherwise it's not very useful.

I agree that knowing the "lastUpdateDate" would be very useful. That is why Australia and other nations have suggested that there be another last updated metadata date.

I'm guessing the other date you're talking about is
MD_DataIdentification/citation/CI_Citation/date, which is the
date of most recent update to the resource that is described
(not the same as the metadata record).

Of course there's always the question of which when the
normal user will expect that AdvancedSearch actually refers to--
--Update date for metadata record (probably not)
--Date of currentness for the resource (maybe)
--Temporal extent that the resource content describes (maybe)

We should be able to index all of them and provide that choice to the designer of the interface. If they have reasons to exclude any of the date searches then they should removed from the interface.

This should apply to most fields within ISO 19115 and other profiles. This process will allow all search capabilities being integrated for any type of profile if that profile contains those elements. All that is needed is the web interface includes those search terms that the users of that interface wish to see.

Thanks.

John

The last one is
MD_DataIdentification/extent/EX_Extent/temporalElement/EX_Temp
oralExtent....

One problem that needs to be fixed is for the AdvancedSearch
UI to clarify which when is 'When?'.

steve

> Hi,
>
> Maybe someone on the users list can help me with this:
>
> When I'm entering a date in the Advanced Search "When?"
section (in GeoNetwork 2.4.1) the following information is
queried (in ISO19139 records):
>
> "Identification Info / Metadata / Date stamp"
>
> As far as I unstand the value of this is set automatically
on creation of a record.
>
> In my opinion it would be _very_ useful to query the value
of the following entry instead:
>
> "Identification Info / Date"
>
> This would allow to search for updated records as well.
>
> It looked like in the trunk version of GeoNetwork, the
search has been already altered to search this field, by I
may be mistaken.
>
> Also the help says:
>
> "The WHEN? section gives you the possibility to restrict
your search in terms of temporal extent, indicating a
specific range of time referred to the data creation or
publication date"
>
> It's a bit confusing to me. How are you using this search feature?
>
> Cheers,
> Michael
>
> -- Michael Stegherr, Computer Scientist CSIRO Exploration
and Mining |
> Phone 08 6436 8572 AARC, 26 Dick Perry Av, Kensington WA
6151, Australia

--
Stephen M. Richard
Section Chief, Geoinformatics
Arizona Geological Survey
416 W. Congress St., #100
Tucson, Arizona, 85701 USA

Phone:
Office: (520) 209-4127
Reception: (520) 770-3500
FAX: (520) 770-3505

email: steve.richard@anonymised.com

--------------------------------------------------------------
----------------
Let Crystal Reports handle the reporting - Free Crystal
Reports 2008 30-Day
trial. Simplify your report design, integration and
deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
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

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
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

michael.stegherr · November 26, 2009, 6:27am

Hi Steve,

-----Original Message-----
From: Stephen M Richard [mailto:steve.richard@anonymised.com]
Sent: Thursday, 26 November 2009 4:48 AM
Subject: Re: [GeoNetwork-users] Advanced search for time
extent in 2.4.1

I'm guessing the other date you're talking about is
MD_DataIdentification/citation/CI_Citation/date, which is the
date of most recent update to the resource that is described
(not the same as the metadata record).

This is correct.

Of course there's always the question of which when the
normal user will expect that AdvancedSearch actually refers to--
--Update date for metadata record (probably not)
--Date of currentness for the resource (maybe)
--Temporal extent that the resource content describes (maybe)

The last one is
MD_DataIdentification/extent/EX_Extent/temporalElement/EX_Temp
oralExtent....

One problem that needs to be fixed is for the AdvancedSearch
UI to clarify which when is 'When?'.

The solutions I worked out with the WA Geothermal CoE people and with help of Simon Pigot is the following:

- easier access to documentation (click on "WHEN?")
- more descriptive labels for When?
("Resource issued" for MD_DataIdentification/citation/CI_Citation/date,
"Dataset issued" for MD_DataIdentification/extent/EX_Extent/temporalElement/EX_TemporalExtent...)

It still needs a lot of refinement, but I attached the patches, if someone is interested. You can also see how it works here:
http://wagcoe.ivec.org/geonetwork/

Cheers,
Michael

(attachments)

Temporal-Extent-GN-trunk.patch (21.3 KB)
Advanced-Search-Help.patch (1.27 KB)

Doug_Nebert · November 30, 2009, 5:13pm

John.Hockaday@anonymised.com wrote:

On Thursday, 26 November 2009 7:48 AM Stephen M Richard wrote:

My understanding is that

MD_Metadata / DateStamp indicates the date the metadata was created (NAP says created or updated, ISO, INSPIRE, ANZLIC just say
created).

The ISO 19115 definition is the "date that the metadata was created".
Under the rules for profiles this can't be changed to "created or
modified". I haven't read the NAP but if this definition is changed
then they should call the element something else.

The utility is to indicate to harvesters if the *metadata record*
has changed since last harvest. Under this reading, any update to
the md record recreates it (i.e. I like the NAP reading); otherwise
it's not very useful.

I agree that knowing the "lastUpdateDate" would be very useful. That
is why Australia and other nations have suggested that there be
another last updated metadata date.

This should be used as the create/update date. There is little use for the original creation date, given that so many other time dimensions are already handled in the metadata. Be practical. Use national profiles and community practice as guidance to make clear what might otherwise not be so.

Doug.

I'm guessing the other date you're talking about is MD_DataIdentification/citation/CI_Citation/date, which is the date
of most recent update to the resource that is described (not the
same as the metadata record).

Of course there's always the question of which when the normal user
will expect that AdvancedSearch actually refers to-- --Update date
for metadata record (probably not) --Date of currentness for the
resource (maybe) --Temporal extent that the resource content
describes (maybe)

We should be able to index all of them and provide that choice to the
designer of the interface. If they have reasons to exclude any of the
date searches then they should removed from the interface.

This should apply to most fields within ISO 19115 and other profiles.
This process will allow all search capabilities being integrated for
any type of profile if that profile contains those elements. All
that is needed is the web interface includes those search terms that
the users of that interface wish to see.

Thanks.

John

The last one is MD_DataIdentification/extent/EX_Extent/temporalElement/EX_Temp oralExtent....

One problem that needs to be fixed is for the AdvancedSearch UI to
clarify which when is 'When?'.

steve

Hi,

Maybe someone on the users list can help me with this:

When I'm entering a date in the Advanced Search "When?"

section (in GeoNetwork 2.4.1) the following information is queried
(in ISO19139 records):

"Identification Info / Metadata / Date stamp"

As far as I unstand the value of this is set automatically

on creation of a record.

In my opinion it would be _very_ useful to query the value

of the following entry instead:

"Identification Info / Date"

This would allow to search for updated records as well.

It looked like in the trunk version of GeoNetwork, the

search has been already altered to search this field, by I may be
mistaken.

Also the help says:

"The WHEN? section gives you the possibility to restrict

your search in terms of temporal extent, indicating a specific
range of time referred to the data creation or publication date"

It's a bit confusing to me. How are you using this search
feature?

Cheers, Michael

-- Michael Stegherr, Computer Scientist CSIRO Exploration

and Mining |

Phone 08 6436 8572 AARC, 26 Dick Perry Av, Kensington WA

6151, Australia

-- Stephen M. Richard Section Chief, Geoinformatics Arizona
Geological Survey 416 W. Congress St., #100 Tucson, Arizona, 85701
USA

Phone: Office: (520) 209-4127 Reception: (520) 770-3500 FAX: (520)
770-3505

email: steve.richard@anonymised.com

-------------------------------------------------------------- ---------------- Let Crystal Reports handle the reporting - Free
Crystal Reports 2008 30-Day trial. Simplify your report design,
integration and deployment - and focus on what you do best, core
application coding. Discover what's new with Crystal Reports now.
http://p.sf.net/sfu/bobj-july _______________________________________________ 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

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day trial. Simplify your report design, integration and deployment
- and focus on what you do best, core application coding. Discover
what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ 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

--
Douglas D. Nebert
Senior Advisor for Geospatial Technology, System-of-Systems Architect
FGDC Secretariat T:703 648 4151 F:703 648-5755 C:703 459-5860

sppigot · November 26, 2009, 4:45pm

Hi Michael and Steve,

I'm interested - been busy with a workshop so have been a little quiet for the last few days - I'll take a look at your patch Michael over the next day or so.

Cheers and thanks,
Simon
_______________________________________
From: Michael.Stegherr@anonymised.com [Michael.Stegherr@anonymised.com]
Sent: Thursday, 26 November 2009 5:27 PM
To: geonetwork-users@lists.sourceforge.net
Cc: geonetwork-devel@lists.sourceforge.net
Subject: [ExternalEmail] Re: [GeoNetwork-devel] [GeoNetwork-users] Advanced search for time extent in 2.4.1