| Version 2 (modified by fxp, 15 months ago) |
|---|
GeoNetwork data directory
| Date | 2012/03/09 |
| Contact(s) | François Prunayre |
| Last edited | |
| Status | Ongoing |
| Assigned to release | 2.7.0 |
| Resources | |
| Ticket # | # |
Overview
The 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).
It is a good idea to define an external data directory when going to production in order to make upgrade easier.
Proposal Type
- Type: Core Change
- App: GeoNetwork
- Module: Config
Links
- Documents:
- Email discussions:
- Other wiki discussions:
Voting History
- Vote proposed by François Prunayre on 2012/03/XX, result was ...
Proposal
Structure of the data directory
- data_directory/
- codelist: The thesaurus in SKOS format
- config: Extra configuration (eg. overrides)
- schemaplugin-uri-catalog.xml
- JZKitConfig.xml
- metadata_data: The data related to metadata records
- index: All indexes used for search
- nonspatial: Lucene index
- spatialindex.*: ESRI Shapefile for the index (if not using PostGIS)
- resources:
- htmlcache
- images
- harvesting
- logo
- statTmp
- removed: Folder with removed metadata.
- svn_repository: The subversion repository
- schemaPlugins: The directory used to store new metadata standards
Backwards Compatibility Issues
Risks
Participants
- Francois Prunayre
Attachments
-
geonetwork-data-dirs.png
(24.3 KB) - added by fxp
15 months ago.
