feature request #4155
closedImplement handler (IHandler) to trigger recursive setting of the publish bit on a taxon subtree
0%
Description
see http://wiki.eclipse.org/Platform_Command_Framework#Executing_a_command_with_parameters
the handler will be registered in the
taxeditor-git/eu.etaxonomy.taxeditor.store/plugin.xml
secure the handler by making use of the expression definition
hasROLE_PUBLISH
create an according command in
taxeditor-git/eu.etaxonomy.taxeditor.store/plugin.xml
create a menu contribution for the TaxonNavigator context menu and secure this one by making use of the expression definition
canUPDATE
whereas the currently selected TaxonNodes should be taken into account for this check.
requires #3740 (Allow recursively setting the publish bit for TaxonBase) to be solved
Related issues
Updated by Andreas Kohlbecker over 9 years ago
- Keywords set to Euro+Med,Migration
Updated by Andreas Müller over 8 years ago
- Target version changed from Euro+Med Migration to Euro+Med Portal Release
Updated by Andreas Müller over 7 years ago
- Target version changed from Euro+Med Portal Release to Euro+Med Migration
Updated by Andreas Müller over 6 years ago
- Tracker changed from task to feature request
- Description updated (diff)
- Assignee changed from Matúš Kempa to Katja Luther
- Priority changed from New to Highest
- Target version changed from Euro+Med Migration to Release 4.11
Updated by Andreas Müller over 6 years ago
- Blocked by feature request #3740: Allow recursively setting the publish bit for TaxonBase added
Updated by Andreas Müller over 6 years ago
- Target version changed from Release 4.11 to Release 4.10
Updated by Andreas Müller over 6 years ago
- Related to feature request #6315: Implement setSecundumForSubtree in TaxEditor added
Updated by Andreas Müller over 6 years ago
- Subject changed from implement handler (IHandler) to trigger recursive setting of the publish bit on a whole calssification branch to Implement handler (IHandler) to trigger recursive setting of the publish bit on a taxon subtree
The blocking ticket is now fixed so we can now start implementing this
Updated by Andreas Müller over 6 years ago
- Target version changed from Release 4.10 to Release 4.11
Updated by Katja Luther over 6 years ago
- Status changed from New to Resolved
- Assignee changed from Katja Luther to Andreas Müller
Updated by Andreas Müller over 6 years ago
- Status changed from Resolved to Feedback
- Assignee changed from Andreas Müller to Katja Luther
Title is still missing in the Configurator dialog.The title for "value" attribute is unclear, in German "Setze das Publish Flag" is not correct, should be something like "value to set", or maybe even better a dropdown list with values "publish", "don't publish" to improve the understanding of the semantics of the field. Or at least we should try to separate this "value" checkbox from those for defining which objects to change (accepted taxa, reused taxa, synonyms) somehow.Is it possible to try to update existing values for open taxa (in name editor or elsewhere). This might be a general issue, however, somehow it is irritating, to run the operation and see the value not changing in the currently opened taxon.
Or alternatively we could require to close all affected taxa, but this requires that we know which taxa are potentially affected, maybe we need a separate service method for this.
Updated by Katja Luther over 6 years ago
- Status changed from Feedback to Closed
close this ticket and create a new one for implementing a service method that returns the affected taxon nodes which should be closed in name editor (#7065)
Updated by Andreas Müller over 6 years ago
- Copied to feature request #7065: When updating a subtree the affected and opened taxa are not updated in name editor this needs to be handled added