Glossary
- a Mediaflux namespace can be thought of as a folder or directory
- a Mediaflux asset is a container holding a file and metadata about that file. When you upload a file, Mediaflux makes an asset, puts the file in the asset, and creates a default set of metadata about the asset including a checksum of the contents of the file.
Project Roles
The standard roles per project that are provided are:
- administrator
- access, create, modify, and destroy project child namespaces
- access, create, modify, and destroy project assets
- manage specialised project metadata definitions and queries
- grant project access to other users (however, this is best done by the Mediaflux support team by raising a ticket).
- participant-a
- access project child namespaces
- access project assets
- participant-acm
- access, create, and modify project child namespaces
- access, create, and modify project assets
- participant-acmd
- access, create and modify (but not destroy) project namespaces
- access, create, modify and destroy project assets
- participant-acmd-n
- access, create, modify and destroy project child namespaces
- access, create, modify and destroy project assets
Note: modify includes move
Examples
- If you wanted to give somebody read only access to your project, then they would be granted the role participant-a
- Give people the role participant-acmd-n if you want them to have as much power as the administrator regarding data, but not allow them the ability to manage metadata definitions or to grant others access to the project