| 7 | | here you can load the example data, or reset to database to its empty form. |
| 8 | | empty means |
| 9 | | * the tables definitions are loaded in the database |
| 10 | | * users admin and anonymous are present |
| 11 | | * usergroups biologist and bioinformatician are present |
| 12 | | * permissions as defined in the gui.xml are loaded: this means which groups can see which screens and are allowed to write which entities |
| | 7 | xQTL can store files in a semi-relational way. In ''Browse data'' -> ''View files'' you can add an entity which depicts a file, and then upload the content of the file. The content is attached to this entity. Some data matrix storage variants (binary, csv) also use this file storage mechanism. In order to use it, you must set and validate a path on the server where the application is running. |
| | 8 | * Start by clicking to ''Settings'', then select ''File storage''. |
| | 9 | * If not path is set, type one in the box and press ''Set path''. |
| | 10 | * The status of 'does it exist' and 'does it have content' is now updated. Consider if you want to use this location. |
| | 11 | * Press ''Validate'' to attempt a mkdir operation if the location does not exist, and attempt to write-read-delete a small test file inside this location next. |
| | 12 | * If this succeeds, you will get a green VALIDATED message. If it fails, you will be informed why at the top, and the message will be UNVALIDATED. |
| | 13 | * Once this path has been set, files will be stored and read from this location. |
| | 14 | * If a path has been set but you are unhappy with it, you can use ''Delete path''. Beware: setting a new path will break existing links to entities and files. |
| 14 | | loading the example data (first set a storage path in File storage): now you have |
| 15 | | * example users 'bio-user' and 'bioinfo-user' |
| 16 | | * additional permissions loaded to give these users functional access to the database |
| 17 | | * example investigation, including |
| 18 | | * annotations for individual, chromosome, etc |
| 19 | | * geno/pheno dataset, tagged for QTL |
| 20 | | * Rqtl analysis ready to be executed |
| | 16 | === Manage the database === |
| 24 | | set a path and press Validate in order to get a location where xQTL can store files |
| | 20 | Making the database 'empty' means: |
| | 21 | * The xQTL data tables definitions are reloaded in the database. |
| | 22 | * Users 'admin' and 'anonymous' are loaded. |
| | 23 | * User groups 'biologist' and 'bioinformatician' are loaded. |
| | 24 | * Permissions (as defined in the application GUI XML) are loaded: this means which groups can see which screens and are allowed to write which entities. In this case, the permissions for biologist and bioinformatician are loaded. |
| | 25 | |
| | 26 | Loading the example data results in: |
| | 27 | * The example users 'bio-user' and 'bioinfo-user' are loaded. |
| | 28 | * Additional permissions to give these users functional access to the database are added. |
| | 29 | * The example investigation is loaded, including: |
| | 30 | * Annotations for individuals, chromosomes, etc. |
| | 31 | * Geno- and phenotype dataset, tagged and ready for QTL analysis. |
| | 32 | * The Rqtl analysis with configured parameters, ready to be executed. |
| | 33 | |
| | 34 | Furthermore, you can view the database connection settings and some relevant application generation properties here. In the future we wish to add more database tools for admin, for example, runtime switching of the connection, or running informative queries. |
