OntologyDBWiki/DeveloperDocumentation/ProjectsSpecification: Difference between revisions
Jump to navigation
Jump to search
imported>KaiRunte No edit summary |
imported>KaiRunte No edit summary |
||
| Line 15: | Line 15: | ||
The ontology database is supposed to be a storing facility for various controlled vocabularies and ontologies. | The ontology database is supposed to be a storing facility for various controlled vocabularies and ontologies. | ||
=== Projects Affiliation === | |||
? | |||
=== Database Name === | === Database Name === | ||
| Line 27: | Line 31: | ||
ONTODB | ONTODB | ||
=== Database Management System Type === | |||
MySQL-4.x | |||
=== New Members === | === New Members === | ||
Revision as of 12:25, 13 April 2005
Specification Ontology Database
GPMS Information
Project Name
ONTODB
Project Class
ONTODB
Project Description
The ontology database is supposed to be a storing facility for various controlled vocabularies and ontologies.
Projects Affiliation
?
Database Name
ontodb_test
Database Description
Contains only test data. Do not try to use it for real research.
Database DataSource_Type
ONTODB
Database Management System Type
MySQL-4.x
New Members
Kai Runte (Admin)
Roles and Rights
| Role | Description | Rights |
| User | Denotes the average user. They can query the ontology database, but nothing else. | basic_access |
| Maintainer | This person can import and export an ontology, but cannot create new ones. | basic_access, export, import, edit |
| Developer | A developer has all the rights of a maintainer. Additionally (s)he should be able to alter a database structure. | basic_access, export, import, edit, modify_db |
| Chief | A chief is responsible for adding/removing users to a project/ontology. | basic_access, export, import, edit, add_user |
| Admin | An admin has basically all rights | basic_access, export, import, edit, add_user, modify_db |