"Seegrid will be due for a migration to confluence on the 1st of August. Any update on or after the 1st of August will NOT be migrated"

GeoNetwork

Evaluation

We are evaluating GeoNetwork as a candidate OGC Catalog Service (CS/W) implementation (see GAP analysis below)

CSW usage

GN comes packaged with a CSW test client which is helpful in developing CSW queries - recommend using it to get started! For AuScope's application, we simply like to get all the records available for a given area (say Australia) and present them on the Googlemap app.

Method Notes Result Test Link
GetCapabilities Returns the capabilities of GN's csw Ok http://auscope-portal.arrc.csiro.au/geonetwork/srv/en/csw?request=GetCapabilities&service=CSW&acceptFormats=application/xml
GetRecords Returns the number of records in GN Ok http://auscope-portal.arrc.csiro.au/geonetwork/srv/en/csw?request=GetRecords&constraintLanguage=CQL_TEXT
GetRecords Returns the full records for each record in GN (47 was the returned value from previous function) Ok http://auscope-portal.arrc.csiro.au/geonetwork/srv/en/csw?request=GetRecords&constraintLanguage=CQL_TEXT&constraint_language_version=1.1.0&resultType=results&maxRecords=47
GetRecords Gets a set of records based on a particular filter Ok http://auscope-portal.arrc.csiro.au/geonetwork/srv/en/csw?request=GetRecords&service=CSW&resultType=results&namespace=csw:http://www.opengis.net/cat/csw&constraint=<Filter xmlns="http://www.opengis.net/ogc" xmlns:gml="http://www.opengis.net/gml"><PropertyIsEqualTo><PropertyName>dc:title</PropertyName><Literal>test</Literal></PropertyIsEqualTo></Filter>&constraintLanguage=FILTER&constraint_language_version=1.1.0
DescribeRecords Returns the descriptions of the records available Ok http://auscope-portal.arrc.csiro.au/geonetwork/srv/en/csw?request=DescribeRecord

Test GeoNetwork node for CSIRO users

  • Our test GeoNetwork node is available at http://apacsrv7.arrc.csiro.au/geonetwork
  • This node runs GeoNetwork 2.1.0 .
  • Current configuration uses Sun Java 6, Apache 2.2, Tomcat 5.5, and a MySQL backend.
  • Map display is broken at the moment as (allegedly) FAO WMS is down. This issue also affects the FAO GeoNetwork node!
  • Sample metadata records have been loaded.
  • A guide to setting up a GeoNetwork 2.1.0 node under Debian 4 can be found in InfosrvicesGeoNetworkSetup.

GeoNetwork resources

-- BenCaradocDavies - 19 Nov 2007

GeoNetwork GAP Analysis for AuScope Grid community (as at Dec 2007)

Analysis conducted by RyanFraser and SimonCox

Results:
  • GN would be a useful starter for our community
  • to enable machine to machine needs to use standard terms
    • replace "free-text" publish/search with "controlled vocabularies" (i.e. registers) as much as possible
  • CS/W interface is OK for discovery, but unproven for service orchestration

Notes from meeting:
  • Provides a UI to create "records" scoped by a variety of schemas
    • ↠ inherits strengths, and limitations, of record schema
    • e.g. ISO 19115/19139 much free text
      • N.B. 19139 is the XML serialisation of 19115 (in a form view it is 19115 so should actually say 19115 and NOT 19139)
    • community profiles would replace free-text with controlled vocabularies ("drop-down menus")
    • ... and vocabs should be interfaces to registers ...
  • "New metadata", should say "New Record"
    • QUESTION -> how to add a new record (metadata) schema?
  • Limited set of "categories" (i.e. resource-types)
    • QUESTION: how was this suite of categories selected? Appears to be an augmentation of ISO MD_ScopeCode
    • QUESTION \x{2192} how to add new "categories"? how should management of "category list" be harmonized with other SDI initiatives?
  • If standard terms replaced "free text" searching/publishing, it could possibly function in machine to machine communications
    • replace text input with prompts based on controlled values
    • THIS WOULD MAKE RECORD CREATION EASIER/QUICKER!
    • QUESTION -> how do we add a thesaurus entry?
    • QUESTION -> what ability does it have to extend drop down menus
    • many complex objets should be pointers to a registry (ie: Persons in people registry)
  • Simon's image of registry "Holy Grails" -> publish/search almost all fields via drop down menus, contents taken from vocabularies published as registers
  • ... and replace all "complex objects" (e.g. "contact information") with pointers to register items
  • TITLE and ABSTRACT should be the only free text fields

  • GN primarily dataset oriented -> reason why states and commonwealth like it
  • GN have done a very good job of presenting ISO19115 metadata records which will be MORE THAN sufficient for our datasets etc
Topic attachments
I Attachment Action Size Date Who Comment
jeeves.docdoc jeeves.doc manage 884.5 K 19 Nov 2007 - 15:36 BenCaradocDavies Jeeves Developer's Manual
Topic revision: r17 - 23 Mar 2015, TerryRankine
 

Current license: All material on this collaboration platform is licensed under a Creative Commons Attribution 3.0 Australia Licence (CC BY 3.0).