Changes between Version 1 and Version 2 of proposals/GeoNetworkDataDir


Ignore:
Timestamp:
Mar 9, 2012, 2:34:11 AM (12 years ago)
Author:
fxp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • proposals/GeoNetworkDataDir

    v1 v2  
    1 = Document and Field boosting =
     1= GeoNetwork data directory =
    22
    33|| '''Date''' || 2012/03/09 ||
    … …  
    1010
    1111== Overview ==
     12
     13The GeoNetwork data directory is the location on the file system where GeoNetwork stores all of its custom configuration. This configuration defines such things as: What thesaurus is used by GeoNetwork? What schema is plugged in GeoNetwork?. The data directory also contains a number of support files used by GeoNetwork for various purposes (eg. Lucene index, spatial index, logos).
     14
     15It is a good idea to define an external data directory when going to production in order to make upgrade easier.
    1216
    1317
    … …  
    3034
    3135
     36=== Structure of the data directory ===
     37
     38 * data_directory/
     39  * codelist: The thesaurus in SKOS format
     40  * config: Extra configuration (eg. overrides)
     41   * schemaplugin-uri-catalog.xml
     42   * JZKitConfig.xml
     43  * metadata_data: The data related to metadata records
     44  * index: All indexes used for search
     45   * nonspatial: Lucene index
     46   * spatialindex.*: ESRI Shapefile for the index (if not using PostGIS)
     47  * resources:
     48   * htmlcache
     49   * images
     50    * harvesting
     51    * logo
     52    * statTmp
     53  * removed: Folder with removed metadata.
     54  * svn_repository: The subversion repository
     55  * schemaPlugins: The directory used to store new metadata standards
     56
    3257=== Backwards Compatibility Issues ===
    3358