Starting in Specify 7.8.4, you can enable a secret preference that allows synonymizing a node that has children and adding children to a synonymized node.
This has been requested by many members of the consortium, including
@Ben, @Plarson, @Schuchert , and @HeatherC.
You can enable this functionality by adding this line to your
Remote User Prefs file in the
App Resources viewer. If you have any questions or need some help, please feel free to send us a message!
Allow Adding Children to Synonymized Parents & Synonymizing a Node with Children
You will need to replace
Taxon or any other tree you wish to enable this behavior for.
For instance, if you wished to modify the behavior of the Taxon tree, you would add this line to your
Remote User Prefs file:
Very interesting! will this also allow a ‘parent’ node (that has a child) to be synonymized to another node?
I ran into this use-case this week. It doesn’t follow all the taxon rules, but relates to legacy and Type nomenclature that we want to maintain (but not encourage further).
Thanks for this insight, I will be looking into learning more about how to personalize these preferences.
Yes it will! Once enabled, you will be able to synonymize a node with children.
This will be included in the Specify 7.8.4 release which will be available in the next couple of weeks. If you would like to have the latest changes on your current instance of Specify Cloud, we can push them sooner!
That sounds great, at the moment, it isn’t urgent for us, so no problem waiting for the next release. But, this does give me some ideas for different Tree behaviour that I wonder if it can be customized… will create a new thread and link.
Possible to customize taxon query?
Since this is implicitly related, I thought I would add here, instead of starting a new thread.
I am spending some time ‘pruning’ our taxon tree. Often that means I am using the query function to review records connected to a node. When I do this, I want to see ‘all’ of them, not just those with current dets. Is there a way that I can configure my default preferences for this taxon query to be ‘any’ instead of ‘True or Empty’?
It isn’t too bad to edit the query each time, BUT once I …