Add field that displays higher level taxonomy separate from taxon full name

[tlammer]

Geneva requested to be able to display the higher level taxon separate from the taxon full name

From Geneva:
Another important information is the higher classification of the identification. Canthis be shown in a read-only calculated field? (minimum Phylum, Class, Order,Family)?

[maxpatiiuk]

Can't you add a field like parent.name to the form definition?
Also, parent.parent.name may work too

[grantfitzsimmons]

db: kufish

[benritchie]

@grantfitzsimmons - can you clarify what is new here? is it just that adding parent.parent.name was previously broken and now works, or is there something else?
specifically (asking as this would unblock some issues we are having) is there a way to specify a particular rank - e.g. to get the family name? (in a way that works whether you are at genus, or species, or variety level?

[maxpatiiuk]

Nothing has changed here in 7.7.0.
We just realized that this use case is already covered by an existing feature.
You can show information about a parent of a parent by setting field name to something like parent.parent.name.

At present, this does not allow to enforce a specific tree rank, but we have a separate ticket for that - #805

[benritchie]

Cool Suggest you update the release note in that case - this is listed as fixed in 7.7 Thanks

…

________________________________ From: Max Patiiuk ***@***.***> Sent: Monday, July 18, 2022 2:48:35 PM To: specify/specify7 ***@***.***> Cc: Ben Ritchie ***@***.***>; Comment ***@***.***> Subject: Re: [specify/specify7] Add field that displays higher level taxonomy separate from taxon full name (#659) Nothing has changed here in 7.7.0. We just realized that this use case is already covered by an existing feature. You can show information about a parent of a parent by setting field name to something like parent.parent.name. At present, this does not allow to enforce a specific tree rank, but we have a separate ticket for that - #805<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fspecify%2Fspecify7%2Fissues%2F805&data=05%7C01%7Cbritchie%40rbge.org.uk%7C66a751cc251b4444a0f008da68c439ff%7Cbb63bb00175e46b7b7b3bc74158e4fd4%7C0%7C0%7C637937489240366365%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5Xe07PtSD8I6OLTaz5fJKrpY7kcmElRUqG3w%2BH5xPEA%3D&reserved=0> — Reply to this email directly, view it on GitHub<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fspecify%2Fspecify7%2Fissues%2F659%23issuecomment-1187478974&data=05%7C01%7Cbritchie%40rbge.org.uk%7C66a751cc251b4444a0f008da68c439ff%7Cbb63bb00175e46b7b7b3bc74158e4fd4%7C0%7C0%7C637937489240366365%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BEs9flQmcJlpkfS16z2Dzgr6z3Zs6tZuI8owCYnjbnI%3D&reserved=0>, or unsubscribe<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB5CQLHVMGEDOALTKLB3AGDVUVODHANCNFSM4MTCAPVQ&data=05%7C01%7Cbritchie%40rbge.org.uk%7C66a751cc251b4444a0f008da68c439ff%7Cbb63bb00175e46b7b7b3bc74158e4fd4%7C0%7C0%7C637937489240366365%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=O6jwCcR5h28IBgbGDUvCphDxyYrHZH7mFKF7vK%2FINZk%3D&reserved=0>. You are receiving this because you commented.Message ID: ***@***.***> The Royal Botanic Garden Edinburgh<https://www.rbge.org.uk> is a charity registered in Scotland (No SC007983) | Support Us<https://www.rbge.org.uk/support-us> This notice applies to this email and to any other email subsequently sent by anyone at RBGE and appearing in the same chain of email correspondence. References below to "this email" should be read accordingly. This e-mail and its attachments (if any) are confidential, may be protected by copyright and may be privileged. If you receive this e-mail in error, notify us immediately by reply e-mail, delete it and do not use, disclose or copy it. Unless we expressly say otherwise in this e-mail, this e-mail does not create, form part of, or vary, any contractual or unilateral obligation. No liability is accepted for viruses and it is your responsibility to scan attachments (if any). Where this e-mail is unrelated to the business of RBGE, the opinions expressed within this e-mail are the opinions of the sender and do not necessarily constitute those of RBGE. RBGE emails are filtered and monitored.