Changes between Version 17 and Version 19 of Ticket #2049


Ignore:
Timestamp:
Dec 8, 2016, 3:36:59 PM (4 years ago)
Author:
Nicklas Nordborg
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2049 – Description

    v17 v19  
    44
    55 1. This feature must be enabled per annotation type. Existing annotation types will have it disabled by default. Once this feature has been enabled it will not be possible to disabled it unless all existing project-specific annotations are first deleted.
    6  2. The current core API should be usable and behave more or less in a backwards compatible way for annotation types that have the option enabled.
     6 2. The current core API should be usable and behave more or less in a backwards compatible way for annotation types that have the option enabled. Exception: The existing API is not enough to be able to create a project-specific annotation when a default value already exists.
    77 3. Existing annotation values doesn't belong to any project and should be treated as '''default values''' if the project-specific setting is enabled for an annotation type.
    88 4. When a users is working without an active project only the default values are visible/editable for annotations that are project-specific.
    9  5. If an annotation has a default value but not any project-specific value when a project is active, the default value is visible and should be treated as if it was a project-specific value, except...
    10  6. Default values are not editable (unless maybe via new API methods) when a project is active. Trying to change a default value results in a project-specific value being created instead. The default value is then no longer visible and should not match queries either.
     9 5. If an annotation has a default value but not any project-specific value when a project is active, the default value is visible and should be treated as if it was a project-specific value.
     10 6. ~~Default values are not editable (unless maybe via new API methods) when a project is active.~~ Trying to change a default value results in a project-specific value being created instead. The default value is then no longer visible and should not match queries either.
     11The core API needs to be updated for this behavior. The existing API will modified the default annotation values even when a project is active.
    1112 7. Deleting a project-specific value makes the default value visible again.
    1213 8. Deleting a default value can only be done when no project is active (unless maybe via new API methods).