Hi,
I read the wiki page at http://trac.osgeo.org/geonetwork/wiki/ISO19119impl on OGC:getCapabilities harvesting.
Generating metatdata from getCapabilities docs makes a lot of sense to me.
Is there working code yet and if so, where and how can I get it to work in my GeoNetwork 2.2 fresh install?
Cheers
Sebastian
Hi Sebastian,
Quoting Sebastian Schmitz <schmitz@anonymised.com>:
Hi,
I read the wiki page at
http://trac.osgeo.org/geonetwork/wiki/ISO19119impl on
OGC:getCapabilities harvesting.
Generating metatdata from getCapabilities docs makes a lot of sense to me.Is there working code yet and if so, where and how can I get it to work
in my GeoNetwork 2.2 fresh install?
This will be available in 2.3.
http://trac.osgeo.org/geonetwork/wiki/proposals
... and a first implementation is in current svn trunk.
HTH. Francois
Hi,
great!
When will 2.3 be released? Roughly?
Cheers
Sebastian
Francois-Xavier Prunayre schrieb:
Hi Sebastian,
Quoting Sebastian Schmitz <schmitz@anonymised.com>:
Hi,
I read the wiki page at
http://trac.osgeo.org/geonetwork/wiki/ISO19119impl on
OGC:getCapabilities harvesting.
Generating metatdata from getCapabilities docs makes a lot of sense to me.Is there working code yet and if so, where and how can I get it to work
in my GeoNetwork 2.2 fresh install?This will be available in 2.3.
http://trac.osgeo.org/geonetwork/wiki/proposals
... and a first implementation is in current svn trunk.HTH. Francois
Hi,
harvesting ogc services works fine using svn trunk. Great - so I can easily generate WMS and other OWS metadata.
This leads me to a pretty basic question, which I could not find an answer to browsing the archives and manual:
I am confused as how to distinguish between data and service metadata from a user point of view.
How would a user easily distinguish between the two in search results displayed? And how could one issue a search only against data respectively service entries - for instance only against WMS services?
Cheers
Sebastian
Francois-Xavier Prunayre schrieb:
Hi Sebastian,
Quoting Sebastian Schmitz <schmitz@anonymised.com>:
Hi,
I read the wiki page at
http://trac.osgeo.org/geonetwork/wiki/ISO19119impl on
OGC:getCapabilities harvesting.
Generating metatdata from getCapabilities docs makes a lot of sense to me.Is there working code yet and if so, where and how can I get it to work
in my GeoNetwork 2.2 fresh install?This will be available in 2.3.
http://trac.osgeo.org/geonetwork/wiki/proposals
... and a first implementation is in current svn trunk.HTH. Francois
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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
Hi Sebastian,
On lun, 2008-05-26 at 23:52 +0200, Sebastian Schmitz wrote:
Hi,
harvesting ogc services works fine using svn trunk. Great - so I can
easily generate WMS and other OWS metadata.
This leads me to a pretty basic question, which I could not find an
answer to browsing the archives and manual:
I am confused as how to distinguish between data and service metadata
from a user point of view.
How would a user easily distinguish between the two in search results
displayed?
For the time being, an option is to use GeoNetwork categories. I'm use
to put service metadata into "interactive resources" and data metadata
in "datasets" (using the option of the harvester).
I plan to add into lucene index an option to search for service indexing
the SV_ServiceIdentification element.
Another option could be to add an icon somewhere in the search result to
identify data, service ... any proposals ? any icon designer on the
list ? 
And how could one issue a search only against data
respectively service entries - for instance only against WMS services?
Service type should also be in the index to search by service type.
That's my ideas for now, but comments and discussion on that are very
welcomed!
Ciao.
Francois
--
View this message in context: http://www.nabble.com/generate-metadata-from-getCapabilities-document-tp17463252p17483684.html
Sent from the geonetwork-users mailing list archive at Nabble.com.
Hi Sebastian,
Currently there's no distinguishing element as far as I know (François?). There is an index that filters on the content-type as defined in the ISO19115 standard, distinguishing paper from digital data, but that does not differentiate services from data. thee's also an index on download (data, pdf's etc) and interactive (WMS and so) which is based on the protocol field in ISO19115. The last index should probably be extended by indexing service metadata (19119) as interactive too. Not sure if that's planned for by François for now.
Ciao,
Jeroen
On May 26, 2008, at 11:52 PM, Sebastian Schmitz wrote:
Hi,
harvesting ogc services works fine using svn trunk. Great - so I can
easily generate WMS and other OWS metadata.
This leads me to a pretty basic question, which I could not find an
answer to browsing the archives and manual:
I am confused as how to distinguish between data and service metadata
from a user point of view.
How would a user easily distinguish between the two in search results
displayed? And how could one issue a search only against data
respectively service entries - for instance only against WMS services?Cheers
Sebastian
Francois-Xavier Prunayre schrieb:
Hi Sebastian,
Quoting Sebastian Schmitz <schmitz@...407...>:
Hi,
I read the wiki page at
ISO19119impl – GeoNetwork opensource Developer website on
OGC:getCapabilities harvesting.
Generating metatdata from getCapabilities docs makes a lot of sense to me.Is there working code yet and if so, where and how can I get it to work
in my GeoNetwork 2.2 fresh install?This will be available in 2.3.
proposals – GeoNetwork opensource Developer website
... and a first implementation is in current svn trunk.HTH. Francois
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
geonetwork-users List Signup and Options
GeoNetwork OpenSource is maintained at GeoNetwork - Geographic Metadata Catalog download | SourceForge.net-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
geonetwork-users List Signup and Options
GeoNetwork OpenSource is maintained at GeoNetwork - Geographic Metadata Catalog download | SourceForge.net
Hi,
On mer, 2008-05-28 at 18:33 +0200, Jeroen Ticheler wrote:
Hi Sebastian,
Currently there's no distinguishing element as far as I know
(François?).
Schema for metadata on data or service is always iso19139 but the
identification section is different : srv:SV_ServiceIdentification for
service and gmd:MD_DataIdentification for data.
There is an index that filters on the content-type as
defined in the ISO19115 standard, distinguishing paper from digital
data, but that does not differentiate services from data. thee's also
an index on download (data, pdf's etc) and interactive (WMS and so)
which is based on the protocol field in ISO19115. The last index
should probably be extended by indexing service metadata (19119) as
interactive too. Not sure if that's planned for by François for now.
It is in the coming month (june or july) ... Maybe we should also have
an option to search for WMS, WFS, ...
Ciao.
Francois
Hi,
Francois-Xavier Prunayre schrieb:
Hi, On mer, 2008-05-28 at 18:33 +0200, Jeroen Ticheler wrote:
Hi Sebastian,
Currently there's no distinguishing element as far as I know (François?).Schema for metadata on data or service is always iso19139 but the
identification section is different : srv:SV_ServiceIdentification for
service and gmd:MD_DataIdentification for data.
So that could be used to distinguish between data and services, right? One could query against the identification section...? I am not yet very familiar with the iso19139 schema.
There is an index that filters on the content-type as defined in the ISO19115 standard, distinguishing paper from digital data, but that does not differentiate services from data. thee's also an index on download (data, pdf's etc) and interactive (WMS and so) which is based on the protocol field in ISO19115. The last index should probably be extended by indexing service metadata (19119) as interactive too. Not sure if that's planned for by François for now.
It is in the coming month (june or july) ... Maybe we should also have
an option to search for WMS, WFS, ...
I believe, allowing to search for all OWS and also allowing to narrow that search down to a specific service type would be a very convenient search option. ServiceType is stored in Identification/ServiceIdentication/ServiceType/Name, right?
Any pointers on how to make that field queryable via search GUI most welcome..
>Cheers
Sebastian
Ciao.
Francois