The server administrators can manage users and projects.
Permissions can be defined per project for each user, granting access to specific features.
Server documents
Server documents are XML files stored in the database with additional metadata.
A server document belongs to a specific project, and can be shared with the other project users.
A server document can be defined as a corpus, making the document's corpus easily loadable in other documents.
A server document defined as a corpus can also be shared, allowing other users to load it in their documents.
History of modifications allows reverting the document to previous versions.
Conversion results (html, pdf, zip...) are stored in a (modifiable) permanent history.
Project Files
Each project has a root directory, usually located in projects like avaa-toolkit/projects/project-id
Files added in the project directory (such as annotation or media files) will be directly accessible from AVAA when editing documents. For instance, you could add a bunch of EAF files, and easily create a corpus by selecting the files.
Files in the project directory are accessible from AVAA by all users of the project.
WebDAV can be configured for native access via a virtual drive of the project directory
User Files
Each user has a personal directory inside the project directory: avaa-toolkit/projects/project-id/users/user-id
User files can be uploaded and managed directly in the browser via
Other users do not have access to these files, however they can use a shared corpus based on such files.
