search

Bauble / bauble.classic

this is how Bauble and Ghini both started
GNU General Public License v2.0
10 stars 34 forks source link

lexicographic position of Genus sp #210

Closed mfrasca closed 8 years ago

mfrasca commented 8 years ago

the sp behind genus is now not correctly handled: it is not part of the species name as if it was a binomial name, it's just an indicator to signify that the species is not known. as such, »Anguloa sp« should really be »Anguloa sp« (sp not italicized). also, it should precede all other species in the genus.

RoDuth commented 8 years ago

Seems to work for me if I put the sp. in the epithet field rather than the species field. Maybe not ideal but it works for now.

mfrasca commented 8 years ago

nice one. so to solve the (sp not italicized) part, the advice would be in this case to use the infraspecific parts, as unranked epithet. screenshot from 2015-12-09 10 38 45

we still need see how to have the correct lexicographic order. untitled

mfrasca commented 8 years ago

could place it at the end, by prefixing the unranked epithet with a zero width space (unicode 200b). untitled (the increased spacing between genus epithet and the 'sp' is given by the difference in italicization, not by the zero width space.) (I would prefer Masdevallia sp to precede all completely specified species, not to follow them, but I prefer it to follow them than to be put in the middle of the list.) comments welcome, and otherwise I will include this change in 1.0.54.

other example (alerting @felipead87 as owner of the data)... untitled

felipead87 commented 8 years ago

I agree, would be better to have sp on top of the list, it would make it easier to access

2015-12-09 15:21 GMT-05:00 Mario Frasca notifications@github.com:

could place it at the end, by prefixing the unranked epithet with a zero width space http://www.fileformat.info/info/unicode/char/200B/index.htm (unicode 200b). [image: untitled] https://cloud.githubusercontent.com/assets/122869/11696890/afd51bc8-9e84-11e5-8550-80e41fa9e48b.png (the increased spacing between genus epithet and the 'sp' is given by the difference in italicization, not by the zero width space.) (I would prefer Masdevallia sp to precede all completely specified species, not to follow them, but I prefer it to follow them than to be put in the middle of the list.) comments welcome, and otherwise I will include this change in 1.0.54.

other example (alerting @felipead87 https://github.com/felipead87 as owner of the data)... [image: untitled] https://cloud.githubusercontent.com/assets/122869/11697298/f181856e-9e86-11e5-9687-68c83e307cee.png

— Reply to this email directly or view it on GitHub https://github.com/Bauble/bauble.classic/issues/210#issuecomment-163372534 .

mfrasca commented 8 years ago

I don't see how to do this in an easy way. at the moment it looks like they will follow the completely specified taxa.

mfrasca commented 8 years ago

I don't like it myself! :unamused:

mfrasca commented 8 years ago

untitled

RoDuth commented 8 years ago

@mfrasca should cases such as this be in the documentation somewhere? i.e. explaining the use of the epithet field in this scenario.

I feel that the documentation could be a little more thorough when it comes to getting started entering data. Seems to stump new users, especially if they have no or little botanic records experience. I have a volunteer whom I am training to do some data entry for me, she has been writing herself notes and making a bit of an internal "guide to Bauble". Maybe I could ask her to use some of this guide to expand the readthedocs documentation? I'm just not sure how to go about editing the readthedocs documents myself! What do you think? If you do think it could be useful, before I look into it myself, any pointers?