Changes between Version 12 and Version 17 of Ticket #2049


Ignore:
Timestamp:
Dec 8, 2016, 1:39:28 PM (8 years ago)
Author:
Nicklas Nordborg
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2049 – Description

    v12 v17  
    33At the core level this must be implemented in a way that doesn't upset existing client code (web client/extensions/plugins).
    44
    5  1. This feature must be enabled per annotation type. Existing annotation types will have it disabled by default.
     5 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.
    66 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.
    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.