Hi,
On Mon, Jun 12, 2017 at 5:41 PM, <
Stephane.Laurencelle.externe@anonymised.com> wrote:
Hello,
I like to know at what serve the directory_data in geonetwork ?
The data directory is the location on the file system where the catalog
stores much of its custom configuration and uploaded files. 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 the
catalog for various purposes:
* Lucene index
* spatial index
* logos
* uploaded document attached to metadata records
* thumbnails
I know that when I import new metadata geonetwork create directory under
it like 00000-00099/4/
And under the 4 directory there is the public and private directory with
nothing in it.
Why geonetwork need it ?
Check this document [1]. Public and private folders contain the files
attached to the metadata, usually uploaded using the editor, for example,
thumbnails or related resources.
Instead of using the geonetwork ways of importing the metadata what is
taking too much time , they develop a home script that create it directly
in the Oracle database and at the end index it in the spatial index. But
using the house script use to add the metadata in the Oracle database the
metadata_data structure is not create.
Could that cause me problem in the future like spatial index corruption or
anything else ?
They don't affect the spatial index. About uploading resources related with
the metadata, GN will create these folders if they don't exist while the
upload process [2].
[1]
http://geonetwork-opensource.org/manuals/3.0.5/eng/users/user-guide/associating-resources/using-filestore.html
[2]
https://github.com/geonetwork/core-geonetwork/blob/develop/services/src/main/java/org/fao/geonet/api/records/attachments/FilesystemStore.java#L261
--
*Vriendelijke groeten / Kind regards,Juan Luis RodrÃguez.
<http://www.geocat.net/>Veenderweg 136721 WD BennekomThe NetherlandsT: +31
(0)318 416664 <+31318416664> <https://www.facebook.com/geocatbv>
<https://twitter.com/geocat_bv>
<https://plus.google.com/u/1/+GeocatNetbv/posts>Please consider the
environment before printing this email.*