OntologyDBWiki/DeveloperDocumentation/ProjectsSpecification: Difference between revisions
Jump to navigation
Jump to search
imported>KaiRunte No edit summary |
imported>KaiRunte No edit summary |
||
Line 6: | Line 6: | ||
=== project name === | === project name === | ||
/ONTODB | |||
=== project class === | === project class === | ||
/ONTODB | |||
=== project description === | === project description === | ||
=== database name === | === database name === | ||
Line 33: | Line 24: | ||
=== database DataSource_Type === | === database DataSource_Type === | ||
MySQL 4.x | /MySQL 4.x | ||
=== New Members === | === New Members === | ||
Kai Runte (Admin) | |||
== Roles and Rights == | == Roles and Rights == |
Revision as of 12:18, 13 April 2005
Specification Ontology Database
GPMS Information
project name
/ONTODB
project class
/ONTODB
project description
database name
ontodb_test
database description
Contains only test data. Do not try to use it for real research.
database DataSource_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 |