RE: [Geonetwork-devel] Validation of XML against ISO 19139 XSDs and other ISO 19115 rules

Hi Jeroen,

I forgot to reply to this email. I have been so excited that you are
considered my suggested user requirements. ;--)

I'm not 100% sure of what you are suggesting in your email but I think that
there was a similar discussion on the metadata@anonymised.com list. I
believe that the identification of when an XML metadata record was last
updated can be gained from the systems date/time stamp on the XML file. For
example, if the XML documents are in a web accessible folder then the
"modified time" from the HTML document headers can be used to identify the
time the file was last modified.

If the XML documents are available via a RDBMS one can use a column to
identify when the XML record was last updated. This seems to be what Andrea
is referring to in her email response to your question. It seems that the
RDBMS field "lastChangeDate" could be used to identify this.

If you are harvesting using z3950 then this may be a problem. I don't think
that there is an option to identify when the record was last updated.

In summary, I think that it is part of the harvesting process that will
identify when an XML record was last modified, not part of the XML record's
content itself.

I hope that this helps.

John

-----Original Message-----
From: geonetwork-devel-admin@lists.sourceforge.net
[mailto:geonetwork-devel-admin@lists.sourceforge.net] On Behalf Of Jeroen
Ticheler
Sent: Saturday, 20 May 2006 12:47 AM
To: Geonetwork-devel Geonetwork-devel
Subject: Re: [Geonetwork-devel] Validation of XML against ISO 19139 XSDs and
other ISO 19115 rules

John and Andrea,
Just one more comment on the point below. I have been looking into this not
so long ago when we were adding convenience calendars to the editor. John,
you are right about the format of that field. However, there is a problematic
issue for which we do not have an answer here and that causes us to actually
fill out the field as if it were a DateTime:
To know when a metadata has been updated, it is not enough to know the day.
For many cases you really need to know exactly when the update occurred. For
instance, when we compare two metadata while harvesting from a system, we
have to know exactly when that metadata was updated last. The same is true
for trivial functions like: what metadata records have a creation date and
dateStamp that only differ by e.g. 1 minute? We can use this to retrieve
metadata records that were added, but than not updated/ edited online by a
user and that may therefor be empty left over records that an admin can clean
up.
Any suggestions on this are very welcome!
Ciao,
Jeroen

On May 19, 2006, at 4:31 PM, Andrea Carboni wrote:

2. The domain for the "dateStamp" element is "Date". "Date" is an ISO 8601
date format not an ISO 8601 DateTime format. GeoNetwork prompts a dateTime
format in the content of the "dateStamp" element. It should be a "Date"
format. For example, yyyy-mm-dd, yyyymmdd, yyyy-mm, yyyy or yy (for the
century although this is not available in the W3C XML Schema implementation)
not yyyy-mm-ddThh:mm:ss. DateTime formats should also include the time zone
eg. yyyy-mm-ddThh:MM:ss+Z so that local times can be used rather than GMT.

Ok, we can fix it.

Hi John,
Another reply :slight_smile:

On May 23, 2006, at 8:30 AM, John.Hockaday@anonymised.com wrote:

Hi Jeroen,

I forgot to reply to this email. I have been so excited that you are
considered my suggested user requirements. ;--)

Good, I like happy people! :slight_smile:

I'm not 100% sure of what you are suggesting in your email but I think that
there was a similar discussion on the metadata@anonymised.com list. I
believe that the identification of when an XML metadata record was last
updated can be gained from the systems date/time stamp on the XML file. For
example, if the XML documents are in a web accessible folder then the
"modified time" from the HTML document headers can be used to identify the
time the file was last modified.

Good idea, not sure if we also provide that info in the header. Andrea would know.

If the XML documents are available via a RDBMS one can use a column to
identify when the XML record was last updated. This seems to be what Andrea
is referring to in her email response to your question. It seems that the
RDBMS field "lastChangeDate" could be used to identify this.

Indeed that was what he (! :wink: ) suggested.

If you are harvesting using z3950 then this may be a problem. I don't think
that there is an option to identify when the record was last updated.

In summary, I think that it is part of the harvesting process that will
identify when an XML record was last modified, not part of the XML record's
content itself.

Yes, correct. Harvesting is not the only place that needs a precise date, but it seems the above covers all options.
Ciao,
Jeroen

I hope that this helps.

John

-----Original Message-----
From: geonetwork-devel-admin@lists.sourceforge.net
[mailto:geonetwork-devel-admin@lists.sourceforge.net] On Behalf Of Jeroen
Ticheler
Sent: Saturday, 20 May 2006 12:47 AM
To: Geonetwork-devel Geonetwork-devel
Subject: Re: [Geonetwork-devel] Validation of XML against ISO 19139 XSDs and
other ISO 19115 rules

John and Andrea,
Just one more comment on the point below. I have been looking into this not
so long ago when we were adding convenience calendars to the editor. John,
you are right about the format of that field. However, there is a problematic
issue for which we do not have an answer here and that causes us to actually
fill out the field as if it were a DateTime:
To know when a metadata has been updated, it is not enough to know the day.
For many cases you really need to know exactly when the update occurred. For
instance, when we compare two metadata while harvesting from a system, we
have to know exactly when that metadata was updated last. The same is true
for trivial functions like: what metadata records have a creation date and
dateStamp that only differ by e.g. 1 minute? We can use this to retrieve
metadata records that were added, but than not updated/ edited online by a
user and that may therefor be empty left over records that an admin can clean
up.
Any suggestions on this are very welcome!
Ciao,
Jeroen

On May 19, 2006, at 4:31 PM, Andrea Carboni wrote:

2. The domain for the "dateStamp" element is "Date". "Date" is an ISO 8601
date format not an ISO 8601 DateTime format. GeoNetwork prompts a dateTime
format in the content of the "dateStamp" element. It should be a "Date"
format. For example, yyyy-mm-dd, yyyymmdd, yyyy-mm, yyyy or yy (for the
century although this is not available in the W3C XML Schema implementation)
not yyyy-mm-ddThh:mm:ss. DateTime formats should also include the time zone
eg. yyyy-mm-ddThh:MM:ss+Z so that local times can be used rather than GMT.

Ok, we can fix it.