You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To view phylogenies, you have a java page. However, in mac os X java in browsers (Firefox, chrome, Safari) has essentially been eliminated. As a result there is no way to edit phylogenies via the Java interface you provide. The only way to change names in phylogenies is to upload a new file. But as you cannot delete existing phylogenies this breaks the whole interface and a submission has to be started again.
If the URL for a submission has already been submitted to a journal this is a major problem. A fix for this needs to be prioritised.
The text was updated successfully, but these errors were encountered:
On May 29, 2018, at 2:48 AM, gwydion1 ***@***.***> wrote:
The only way to change names in phylogenies is to upload a new file.
Taxon labels can be edited, but overall it’s much better to delete all associated matrices and tree blocks and then re-upload the data.
On May 29, 2018, at 2:53 AM, gwydion1 ***@***.***> wrote:
I have a new taxon, Tripidium which has not yet trickled through the taxonomy databases. As a result I need to use the 'no association' radio button for each of these species. However, when I click on the 'no association' button nothing happens... All the species still report that 'This taxon has not been linked to an external taxonomy'
It’s perfectly okay to leave taxon labels unconnected to uBIo IDs. No need to choose “no association” — this is only for cases where the automated taxon machine has caused a false-positive.
bp
To view phylogenies, you have a java page. However, in mac os X java in browsers (Firefox, chrome, Safari) has essentially been eliminated. As a result there is no way to edit phylogenies via the Java interface you provide. The only way to change names in phylogenies is to upload a new file. But as you cannot delete existing phylogenies this breaks the whole interface and a submission has to be started again.
If the URL for a submission has already been submitted to a journal this is a major problem. A fix for this needs to be prioritised.
The text was updated successfully, but these errors were encountered: