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
Ah, makes sense. Leads to a quite inconsistent API unfortunately. I was strongly hoping to restrict labels to usages (which have namePhrase etc) and was glad to remove them from pure names.
What if the TaxonInfo object would already contain relations and resolve them to actual usages, not names?
As a quick fix you can just render the scientificName & authorship of the name.
The label really becomes tricky only for usages with accordingTo and namePhrases
After labelHtml was removed from names, the related names on taxon pages are broken.
The UI receives name relations through the https://api.catalogue.life/dataset/2207/name/359/relations endpoint, and subsequently fetches each name:
https://api.catalogue.life/dataset/2207/name/360
https://api.catalogue.life/dataset/2207/name/362
It would be ideal if the https://api.catalogue.life/dataset/2207/name/359/relations endpoint include the labelHtml , that would even save the subsequent calls to the /name endpoint
The text was updated successfully, but these errors were encountered: