An annotation is a region of an image that can be labeled by the users.
Pivot object for the connection between Annotations and Labels.
An annotation session groups multiple annotations of a volume based on their creation date.
An annotation model.
A label source adapter.
A service that generates thumbnail images for newly created volumes.
Middleware to allow session cookie authentication for the route only.
This model stores information on an image file in the file system.
Pivot object for the connection between Images and Labels.
Job
Annotations on an image can have multiple labels. A label is e.g. the type of the object visible in the region of the annotation. So if you put a circle annotation around a rock, you would label the annotation with rock.
The source (database) of a label.
A label tree is a group of labels. Projects can choose to used different label trees, which are then offered for labeling things in the project.
Volumes can contain different types of image-series. One type would be a time-series of a static camera taking photos in regular intervals for example. Another type coud be images from a moving camera.
A notification that is displayed through the in-app notification system.
A policy for caching the return values of the authorization rules during a request.
A role of a user. Users have one global role and can have many project- specific roles.
The module registry service.
The image tile cache.
A shape, e.g. point or circle.
System messages are broadcasts from the application administrators that reach all users of the instance. Whenevr a new system message is published, each user will get a notification to read it.
Some models have fixed, "constant" instances. An example is the Role model, which may have e.g. the roles "admin" and "user". These are always the same and do not change.
The visibility of a model.
A volume is a collection of images. Volumes belong to one or many projects.