Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
filereference:dbssystem [2015/03/27 08:46] – enviadmin | filereference:dbssystem [2021/10/20 14:18] – [System Database and User/Project Database: Basic Concept] enviadmin | ||
---|---|---|---|
Line 6: | Line 6: | ||
To link the information stored in the Area input files with the different database information, | To link the information stored in the Area input files with the different database information, | ||
- | Each database entry is defined by a unique key, which has to be a **two-sign alphanumerical ID** in ENVI-met | + | Each database entry is defined by a unique key, which has to be a **six-sign alphanumerical ID** in ENVI-met. Any reference to a database entry, may it be in an Area Input file or some other table of the database |
The ENVI-met database system is a global system which is used for each simulation and all ENVI-met applications. | The ENVI-met database system is a global system which is used for each simulation and all ENVI-met applications. | ||
Line 14: | Line 14: | ||
===== Database Design ===== | ===== Database Design ===== | ||
- | [{{ : | + | {{ : |
Each ENVI-met database, System or User/ | Each ENVI-met database, System or User/ | ||
Line 35: | Line 35: | ||
If they all use different IDs, the resulting set will be simply the sum of the items in both databases with all items available. However, if you use the same ID for items in both the System DB and the User/ | If they all use different IDs, the resulting set will be simply the sum of the items in both databases with all items available. However, if you use the same ID for items in both the System DB and the User/ | ||
- | In the example below, the System DB introduces 3 elements: '' | + | In the example below, the System DB introduces 3 elements: '' |
- | + | ||
- | [{{ : | + | |
+ | {{ : | ||
Line 46: | Line 45: | ||
=== User Database === | === User Database === | ||
The **//User Database// | The **//User Database// | ||
+ | |||
+ | By default, the User Database is stored in the ENVI-met program folder under **sys.userdata**. Starting with ENVI-met 5, you can also specifiy a different location for the User Database e.g. on a netwwork drive or in the cloud. | ||
+ | |||
+ | Do do so, change the path options (1) in the Workspace Manager in the ENVI-met Settings tab (see below) | ||
+ | |||
+ | {{ : | ||
+ | |||
=== Project Database === | === Project Database === | ||
Line 51: | Line 57: | ||
However, if you have a lot of different projects or very specific projects, it might not be the best idea to store all the user-defined items in one big database. Especially if you want to adjust certian properties of items, e.g. soil materials, for certain simulations or projects, it might be undesirable that these material changes will effect all other simulations as well - which will be the case if edited in the global User Database. | However, if you have a lot of different projects or very specific projects, it might not be the best idea to store all the user-defined items in one big database. Especially if you want to adjust certian properties of items, e.g. soil materials, for certain simulations or projects, it might be undesirable that these material changes will effect all other simulations as well - which will be the case if edited in the global User Database. | ||
- | For an easier handling of data, ENVI-met gives the option to specify an individual **//Project Database// | + | For an easier handling of data, ENVI-met gives the option to specify an individual **//Project Database// |
Line 82: | Line 89: | ||
===== The Database Manager ===== | ===== The Database Manager ===== | ||
- | Although the database files follow the XML-standard, | + | Although the database files follow the XML-standard, |