Changes between Version 3 and Version 4 of CSW202Improvements
- Timestamp:
- Feb 19, 2009, 3:43:07 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CSW202Improvements
v3 v4 1 1 2 2 == Context == 3 !GeoNetwork CSW current implementation has some known issues or missing functionnalities. The purpose of this document is to analyse the missing or incomplete elements in !GeoNetwork according to CSW ISO 2.0.2 specification. The work will be based on current !GeoNetwork trunk and focus on apply patch to !GeoNetwork project and GeoSource.3 !GeoNetwork CSW current implementation has some known issues or missing functionnalities. The purpose of this document is to analyse the missing or incomplete elements in !GeoNetwork according to CSW ISO 2.0.2 specification. The work will be based on current !GeoNetwork trunk and focus on apply patch to !GeoNetwork project and !GeoSource. 4 4 5 5 ---- … … 10 10 * Specifications: 11 11 * http://portal.opengeospatial.org/files/?artifact_id=21460 12 * INSPIRE Service attachment:INSPIRE-CSW-Synthese.doc12 * INSPIRE Service !attachment:INSPIRE-CSW-Synthese.doc 13 13 * Implementing/compliant tools : 14 14 * http://www.mdweb-project.org/ … … 42 42 43 43 ===== Issues ===== 44 * How to handle '''namespace''' properly ? GeoNetwork will be as much flexible as possible and compliant to the specification regarding namespace handling.44 * How to handle '''namespace''' properly ? !GeoNetwork will be as much flexible as possible and compliant to the specification regarding namespace handling. 45 45 1. remove namespace from mapping (dc, csw, apiso ...) 46 46 2. mapped all properties with apiso namespace and dc (ie !SupportedISOQueryables, !SupportedDublinCoreQueryables) 47 47 3. handled properties without dealing with namespace (ie whatever we provide : dc, csw, apiso... csw should be able to perform operation and to handle search parameters) 48 48 49 * All GeoNetwork search parameters will be supported in CSW search (even if not list in the GetCapabilities documents). Eg. any = africa will work andAnyText = africa also.49 * All !GeoNetwork search parameters will be supported in CSW search (even if not list in the !GetCapabilities documents). Eg. any = africa will work and !AnyText = africa also. 50 50 51 51 * Updated CSW202 schema to make validate option working. … … 79 79 ||!AnyText || No || No || - || 80 80 ||Format || No || No || - || 81 ||Identifier || No || Yes || must be mapped to FileIdentifier (fileId in lucene index)||82 ||Modified || No || Yes || modified currently mapped to changeDate which is only indexed for dc schema in geonetwork. Modified must be mapped to dateStamp.Date or DateTime in ISO schema ??? ||81 ||Identifier || No || Yes || must be mapped to !FileIdentifier (fileId in lucene index)|| 82 ||Modified || No || Yes || modified currently mapped to changeDate which is only indexed for dc schema in geonetwork. Modified must be mapped to dateStamp.Date or !DateTime in ISO schema ??? || 83 83 ||Type || No || No || - || 84 84 ||!WestBoundLongitude || '''Yes''' || - || -> westBL in lucene index, check spatial search in lucene since Jesse's work || … … 131 131 || Operation || Yes || - || add operation to lucene index || 132 132 || !GeographicDescriptionCode || No || No || e.g. !GeographicDescriptionCode for dataset || 133 || !OperatesOn || '''Yes''' || - || add OperatesOn to lucene index, should map MD_DataIdentification.citation.CI_Citation.identifier but in Geonetwork/Geosource, identifier is store in '''uuidref attribute''' of MD_DataIndetification ||133 || !OperatesOn || '''Yes''' || - || add !OperatesOn to lucene index, should map MD_DataIdentification.citation.CI_Citation.identifier but in Geonetwork/Geosource, identifier is store in '''uuidref attribute''' of MD_DataIndetification || 134 134 || !OperatesOnIdentifier || '''Yes''' || - || add !OperatesOnIdentifier to lucene index || 135 135 || !OperatesOnName || '''Yes''' || - || add !OperatesOnName to lucene index || … … 189 189 <parameter name="CswParameterName" field="LuceneFieldKey" type="CswType" /> 190 190 }}} 191 * Profil support in CSW for DescribeRecord operation191 * Profil support in CSW for !DescribeRecord operation 192 192 {{{ 193 193 <operation name="DescribeRecord"> … … 205 205 ---- 206 206 == OGC-CSW Iso Profil management == 207 * Add the profil for DescribeRecord operation in config-csw.xml207 * Add the profil for !DescribeRecord operation in config-csw.xml 208 208 * Add schema to xml/validation/csw202_apiso100/csw/2.0.2 209 * Add profil-brief.xsl, profil-summary.xsl, profil-full.xsl in xml/csw/schemas/iso19139 directory for GetRecords output.210 211 ---- 212 == OGC-CSW TestSuite ==209 * Add profil-brief.xsl, profil-summary.xsl, profil-full.xsl in xml/csw/schemas/iso19139 directory for !GetRecords output. 210 211 ---- 212 == OGC-CSW !TestSuite == 213 213 214 214 === Teamengine === … … 221 221 * [https://project.camptocamp.com/doc/brgm_geosourcev2/testSuiteResults OGC test suite results] 222 222 223 * Make Test csw:level1.1 passed by modifying GetRecords-InvalidRequest operation : Typenames must be an attribute of the query element. (but in specificiation, should be csw:Record by default ??)224 * Added private checkTypenames method in GetRecords class225 226 * csw:level1.2 / !DescribeRecord- ValidResponseStructure223 * Make Test csw:level1.1 passed by modifying !GetRecords-!InvalidRequest operation : Typenames must be an attribute of the query element. (but in specificiation, should be csw:Record by default ??) 224 * Added private checkTypenames method in !GetRecords class 225 226 * csw:level1.2 / !DescribeRecord-!ValidResponseStructure 227 227 * Regarding the BRGM specification : The !DescribeRecordResponse must include three "!SchemaComponent" elements : 228 228 * identification.xsd for data (ISO19115/19139) … … 236 236 * Fix namespace for !TypeName parameter : The value of !TypeName has to be qualified by a namespace or should be the default document namespace. There is currently an exception if any namespace sent in request. 237 237 238 * csw:level1.3 / csw. GetCapabilities.document:239 * Is there a reason to comment NullCheck !ComparisonOperator in GN ?240 * Regarding this test, 7 commons parameters are expected, idem -> what to do with common constraints (i.e. IsoProfiles, postEncoding)238 * csw:level1.3 / csw.!GetCapabilities.document: 239 * Is there a reason to comment !NullCheck !ComparisonOperator in GN ? 240 * Regarding this test, 7 commons parameters are expected, idem -> what to do with common constraints (i.e. !IsoProfiles, postEncoding) 241 241 {{{ 242 242 ... … … 261 261 262 262 * Test methodology: 263 * GeoNetwork & Geosource : Harvesting mechanism264 * MdWeb : Distributed search mechanism263 * !GeoNetwork & Geosource : Harvesting mechanism 264 * !MdWeb : Distributed search mechanism 265 265 266 266 === Test URL === … … 275 275 276 276 ---- 277 == OGC-CSW extension in GeoNetwork ==278 === GetRecords operation ===277 == OGC-CSW extension in !GeoNetwork == 278 === !GetRecords operation === 279 279 * Added resultsType="results_with_summary" for narrow your search option (see geocat.ch sandbox) 280 280 * Added outputSchema="own" to return metadata record in their own format (dc, fgdc, iso, ...) … … 292 292 293 293 === output/format === 294 * csw.pdf : GetRecords operation results in pdf format.295 * csw.txt : GetRecords operation results in txt format.294 * csw.pdf : !GetRecords operation results in pdf format. 295 * csw.txt : !GetRecords operation results in txt format. 296 296 : to be defined rss 297