A small in-houses annotation team wants to use DDS with a small number of internal users, e.g. 1-3 user(s). The team does not need the full collaboration features, however persistance of the annotation is mandatory.
Issues
There are several areas that could benefit from improvements to enhance usability and comprehension, especially for users who may not consult documents before proceeding:
In the current setup, the "quick mode" does not persist annotations in the database. This fact, although mentioned in the tutorials and documents, is not explicitly stated within the user interface. This oversight could affect those who lean towards "quick mode" usage without prior reading of the accompanying documentation.
The existing process for setting up a team in the collaborative mode appears excessive for use cases that primarily require simple shared annotation usage. This complexity could deter users looking for a more straightforward annotation solution.
Certain compulsory steps for using the collaborative mode, such as user creation, dataset creation, etc., may not be intuitively understandable from the user interface alone. This lack of clarity could be a hurdle for users who do not delve into the documents before initiating usage.
Proposals
Clarify in the "quick mode" that annotations are not saved automatically, and that users need to manually export for the preservation of annotated results.
Introduce a set of "collaborative annotation recipes" for a simplified, one-click setup in the collaborative mode. These should include automatic setup of initial users, datasets, permissions, and so on.
Ensure the user interface explicitly communicates that certain steps need to be executed via the command line interface (CLI). This should help guide users who may not be aware of this necessity before reading the tutorials.
Background
A small in-houses annotation team wants to use DDS with a small number of internal users, e.g. 1-3 user(s). The team does not need the full collaboration features, however persistance of the annotation is mandatory.
Issues
There are several areas that could benefit from improvements to enhance usability and comprehension, especially for users who may not consult documents before proceeding:
In the current setup, the "quick mode" does not persist annotations in the database. This fact, although mentioned in the tutorials and documents, is not explicitly stated within the user interface. This oversight could affect those who lean towards "quick mode" usage without prior reading of the accompanying documentation.
The existing process for setting up a team in the collaborative mode appears excessive for use cases that primarily require simple shared annotation usage. This complexity could deter users looking for a more straightforward annotation solution.
Certain compulsory steps for using the collaborative mode, such as user creation, dataset creation, etc., may not be intuitively understandable from the user interface alone. This lack of clarity could be a hurdle for users who do not delve into the documents before initiating usage.
Proposals
Clarify in the "quick mode" that annotations are not saved automatically, and that users need to manually export for the preservation of annotated results.
Introduce a set of "collaborative annotation recipes" for a simplified, one-click setup in the collaborative mode. These should include automatic setup of initial users, datasets, permissions, and so on.
Ensure the user interface explicitly communicates that certain steps need to be executed via the command line interface (CLI). This should help guide users who may not be aware of this necessity before reading the tutorials.