Module talk:Taxontree
- @RexxS: Hello, it would be great if we could integrate that property and the corresponding value to the taxon tree. This property is used as qualifier of parent taxon (P171) and accept as value something that is a taxonomic rank (Q427626).
Two examples where it is used:
- Ophiomastus (Q3545450) → Category:Ophiomastus
- What should be seen in the taxon tree (highlighted in bold):
- Kingdom Animalia
- Subkingdom Bilateria
- Infrakingdom Deuterostomia
- Phylum Echinodermata
- Subphylum Eleutherozoa
- Superclass Asterozoa
- Class Ophiuroidea
- Order Ophiurida
- Suborder incertae sedis
- Genus Ophiomastus
- What should be seen in the taxon tree (highlighted in bold):
- Cyclocorus (Q3008467) → Category:Cyclocorus
- What should be seen (highlighted in bold):
- Kingdom Animalia
- Subkingdom Bilateria
- Infrakingdom Deuterostomia
- Phylum Chordata
- Subphylum Vertebrata
- Infraphylum Gnathostomata
- Superclass Tetrapoda
- Class Reptilia
- Infraclass Lepidosauromorpha
- Superorder Lepidosauria
- Order Squamata
- Suborder Serpentes
- Infraorder Alethinophidia
- Infraorder Caenophidia
- Family Colubridae
- Subfamily incertae sedis
- Genus Cyclocorus
- What should be seen (highlighted in bold):
Example of manual rendering in a Wikipedia infobox : en:Paradinandra
Regards, Christian Ferrer (talk) 11:46, 29 December 2018 (UTC)
- @Christian Ferrer: I've made a test version in the Module:Taxontree/sandbox. This doesn't handle multiple values, so please test it and see if there are any issues or exceptions that you can find.
- Ophiomastus (Q3545450):
Kingdom Animalia Subkingdom Eumetazoa Subkingdom Bilateria Superphylum Deuterostomia Phylum Echinodermata Subphylum Asterozoa Class Ophiuroidea Subclass Myophiuroida Infraclass Metophiurida Superorder Euryophiurida Order Ophiurida Suborder incertae sedis Genus Ophiomastus
Megaclass Osteichthyes Superclass Sarcopterygii Infraclass Elpistostegalia Superclass Tetrapoda Class Reptilia Infraclass Lepidosauromorpha Superorder Lepidosauria Order Squamata Suborder Serpentes Infraorder Alethinophidia Parvorder Caenophidia Superfamily Colubroidea Family Colubridae Subfamily incertae sedis Genus Cyclocorus
- Cheers --RexxS (talk) 17:16, 30 December 2018 (UTC)
- Thanks you. I tested several cases at preview, all is working well. The only case that could have been an exception I found is the one quoted in d:Property talk:P678, that is en:Phialophora asteris, however the parent taxons chain in Wikidata is not the same (that happens sometimes, as several classification are coexisting...). Therefore for the moment I think there is no problem, and that you can bring this addition to the Taxontree. Christian Ferrer (talk) 18:26, 30 December 2018 (UTC)
- @Christian Ferrer: I've updated the main module from the sandbox. Ping me if you spot any problems. --RexxS (talk) 23:18, 30 December 2018 (UTC)
- Very great, thanks you. Happy Holidays! Christian Ferrer (talk) 06:07, 31 December 2018 (UTC)
@RexxS: Hello, this new property have just been created, I give you a few explanation about the context. The author citation is something almost mandatory when talking about a taxon. One example, see the infobox in en:Lion, just below the section "Binomial name" you can read Panthera leo (Linnaeus, 1758). You will see exactly the same kind of thing in all infoboxes for all our project languages, and for all taxa. As well as in other medias [1], [2], ect... In summary, to be complete, the taxontree has to retrieve the author citation of the item we talk about.
Of course we have taxon author (P405) that is already retrieved in {{Wikidata Infobox}}, but this is not the same thing; P405 is useful regarding the structured data side but don't allow to respect the various en:Nomenclature codes. And the nomenclatures are so complex and various that there is currently no code to retrieve automatically that, may be in the future but not immediately. Thus the choice of a string value property.
I think we should integrate that property to the taxontree instead of the infobox, because the taxon name should normaly not be separate from the author citation.
What we currently have is :
Kingdom Animalia Subkingdom Eumetazoa Subkingdom Bilateria Superphylum Deuterostomia Phylum Echinodermata Subphylum Echinozoa Class Echinoidea Subclass Euechinoidea Order Echinothurioida Family Echinothuriidae Subfamily Sperosomatinae Genus Tromikosoma Species Tromikosoma uranus
- see also Category:Tromikosoma uranus and Tromikosoma uranus (Q2178790)
What would be perfect is :
- Kingdom Animalia
- Subkingdom Bilateria
- Infrakingdom Deuterostomia
- Phylum Echinodermata
- Class Echinoidea
- Subclass Euechinoidea
- Order Echinothurioida
- Family Echinothuriidae
- Subfamily Sperosomatinae
- Genus Tromikosoma
- Species Tromikosoma uranus
- (Thomson, 1877)
or a little more elaborate, and inspirated from the wikipedia infoboxes (not especially better) :
Kingdom | Animalia |
Subkingdom | Bilateria |
Infrakingdom | Deuterostomia |
Phylum | Echinodermata |
Class | Echinoidea |
Subclass | Euechinoidea |
Order | Echinothurioida |
Family | Echinothuriidae |
Subfamily | Sperosomatinae |
Genus | Tromikosoma |
Species | |
Tromikosoma uranus (Thomson, 1877) |
The more important being that the author citation be near the taxon name,
- just after, such as Tromikosoma uranus (Thomson, 1877)
- or directly below, (see the examples above) such as
- Tromikosoma uranus
(Thomson, 1877)
- Tromikosoma uranus
- Hope we can manage to have something satisfactory. Take all the time you need, we have lived without so far. Regards, Christian Ferrer (talk) 10:02, 16 February 2019 (UTC)
- @Christian Ferrer: I've added it as a separate line to {{Wikidata Infobox/sandbox}} for now, see how that looks? Up to RexxS if he wants to integrate it directly into this module. Thanks. Mike Peel (talk) 15:54, 16 February 2019 (UTC)
- @Mike Peel: Thanks you, but not in this way, example look at this article nl:Tromikosoma uranus, you see that "(Thomson, 1877)" is directly below the species name, and in the same field. That is important that this info be in the same field. If we integrate it to the infobox it should be one single field, as wide as the infobox, a bit as the taxon header "taxonomy"; and that field could be placed above or below the taxon tree, as well. Exemple:
Tromikosoma uranus (Thomson, 1877) | |
Taxonomy | |
Kingdom | Animalia |
Subkingdom | Bilateria |
Finally, that could be a good idea to put that in the infobox, and just after the taxon tree, and why not with the same color, that will be a kind of visual answer of the header "taxonomy", and that will close the "tree". Can you make a try? Christian Ferrer (talk) 16:26, 16 February 2019 (UTC)
- @Mike Peel: I just realize that when we hide "taxonomy" we hide all the fields relative to taxa, however en:Taxonomy (general) is about the classification, no more. we are doing at minimum a fault of good taste. I think that we should close the taxon header just after the Taxontree, or that we should rename the header, but I will prefer the first option. Christian Ferrer (talk) 16:42, 16 February 2019 (UTC)
- I made a test for the collaspable section in Category:Tromikosoma uranus, it is better IMO. Christian Ferrer (talk) 16:50, 16 February 2019 (UTC)
Main | Sandbox | Sandbox when citation is missing |
---|---|---|
{{Wikidata Infobox |qid=Q2178790}}
|
{{Wikidata Infobox/sandbox |qid=Q2178790}}
|
{{Wikidata Infobox/sandbox |qid=Q2591103}}
|
@Christian Ferrer and Mike Peel: From my point of view, calling code to retrieve a taxon tree and then calling code to retrieve taxon author citation (P6507) makes sense, just in case somebody wants to re-use or adapt the taxon tree code for another purpose without wanting the bit that fetches the taxon author citation. So my initial inclination is not to integrate the P6507 into the taxon tree call. I've made a demo of how I think you want the display in the Template:Wikidata Infobox/core/sandbox. Let me know if that's the sort of display you want. --RexxS (talk) 18:28, 16 February 2019 (UTC)
- Ok for the principle not to integrate that in the taxon tree, and it is better now, thanks you. I would have want to make an attempt to have a 100% wide field such as the "taxonomy" header, and after the taxon tree, that will contains :
Tromikosoma uranus (Thomson, 1877) |
...however there is the "italics" issue for all that is below the genus taxon rank, and that will need a lot of work. For me that is ok. If every one agree, I think we can move all that, including order changes (it looks more srutured like this), to the infobox. Christian Ferrer (talk) 19:22, 16 February 2019 (UTC)
- well.. apparently not an issue in Category:Tromikosoma uranus Christian Ferrer (talk) 19:31, 16 February 2019 (UTC)
- It doesn't look right to have a white area in the left-hand column: that should either be shaded purple, or better yet we have the 'taxon author citation' text back so that it's clearer what the thing in brackets is. Would that be OK? Thanks. Mike Peel (talk) 19:28, 16 February 2019 (UTC)
- well ok, give it a try. Christian Ferrer (talk) 19:31, 16 February 2019 (UTC)
- (Edit conflict) No, it looks awful. I tried it and rejected it. If you want to see how it looks, all you have to do is put back the
class="wikidatainfobox-lcell"
to the<th
for the 'taxon author citation' row. --RexxS (talk) 19:34, 16 February 2019 (UTC)- I've just made the edit, see how that looks. Alternatively, we either centre- or right-align the text in a full-width cell. Thanks. Mike Peel (talk) 19:43, 16 February 2019 (UTC)
- Don't like very much this one, can you try to centre-align the text in a full-width cell, please? Christian Ferrer (talk) 19:45, 16 February 2019 (UTC)
- How's that? Thanks. Mike Peel (talk) 19:51, 16 February 2019 (UTC)
- Yes that seems better... I wonder if RexxS can write something in Lua with all local italicvalues constraints such as for the taxontree module in order to retrieve that :
- How's that? Thanks. Mike Peel (talk) 19:51, 16 February 2019 (UTC)
Tromikosoma uranus (Thomson, 1877) |
... and then to call the module in the infobox, as it is done for the taxontree? Christian Ferrer (talk) 20:00, 16 February 2019 (UTC)
- That will give us the possibility to move it in the infobox, if we want so, and it will look more structured, and we could add a purple color.... Christian Ferrer (talk) 20:05, 16 February 2019 (UTC) but the call of such a module should be conditioned on the fact that there is indeed a "taxon author citation" in the item.... Christian Ferrer (talk) 20:11, 16 February 2019 (UTC)
- @Christian Ferrer: Sod it. I'll incorporate taxon author citation (P6507) into Module:Taxontree, otherwise it gets too complicated. You can turn on display of 'taxon author citation' by setting
|authorcite=true
(aliases|ac=
and 'yes'); default is false for backwards compatibility. This is what it gives: {| {{#invoke:Taxontree |show |qid=Q2178790 |first=n |ac=yes |lang=}} |}
- @Mike Peel: You'll have to set the styling for class
.taxontree-fullcell
in Template:Wikidata Infobox/styles.css. As usual, I can't. My own fault. --RexxS (talk) 23:40, 16 February 2019 (UTC)- @RexxS: that's great, excellent, thanks you. I think that the style should be centered with a white background, and that we now need a new field. May I ask to have, just above this full cell, an additional new full cell with the corresponding taxon rank, that is now missing, and with a purple background? Christian Ferrer (talk) 07:26, 17 February 2019 (UTC)
- @Christian Ferrer: Okay, I've added a header row for the first taxon. Mike Peel will have to set the style for class
.taxontree-hdrcell
in Template:Wikidata Infobox/styles.css. Cheers --RexxS (talk) 18:26, 17 February 2019 (UTC)- Thanks you RexxS, for your efforts, I did that, I don't know if it is ok, though. Christian Ferrer (talk) 18:50, 17 February 2019 (UTC)
- @Christian Ferrer: Looks fine to me. It won't show in the infobox until it's updated from the sandbox, of course. --RexxS (talk) 20:41, 17 February 2019 (UTC)
- Excelent, it's a real improvement. Christian Ferrer (talk) 21:45, 17 February 2019 (UTC)
- @Christian Ferrer: Looks fine to me. It won't show in the infobox until it's updated from the sandbox, of course. --RexxS (talk) 20:41, 17 February 2019 (UTC)
- Thanks you RexxS, for your efforts, I did that, I don't know if it is ok, though. Christian Ferrer (talk) 18:50, 17 February 2019 (UTC)
- @Christian Ferrer: Okay, I've added a header row for the first taxon. Mike Peel will have to set the style for class
- @RexxS: that's great, excellent, thanks you. I think that the style should be centered with a white background, and that we now need a new field. May I ask to have, just above this full cell, an additional new full cell with the corresponding taxon rank, that is now missing, and with a purple background? Christian Ferrer (talk) 07:26, 17 February 2019 (UTC)
- @Christian Ferrer: Sod it. I'll incorporate taxon author citation (P6507) into Module:Taxontree, otherwise it gets too complicated. You can turn on display of 'taxon author citation' by setting
- @RexxS: I managed to retrieve the BHL link, as I asked it last time, see the example above. However at this occasion I discovered a bug for the citation, when the citation is missing then the taxon name as well as the taxon rank, for the taxon that we look at, are missing. See the same example. Christian Ferrer (talk) 22:43, 17 February 2019 (UTC)
- @Christian Ferrer: Yes, it's a logic bug - we need to specify
|first=yes
in Template:Wikidata Infobox/core/sandbox as a fallback, so that it shows the first taxon if taxon author citation (P6507) is missing. I've implemented that in the module and its sandbox, and in the template sandbox. --RexxS (talk) 23:16, 17 February 2019 (UTC)
- @Christian Ferrer: Yes, it's a logic bug - we need to specify
- ok, great, thanks you Christian Ferrer (talk) 05:49, 18 February 2019 (UTC)
- I moved the changes to the infobox, that look fine, the only bug is from me. See Template talk:Wikidata Infobox#Links to BHL pages Christian Ferrer (talk) 11:53, 18 February 2019 (UTC)
- ok, great, thanks you Christian Ferrer (talk) 05:49, 18 February 2019 (UTC)
- ??? can someone explain why there is a link leading to nl:Tromikosoma uranus when I click on expend of the field "taxon common name"? Christian Ferrer (talk) 19:26, 16 February 2019 (UTC)
- @Christian Ferrer: That's a bug with Template:VNNoDisplay, it's reproducable by
{{User:Mike Peel/Test}}
-> User:Mike Peel/Test . Perhaps @Liné1: can help? Thanks. Mike Peel (talk) 20:08, 16 February 2019 (UTC)
- @Christian Ferrer: That's a bug with Template:VNNoDisplay, it's reproducable by
Two different labels for one taxon rank for one or more langages
edit- @RexxS: , Hope you're well. I come here to in case you could have an idea how to handle a little issue, and also because Wikimedia Commons is multilingual.
- See also: wikidata:Wikidata_talk:WikiProject_Taxonomy#order_(Q36602)_and_order_(Q10861678)
- Summary: in taxonboxes the taxonomic rank that we read is in fact the label of that taxon rank, that allow to access at different langages, and if I missed nothing this is done at ligne 127 of this module.
- There are potentialy several cases, but I will restrict to a specific example for a single language, for now. In Russian:
- there is one way to say order (Q36602) when order (Q36602) is a child of animal (Q729) → " отряд ", which is significant because there are a large number of animals.
- and for everything else order (Q36602) is said " порядок ", which is also significant...
- for the moment, the label in Wikidata is " отряд / порядок " (this is a the way how GBIF handle that: https://www.gbif.org/ru/species/150769016)
- To have the right labels at the right places an user created in Wikidata order (Q10861678), in the purpose to add this value as an additional taxon rank in the concerned taxa items, however there are ongoing disagreements, see link above + [3] with that solution, because taxon ranks are based on official taxonomic nomenclature, and they are not doing this distinction. Also this is IMO not a suitable solution because imagine a langage with 3 different values (e.g. 1 for Animalia, 1 for Plantae and one for Bacteria), does that mean tha we need to creat a third item "order"? no IMO, we can not create an item for each possible translation of one word. This is a bit at the opposite of the purpose of Wikidata and this will potentialy create a mess with potential future queries.
- Where and how do you think it's best to handle this, in a module like this one or in Wikidata?
- Hope you will understand my english. Thanks you, Christian Ferrer (talk) 18:01, 17 March 2021 (UTC)