It this task-data-plugin is installed, it sets segments with certain segment-alternative-attributes to the autoState "blocked" and on editable=0

For which segment attributes this is done is configureable
– by installation instance of plugin
– by a method calling the plugin

It is also possible to configure the plugin to set segments to autoState "blocked" and on editable=0, which do NOT have a certain custom segment-alternative-attribute.

As planned for all task-data-plugins, this plugin in the future should be callable

• after each import via system-config (sufficient in 2014)
• by a dedicated call of another process
• via REST-API.

Goals of this architecture

The goal of this plugin for the beo-1-issue is to be able to lock the segments, which should not be editable (see beo-1) in a standardized way.

General goal of this architecture:

• It should be possible to extend the plugin in a way to add task properties in the GUI as part of the plugin. This is done in order to be able to use this feature to configure a task through the GUI in the future

Be careful

• currently locking segments is only possible on segment-level, not on alternative level. but it should be done on alternative level in the future.
• Same is true for the attributes. Currently we only have attributes on segment-level. In the future most (or all) of them should be on alternative level. This can not be accomplished by this task though, but should be kept in mind.