Project

General

Profile

feature request #4155

Implement handler (IHandler) to trigger recursive setting of the publish bit on a taxon subtree

Added by Andreas Kohlbecker over 4 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Highest
Assignee:
Category:
taxeditor
Target version:
Start date:
03/24/2014
Due date:
% Done:

0%

Severity:
normal

Description

see http://wiki.eclipse.org/Platform_Command_Framework#Executing_a_command_with_parameters

  1. the handler will be registered in the taxeditor-git/eu.etaxonomy.taxeditor.store/plugin.xml

  2. secure the handler by making use of the expression definition hasROLE_PUBLISH

  3. create an according command in taxeditor-git/eu.etaxonomy.taxeditor.store/plugin.xml

  4. 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

Related to Edit - feature request #6315: Implement setSecundumForSubtree in TaxEditor Feedback 02/09/2017
Blocked by Edit - feature request #3740: Allow recursively setting the publish bit for TaxonBase Closed 09/27/2013
Copied to Edit - feature request #7065: When updating a subtree the affected and opened taxa are not updated in name editor this needs to be handled Closed 11/07/2017

Associated revisions

Revision 1a6c4078 (diff)
Added by Katja Luther about 1 year ago

enable setPublishFlagForSubtree in edior

Revision 09cef664 (diff)
Added by Katja Luther about 1 year ago

save updated taxa/synonyms in setPublishedFlag

Revision dfa80bce (diff)
Added by Katja Luther about 1 year ago

setPublishFlag needs to be transactional

Revision 6a3a26fb (diff)
Added by Katja Luther about 1 year ago

revert saveOrUpdate adding

Revision 7d3b42ec (diff)
Added by Katja Luther about 1 year ago

ref #4155: adaptions in setPublishForSubTree config wizard

History

#1 Updated by Andreas Kohlbecker over 4 years ago

  • Keywords set to Euro+Med,Migration

#2 Updated by Andreas Müller over 3 years ago

  • Target version changed from Euro+Med Migration to Euro+Med Portal Release

#3 Updated by Andreas Müller over 2 years ago

  • Target version changed from Euro+Med Portal Release to Euro+Med Migration

#4 Updated by Andreas Müller about 1 year 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

#5 Updated by Andreas Müller about 1 year ago

#6 Updated by Andreas Müller about 1 year ago

  • Target version changed from Release 4.11 to Release 4.10

#7 Updated by Andreas Müller about 1 year ago

#8 Updated by Andreas Müller about 1 year 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

#9 Updated by Andreas Müller about 1 year ago

  • Private changed from Yes to No

#10 Updated by Andreas Müller about 1 year ago

  • Target version changed from Release 4.10 to Release 4.11

#11 Updated by Katja Luther about 1 year ago

  • Status changed from New to Resolved
  • Assignee changed from Katja Luther to Andreas Müller

#12 Updated by Andreas Müller about 1 year 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.

#13 Updated by Katja Luther about 1 year 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)

#14 Updated by Andreas Müller about 1 year 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

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)