Wikipedia talk:WikiProject Plants/Archive64

This is an archive of past discussions on Wikipedia:WikiProject Plants. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.

Archive 60

←

Archive 62

→

Leaflet For Wikiproject Plants At Wikimania 2014

Hi all,

My name is Adi Khajuria and I am helping out with Wikimania 2014 in London.

One of our initiatives is to create leaflets to increase the discoverability of various wikimedia projects, and showcase the breadth of activity within wikimedia. Any kind of project can have a physical paper leaflet designed - for free - as a tool to help recruit new contributors. These leaflets will be printed at Wikimania 2014, and the designs can be re-used in the future at other events and locations.

This is particularly aimed at highlighting less discoverable but successful projects, e.g:

• Active Wikiprojects: Wikiproject Medicine, WikiProject Video Games, Wikiproject Film

• Tech projects/Tools, which may be looking for either users or developers.

• Less known major projects: Wikinews, Wikidata, Wikivoyage, etc.

• Wiki Loves Parliaments, Wiki Loves Monuments, Wiki Loves ____

• Wikimedia thematic organisations, Wikiwomen’s Collaborative, The Signpost

For more information or to sign up for one for your project, go to:
Project leaflets
Adikhajuria (talk) 11:01, 18 June 2014 (UTC)

Vasqueziella

I got a good chuckle out of this one and could not resist sharing it. I suggest looking at the history of the page on Vasqueziella. Several people edited this without noticing that the two species listed were in the wrong genus.Joseph Laferriere (talk) 14:36, 19 June 2014 (UTC)

Bamboo

Does anyone have a good understanding of the taxonomy of Bamboos? Bamboo is generally about tribe Bambuseae, but in the section called "Genus and geography" (yes, the page needs a lot of editing) is the sourced statement "Bamboo grows in two main forms: the woody bamboos (Arundinarieae and Bambuseae) and the understory herbaceous bamboos (Olyreae)." Does anyone know what rank or clade or non-monophyletic group is the term "bamboo" generally used to mean? Sminthopsis84 (talk) 14:49, 21 June 2014 (UTC)

Hmmm...I know about Runners and Clumpers...but not much more...might be time to do some reading.....Cas Liber (talk · contribs) 15:27, 21 June 2014 (UTC)

Looks to me like parts of the article treat the subtribes at tribe level, and there is a mix-up between common English terms (bamboo) and taxonomic ranks. Circéus (talk) 00:49, 22 June 2014 (UTC)

type species

I assume that it is considered undesirable for Wikipedia to be containing misinformation, and that part of the editor's job is to catch errors. Hence the entire "verifiability" phenomenon as I understand it. There are certain errors I keep seeing over and over, so I point this out so that people might be alerted to it. My policy, incidentally, has become that I shall add to an existing website, but I shall not delete anything unless it is egregiously erroneous. I found one plant page with an entire paragraph-long description in Latin. I had to question the wisdom of having this in Wikipedia, but I do not feel comfortable deleting someone else's work. Anyway, my point today has to do with type species. This is another esoteric topic of interest only to professional taxonomists, hence should be relegated to the taxobox, if even there, but some people want to give it more emphasis than it deserves. I feel that if it is to be included, we should at least make an effort to get it right. Here's the problem. Suppose I discover a new genus and name it "Gondoria." I designate "Gondoria gandalfii" as type species. Years later, someone points out that the same plant was previously described in the Nazgul Journal of Botany under the name "Modoria sauronii." Priority rules dictate that my species now becomes "Gondoria sauronii." Does this mean that "Gondoria sauronii" is now type species of "Gondoria?" No. "Gondoria gandalfii" remains type. This is so that if at some even later date, DNA analysis reveals that the two deserve to be considered separate genera, the name Gondoria must forever include "Gondoria gandalfii." On a practical level, this does not make a whole lot of difference, but as I said, if we are going to do this, we might as well get it right. Tropicos, incidentally, does frequently have info on type species for various genera.Joseph Laferriere (talk) 12:14, 15 June 2014 (UTC)

Although the terms "type species" and "type genus" are widely used, they aren't in Article 10 of the ICN which covers the typification of genus and family names. A taxon cannot be a type. The type of the name of a genus is the type of the name of a species; the type of the name of a family is the type of the name of a genus which is in turn the type of the name of a species. In Joseph's example, the type of the name Gondoria is the type of the name Gondoria gandalfii, regardless of what that name may later be synonymized with. (An interesting exercise is to explain precisely the typification of the names Cactaceae and Mammillaria.) I wish I had understood that "type species" and "type genus" are actually shorthands for more subtle notions when I first tried to understand botanical taxonomy! Peter coxhead (talk) 02:04, 16 June 2014 (UTC)

A whole paragraph of Latin? Wow. I would delete that per MOS:FOREIGN: "Foreign words should be used sparingly". If you want to preserve someone's hard work, and you are proficient in Latin, you could transfer it to the Latin Wikipedia. Tdslk (talk) 05:02, 16 June 2014 (UTC)

>Peter: Exactly my point, yet I have seen many people get this wrong, including professional botanists. Another complicating factor is that many older names from the 18th and early 19th centuries do not have type designations with their original descriptions. This is for much the same reason as herbarium specimens from that era not having GPS coordinates on the labels. So typification has to be done retroactively, which is why taxonomists buy so much acetaminophen. Joseph Laferriere (talk) 11:37, 16 June 2014 (UTC)

Tdslk - I forget just where that paragraph was, off-hand. I see a lot of pages with esoteric stuff like that, but I generally ignore it. Sometimes I can rephrase and reformat things a bit, but I prefer adding my own material. Oh, and Classical Latin and Botanical Latin are generally considered two distinct languages, as Pliny the Elder would recognize only a tiny fraction of the words in a modern botanical description.Joseph Laferriere (talk) 11:37, 16 June 2014 (UTC)

A paragraph of Latin? That sends up a red flag for me as being a potential copyright violation. I've repeatedly come across several sentences of technical description in English, and every time, it turns out to have been copied directly from another source. It's possible that the paragraph of Latin is copied from a protologue that is old enough to be out of copyright. But even if it's not copyrighted, lengthy technical descriptions in English or Latin aren't appropriate for Wikipedia's general audience. Plantdrew (talk) 14:51, 16 June 2014 (UTC)

I wish I had made a note of where I saw that so that I could go back to it. As I recall, it said something like "And here is the author's original Latin description ..." So, yes, it did appear to have been cut/pasted from somewhere else. But I do think it was some 19th-Century source, so long out of copyright. I do agree that it was a waste of pixels putting it on Wikipedia.Joseph Laferriere (talk) 15:03, 16 June 2014 (UTC)

@Joseph Laferriere: so should we be using the "type species" terminology, given that it's clearly misleading? Peter coxhead (talk) 17:03, 16 June 2014 (UTC)

Aside: I don't expect this to be a common opinion, but I'd like to see type species and type specimen information not included for taxa in wikipedia, unless there is some notable point to be made (such as whether Linnaeus is the type of Homo sapiens). We have to draw the line somewhere about what we duplicate here, and there are other databases working towards tabulating all that information (even wikispecies, which, unfortunately, uses a one-classification-is-correct approach that to my mind makes wikispecies seriously flawed). Type information, I think, makes wikipedia less accessible, and accessibility has paramount importance. Sminthopsis84 (talk) 10:43, 17 June 2014 (UTC)

You make a compelling argument, but I'm a little conflicted. More and more type specimens are becoming available in super-high-def online now, and these have been extremely helpful to me in sorting out species. Not just esoteric taxonomy, but figuring out what kind of plants we may actually have out there in the jungle when I can't go myself, and clearing up confusion on the true nature of species we already know about. Finding those specimens online is often difficult, and I had been hoping that one day as Wikipedia grew it might contain either those images or links to them as part of the type info in every plant article. The types answer the fundamental question "what is this species, really?". That would seem to be a valid component of this encyclopedia at its best. A policy of generally excluding a type of information because it may be hard to understand sounds concerning. I really do care about accessibility and readability though. I don't know... --Tom Hulse (talk) 16:11, 18 June 2014 (UTC)

Hi Tom, it's nice to see that you didn't immediately disagree with me. Yes, easy access to good images of types is enormously valuable, essential. It isn't generally available, though, so linking to it is often not possible. Many herbaria don't even have a large proportion of their specimens catalogued, though they may have the types that they know they have nicely imaged. In the last couple of years, the aggregator databases have made such dramatic progress, that I hope that with another couple of years we may be able to simply point to one database that will have all the images (perhaps GBIF), and that that database will be well inter-linked with others, so we might be pointing to the equivalent of IPNI or ThePlantList, and it would be just another click further to see the type specimens (and other well-curated images). Tropicos already gives access to specimen data, but not, I think, in a way that an average wikipedia reader could find their way through with ease. So, as well as keeping wikipedia more easily readable to the non-specialist, I think that a general strategy statement for WP:PLANTS of "let's not spend effort on adding type information", would benefit other components, so that in a couple of years we'd be ahead overall. I don't think that there are enough of us to be able to make the sort of progress with plant coverage that is needed, and streamlining efforts could pay off. Sminthopsis84 (talk) 19:57, 18 June 2014 (UTC)

I agree with Sminthopsis84 that I would prefer omitting info on type species from Wikipedia genus pages entirely. That information is useful only to taxonomists, and even to them it is helpful only when they are contemplating splitting a genus (or moving species out of a genus, as you are not allowed to move the type species out of the genus). But when I look at existing pages, they very frequently already have this information, sometimes giving it much more emphasis than it deserves. In revising a page, I generally move the info to the taxobox. As I said, I prefer not bothering with it, but if we are going to do it, we might as well get it right.Joseph Laferriere (talk) 01:13, 22 June 2014 (UTC)

infraspecific hierarchy

I am hoping you good people might have an idea on how to handle a particular situation, some ideas that I have not considered. Problem lies with infrapsecific taxa. Several times, I have encountered species in which Plant List and Kew's World Checklist and other such sources accept names at more than one infraspecific level. So one species will contain both varieties and subspecies. Problem is that these are supposed to be hierarchical. Just as each genus is supposed to be part of a family and each species is supposed to be part of a genus, so too each variety is supposed to be part of a subspecies, if indeed both exist with the same species. Yet these secondary sources never have this sort of information, which variety is supposed to belong to which subspecies. Indeed, it usually seems that the various authors of the infraspecific taxa were blissfully unaware of each other, so it would some investigation and access to appropriate type specimens to sort this out. What I have been doing is simply ignoring this, listing the infraspecific taxa as reported in the World Checklist and pretending that there is nothing wrong with this. Anyone have any better suggestions?Joseph Laferriere (talk) 01:00, 22 June 2014 (UTC)

Hi Joseph, I don't have a useful suggestion. In quite a few cases with the plants that I work with, the variety and sub-species level are different worker's names for the same taxon. I've been taught that those who follow Asa Gray use variety, and those from the west coast of North America use sub-species. Consequently, the species as a whole doesn't necessarily have a consistent taxonomy, since new taxa may have been named at either the variety or sub-species level without a whole-species revision being done. The same thing happens with infra-generics: sub-genus, section, sub-section, series, sub-series. With apomictic (asexual) plants there is a school-of-thought that the clearly different lineages that have been called species should continue to be named as species, and that the series level is in some sense equivalent to the species level in purely sexual genera. Perhaps as a consequence of that attitude, there are people who make new series without assigning them to sub-genera or sections, even though the genus has many series and sections already; I think they see it as equivalent to naming a species within a sexual genus. (The basic reason for all this chaos is that there is no good phylogeny of the genus or a way of making one, so different people put the lower-level taxa into higher taxa more-or-less as the mood strikes them. The code of nomenclature, I believe, is as non-binding as it is because people would have had a very hard time coping with any stronger requirements about specifying the hierarchy within species.) Sminthopsis84 (talk) 14:26, 22 June 2014 (UTC)

Sminthopsis84 Indeed. Nobody is forcing the authors of varieties to recognize subspecies created by someone else. But by the same token, nobody is forcing the good people creating the Kew Checklist to designate any of these names as "accepted." I suppose the best we can do is to do what I have been doing, offering lists of what taxa Kew is accepting and leave it to some enterprising taxonomist to straighten things out. This does appear to be the source of the problem in most cases. I believe that I have previously mentioned a mess that I worked on when I was at Harvard. One gentlemen in one paper created subspecies, infraspecies, varieties, subvarieties, infravarieties, forms and subforms for the same two species, none of this hierarchical. I do not think he did any infraforms. He also did other delightfully wacky things such as designate as "lectotypes" specimens collected a century after the name had been created. But this is an anomalous case of someone misunderstanding the most basic principles of the Code.Joseph Laferriere (talk) 23:10, 22 June 2014 (UTC)

Admin needed for move

We have been using WCSP for Agave species. According to WCSP, Agave boscii is a synonym of Agave geminiflora, not the other way round. Could an admin please move Agave boscii to Agave geminiflora? Thanks. Peter coxhead (talk) 19:49, 24 June 2014 (UTC)

I just looked but could not find Agave boscii at all. The Wiki page says "ined." which means the name has not been published at all or has been published since the page was made. I did find a "Yucca boscii" dating from 1813, which if transferred to Agave would predate the geminiflora epithet by 3 years, but the Yucca boscii name carries the notation "nom. rej. prop." meaning that someone is proposing overriding the priority rules and pretending that geminiflora has priority. Either way, yes, Agave geminiflora should stand as the acceptable name.Joseph Laferriere (talk) 22:56, 24 June 2014 (UTC)

moved now. Cas Liber (talk · contribs) 23:50, 24 June 2014 (UTC)

I just went in and added a few things. Synonymy list says someone actually put this in Tillandsia. Interesting story there, I'm sure.Joseph Laferriere (talk) 10:11, 25 June 2014 (UTC)

Aside: interesting that there is no conservation/rejection proposal listed at proposals and disposals. Sminthopsis84 (talk) 11:13, 25 June 2014 (UTC)

Criteria for inclusion of plant species info

I am new to WikiProject Plants and would like to contribute articles, but I would like to get a better idea for how robust datasources need to be. My idea is to provide information for species for which there is not a lot information in the form of published literature by mining herbarium specimen notes and synthesizing that information (giving credit to herbaria and collectors) and by interviewing local experts who have spent their lives in the field. However, I am concerned that such an approach might 1) be perceived as "orginal research" in that it is synthesis of primary source information and 2) not meet the criteria for providing authoratative sources, even though the men and women providing the information are the best in the field. Would biographical information on each collector or interviewee need to be provided to make my case? I am also wondering about whether or not observations in the field can be used, such as a specific butterfly visiting a specific plant species. Thanks for your input. Krobertson1970 16:06, 24 July 2014

Hi, and welcome to WikiProject Plants! As a quick answer to your question, my impression is that all of the worthy material that you propose to add is not acceptable under wikipedia's rules about citations and original research, that everything cited has to be previously published, and that herbarium specimen notes are not considered acceptable citations. Sorry about that. If you would like suggestions about how to use your expertise to contribute in other ways, the project members probably have suggestions. As an additional point, if you find yourself interested in adding biographical material about people, you need to be aware that the community is very stringent in its requirements about biographical material on living people, and that establishing that a person (living or dead) is sufficiently notable to warrant a wikipedia page can be quite challenging. Sminthopsis84 (talk) 11:25, 25 June 2014 (UTC)

Thanks for your answer. I appreciate the high standards maintained by WikiProject Plants, although I do think it is unfortunate in the case of the kind of information I am proposing. A great deal of ecological information about plants, such as habitat requirements, response to disturbance, flowering phenology, etc., is purely observational by its nature, as opposed to the chemical constituents of plants, genetics, and physiology which require systematic scientific investigation. It seems that this format provides an excellent opportunity to gather a wide range of ecological information under many careful and critical eyes which is otherwise not available. Naturalists are taking with them volumes of information when they leave this world because it is humanly impossible to publish it all. Perhaps I can find an alternate and more appropriate outlet for our project, but I do think that it is too bad that there will continue to be a dearth of ecological information on plant species on Wikipedia pages as is currently the case when actually much is known about them. User:Krobertson1970 1:35, 25 June 2014 (UTC)

I strongly sympathize with your concern, particularly since, at least in the UK, the number of field naturalists is declining and they often do possess important information which has not been published. However, Wikipedia rightly has clear policies on sourcing, as Sminthopsis84 notes above, and all information needs to be supported by a reliable source. Have you considered that there are journals and proceedings of natural history societies in which such material could be published? Peter coxhead (talk) 16:16, 25 June 2014 (UTC)

Indeed, there are many publications (formal and informal) that would be interested in publishing such information, whether on-line or on paper. After it is published, then the information can be cited on wikipedia, assuming that it is important enough. I do wish to point out that gleaning information from herbarium specimens is hardly a new idea. It is exactly what botanists have been doing for centuries.Joseph Laferriere (talk) 17:53, 25 June 2014 (UTC)

Botanical authorities are 'notable'

I was alerted earlier today that a botanical authority page was nominated for speedy deletion as not notable. Fortunately the nomination was withdrawn after vigorous protest.

I am proposing that we should, as a matter of priciple, declare that botanical authorities are 'notable by definition, and should not be deleted. --Michael Goodyear (talk) 01:41, 9 May 2014 (UTC)

Where's a detailed rationale for this proposed declaration?--Melburnian (talk) 03:11, 9 May 2014 (UTC)

But are they? I don't think it's implausible that someone could write a single diagnosis and otherwise be completely biographically obscure. Choess (talk) 03:16, 9 May 2014 (UTC)

Yes - it is possible. I can recall at least one obscure person that only published one or two names who'd not likely satisfy notability, and suspect there'd be a few others - not many historically but not none either. Cas Liber (talk · contribs) 03:29, 9 May 2014 (UTC)

I assume "botanical authorities are notable by definition" would encompass anybody with a listing on IPNI. I have a colleague with an IPNI author listing based on their being the 3rd author on papers describing 3 species. The primary author was generous in attributing co-authors. Being listed as an authority on IPNI isn't a guarantee of notability. What's the status of "all species are inherently notable"? I know there's something to that effect on Wikipedia, and while it doesn't seem to be controversial, if I recall correctly, species notability isn't a Wikipedia policy or a guideline. I'd go for getting species notability enshrined as a guideline before adopting a WikiProject standard that species authorities are inherently notable. Plantdrew (talk) 06:34, 9 May 2014 (UTC)

There is a mention at WP:SPECIESOUTCOMES. This is not a guideline, but reflects AfD precedent. That's about as good as it gets, every article needs to meet WP:GNG on its own merit at the end of the day.--Melburnian (talk) 07:11, 9 May 2014 (UTC)

I would rather say "species are inevitably notable", rather than "inherently" simply because the processes that determine the existence of a distinct species inevitably result in the creation of reliable sources of the highest quality - scientific journal articles. Roger (Dodger67) (talk) 21:30, 17 May 2014 (UTC)

I have a listing on IPNI (one name in one paper in a horticultural journal), and have been cited/mentioned in a score or more of papers. I don't think I qualify as notable. Lavateraguy (talk) 09:03, 9 May 2014 (UTC)

@Lavateraguy: well, if the taxon has an article and your author abbreviation is in the taxobox, how do you suggest it's linked to explain it to readers if not via an article? Peter coxhead (talk) 18:10, 10 May 2014 (UTC)

My argument in the specific case was that if there's a taxobox containing that person's standard author abbreviation, then it should be wikilinked, which requires there to be an article. This isn't saying that we should create articles on authors in advance, but that once the author abbreviation is used, it is right to create an article.

Now this idea could be qualified; e.g. we could say that the person has to have been a (co)author of X names, where X > 1. Or we could say that it applies when the author abbreviation is not obvious, so that, say, "J.Smith" wouldn't need an article if X is small, but "Sm.f." would. It's the desire/need to wikilink which drives my wish to have an article. Peter coxhead (talk) 08:23, 9 May 2014 (UTC)

Isn't one of the fundamental guiding principles of Wikipedia that everything must be cited and verifiable? The decision has already been made that all species are notable. I support this. Common species are notable because people will encounter them frequently. Rare species are notable because they are very frequently the focus of conservation efforts. And the decision has been made that all species should have the authors cited in the taxoboxes. If we are required to include this author information, it seems to me that combining this with the principle of universal verifiability means that we need to provide the reader with some means of decoding these author abbreviations. In other words, if a person described only one species, and we are required to have an abbreviation of this person's name on that plant's page, we need to provide the reader with some means of figuring out who this person is/was.Joseph Laferriere (talk) 00:46, 10 May 2014 (UTC)

I agree. We could be more restrictive! but I personally wouldn't. Peter coxhead (talk) 07:07, 10 May 2014 (UTC)

@Joseph Laferriere...I hadn't thought of it like that before and it makes sense...colour me converted. Cas Liber (talk · contribs) 20:15, 10 May 2014 (UTC)

Maybe authorities without articles should be linked to List of botanists by author abbreviation or similar? Stuartyeates (talk) 07:22, 10 May 2014 (UTC)

Stuartyeates That would be a good idea if the list were more complete. That page gives only full name plus birth and death dates, with the name linked to a bio page (about 30-40% red linked). And the list is not complete. I tried looking several colleagues whom I know have authored numerous names, but could not find them.Joseph Laferriere (talk) 10:40, 10 May 2014 (UTC)

Well, just add them! The list is constantly being built up. Peter coxhead (talk) 18:05, 10 May 2014 (UTC)

I did one, an old professor of mine from Arizona. There were a few others I was tempted to do, but could not find sufficient biographical information.Joseph Laferriere (talk) 19:29, 10 May 2014 (UTC)

Actually, my name is on the list, but I figured it would be uncool for me to write a page about myself.Joseph Laferriere (talk) 19:36, 10 May 2014 (UTC)

(The first step would be to give IPNI your date of birth, so it doesn't just say "fl. 1990"! Peter coxhead (talk) 20:45, 10 May 2014 (UTC))

I'm in the camp that not all botanical authorities are notable, though many are. I mean... I'm a botanical authority myself, and I am most forcefully not notable. Circéus (talk) 22:42, 10 May 2014 (UTC)

Peter coxhead: I must have been looking at a different page. The list I looked at a few hours ago did give my dob (1955). Joseph Laferriere (talk) 00:51, 11 May 2014 (UTC)

Circéus: The point here is not what you think of yourself, but rather whether the readers of Wikipedia have the right to know who coined the name.Joseph Laferriere (talk) 00:51, 11 May 2014 (UTC)

I strongly agree that not all authorities are notable. Readers should be able find out who the authority is by reading the taxonomy section. Sasata (talk) 00:59, 11 May 2014 (UTC)

@Sasata: we'd have to alter the way we word many of those sections for this to work. I always try to write things like "Scadoxus cinnabarinus was first described by Joseph Decaisne", but I haven't been adding "whose standard author abbreviation is 'Decne.'"; however, without this, where the abbreviation isn't initials + name, the ordinary reader probably won't connect the entry in the taxobox with the text in the article. Peter coxhead (talk) 08:24, 11 May 2014 (UTC)

Is there any evidence that the "ordinary reader" actually cares about this? I can't recall ever seeing a talk page query about the identity of an unlinked authority abbrieviation. Have you? Sasata (talk) 09:26, 11 May 2014 (UTC)

Only a tiny percentage of any of these taxonomy sections contain any shred of information about who the authority is/was.Joseph Laferriere (talk) 01:45, 11 May 2014 (UTC)

I don't know how WikiData works, but could it possibly be used to address this? The taxobox template could be used to map abbreviation to authority, and if there is no article for the authority to link to the list of author abbreviations, which in turn can point to the IPNI Author Search for authorities not included in that list. Lavateraguy (talk) 11:32, 11 May 2014 (UTC)

Acacia didyma is a case where one of the coauthors does not have an article. Considering some of the discussion points here, I've removed the orphan red link, added a footnote to explain the author abbreviations and inserted IPNI author cites for both authors in the text.--Melburnian (talk) 13:08, 11 May 2014 (UTC)

With all due respect,I think that this is a bit awkward Joseph Laferriere (talk) 14:41, 12 May 2014 (UTC)

I have to say that I agree. It also makes a decision about whether the person is notable, which I'm not sure can be made until someone actually tries to write an article about them. Some way of producing a default wikilink, as Lavateraguy suggested, would be better, though it's not clear how to do it. Peter coxhead (talk) 18:21, 12 May 2014 (UTC)

What I meant was that the footnote creates a disjointed page with duplicate information. The names are already in the text; the footnote adds the middle names but nothing more. So the footnote I find distracting. I like having it buried in a link so the reader can click on the link to obtain that information if she or he needs it, but can sit and admire the pretty blue letters if she or he does not need the info.Joseph Laferriere (talk) 01:50, 13 May 2014 (UTC)

@Peter coxhead: No, its the other way around. Inserting a redlink is making a decision about notability as defined for Wikipedia. WP:REDYES states that "creating a redlink also carries the reponsibility to first ascertain...that its foreseeable subject matter will meet the WP:notability guidelines for topics covering covering people (WP:BIO)". That means if you are writing the article and you are not sure about the notability of a subject, don't insert a redlink. That doesn't stop another editor who is sure (or oneself after further investigation) later adding a redlink or writing an article.--Melburnian (talk) 02:03, 13 May 2014 (UTC)

Ah, right. I took it to be the case that we agreed that everyone with a standard form in IPNI was a priori notable, so it requires evidence to say otherwise. Clearly, this isn't the case, so I was wrong. However, in the specific case, Maslin is clearly notable, and has an article; "A.R.Chapm." is associated with 32 unique names in IPNI (see here), so I would say is also notable by any reasonable standard. Peter coxhead (talk) 08:28, 13 May 2014 (UTC)

The general problem is that there is a paucity of substantial written information about living botanists (even prolific ones) in reliable secondary sources. For Australian botanists, there is Australian Plant Collectors and Illustrators 1780s-1980s which is a list that has links to notes for many of the entries. Often such mini-biographies are not written until the subject retires or dies, so many of those in the middle of their careers don't tend to have good coverage.--Melburnian (talk) 01:21, 14 May 2014 (UTC)

@Peter coxhead: You say "No, its the other way around." Please reread my previous note. I said I like blue links. I never said I liked the red ones.Joseph Laferriere (talk) 01:56, 14 May 2014 (UTC)

""No, its the other way around" was me replying to Peter coxhead's [18:21, 12 May 2014 (UTC)] comment.--Melburnian (talk) 02:36, 14 May 2014 (UTC)

Humble apologies. It was late in the evening when I read that.Joseph Laferriere (talk) 09:43, 14 May 2014 (UTC)

It would have been good to have reached a consensus on this, but I think we haven't. There seem to be two issues:

Whether authoring a taxon is in and of itself sufficient to make the author notable; on this we simply disagree. Can we perhaps agree that authoring say 20+ taxa makes the author notable, while agreeing to differ about a figure lower than this?
Whether it's worth writing a stub article given that sufficient information in reliable secondary sources is often hard to find, especially for living authors. I'm not clear whether Melburnian is simply commenting or arguing that it's not worth writing a stub article. If the latter, again I think we don't agree; in most cases it's possible to say something worthwhile based on papers, etc. I'd like to know more about A.S. Losina-Losinskaja, but what is in the article is surely better than nothing?

Peter coxhead (talk) 07:16, 18 May 2014 (UTC)

It's worthwhile writing a stub article, providing you can establish notability.--Melburnian (talk) 02:53, 19 May 2014 (UTC)

Ok, so the only issue is the one we started with, namely whether botanical authors are automatically notable. If you look at the list of criteria at Wikipedia:NOTE#General notability guideline, botanical authors will pass most tests, in relation to their authorship status – this is in reliable third party sources; there will be at least one primary source, whose use is justified by the secondary sources; outline biographical information, such as institutional affiliations over time is easily gleaned from publications without the need for OR. I guess the issue is whether botanical authorship amounts to just "a passing mention", since more than this is required. I incline to the view that it is more than this; it's an integral part of the full citation of the scientific name. Maybe if the person has authored only one or two names he or she isn't notable, but I contend that most authors will be. Peter coxhead (talk) 08:14, 20 May 2014 (UTC)

That sounds like that an inherited notability argument to me.--Melburnian (talk) 01:21, 21 May 2014 (UTC)

"Maybe if the person has authored only one or two names he or she isn't notable" is a distasteful argument since some of the people who do the best work publish very few or even zero names, generally because they are cleaning up after people who publish a lot of names (e.g., Willard Webster Eggleston tidying up after Charles Sprague Sargent and William Willard Ashe), or Robert Brown (botanist) being notably less well known than less careful workers. It's an argument that parallels judging the worth of wikipedians by counting their edits, or of programmers by counting the number of lines of code that they write (or duplicate into irrelevant places). I'd be distressed to see name-counting enshrined as a criterion of notability. Sminthopsis84 (talk) 16:35, 21 May 2014 (UTC)

@Sminthopsis84: I think you've taken my wording out of context. I meant "if the person has authored only one or two names he or she isn't notable purely on that account" – clearly they may be notable on other accounts. The issue is whether authoring botanical names in and of itself makes someone notable. Melburnian seems to say that it doesn't, although hasn't directly picked up my point about numbers. I'm inclined to think that someone who has authored a "reasonable" number of names, whatever number that is, is notable purely on that account. Of course they may be notable on other accounts, as may botanists who have never authored a name. Peter coxhead (talk) 06:34, 22 May 2014 (UTC)

Peter, I would argue that authoring botanical names does not in and of itself make someone notable. A "reasonable number" doesn't really have a meaning when satisfying the requirements as specified in the Code of Nomenclature has next to nothing to do with whether a name should be published. Horror stories of bad behaviour by people who have published names abound, which is the reason for the perennial discussions among nomenclaturists about how to move away from attaching author names to taxon names. Just one example is where the same author in a series of publications moved species between various candidate genera, with the effect that no matter what later competent botanists decide about placement, his authorship will be attached to the correct name. To say that that person must be notable is the equivalent of applauding a vandal. Sminthopsis84 (talk) 11:50, 22 May 2014 (UTC)

Applauding? Nobody is applauding anybody here. It is just a statement of fact, informing the reader as to who coined the name. And nothing more than that. It is not our job here to pass judgement on whether these authors were nice people or not, nor whether they coined one name or a thousand. Joseph Laferriere (talk) 02:06, 23 May 2014 (UTC)

I have to say I agree with Joseph here. Curt Backeberg was described by David Hunt as having "left a trail of nomenclatural chaos that will probably vex cactus taxonomists for centuries", including describing new species from the window of a passing train. He's notable precisely because cactus taxonomists have had to spend so long sorting out his names. Pierre Delforge ("P.Delforge" in IPNI) has been very influential in naming orchids, and has created a large number of species names in the genus Ophrys (up to 10 times the number others recognize), a number quite unsupported by all the recent molecular phylogenetic research. He doesn't yet have an article, but he should have because he is definitely notable, partly precisely because other botanists have to deal with his names whether they agree with them or not. Peter coxhead (talk) 09:33, 23 May 2014 (UTC)

My favorite is Rafinesque. I have seen some of his books, published in the 1830s and 1840s. Some of these are on BHL so you can see for yourself. Very long lists of new names, some of which are new names of other people's taxa, which he decided to change because he did not like the sound of the existing names (in his defense, this was before priority rules came into vogue). Others were new species with cryptic descriptions 5 or 6 words long, half the words abbr. One time I saw him create a new name on line 6 of a particular page, then create a homonym for it on line 7. And his private herbarium got burned after he died, so there are no lectotypes. But many of his names did in fact represent new species, so there are hundreds of names with "Raf." at the end. Joseph Laferriere (talk) 10:46, 23 May 2014 (UTC)

Summation: I think this has been a useful discussion, and as I anticipated, has seen a variety of opinions. Obviously no issue is ever completely black and white, and all Wikipedia style pages are to some extent guidelines not laws. Thus 'notability' is partly subjective. From that perspective there are two issues, one being Wikipedia's general guidelines on notability, and the other being the more specific issue of notability to botanists. I think the whole point of having WikiProjects is that we can have a certain degree of autonomy in setting guidelines specific to our own subject. To be completely logical, if standard nomenclature attaches an authors name to a taxon, that name has been 'noted. This issue arose because I wrote a page to provide information on a taxa's authority, and someone tried to delete it on notability grounds, untill I explained the whole concept of botanical authority. However there were no guidelines to point to, hence this discussion.

There is no point in having these discussions unless it leads to some sort of policy, or we will have them all over again in a few years, and other editors will be none the wiser. So I am going to try and translate this into some sort of policy on our page which is more of a guideline than a black and white law. In describing a taxa with an authority, it would be preferable to have a link to information about that authority, and there are certain basic elements that should be in that page, including IPNI, the {{botanist}} template, and links to the taxon or taxa, and vice versa, and also inclusion in our list of authorities. If you write a page about a botanist who is linked to a taxon, and someone tries to delete it, point them to this guideline (still to be written). At present we have no guidelines regarding botanist pages, and as such that would be useful in itself. --Michael Goodyear (talk) 13:42, 29 June 2014 (UTC)

@Mgoodyear: I agree that it's a good idea to add something to the project page. Peter coxhead (talk) 20:45, 29 June 2014 (UTC)

I have provided an initial version at WP:WikiProject Plants#Botanists.--Michael Goodyear (talk) 03:29, 30 June 2014 (UTC)

Identification request

Can anyone identify the plant in this featured image for me (and the community)? ResMar 02:03, 30 June 2014 (UTC)

Not an expert on Hawaiian flora, but after a little poking around, it looks like Metrosideros polymorpha. Tdslk (talk) 02:09, 30 June 2014 (UTC)

Reddit came to the same conclusion, so that looks to be it. I was about to ask about how likely that this was planted into the lava flow, but a quick look at its Wikipedia page says otherwise: "colonizer of recent lava flows". Beautiful picture. ResMar 03:44, 30 June 2014 (UTC)

For more information, see kīpuka. Viriditas (talk) 04:41, 30 June 2014 (UTC)

Discussion of whether or not use of the content in Jepson, or field guides based on Jepson, constitutes a violation of WP:Copyright

There is a discussion of whether or not use of the content in Jepson, or use of content in plant field guides that cite Jepson as their authority, constitutes a violation of WP:Copyright. The discussion can be found hereTalk:Hilaria_rigida#Copyright_problem_removed, and a realted discussion is here Copyright investigations (manual article tagging) Syntrichopappus fremontii. FloraWilde (talk) 15:40, 30 June 2014 (UTC)

garidella

Hello. I was wondering if any of you would be interested in creating a page on garidella, a subclass of the thalamiflorae, named in honour of French botanist Pierre Joseph Garidel. Let me know if you are. Please reply on my talkpage. Thank you.Zigzig20s (talk) 18:53, 8 July 2014 (UTC)

Categories "flora by countries"

I think these categories have not much botanic sense, since plants do not recognize national borders, and they create a huge mass of categories for some species. As an example Lily of the valley has about thirty such categories. I propose to suppress these categories, or admit only those that are for English speaking countries.--Auró (talk) 21:38, 7 July 2014 (UTC)

I agree. I have raised this once before here but without much success. Regards Velella ^{Velella Talk} 23:01, 7 July 2014 (UTC)

The mess you found at Lily of the valley was the result of a misapplication of the flora categories and overcategorization. For example, the plant was in both Category:Flora of Europe and many of the country categories within Europe. As the distribution for this plant is best accurately described at the higher level, we remove child categories and upmerge as long as that category higher in the hierarchy still accurately describes the distribution. I cleaned it up, and for the most part the plant is native to temperate Asia, Europe, and the southeastern US.

It doesn't matter what the plant thinks about political borders. This is how we discuss, write about, define, and think about plants. Political borders are a convenient way to discuss plant distributions, which is why we use the World Geographical Scheme for Recording Plant Distributions. Books and flora treatments are written on the plants native to areas defined by political boundaries. When you find category clutter like that on the lily of the valley article, it is not the fault of the category scheme but a few overzealous editors who seem to think a plant must be included in every country category it can be found in. Be bold and clean it up by upmerging! I wrote some advice here: WP:PLANTS/WGSRPD. Rkitko ^(talk) 23:19, 7 July 2014 (UTC)

We have discussed this at great length before. I have only one thing to say at this juncture, i.e., that I very strongly and unequivocally object to the bit about "admit only those that are for English speaking countries." I cannot think of a single polite thing to say about that idea.Joseph Laferriere (talk) 02:02, 8 July 2014 (UTC)

I think that my suggestion about limiting the category flora by country to the English speaking countries has been taken in a sense that was not intended by me. Fortunately there are many Wikipedia projects, for many languages. If Wikipedia Catalana, for instance, contains a category named "Flora de Catalunya" I would find it quite normal, but to admit that English Wikipedia has to contain "Flora from Catalonia" as well as any of world countries and regions is not sensible. I hope my point is now clear.--Auró (talk) 21:28, 8 July 2014 (UTC)

Since the geographical areas of distribution for plants tend to be larger than a single country, merging up could in fact suppress about 90% of the categories by country. It is a practical solution.--Auró (talk) 21:38, 8 July 2014 (UTC)

Auró - Two assumptions here: 1) People will be reading Wikipedia only in their own native languages. Much of the information is available in one language but not another. In general, the English wikipedia tends to cover more information than the versions in other languages, though of course with exceptions. Many people whose first language is not English will be reading the English-language wikipedia pages. 2) People are interested only in plants native to their native countries. This is hardly true. Many botanists cross international boundaries in their work and need information about plants around the world. I personally have worked much in Latin America and frequently make use of websites in Spanish and occasionally in French or Portuguese. The current system offers the option of large-range categories or short-range categories. If a plant is widespread across most of Africa, it goes into the "Flora of Africa" category but if it is endemic to Botswana it goes in the "Flora of Botswana" category. You are proposing eliminating that option.Joseph Laferriere (talk) 22:38, 8 July 2014 (UTC)

Joseph - For me the question is settled by means of Rkitko up merging solution.--Auró (talk) 21:36, 9 July 2014 (UTC)

Tools for adding lists to plant pages

I've been working with @Peter coxhead: and getting valuable advice from @V111P:, creating tools that might be of interest to other plant editors, for rapidly reformatting synonym lists and species lists. A prototype tool is described at User:Sminthopsis84/TPLSynonyms. That one uses synonym data from http://www.theplantlist.org chosen by the wikipedian, who uses copy/paste to give input data to the program and to add the result to wikipedia. The program is written in HTML and javascript, and would run in your browser (we've tested it on a few of the many available browsers), thereby avoiding the security problems that come with a compiled language like java. I'd be very interested to know if people think this would be useful, and happy to answer questions. It is possible to create programs that work with other databases, WCSP, algaebase, ...

We've discussed possibly integrating such tools further into wikipedia, perhaps creating a button that you would click to go to the program, and perhaps working directly from the plant database without using copy/paste. Those sophisticated additions don't seem to be warranted at present, unless people think they would be helpful.

The prototype tool is easily downloaded as described at User:Sminthopsis84/TPLSynonyms. You would put the two files into the same directory anywhere on your computer, and then open one of them with your browser. Sminthopsis84 (talk) 17:53, 11 July 2014 (UTC)

Nice work! I do want to mention I still have some concerns about using TPL or WCSP exclusively for synonym lists. I've found some egregious errors on both, as is natural for databases of their scope. Often, the synonymy lists are informed by a single editor and no supporting documentation is provided. I'd rather not see existing synonym lists compiled from recent monographs and other sources be overwritten by TPL or WCSP, though I'm not suggested that would happen. Scripts just make the possibility of such errors a little more likely. Anyway, just my two cents, and really more of a response to lots of recent conversations here that have treated TPL or WCSP as authoritative sources when they should be used more carefully. Not a criticism of the tool you've created! Cheers, Rkitko ^(talk) 21:55, 11 July 2014 (UTC)

Yes, I entirely agree that these aggregator databases must not overwrite more authoritative information. They have errors, and may simply be working from less than the complete set of authoritative literature. I think it is encouraging, though, how much they have been updated in the last couple of years, and (funding permitting) seem likely to continue to improve. My feeling is that the need to carefully consider the contents of those databases is a good reason to not further automate the tools. Sminthopsis84 (talk) 11:51, 12 July 2014 (UTC)

For synonym lists, I agree that multiple sources can be used, although there are problems: using monographs is sometimes against the preference of WP:RS for secondary sources, and combining sources can lead to inconsistencies unless care is taken. Obviously it's always necessary to review the information in any source, TPL, WCSP or whatever, before using it. Peter coxhead (talk) 08:06, 12 July 2014 (UTC)

Addendum: Rafaël Govaerts at WCSP (use the "contact" link on the WCSP page) is, in my experience, very helpful and very quick to correct errors for which evidence can be provided. TPL is different: it seems that they "scrape" other databases only once for a version, so corrections and changes to WCSP, Tropicos, etc. won't show up until the next version. Peter coxhead (talk) 08:09, 12 July 2014 (UTC)

I had a problem a few weeks ago. I put together a species list to put onto a genus page, as I have done many times before. But this one time, I got a nasty note from some bot accusing me of violating copyright by, according to the bot, swiping the list from TLP. I had not even consulted TLP at all on this; I had swiped it from WCSP. The bot note went on to say "you can obtain information from another source, but you must rephrase it." You can't rephrase a scientific name. Can a list be copyrighted? Maybe if I were to de-alphabetize the list, the bot might accept that as rephrasing. Bots are not all that bright. Anyhow, nothing came of this, and the list is still on the wikipage.Joseph Laferriere (talk) 23:11, 11 July 2014 (UTC)

I'm no expert on US copyright law which applies to Wikipedia, but the information in a list can't be copyrighted, although the layout and precise wording can. So long as we extract only scientific names and authorities and put them into WP's format, there shouldn't be a problem. Peter coxhead (talk) 08:06, 12 July 2014 (UTC)

There's a working prototype temporarily here which takes a list of species pasted from a WCSP checklist (using the "Build a checklist" option in the left column), extracts records according to selected criteria, and produces a wikified list for copying and pasting into Wikipedia. WCSP is not entirely consistent in its formatting, so automated parsing doesn't always work; careful review of the output is needed! Comments welcome. Peter coxhead (talk) 08:06, 12 July 2014 (UTC)

Peter coxhead That's what I figured. I was not copying anybody's format, adding links and a brief range statement for each species on the list, the range information taken again from WCSP but reworded. It is much easier to reword a range statement than it is to edit the name of a species (simply say "Staffordshire and Tajkistan" instead of "Tajkistan and Staffordshire)." But these bots are not consulting with lawyers before they send out these threatening notes.Joseph Laferriere (talk) 09:57, 12 July 2014 (UTC)

@Joseph Laferriere: can you provide the details of where this bot ambushed you? Perhaps WP:PLANTS people could mount an argument somewhere about how to improve its behaviour. Sminthopsis84 (talk) 11:51, 12 July 2014 (UTC)

Sure. I can give you the direct quote, cut/pasted from my talk page: "This is an automated message from CorenSearchBot. I have performed a web search with the contents of Globba, and it appears to include material copied directly from http://www.theplantlist.org/browse/A/Zingiberaceae/Globba" Joseph Laferriere (talk) 13:14, 12 July 2014 (UTC)

I see what you mean by a not-very-bright bot. Apparently, CorenSearchBot will leave alone additions that use a citation template like {{1911}}. There doesn't seem to be such a template for WCSP, but there is one made by @Plantdrew: for The Plant List, and that isn't being used by the tool described above. Plantdrew, could you please have a look at the more complex example listed here, and see what you think about how to interface your template with that? I could write code that looks for two different situations, a URL that includes "record" and one that includes "search", using your template only for the former case. The tool would also need to be modified to pick up the taxon name and authority from the TPL page for that case. Sminthopsis84 (talk) 18:08, 12 July 2014 (UTC)

I have templates for both TPL and WCSP which I use regularly: see User:Peter coxhead/TPL and User:Peter coxhead/WCSP. The problem with "citation templates" is that preferred styles vary; e.g. my templates default to my preferred style of Template:Citation and to ISO dates for the access date, etc. which may not be to other people's tastes. Peter coxhead (talk) 20:24, 12 July 2014 (UTC)

A few thoughts, my friends. First, I have done hundreds of these pages, but CorenSearchBot objected only the one time. Second, Peter, you mentioned US copyright law. Why US? Indeed, what country's laws are applicable to an international phenomenon such as wikipedia? Plant List comes out of Kew, or so I thought. Kew is in the UK, or was last time I checked. Third, I am a bit uncomfortable with things like this being done automatically. That seems almost certain to introduce new errors. Old-fashioned cut/past may be more time-consuming, but it does allow for an actual human to double-check to make sure the not-so-bright bot is not doing something totally daft.Joseph Laferriere (talk) 04:05, 13 July 2014 (UTC)

@Joseph Laferriere: (1) Wikipedia is held on servers in the US, so US copyright law applies – see Wikipedia:Copyrights#Governing copyright law. (2) I would never suggest automatically extracting information from any database. For example, all my WCSP tool does is to re-format information copy-and-pasted from a WCSP checklist. It's intended solely to make it easier to format information consistently in the style we use. Peter coxhead (talk) 06:00, 13 July 2014 (UTC)

Interesting that CorenSearchBot doesn't often react. I hope we can ignore it, and just revert its action when it strikes.
I don't like the idea of automatic extraction either.
So, what is the general consensus about whether tools like TPLSynonyms should use a template rather than coding their own format for the citation? Is that premature because the templates aren't universally beloved? I've described two possible embellishments at User talk:Sminthopsis84/TPLSynonyms and would welcome opinions there. Sminthopsis84 (talk) 16:13, 13 July 2014 (UTC)

Inaccuracy of TPL

The accuracy of TPL has been questioned in these talk pages in the past. I entirely agree; for those plant families it covers I've found WCSP much more reliable. A particular problem with TPL is that it does not extract information correctly from Tropicos. Here's just one example I've found.

Search TPL for "Maurandya acerifolia". Response: Maurandya acerifolia Pennell is an accepted name, citing Tropicos.
Search TPL for "Mabrya acerifolia". Response: Mabrya acerifolia (Pennell) Elisens is an accepted name, citing Tropicos.

The authorities should ring an alarm bell, so let's look at Tropicos directly.

Search Tropicos for "Maurandya acerifolia". On the response page there's a tab "Accepted Names (1)" under which we find Mabrya acerifolia (Pennell) Elisens.

So Tropicos does not accept Maurandya acerifolia Pennell; it regards it as a synonym of the name it accepts, Mabrya acerifolia (Pennell) Elisens.

Sadly this isn't an isolated example. The status of names in TPL derived from Tropicos needs to be checked directly with Tropicos.

However, Tropicos isn't itself a reliable source for the status of names, since it collates information including specimens in herbaria, which may well be wrongly labelled. Here's an example. TPL claims that Lophospermum nubiculum Elisens is an accepted name in Tropicos. Tropicos does indeed have an entry for Lophospermum nubiculum Elisens, but doesn't cite the source of the name, only a secondary source. The name isn't in IPNI; a search of plant names by author in IPNI shows that Elisens didn't name species after 1985. His 1985 monograph which covers Lophospermum is online; there's no such name as Lophospermum nubiculum although there is a Lophospermum nubicola. The epithet nubiculum appears to be an orthographic error based on the re-labelling of a single herbarium specimen (see here) which cites Elisens (1985) which doesn't contain the name.

This probably counts as original taxonomic research so can't be included in Wikipedia, but the moral seems to be "don't believe what you see in (some?) online taxonomic databases". Peter coxhead (talk) 06:30, 13 July 2014 (UTC)

The phrase "orthographic error" is another way of saying "misspelled word." We are not allowed to correct misspellings? Suppose I were to say that the Queen of England lives in Buckleham Palace. We are not allowed to correct the error because this would constitute original research? Joseph Laferriere (talk) 07:34, 13 July 2014 (UTC)

We do correct names, by following the rules in the ICN. So do other botanists, and sometimes they do so incorrectly. I think that what went wrong with TPL here is that it didn't downgrade all names to low confidence if there was no original citation listed in Tropicos.org. To TPL's credit, the most recent update did correct a lot of crossed pointers. At least one of those crosses, though, was crossed in Tropicos, and has since been corrected. The next update of TPL should correct at least that one. In general, I believe that IPNI has done a superb job of incorporating the changes to articles 60, 61, and 62 of the ICN, so a good rule of thumb is to use IPNI's spelling. I've witnessed the anguish at two botanical congresses (6 years apart, as always, the next will be in 2017) where both times there were a huge number of proposals to change or clarify those articles about orthography, and both times the congress latched with alacrity onto the suggestion to refer them all as a block to the editorial committee. Those articles have been nightmarish. In 2001, it was much harder to figure out how to apply them. I suspect that those authors either goofed or did not, but in any case are now considered to have been mistaken. Botanists and wikipedians should ignore that name.

There are certainly errors in TPL: I don't remember where, but I saw a species listed as a synonym of its own autonymous variety …

I've sometimes set off to place synonym lists and move plant pages as appropriate and found that there is no database that I can find that gives a good account of what the current accepted taxonomy might be, then had to back-track. In many cases, there is no recent authoritative monograph either, the plant group simply hasn't been revised in living memory. Sminthopsis84 (talk) 16:13, 13 July 2014 (UTC)

@Joseph Laferriere: well, if you came across, say, "Lopospermum" in a context which clearly meant "Lophospermum", then it would be like "Buckleham Palace". In my example, it's not so obvious that it's an orthographic error. I've contented myself with a footnote at Lophospermum, but maybe I should have been bolder and not listed the name at all?

@Sminthopsis84: I'm a bit wary about applying the orthographic correction rules in the ICN directly in Wikipedia. For example, epithets with "ae" instead of "i" can be corrected (as I understand the rules). Thus if you find e.g. alliariaefolia or yuccaeflorum they can be corrected to alliariifolia and yucciflorum. If I found such cases in the online databases, I've preferred so far to report them and wait for the change. Again, I can only applaud Rafaël at WCSP who's been very quick to make corrections. Peter coxhead (talk) 20:48, 13 July 2014 (UTC)

Peter coxhead Okay. I can see the point about waiting until WCSP changes the error its database before we correct it on Wikipedia. Having them spell it one way and us spell it another would create confusion, even if we are right according to the ICN and they are wrong. The ICN exists for a reason, i.e., to solve problems rather than to create them. Any good botanist knows this and tries to follow the ICN as closely as possible. Yes, it can be complicated, but is mostly due to the retroactive nature of the rules, trying to apply 21st Century rules to 18th- and 19th-Century publications. But sometimes botanists (esp many of my fellow Americans) have a poor knowledge of Latin, resulting in mistakes. I saw one paper in which a male botanist said he was naming a species after his wife, then proceeded to use the male -ii instead of the female -iae.Joseph Laferriere (talk) 22:14, 13 July 2014 (UTC)

Update Tropicos (in the person of Jim Solomon, the Curator of the Herbarium) has now removed "Lophospermum nubiculum", so I can fix the Lophospermum article. For me, this yet again points to the undesirability of using The Plant List as a source, because it only seems to change its data when a new version appears. Peter coxhead (talk) 05:53, 16 July 2014 (UTC)

I agree that getting the databases corrected when we discover an error is by far the best course. I think that working on plant taxonomy in wikipedia is valuable in large part because of the errors that it reveals in those external databases. No single database covers all that we need, however: e.g., WCSP doesn't cover Rosaceae; Tropicos and the Kew databases don't cover Boronea. APNI doesn't decide on a single synonym list, but list the opinions of various authors, as for example here, and Wikipedia doesn't work that way (neither does wikispecies, the wiki world apparently isn't ready for multiple taxonomies or for incomplete resolution in the taxonomy). Tropicos doesn't have any sort of "confidence" indicator, and I would prefer to see that ThePlantList says that Baissea names derived from Tropicos should be taken with a small grain of salt, than to look directly at Tropicos and see no such indication. I very much hope that ThePlantList will, in future, be making small updates more frequently than it did in the first two upheavals. For species-level taxonomy, it is different from the other sources, and potentially the final checklist. Sminthopsis84 (talk) 12:43, 16 July 2014 (UTC)

The most up to date checklists

Please cite and link to the most up to the moment (date) and highest quality plant species and genera checklists for Europe and more specifically for the British Isles?
The "Florical" high quality taxonomic database of the indigenous flora of New Caledonia recently updated its checklist in international peer–reviewed published form in Dec. 2012, as cited below:
- Morat, P.; Jaffré, T.; Tronchet, F.; Munzinger, J.; Pillon, Y.; Veillon, J.-M.; Chalopin, M. (Dec 2012). "The taxonomic database "Florical" and characteristics of the indigenous Flora of New Caledonia". Adansonia. sér. 3. 34 (2): 177–219. Retrieved 14 July 2014. —Further updated more recent 27th June 2014 version available therein.
The Australian Plant Name Index, here (about it, higher standards and validation),

gets updated to the latest available highest quality taxonomy at least as frequently as twice a year and often within days or weeks of the new taxonomy publication date (if it’s already widely accepted) by means of thorough taxonomy review by the Council of the Heads of Australasian Herbaria (CHAH) including coordination of taxonomic botany specialists—as written by the manager of botanical information to me. The best standard plant taxonomy and nomenclature database that i know of in the world … for all others to be compared to … many more reliable sources about this can be provided … . --Macropneuma 05:46, 14 July 2014 (UTC)

Regional/national databases are fine for endemic taxa of whatever rank. The problem with using them more generally is possible inconsistency with the treatment of the same taxon in other countries. Peter coxhead (talk) 15:41, 14 July 2014 (UTC)

Again, please Peter Coxhead reply to the above request about Europe and the British Isles most up to the moment (date) and highest quality plant species and genera checklists.

Not a problem. Compare the most up to date highest quality taxonomy checklists (secondary and most reliable sources) and read through the body of taxonomic literature on the subject genus, especially the most recently published (so called primary sources, in terms of well attested human taxonomies of plant species and genera).

Real, topical, example (—JL), compare the Gahnia genus (Cyperaceae family) taxonomy and nomenclature in the Australian Plant Name Index here, Florical (linked above), NZ plant taxonomy database (online) and so on —the most up to date and highest quality taxonomy checklists, with the World Checklist of Selected Plant Families (WCSP), here and through the means of its "Build a Checklist" link with the setting of the family to Cyperaceae and genus to Gahnia. Quotation below of WCSP’s own citations of their sources and of how up to date they are—does this mean this Cyperaceae checklist was compiled in database form in 2004 and published in paper form in 2007 without update or that they did do more checking of the taxonomy after 2004 before going into hard copy print in 2007. Clearly it means that no update has happened since 2007 for their Cyperaceae family checklist of species and genera available in WCSP and The Plant List.

Govaerts, R. (2004). World Checklist of Monocotyledons Database in ACCESS: 1-54382. The Board of Trustees of the Royal Botanic Gardens, Kew.
Govaerts, R. & Simpson, D.A. (2007). World Checklist of Cyperaceae. Sedges: 1-765. The Board of Trustees of the Royal Botanic Gardens, Kew.

—--Macropneuma 00:41, 15 July 2014 (UTC) —addendum: here we see who the few Cyperaceae (family) actual plant taxonomist reviewers were, partial info on what they reviewed and when they last did review so for WCSP (from 2004 to 2008 —of course, Govaerts merely compiles). —--Macropneuma 23:37, 15 July 2014 (UTC)

Gmelina (Lamiaceae) was a genus WCSP got up to date (superfluously for WP purposes, here) based directly on the taxonomy of de Kok’s high quality worldwide genus revision published in 2012 in Kew Bulletin—hardly surprising really, has everyone heard of the Johari window (here referred to not literally but rather figuratively for the ethnic group social scale rather than the usual individual person scale)? —--Macropneuma 01:12, 15 July 2014 (UTC)

For this genus, a quotation of WCSP’s own citations of their sources:

Govaerts, R. (2003). World Checklist of Selected Plant Families Database in ACCESS: 1-216203. The Board of Trustees of the Royal Botanic Gardens, Kew.
de Kok, R. (2012). A revision of the genus Gmelina (Lamiaceae). Kew Bulletin 67: 293-329.

—--Macropneuma 03:21, 15 July 2014 (UTC)

Where WCSP, Tropicos, etc. state the sources they use, then if more recent monographs covering the entire taxon are available, one would of course use them, with the usual caveats about single primary sources as per WP:OR. However, in many cases, they simply aren't available. Producing detailed taxonomically reliable monographs seems to be a dying activity; most modern papers on a taxon consist of molecular phylogenetic studies on those subtaxa which have gene sequences available.

@Macropneuma: sorry, didn't realize you were asking a question. For Europe as a whole, I know of no up-to-date reliable source. For the British Isles, we use Stace, Clive (2010), New Flora of the British Isles (3rd ed.), Cambridge, UK: Cambridge University Press, ISBN 978-0-521-70772-5 plus updates published by the BSBI in its journal Watsonia and its bulletin. There isn't yet a single consolidated list (to my knowledge); I use the 2007 list + the updates at [1]. It should be noted that Clive Stace is an explicit supporter of paraphyletic taxa where he feels these make best sense, so e.g. Lemnaceae is recognized independently of Araceae. Recent British Floras (e.g. the Flora of Birmingham and the Black Country, 2013) follow Stace + updates. Peter coxhead (talk) 09:37, 15 July 2014 (UTC)

I was going to suggest the Euro+Med plant database for Europe, but checking out its Malvaceae listing, there are a few errors in there (e.g., they've sunk Lavatera in Malva, but haven't transferred Althaea sect. Hirsutae and haven't sunk Malvaltheaea). Lavateraguy (talk) 10:23, 15 July 2014 (UTC)

… Thanks. Around twenty years ago in the late 1980s and early 1990s we used and cited Flora Europaea. I’ve just been reading various sources about the Euro+Med plant database, how Flora Europaea volume 1 was revised and the new edition published in 1993, then all volumes were digitised and released on CDs in Dec. 2001, then all this information has been used in this Euro+Med plant database wherein they have started doing many packages of work on updating it all; see here. … —--Macropneuma 12:11, 15 July 2014 (UTC)

Flora Europaea was a fantastic resource – actually I still use my copy from time to time (and some groups have been round in a circle, e.g. FE‘s conservative treatment of Ophrys fell out of fashion as botanists like Delforges multiplied the species ten-fold, but recent molecular work tends to support FE‘s approach). I have about ~20,000 slides of European plants (mine and two late friends), which were originally (re)labelled using FE. The issue for these is not whether the latest taxonomy has been used, but whether there is a complete and self-consistent list. At present it doesn't seem that there is. Peter coxhead (talk) 18:29, 15 July 2014 (UTC)

Rename request: Dandelion_(disambiguation) to Dandelion

Dandelion currently redirects to Taraxacum. Opinions are invited at Talk:Dandelion_(disambiguation) on a proposal to rename and move Dandelion (disambiguation) to Dandelion. Sminthopsis84 (talk) 16:32, 16 July 2014 (UTC)

Recent changes to article template

User:FloraWilde recently made some significant changes to the Project's Article Template, including re-ordering and renaming the "Distribution and habitat" section. Such changes need discussion and consensus here first, so I reverted them wholesale and then added back changes some I thought useful and uncontroversial. Please revert these too if you don't agree. Peter coxhead (talk) 20:28, 19 July 2014 (UTC)

~~:Talk page discussion of possible revisions is here. FloraWilde (talk) 20:48, 19 July 2014 (UTC)~~ (I think it's better to discuss it here; this page is more often visited and it's where we've usually discussed changes to the project's subpages. Peter coxhead (talk) 21:30, 19 July 2014 (UTC))

Plant ID or description starts with distribution/habitat/range - It grows at location A, at elevation B, in soil type C, among vegetation type D, and consists in about E of the ground cover.
Next comes what the plant looks like overall, the growth pattern - It is an annual/perennial Tree/bush/shrub/herb growing from central/branching stems and reaches a height F and is shaped like G.
Next comes a description of leaves, stems, roots.
Then comes a description of inflorescence and fruit.
Other information, such as uses, ecological interaction, technical taxonomical information, etc., then follows.
I suggest these revisions.

FloraWilde (talk) 20:48, 19 July 2014 (UTC)

Several points.

I think that Wikipedia readers want to know first of all what a plant looks like, i.e. to have a description of it.
In the description, after some overall statements about the growth habit, most sources I use tend to start from the bottom upwards which is also roughly growth order, i.e. roots, stems, leaves, inflorescence (for flowering plants), fruit/seeds/etc.
For taxa with no subdivisions, it's possible, I guess, to move the Distribution and habitat section to the top, but for families, genera, and species with significant infraspecific taxa, it doesn't really work, because you have to say something about the distribution of these subtaxa, which means you need the material in the usual Taxonomy section to be first, since it's there that we list the subdivisions.

I have to say that when I first encountered WP:WikiProject Plants/Template, I had some doubts about the order of the sections, but the more articles I work on (especially new ones) the more I see why the order in the template makes sense. Peter coxhead (talk) 21:30, 19 July 2014 (UTC)

I agree "Wikipedia readers want to know first of all what a plant looks like". So do I, in most cases. General appearance is a good thing to put in the lead first sentence. This is especially true for plants that are used for visual aesthetics, such as for flowers, landscape plants, etc. In certain specific instances, like for food plants, readers likely want to first know how food plants are used as food, and then appearance. If a plant has a high commercial use, that should be in the first sentence in the lead, which is for general information. The lead should also generally describe range and habitat, like "a North American desert plant that grows in sand dunes", with specificity in sections below.

Following the lead, in the more technical oriented sections below the lead, I am suggesting that the first two sections should be about distribution, habitat, and range, and then technical appearance, including growth pattern, leaves and stems (and roots), and inflorescence and fruit (seed). This is stuff more technical (and should use plain English, with technical nomenclature in parentheses) , but it is stuff that general readers can still read without much background knowledge, and is what is in books at the local store. I am suggesting moving distribution, range, habitat, to a section ahead of taxonomy, because the taxonomy section is something that requires more background knowledge than general readers likely have.

But you wrote, "the more articles I work on... the more I see why the order in the template makes sense". I defer to your experience on that.

Re "most sources... start from the bottom to the top, roots, stems, leaves, inflorescence, fruit." That is the most logical order, and it has parallels to each subject: growth, physiology, and moving from birth to reproducing. The advice "follow the approach used by standard Flora" in the template is also good (maybe tweaking this to "Flora or manual"). Floras differ from region to region in this ordering.
Re "but for families, genera, and species with significant infraspecific taxa, it doesn't really work." That is true. A reason for having distribution next to description for species in most cases, is that for general readers, that is often all they want. I am basing that on the fact that this is the way most plant books in a general bookstore have it, such as in field guides and slightly technical books that can still be read by non-experts. Its not that important, and the article template is only for general guidance anyway.
Re my bonehead waste of your time - I did not notice that you already restored most of my edits before I started writing all this.
The other changes I made that you did not already restore generalizes the sections and subsections I have been finding underly many articles already written. I was just trying to formalize that. -

Subsections might include "growth pattern", "stems and leaves (and maybe roots)", "inflorescence and fruit", or further subdivisions of these subsections. For example, "it is a branching perennial shrub that grows to 1 meter with a taproot. Stems are woody and covered with corky bark. Foul smelling leaves are opposite, compound pinnate, with hairy oval opposite leaflets having toothed edges. The inflorescence is a a corymb. Fragrant, radially symmetric flowers have five pointed green sepals and blue to violet petals fused into a tube flaring five lobes, with five anthers opposed to the petals. Pistils have three-parted styles. Ovaries are superior. Fruits have three dehiscent chambers filled with many black seeds."

The example should probably not be the one I made up from a chimerical plant that appeared in my mind as I typed, but instead be a clear and illustrative one from a "gold star" article (or whatever Wikipedians call their best articles). FloraWilde (talk) 02:42, 20 July 2014 (UTC)

I agree with Peter that a description section should come first, before distribution and habitat etc. Regarding FloraWilde's concerns, I wonder if some plant articles might appear 'too technical' at the start simply because their leads aren't sufficiently fleshed out to give a good general overview - I think this applies to quite a few plant articles. Also in some plant articles the taxonomy sections are far more detailed than any other section, giving an impression of technical impenetrability, but I think the solution to these situations is not necessarily to reorder sections, but to expand and rewrite information so that articles are more balanced and the text is easier for laypeople to understand. PaleCloudedWhite (talk) 18:55, 20 July 2014 (UTC)

I agree with PaleCloudedWhite. The distribution, at least, is likely to be more accessible to the lay reader because there's only so much you can do to make it impenetrable; but description, taxonomy, ecology and even habitat can all be rendered technically overwhelming pretty quickly. In theory, the lay reader should be able to read over the lead and come away with the kind of general information you might find in a field guide; in practice, Wikipedia in general has problems with poor lead construction. (It's probably partly due to the accretive way in which we write articles; when I write a new article, I tend to write the lead last, because I find I need to look over the completed article in order to write an orderly summary.) As it stands, the "Introduction" section of the template is very cursory; perhaps we could place more emphasis on this role, at the expense of repeating some of WP:LEAD.

BTW, welcome to Wikipedia, Flora. Your boldness in making useful changes to the article template and your graciousness when some of them have been disputed are both commendable. It's always nice to see someone else added to our little botanical community here, and I hope you have more ideas for making our articles better. Choess (talk) 14:28, 21 July 2014 (UTC)

I think making major changes to the order of sections at this stage would be disastrous, since it would literally require thousands of pages to be rewritten. As it is I revise several every day. I think a well written lead section gives the general reader all they they need to know and the following sections amplify this. --Michael Goodyear (talk) 00:06, 22 July 2014 (UTC)

Admin needed for move

A new user has moved Dracaena braunii to Dracaena braunii (Lucky Bamboo) thereby violating several principles of article titling. I've explained on their talk page, but could some admin please move it back. Thanks. Peter coxhead (talk) 07:04, 23 July 2014 (UTC)

He's also deleted half the article. Lavateraguy (talk) 07:53, 23 July 2014 (UTC)

I moved it back - I looked at what he's removed and some is (I think) right but (a) we're not a how-to manual and (b) some I think was possibly wrong, so I might leave it and have a hunt for sources before readding. Cas Liber (talk · contribs) 08:23, 23 July 2014 (UTC)

Inappropriate tagging

Single source

I have found several pages recently where lists of species have been tagged {{one source}} by an enthusiastic editor who does not realise that something like the Plant List or Checklist is the authoritative source. --Michael Goodyear (talk) 03:28, 22 July 2014 (UTC)

If you have a problem getting these tags removed, come here and I'm sure many of us will help. More common is the reverse: editors who don't understand the problems merge together lists from several sources so listing the same species under several synonyms. Quite what we can do about this, I don't know, other than the usual work of editing/maintaining plant articles. Peter coxhead (talk) 07:27, 22 July 2014 (UTC)

Michael Goodyear How can two places both be "the authoritative source?" Either one is, or the other, or neither, but not both. I vote for neither, as I have seen errors in both. More germane than being "authoritative" (a matter of opinion) is that these secondary sources represent compilations and distillations of information from thousands of different sources. Hence one Checklist citation is worth at least a dozen ordinary citations, if not hundreds. Joseph Laferriere (talk) 02:04, 24 July 2014 (UTC)

Plant field guides and manuals do not meet WP:MEDRS standards for reliability of medical information

Many authors of plant field guides are notable experts at plant identification. But they often add comments about traditional or alternative medicine uses, or exaggerate actual or potential medical use, often with an apparent end of furthering a conservation agenda by trying to find some reason other than just loving the plants for conservation of them. They are often not qualified to even read a proper medical study. Plant field guides and manuals do not meet WP:MEDRS standards for reliability of medical information. This should be stated in the template.FloraWilde (talk) 21:35, 20 July 2014 (UTC)

While I agree that this is true, it's also important in my view to report (without any hint of endorsement) traditional uses for plants. There have been some problems with over-enthusiastic WP:MEDRS-influenced editors trying to remove historical and ethnobotanical information of this kind. There is significant scholarly ethnobotany literature which can be used to support this kind of material. So I believe it's important a balance is struck. Peter coxhead (talk) 07:09, 21 July 2014 (UTC)

Exaggerating actual or potential medical uses would be a problem, but ethnobotany and traditional medicine are important areas of scholarship. Without the material studied by those disciplines, modern medicine would hardly exist, and neither would the hypotheses that medical trials aim to test, which come largely from traditional practices. I've seen the problem that Peter mentions, that WP:MEDRS enthusiasts expunge simple unproblematic statements or entire sections, but I hope that it is still rare. Literal and unthinking application of WP:MOS and various guidelines is, I believe, becoming a serious problem, and I would not be happy to see the proposed statement in the template. As Peter coxhead says, balance is needed. Sminthopsis84 (talk) 12:35, 21 July 2014 (UTC)

I see two countervailing tendencies, both of which are to be avoided. The first, as Sminthopsis mentions, is expurgation of ethnobotanical/folk medical information under the aegis of WP:MEDRS. This is a problem, because that information is useful in an anthropological, if not a medical, context. On the flip side, one often sees (even in the published literature!) a sort of WP:SYNTH problem: plant X is reported to have a traditional use, say, treatment of wounds. A crude extract of plant X, or some compound present in plant X, is found to have some kind of biological activity in vitro. The inference is implicitly or explicitly drawn that the in vitro findings ratify the traditional in vivo use. I think it might be appropriate to say something like "The use of plants to treat illness is traditional in most societies. However, most of these uses have not been scientifically validated. Unless the plant itself, or its extracts, has been reliably shown to be effective in treating illness, as defined by WP:MEDRS, it should not be described as medically effective, only as traditionally used in certain cultural contexts." Choess (talk) 14:04, 21 July 2014 (UTC)

I agree with Choess in that we try to keep to what the sources say and keep things circumscribed if at all possible. mention cultural/folk-use context and clarify that and avoid mentioning medical effectiveness unless there is a MEDRS doing so. Cas Liber (talk · contribs) 14:25, 21 July 2014 (UTC)

As an aside, but I think related: at a conference related to ethnopharmacology I was impressed by talks that discussed two things (1) that traditional medicine is the intellectual property of the cultures that developed it and must not be "stolen" by others for profit and (2) that traditional medicine needs to be documented so that the knowledge is still available. An example given was a cholera outbreak in Micronesia where western medicines ran out and people died, when the plants traditionally used to treat cholera were growing right outside the clinic but the young staff didn't have their grandparents' knowledge that would have made use of those plants. I don't know what in wikipedia prevents people from giving too much detail that is IP, such as the various ethnobotanical manuals that are being prepared around the world. Sminthopsis84 (talk) 15:01, 21 July 2014 (UTC)

I also agree with Choess. This is a frequent issue in plant articles, and one where it would be helpful for there to be some sort of guidance on how to approach things. Tdslk (talk) 19:14, 21 July 2014 (UTC)

Agreed with above comments as to use as sources for historical/anthropological/sociological material on traditional medicine belief systems. Not putting in historical uses of traditional medicine belief systems would be like leaving religion out of a history article. My point is that the way the wording often occurs in these field guides, they appear to endorse some kind of actual usefulness or efficacy, when there is none, or none has been proven.

If I understand what Choess said, it is exactly the example I was thinking of. A tribe rubs a plant on a wound. Some lab finds chemical in an extract from the plant which, if injected in sufficient concentration, has antibiotic efficacy. But rubbing the plant never reaches the level of concentration needed for minimal efficacy. The field guide only says in a mis-blending of two facts with values, "they use it to treat wounds and it has been found to have antibiotic properties, so we need conservation efforts in this beautiful area". The inference any reader would take from this both that it is useful to rub it on wounds, and that there is a pragmatic reason to conserve the area, other than just to preserve its aesthetic value. The chemical may be readily available without the plant, very expensive to obtain from the plant, and rubbing it on a wound does nothing. The Wikipedia editor has this as their source, and reads it just as any other reader would. Strictly following the source would violate MEDRS. FloraWilde (talk) 20:12, 21 July 2014 (UTC)

Yes, that's just what I was getting at. I think it would be reasonable to add something to my above notes for the template to the effect that field guides and the like may be reliable sources for ethnobotanical claims but not for medical claims, and that the latter should only be made on the basis of reliable secondary sources as described at MEDRS. (As a side note, ethnobotanical material is interesting not only because the medical claims it makes might bear scientific investigation, but because of the light it throws on cultural beliefs about plants. And yet the belief systems it illuminates--like the doctrine of signatures--may have mediated the plant's entry into the culture's pharmacopeia despite a lack of reliable empirical evidence!) As a crotchety biochemist, I think we should also be fairly selective about what lab results we report. There seems to be a perpetual flow of papers in obscure and local journals of biochemistry and the like showing that the crude extracts of [plant used in traditional medicine] kill bacteria or fungi or the authors' favorite cancer cell line in vitro. These results almost never have in vivo pharmacological applicability. There are probably enough exceptions to this that I wouldn't want to draft a broad rule banning them, but I think it should be legitimate to sweep out that sort of "extract did this in vitro" material unless there's a very compelling reason to keep it. Choess (talk) 03:26, 24 July 2014 (UTC)

Note - There is a related discussion at Wikipedia_talk:WikiProject_Plants/Template#Uses. FloraWilde (talk) 10:01, 22 July 2014 (UTC)

I think the key issue is to distinguish between traditional folk or cultural use, and actual pharmacological and clinical data - both have their place but need to be carefully distinguished. --Michael Goodyear (talk) 00:10, 22 July 2014 (UTC)

"English rose"

I've suggested a split of English rose (personal description) into a girl and a plant article. See talk:English rose (personal description). Is this plant concept significant? -- 65.94.169.222 (talk) 06:37, 1 August 2014 (UTC)

Wikipedia:Articles for deletion/Flora of the Sierra Nevada alpine zone

Wikipedia:Articles for deletion/Flora of the Sierra Nevada alpine zone. FloraWilde (talk) 02:27, 7 August 2014 (UTC)

Botanist template flagged for deletion

You may wish to comment at Wikipedia:Templates for discussion/Log/2014 August 7#Template:Botanist where it is proposed that the {{Botanist}} template is deleted. Peter coxhead (talk) 13:39, 7 August 2014 (UTC)

I think that would be a disaster. Final say should remain with this group. --Michael Goodyear (talk) 22:45, 8 August 2014 (UTC)

Dioscorea opposita

What should be done with Dioscorea opposita (see Talk:Dioscorea opposita#Nomenclature_is_all_mixed_up for some background)? I'm kind of confused by it, but what I think I understand follows. Nomenclaturally, D. opposita is an illegitimate and superfluous name for the south Asian (India) species Dioscorea oppositifolia (and thus a synonym of that species). However, the name Dioscorea opposita is widely used to refer to an east Asian (Japan, China, South Korea) species that is used as a vegetable and which is naturalized/invasive in the United States. The vegetable/invasive is apparently best treated as Dioscorea polystachya.

Most people searching for D. opposita are probably interested in the east Asian vegetable/invasive, not the Indian species. There would be less need to disambiguate incoming links to Dioscorea opposita if it redirects to D. polystachya. But that doesn't mesh with the nomenclature situation. Would it be better to redirect to D. polystachya or would it be better to make D. opposita into a disambiguation page, or is it best to redirect oppposita to oppositifolia as nomenclatural rules prescribe? Plantdrew (talk) 05:48, 28 July 2014 (UTC)

My view is that we're here to serve readers, not knowledgeable botanists/editors (although I don't always like the consequences of this view!). So I would redirect it to D. polystachya with a prominent explanation in the lead section that this plant is widely but incorrectly called D. opposita. (One reason for calling the R template "R from alternative scientific name" rather than e.g. "R from taxonomic synonym" is that there's no claim that the alternative name is a valid synonym.) Peter coxhead (talk) 06:40, 28 July 2014 (UTC)

Similar things have happened many times before, someone discovering that a name has been applied to the wrong plant for years. There is even a standard, technical way of writing it: "Quercus nigra auct. non L." to mean a misapplication of L's name to some species other than the real Quercus nigra. You can put "D. opposita auct. non ..." as a synonym in the taxobox section of D. polystachya. As for the redirect question, you can treat this "auct. non" name the way you would treat a legitimately published synonym, forwarding it directly the the D. polystachya page. And be sure to say prominently in the first paragraph "D. polystachya often misidentified as D. opposita" or something to that effect. That would work.Joseph Laferriere (talk) 02:03, 29 July 2014 (UTC)

I'd say that that sounds like the perfect solution. USDA GRIN can be cited to say that D. opposita auct. is D. polystachya. Sminthopsis84 (talk) 16:17, 31 July 2014 (UTC)

I've tried to explain some of this by removing the taxobox from the Dioscorea opposita page, and adding taxonomy sections there, on Dioscorea polystachya, and Dioscorea oppositifolia. I don't know whether these species are interchangeable as food and medicine, in particular whether Dioscorea oppositifolia is known by the various common names that were listed there and whether it can be safely eaten raw. For now, I've removed that material from Dioscorea oppositifolia. If anyone has that knowledge, please re-add the statements. Sminthopsis84 (talk) 14:15, 12 August 2014 (UTC)

Request for closure: Category:Drosera by synonymy and others

Please could an uninvolved person from this project close the discussion at Wikipedia:Categories for discussion/Log/2014 April 27#Category:Drosera by synonymy? If the closure is done by a non-admin and requires admin action to implement it, just ping me. – Fayenatic London 15:01, 14 August 2014 (UTC)

I don't think there's really been enough participation in this discussion by members of this project to reach a consensus. I've added my view; I'd like to see some views from others interested in the categorization of plant articles. Peter coxhead (talk) 19:24, 14 August 2014 (UTC)

Could the wording be improved?

A reader contacted the Wikimedia Foundation, noting that Leontopodium alpinum states it belongs to the sunflower family. while Leontopodium states it is in the daisy family,.

The implication being that one or the other is wrong.

I looked at Asteraceae, which suggest that the same family is known by both names.

I'm out of my depth, but would it make sense to have more harmonized wording. If one usage is more common, change one, or if both are quite common, refer to both?--S Philbrick (Talk) 15:29, 16 August 2014 (UTC)

This is a good example of the problems caused by using English names. Any of aster, daisy, composite or sunflower family is equally "right". A Google ngram suggests that since 2000 the use of "composite family" has dropped markedly, leaving "daisy family" and "sunflower family" about equally common. However, there's a marked ENGVAR difference: in British English, "daisy family" is much more common, whereas in American English, "sunflower family" is increasingly dominant. So it seems sensible to use both English names. I'll fix the two articles mentioned, but there must be many more. Peter coxhead (talk) 19:15, 16 August 2014 (UTC)

As an Australian, I think of daisy as the more natural term for the family, and think of a sunflower as a type of daisy (not vice versa)...just sayin' Cas Liber (talk · contribs) 21:39, 16 August 2014 (UTC)

"Aster family."Joseph Laferriere (talk) 09:31, 19 August 2014 (UTC)

Well, if I were choosing freely, then this would be my choice too. (Although the genus Aster has been so changed lately that most of the plants I think of as asters aren't now in this genus!) However, Wikipedia policies require us to reflect usage not impose it. I think "Asteraceae, the daisy or sunflower family" is the best compromise. Peter coxhead (talk) 09:58, 19 August 2014 (UTC)

Ok. Sounds good. Actually, the common term among botanists in the US is "DYC," short for "darned yellow composites." They are very difficult to tell apart sometimes. Me? I never saw anything wrong with "composites."Joseph Laferriere (talk) 10:12, 19 August 2014 (UTC)

Epacris impressa

..is at FAC..Wikipedia:Featured article candidates/Epacris impressa/archive1...and it's going pretty slowly. Would appreciate any input from folks....especially botanists..cheers, Cas Liber (talk · contribs) 06:05, 20 August 2014 (UTC)

please develop some botanical articles by me

i have put the photos of some bamboo species in their respective pages,Bambusa membranaceus,Bambusa multiplex var yellow,Bombus affinis,Bambusa oldhamii ,‎ Bambusa wamin ‎ ,Bambusa teris. ‎, Bambusa multiplex ‎ , ‎ Bambusa tulda please develop these pages. --Dvellakat (talk) 14:09, 15 August 2014 (UTC)

ok. Will do.Joseph Laferriere (talk) 09:30, 19 August 2014 (UTC)

Dvellakat A few problems. The names Bambusa teris, Bambusa multiplex var yellow, and Bambusa wamin do not apply to names accepted by the World Checklist. Bombus affinis is a bumblebee.Joseph Laferriere (talk) 11:07, 19 August 2014 (UTC)

teris may be an error for teres. I see nothing in IPNI for which wamin is a plausible orthographical error. (There is a Bambusa affinis.) Lavateraguy (talk) 09:51, 20 August 2014 (UTC)

10th anniversary of WikiProject Plants

Happy anniversary to all plant editors, past and present, and thanks for your improvement to plant articles and contributions to the many informative discussions here over 10 years.--Melburnian (talk) 13:55, 20 August 2014 (UTC)

AfC request for assistance from subject expert

Hello from AfC! Can someone please review the draft article located at Draft:Chloroplast migration, which is fairly technical, and check if it is original research or not, or if it makes sense? Thanks. Revent^talk 23:55, 22 August 2014 (UTC)

So how to we go about saying that is contains copyright violation from this web site? Sminthopsis84 (talk) 18:31, 26 August 2014 (UTC)

Image request for Aristolochia watsonii

Image request for Aristolochia watsonii. FloraWilde (talk) 01:02, 28 August 2014 (UTC)

Discrepency regarding Euphorbia and List of the largest genera of flowering plants

The Euphorbia Planetary Biodiversity Inventory project web page, last updated July 2012, says[2] -

"Euphorbia. With over 2000 accepted species, it is second in size only to the legume genus Astragalus among the flowering plants."

This is inconsistent with information in the List of the largest genera of flowering plants.

The Euphorbia PBI is "Supported by the Planetary Biodiversity Inventory (PBI) Program of the National Science Foundation", Smithsonian Institution, University of Michigan, and University of Florida, which is pretty good support as a reliable source. Can anyone resolve the inconsistency. Can anyone help resolve the inconsistency? FloraWilde (talk) 18:18, 30 August 2014 (UTC)

I am always unhappy with lists like those at List of the largest genera of flowering plants which combine information from sources of different ages, different reliability, and different standards and criteria. The only accurate statement would be something like "Based on the list of species in genus X accepted by SOURCE1 as of DATE1 and the list of species in genus Y accepted by SOURCE2 as of DATE2, X is a larger genus than Y." More than this is simply not meaningful. Peter coxhead (talk) 09:17, 31 August 2014 (UTC)

I agree with Peter. I purposely avoid trying to estimate the number of species in any genus. Two reasons: various authors will frequently disagree on which ones to recognize and where to draw generic boundaries, and, second, for many genera, perhaps the majority of genera, there are probably more species happily turning leaves toward the sun, never having been seen by any human botanists. So instead of saying "This genus has 53 species," I say "This genus has approximately 50-60 known species." The "known" is a disclaimer.Joseph Laferriere (talk) 18:49, 1 September 2014 (UTC)

Peter is correct as to being meaningful, and without implementing something like his operational definition-like language, the article may approach the opposite (i.e, get close to nonsense). The comment on "different standards and criteria" is an instantiation of the species problem, of which there is the same "genus problem". But I still like Wikipedia's various "extreme" lists - "List of the largest...", "List of the oldest...", "List of the strangest", etc., both for their entertainment value, and sometimes for edification. Peter's criticism on being meaningful generalizes beyond a list of genera, and beyond articles on plant topics. (Using Peter's qualifiers for a start), it would be helpful to suggest qualifiers in Wikipedia's "list of most..." articles generally - suggesting always to use "as of date D", "according to source S (and maybe commenting on the basis of its reliability)...", "judging by standard S...", "using criteria C...", "from the perspective of P...", "using definition D...", etc. Perhaps these suggestions can at least be added to the plant article template (or other appropriate place).

Joseph's qualifiers "known" and "approximately" should be suggested in the plant article template. Joseph's second point of expected shifting numbers because of yet-to-be-discovered species "never having been seen by any human botanist" (or by any human, for that matter), made me recall these recent words by botanists Kara A. Moore and James M. Andre (January 2014 Vol 42 No 1 issue of Fremontia Journal of California Native Plant Society, p. 8)</ref> (The context was talking about the unexplored bloom after rare heavy and long summer monsoon rains in the eastern Mojave Desert, when temperatures are so extreme that human survival is challenged just to sit in one place, let alone hike up and over a mountain) "... the California desert is indeed a major hotbed for taxonomic discovery... This resurgent golden age of discovery..." If you read the whole issue, you may feel the urge to experience this resurgent golden age and get out there next summer (and almost die, too).

Does anyone know any sources to establish notability of Allan A. Schoenherr?

Resolved

Allan A. Schoenherr wrote A Natural History of California. His book is a classic. A [Google Scholar search] produces many results. Does anyone know any sources to establish notability for a Wikipedia article on him, or on his book? FloraWilde (talk) 04:00, 3 September 2014 (UTC)

@FloraWilde: actually a lot of the results don't refer to Allan A. Schoenherr. If you do a better search in Google Scholar, namely author:"Allan A Schoenherr", you get only 15 results listing only 7 publications. So I'm not sure whether he is sufficiently notable. Peter coxhead (talk) 18:50, 3 September 2014 (UTC)

Thanks. It does look pretty weak in the publication department. I established notability with mainstream news sources as the area's go-to-guy "naturalist" on California natural history. FloraWilde (talk) 00:34, 4 September 2014 (UTC)

Changing digger pine -> gray pine in articles

Pinus sabiniana has various names, among them are "digger pine" and "gray pine". The problem with the usage of digger pine is two-fold. For one the term "digger" originated as a derogatory term for native Americans in the central California region around which Pinus sabiniana is distributed. To quote an historical interpreter for the California State Indian Museum in Sacramento:

To call a California Indian a `digger' means you are either ignorant or you are purposely trying to insult him. It is a very derisive word." These observers concur in the opinion that "the term digger is as offensive to California's Native Americans as the term 'nigger' is to African Americans." The terms "foothills pine" or "gray pine" are now officially preferred.

To see that the latter two terms are officially preferred is easily verifiable by visiting the webpages concerning Pinus sabiniana on any official website such as the USDA plant database.

The second problem is that of usage, which although I have only my own personal experience as well as Google results to support, I believe "gray pine" to be the most widely used common name. The relevant Google search counts are: digger pine = 35,300, gray pine = 42,700, grey pine = 96,500, foothill pine = 11,400. The reason I support the choice of gray over grey is because gray is the American spelling and the tree is American and I expect most articles mentioning the gray pine to be concerned with American ecology, although I'm not concerned with either one being used. I will await responses and if there are no objections I will start switching out mentions of "digger pine" to "gray pine".AioftheStorm (talk) 19:27, 3 September 2014 (UTC)

@AioftheStorm: um... Wikipedia doesn't censor, nor does it restrict itself to "officially preferred" names. So if by "switching out mentions" you mean "removing all mentions" this would be quite wrong. What exactly do you have in mind? Peter coxhead (talk) 19:33, 3 September 2014 (UTC)

What I have in mind is going to articles which mention "digger pine" and changing that mention to "gray pine", and my reasons are based both on not using a historic and offensive name, as well as using what I believe to be the most commonly used name.AioftheStorm (talk) 19:36, 3 September 2014 (UTC)

To add to this, I wouldn't be removing "digger pine" from lists of alternative names for Pinus Sabinia, I would just be switching out "digger pine" with "gray pine" where digger pine appears alone within an article.AioftheStorm (talk) 19:39, 3 September 2014 (UTC)

Since the combination "gray pine" + "grey pine" is almost 4x as common in Google searches as "digger pine", this would seem reasonable regardless of any offensive connotations, provided that, as you say, it still appears as an alternative name in the main article. Peter coxhead (talk) 20:05, 3 September 2014 (UTC)

Perhaps this doesn't affect what you are doing, but Pinus banksiana is called "grey pine" in eastern Canada. I've just added a (very old) citation, since I can't find a good recent one that reflects what people say. Sminthopsis84 (talk) 17:05, 4 September 2014 (UTC)

Interestingly Grey pine doesn't exist. Perhaps we should stick a hatnote on Pinus sabiniana telling them that "Gray pine redirects here, for the eastern Canadian tree see Pinus banksiana" and then create Grey pine and either make it a disambiguation page, a redirect to Pinus sabiniana, or a redirect to Pinus banksiana with a hatnote redirecting to Pinus sabiniana.AioftheStorm (talk) 04:43, 5 September 2014 (UTC)

That would be good. I hadn't got around to it; am vaguely wondering if there might be others that share these common names, or have a species epithet grayana and are pine-like but not Pinus. Haven't found any yet. There are too many "grey pine" flooring companies and hostels. Of course, there's the Icee Blue® Podocarpus with "lime-gray-blue" foliage! Sminthopsis84 (talk) 18:16, 5 September 2014 (UTC)

Discussion of a proposed Barnstar - For improving botany and plant related articles

There is a discussion of a proposed Barnstar - For improving botany and plant related articles here[3]. FloraWilde (talk) 18:58, 5 September 2014 (UTC)

Admin move request

Could an admin please move Lanariaceae to Lanaria in accordance with our policy on monotypic taxa? Thanks. Peter coxhead (talk) 21:35, 1 September 2014 (UTC)

Done. But perhaps we should upmerge Category:Lanariaceae and Category:Lanariaceae genera per WP:SMALLCAT? Rkitko ^(talk) 23:41, 1 September 2014 (UTC)

@Rkitko: Thanks for the move. Yes, I agree about upmerging. I've moved the articles up in the category hierarchy and marked both Category:Lanariaceae and Category:Lanariaceae genera with {{Db-c1}}. Could you delete them? Peter coxhead (talk) 08:52, 2 September 2014 (UTC)

Sure, consider it done. Rkitko ^(talk) 23:36, 5 September 2014 (UTC)

Admin move request (2)

According to the last paragraph of Wikipedia:Naming conventions (flora)#Monotypic taxa when a monospecific genus needs to be disambiguated, instead of creating the article at the disambiguated plant genus, it should be created at the species name. I've checked all of Category:Monotypic_plant_genera and the only case left is Stokesia (plant) which should be moved to Stokesia laevis. Peter coxhead (talk) 18:31, 3 September 2014 (UTC)

Done Rkitko ^(talk) 23:37, 5 September 2014 (UTC)

Request for comments: categorizing monotypic redirects

Arising from the move above (Lanariaceae to Lanaria), there's an issue about categorizing articles and redirects involving monotypic taxa. The project's current advice is here but only covers the "R" templates. The issue that concerns me is the main taxonomic categories. There seem to be three choices:

Categorize the single article on the monotypic taxon for each of the actual taxa covered in the article. Thus for Lanaria (only genus in family, only one species), the article would be categorized as the family article Lanariaceae, as the genus article Lanaria, and as the species article Lanaria lanata.
The argument for is that it's the article that should be categorized.
The argument against is that the category contents then look odd; e.g. a genus name will appear in a list otherwise of families.
Categorize the single article on the monotypic taxon only for the taxon used in the title. Thus for Lanaria, the article would be categorized only as a genus article. Categorize the redirects from higher or lower taxa appropriate to their rank. Thus the redirect at Lanariaceae would be categorized as a family article, the redirect at Lanaria lanata as a species article.
The argument for is that the category contents then contain taxa at the expected rank.
The argument against is that normally it's articles that get categorized in "proper" categories; redirects are categorized by their type via the "R" templates. Also there wouldn't be related sourcing for some of the categorization – Lanaria lanata was first described by Linnaeus in 1753 (as Hyacinthus lanatus) so should be in the Category:Plants described in 1753. Normally this information is sourced in the categorized article, but would only be done indirectly for the redirect.
Do both of (1) and (2), i.e. categorize the single article for each of the taxa covered in the article and categorize the redirects appropriate to their rank. This has the advantages and disadvantages of both (1) and (2).

I think we've discussed this before, but not added the conclusions to the project page (as often seems to happen). At present, we're somewhat inconsistent (at least I know I am).

Comments, please.

I plead guilty to being the person who created the Lanaria pages. I struggled with the decision of how to do this. Obviously, there needed to be three pages, with two of them redirected to the third. But which gets the actual info? I decided to put it on the familial page, with the generic and specific pages redirected. Apparently, I chose the wrong one. Mea culpa. As for categorization, sorry, but your explanation above is as clear as mud.Joseph Laferriere (talk) 10:04, 2 September 2014 (UTC)

It's an arbitrary choice, but the project decided to use genus page as the main one in such cases, so it's better to be consistent.
To give a specific example of the choices, one of the categories to be used somewhere is Category:Plants described in 1753 for the species Lanaria lanata. So where should this category be put? (1) On the article Lanaria? (2) On the redirect Lanaria lanata? (3) On both?
Does this example help? Peter coxhead (talk) 11:50, 2 September 2014 (UTC)

I did not realize that redirect pages could be put into categories.Joseph Laferriere (talk) 12:28, 2 September 2014 (UTC)

Peter, the previous discussion I'm aware of was at Wikipedia talk:WikiProject Tree of Life/Archive 33#Categorizing taxa vs. common names. At this point, sets of articles and redirects for monotypic plants (but not animals) are pretty consistently categorized following choice #2. Some people are unaware that redirects can be categorized, and others are generally opposed to categorizing redirects; indeed, the practice of categorizing redirects (aside from via the "R from/to" maintenance templates) is generally discouraged. However, the guideline at WP:INCOMPATIBLE suggests some situations where categorizing redirects is appropriate. The Lanaria article at the genus title is WP:INCOMPATIBLE with Category:Asparagales families and Category:Monogeneric plant families, but the Lanariaceae redirect is "compatible" with these categories.

And the related issue which kicked off the thread at Tree of Life was how to categorize redirects from scientific names to articles with a common name title. We have very few of these for plants. In the handful of cases where a plant article has a common name title, both the scientific name redirect and the common name article are usually categorized (i.e. the Allium sativum redirect and the Garlic article are both in Category:Plants described in 1753 and Category:Allium). I don't mind the duplicated categorization, but I'd probably argue that "garlic" was incompatible with Category:Allium if I had to pick only the species redirect or the article for the genus category.

"Described in year" categories are a whole other issue which I've complained about being problematic before. The status quo is that (were it not monotypic), a Lanaria lanata article would get placed in the described in 1753 category, not the Hyacinthus lanatus redirect. I don't particularly like that situation, but I can accept it. Putting the "described in year" category at the monotypic genus article just seems like a really bad idea though. "Described in year" categories are almost entirely species. If genera are getting a description date category, it should be a parallel set of year categories. It just seems super misleading to have Lanaria in "Category:Plants (species) described in 1753" and not a hypothetical Category:Plant genera described in 1789. Plantdrew (talk) 05:13, 3 September 2014 (UTC)

@Plantdrew: I agree that choice #2 is, on balance, best. I tried to present the choices as neutrally as possible above to encourage discussion. (My impression is that only a handful – if that! – of editors have any interest in categorization.) Pending this discussion, I left the approach to categorization at Lanaria as I found it. Peter coxhead (talk) 07:20, 3 September 2014 (UTC)

Geez. I try to do these things the way you good people want them done, but when you cannot agree... One thing I learned many, many years ago in the last century is that if you are designing a system that you want many people to use, keep it simple. Otherwise, you spend all your time explaining esoteric little details and losing the big picture. I look at pages other people have written and see major problems with some of them. The most common are people not knowing what the word "endemic" means or aiming their writing at people in their own narrow little field of expertise or their own small geographic area. I myself am much more interested in cleaning up those sorts of errors rather than in arguing formatting details.Joseph Laferriere (talk) 10:16, 3 September 2014 (UTC)

Actually Plantdrew and I do agree on categorization. I could just edit the project page to say what we think, but I was trying to get some more input first. Peter coxhead (talk) 10:51, 3 September 2014 (UTC)

Okay. You deal with that, and I'll deal with the page saying "This plant is endemic to South America. Its country of origin is Mexico." No, I did not make that up. One question concerning monotypic pages: What is to be done with specific synonyms? It is fine to put a category statement on a redirect page, but if we put the specific synonymy on a redirect page, nobody will ever see it. It needs to go on the generic page. But where? In the taxobox or in the text? My contention is that in the case of a monotypic genus, the generic name and the specific name are essentially synonyms of each otherJoseph Laferriere (talk) 13:05, 3 September 2014 (UTC)

At Lanaria I separated the list of synonyms in the taxobox into genus and species, which seems to me to work. Peter coxhead (talk) 17:02, 3 September 2014 (UTC)

As no-one seems to dissent (or be very interested!), I'm going to edit the project page to reflect (2) above, which is what mostly seem to happen currently. Revert if you don't agree! Peter coxhead (talk) 15:42, 5 September 2014 (UTC)

Just adding my support to the option preferred by you and Plantdrew. I agree with the description given in number 2 above and to the change made to the project page. I'm glad someone is keeping the project on task of recording the results of discussions somewhere! Rkitko ^(talk) 23:41, 5 September 2014 (UTC)

Input requested

at Talk:Acacia pycnantha regarding phytochemistry. An issue with alot of acacia pages I see. Cas Liber (talk · contribs) 02:48, 8 September 2014 (UTC)

geographic catorization

Here is an update on something we were discussing a few weeks ago. You may recall that we were discussing the use of geographic categories on plant pages. Policy is to use the highest-level category instead of listing all the more local categories, e.g. "Flora of Africa" instead of "Flora of Ghana" + "Flora of Togo' + "Flora of Benin" etc. I have been attempting to comply with those guidelines that were outlined here on this page. Problem is that I have received complaints about this, people reverting my changes to existing pages or sending me strongly worded emails. One person objected strongly to my deletion of "Flora of Lebanon" category from one page, despite that the plant discussed on that particular page does not grow in Lebanon.Joseph Laferriere (talk) 18:01, 7 September 2014 (UTC)

Ah, yes. A few years ago we had a persistent IP editor adding hundreds of plant articles to Category:Flora of Pakistan. A similar thing happened with Category:Flora of Lebanon -- there are editors who feel they have a certain amount of ownership of a category or set of articles. Perhaps it's best to ignore these complaints, but maybe the best thing to do would be to clarify our positions at Wikipedia:WikiProject Plants/Template#Categories and Wikipedia:WikiProject Plants/Categorization so that there is project consensus you could point other editors to when a conflict arises. That way discussion will be directed here instead of user talk pages. I tried my best in the intro of WP:PLANTS/WGSRPD to explain my understanding of the geographic categorization. Please modify it for clarity if it is needed. Rkitko ^(talk) 21:29, 7 September 2014 (UTC)

The problem is that "highest level category" is defined differently for different editors. An editor editing on Lebanon may think flora of Lebanon, mountains of Lebanon, climate of Lebanon, birds of Lebanon, etc., are subcategories of Natural History of Lebanon, and that Natural History of Lebanon and Political Parties of Lebanon, etc., are subcategories of Lebanon. An editor editing about plants may think that Flora of Lebanon is a subcategory of Flora of Eastern Mediterranean Countries, which is a subcategory of Flora. If the issue came up at the ProjectLebanon, there would likely be a consensus, as there would be at the ProjectPlant talk page. But the two consensuses would be different from each other. Categories are a non-hierarchical network ("reticulate"). FloraWilde (talk) 21:52, 7 September 2014 (UTC)

I don't think there's any chance of a conflict between various WikiProjects. Geographic categorization for flora is clearly going to be a hierarchy of smaller regions nested within larger regions. (Category:Flora of Lebanon is one of 12 countries or regions in Category:Flora of Western Asia.) Categories are not necessarily a strict tree, meaning that you can get to the same subcategory via different parent categories, but they are generally hierarchical -- WP:CAT says as much. Rkitko ^(talk) 22:51, 7 September 2014 (UTC)

I do not think that the problem here lies in categories on birds or mountains. We are discussing floral categories. Problem is that if a plant is found in every country from Portugal to Korea, it will have been put in the Flora of Lebanon category and in no other floral categories. No, that is not acceptable. Joseph Laferriere (talk) 22:52, 7 September 2014 (UTC)

Yes, WP:OVERCATEGORIZATION is still a problem. The same goes for Category:Flora of Delaware. It was placed on so many articles where the only other flora category was Category:Flora of North America because the taxon had a wide distribution. I reverted many of these but the task was so large that I gave up. What we need is an intuitive approach and clear directions repeated on this project page. Each category should then link to those instructions, transclude them, repeat them, or clearly define the circumscription. I tried doing this on some of the North American, African, European, and Asian category hierarchy, e.g. Category:Flora of the Northeastern United States, but it still needs work. Rkitko ^(talk) 23:02, 7 September 2014 (UTC)

I went through the Flora of Delaware category examining many of the pages listed there. I cleaned up as many as I could. The problem with the instruction pages is that many people do not read them. I see many pages with very major problems, people not even following basic tenets of grammar, sentence structure, logical organization, whatever, never mind the content difficulties. I try to clean things up when I can, but sometimes I cannot figure out what the authors are trying to say.Joseph Laferriere (talk) 23:45, 7 September 2014 (UTC)

I do remember seeing your work on cleaning up the Delaware category some time ago. Thanks for tackling that difficult and tedious job. While it can be frustrating to find sub-par articles below our standards, it's important to remember why Wikipedia was established to be edited by anyone and that it will always be a work in progress. So putting everything else aside, how can we best communicate our categorization goals? I suggested clearly and simply explaining the categorization normally applied to plants in one place that can be consulted, linked to, and used in discussions to justify and explain edits to others. There will always be new editors or those unfamiliar with plant article categorization and they will usually make a few mistakes, but a quick link to a project guideline and they will likely join the effort to sort it all out as long as our categorization schemes are reasonable. Many mundane and routine tasks can be bot- or script-assisted. So my questions would be: 1) Does consensus exist for following the WGSRPD? If yes, how far can or should we deviate from it and where will we make these decisions? N.B. I nominated Category:Flora of the Great Basin desert region as largely redundant to Category:Flora of the Southwestern United States but there has been little discussion as of yet. 2) Shall we develop appropriate guidelines for geographic categorization that mostly follow current ideal practices or do we need to re-examine our scheme? There appears to be some pushback against geographic categorization as a whole -- some editors cite WP:DEFINING, suggesting that being native to a country is not a defining attribute of the species. See Wikipedia:Categories for discussion/Log/2014 August 29#Category:Birds of Suriname for a current discussion with no participation. Earlier, all European fish categories by country were upmerged to "Fish of Europe" even though some had enough endemic species to exist on their own if the categories had been re-defined (see archived discussion here). And 3) Shall each flora geographic category contain an explanation or a brief circumscription and link to our newly created guideline? I suggest that tackling these questions as a project (not limited to just this list, of course) would help us on our way to curating the categories more effectively. Finally, we'd need to jettison many of the categories that overlap wholly and mostly with the WGSRPD. I had a recent discussion with an editor who prefers the parallel floristic kingdom category hierarchy -- should we have both (more categories on each plant article that largely overlap with one another) or should we just use one? Rkitko ^(talk) 01:05, 8 September 2014 (UTC)

@User:Joseph Laferriere, can you provide a link to the discussion you referred to as "those guidelines that were outlined here on this page"? Is there somewhere "highest-level category" was defined? @User:Rkitko, does "geographic category" mean political geography or a contiguous area with some shared environmental feature, as what might lead to creation of a plant community or vegetation type? In this case, a category like "flora of the Golan Heights", makes much more sense than "flora of Syria" or "flora of Israel". Similarly "Flora of the Great Basin desert region", Flora of the Sonoran Desert, Flora of the Mojave Desert, make sense. Putting the former two in a category defined by political boundaries is possible, since both are in the western US, but the latter crosses over international boundaries. Is there a place that defines a purpose or intended use of categories? FloraWilde (talk) 02:54, 8 September 2014 (UTC)

@FloraWilde: Your question is related to one of mine. The few folks who have participated in past discussions have seemed to embrace the World Geographical Scheme for Recording Plant Distributions. I have drafted our category structure at WP:PLANTS/WGSRPD. For the most part, it follows political boundaries, but you'll note that it doesn't make Greenland subordinate to Denmark, for example. This is done for practical reasons: plenty of sources exist that describe the flora native to regions confined to political boundaries (floras of countries, states, and provinces) while there are fewer resources, such as checklists, available for regions that cross borders such as those you mention. Further, places like the "Great Basin desert region" sometimes have ill-defined boundaries. More to the point, we already discuss and describe flora by their endemism, native or invasive status, and rarity by political boundaries. It is expected that an article will describe a taxon as rare in New Mexico, but wholly unexpected to find a sentence that indicates it is rare within the Sonoran Desert. "Flora of Syria" means more to the general reader than "Flora of Golan Heights". And finally, the WGSRPD is a good scheme to follow because we get to defend our choices against those who wish to see all categories upmerged to the continent scale by using a published system also used by GRIN and other references instead of trying to defend a system we hack together ourselves. And to answer your last question, WP:CAT is the good place to start for general category guidelines. Categories are for aiding navigation and browsing. They are not meant to duplicate list articles. If that doesn't sufficiently answer your questions, let me know and I'll take another stab. But once we settle those issues, I'd really like to get on to figuring out how to improve the system. Cheers, Rkitko ^(talk) 03:24, 8 September 2014 (UTC)

FloraWilde Just now, I scanned past postings for this subject but could not find it. It was a few weeks ago but I do not remember the exact date. Also, "Great Basin" does have definite boundaries and they are not synonymous with the region known as the Southwest, not even close. The Great Basin is a large region which drains neither into the Atlantic nor into the Pacific. Rivers in that area drain into inland salt lakes or else disappear in the desert. This is well to the north of The Southwest, which is drained mostly by the Rio Grande and the Rio Colorado.Joseph Laferriere (talk) 08:41, 8 September 2014 (UTC)

But the borders of the Great Basin are neither clearly marked on maps or familiar to the general reader. I did not suggest the two are synonymous, just that the Great Basin and Southwestern US categories largely overlap and thus a plant article placed in both would be unnecessary. I prefer sticking with WGSRPD geographic categories whose boundaries are more familiar. The other categories are also incompletely hierarchical -- that is, we have Category:Flora of the Sonoran Deserts and Category:Natural history of the Mojave Desert (acting largely as a flora category), which would both be in the Great Basin region, but what subcategory exists or would exist for areas within the Great Basin not included in those recognizable regions? With the WGSRPD, all land is accounted for in a way that is simple and familiar, aligning with books and other resources written on flora by political boundaries. I don't see why the choice isn't simple here. Rkitko ^(talk) 12:34, 8 September 2014 (UTC)

Okay. We discussed this at some length some time ago. There is some confusion over the purpose of the categories, which in turn should determine how they are designed. A biologist would likely prefer ecological boundaries, while a layperon would be more comfortable with political regions. But we are using secondary sources for Wikipedia, therefore the decision is pretty much made for us and we are stuck with the political scheme. I made the point some time ago that we should not only in categories but in the text avoid geographic terms that the reader is not going to be able to find on a map. A term as simple as "New England" or "Scandinavia" may be obvious to most of us, but imagine the reader in Kyrgyzstan trying to find them on a map. Never mind "Macaronesia" or "The Holarctic floristic province." Wikipedia is supposed to be educating people, not confusing the bejeebers out of them.Joseph Laferriere (talk) 14:00, 8 September 2014 (UTC)

Helianthemum squamatum

Hi All

I've started writing about Helianthemum squamatum, it's the only know species able to extract water of crystallization from rock. I know a little about plants but would really appreciate help in writing the article if anyone is interested.

Many thanks

--Mrjohncummings (talk) 16:05, 9 September 2014 (UTC)

Taxonomy categories

There are some plant categories with "taxonomy" in their name. For example Category:Taxonomy of Banksia which is placed in Category:Angiosperm taxonomy. These categories are for articles about taxonomy not for the taxonomy/classification itself. Thus we don't put Category:Asparagales into "Category:Taxonomy of monocots" but directly into Category:Monocots. I've been sorting out all the incorrectly used "taxonomy" categories that I've found, but if you come across any used incorrectly, please fix them. Peter coxhead (talk) 19:42, 9 September 2014 (UTC)

Comments sought on renaming Taxonomy of the Bambuseae

Please comment at Talk:Taxonomy of the Bambuseae. Thanks. Peter coxhead (talk) 09:22, 11 September 2014 (UTC)

Opopanax

Opinions are invited about recent changes on Opopanax, which in part involve a difference of opinion about how to treat the multiple plants historically used, in light of a statement that currently "all production" is from one species. A copyright issue has also surfaced. Sminthopsis84 (talk) 19:50, 12 September 2014 (UTC)

Proposal for Plant article template - Don't hide the family name

MOS says use plain English. But that does not mean we should not include the technical term after the plain English. I propose that the plant article template suggest stating a common name for the family in the lead sentence, followed by the scientific name in parentheses with a link, as here - Sarcodes. FloraWilde (talk) 15:57, 13 September 2014 (UTC)

I wouldn't "suggest", I would insist that if an English name for the family appears first, the scientific name must be given. In many cases different English names are used, often in different countries (see the discussion of the Asteraceae above), so they are not universally understood. Peter coxhead (talk) 18:47, 13 September 2014 (UTC)

Many taxa (famlies, genera, species etc.) have no common name at all.Joseph Laferriere (talk) 02:29, 14 September 2014 (UTC)

Araujia sericifera edit

Can anyone shed light on the veracity (or not) of this edit and its source? PaleCloudedWhite (talk) 22:04, 13 September 2014 (UTC)

It links to the Jepson Manual, which does use that spelling, and the Jepson Manual is a "reliable source". (Tropicos documents sericefera as another orthographic variant.) My first thought was that it was a mistake in the Jepson Manual, but if one goes back to Brotero's 1818 paper one finds that Brotero also used that spelling, so the Jepson Manual spelling may have been deliberate. That suggests that sericofera is a correctable spelling error under the IC(B)N. One needs a rules lawyer.

Wikipedia FR has a footnote which translates to "The original name given by Felix de Avellar Brotero was Araujia sericofera ; it was corrected Araujia sericifera the same year".

One might question the notability of orthographic variants. Lavateraguy (talk) 07:36, 14 September 2014 (UTC)

Thanks! I had also wondered if the Jepson Manual was in error, but my lack of knowledge on these matters is such that I wasn't even aware that orthographic variants are not just dismissed as wrong. It seems surprising; is it not the case that names are either documented as synonyms, or just not recognised? PaleCloudedWhite (talk) 07:54, 14 September 2014 (UTC)

Article 60.1 of the ICN says that "the original spelling of a name or epithet is to be retained, except for the correction of typographical or orthographical errors and the standardizations imposed by [list of ICN articles]." One of the standardizations which over-ride the original spelling is Recommendation 60G, namely that compounds formed from Latin roots should use "-i-" as the compounding vowel, whereas those formed from Greek roots should use "-o-". Since sericus (also sericeus) and -fera are of Latin origin, the correct form is sericifera and any other spelling should be corrected to this. The alternative spellings aren't synonyms (because they aren't possible names under the ICN) but orthographic variants. I'm not sure when this "correction provision" came in, but as the ICN applies retrospectively, names which once would have been acceptable with their original spelling now aren't.

As a newcomer to plant taxonomy and nomenclature, I find the vagaries of the ICN quite fascinating (which is doubtless some kind of negative comment on my personality!). I've had quite a few names corrected in WCSP and elsewhere, both changes from the original version (the latest being Rhodochiton atrosanguineus which was published as R. atrosanguineum, but the ICN requires genders to be corrected, and the Greek chiton is masculine) and changes back to the original version (e.g. Allium bigelovii was published as this, but has been written as Allium bigelowii, as it's named after Bigelow, and this form was previously used in WCSP; however the original isn't changeable under the ICN since it was based on the latinized Bigelovius). Peter coxhead (talk) 10:09, 14 September 2014 (UTC)

A few points: 1) So-called "authoritative sources" do make errors. The ICN exists to provide some way of solving dilemmas about which name or which spelling is correct. Imagine if authors could create as many orthographic variants as they want with no way to settle the arguments. 2) The question "Is this orthographic variant worthy of the status of formally recognized synonym?" is different from the question "Should we here at Wikipedia make note of such variant spellings in widely used sources and provide redirect pages to aid the reader in locating the appropriate information?"Joseph Laferriere (talk) 12:09, 14 September 2014 (UTC)

Absolutely – I'm all in favour of as many redirect pages as editors have the energy to create, and well-used orthographic variants, some of which are historically more common than the spelling currently regarded as correct, should certainly be listed in the taxobox under "Synonyms" (labelled as "orth. var.") and be redirects. Peter coxhead (talk) 16:24, 14 September 2014 (UTC)

Peter coxhead Certainly. I have been doing this for some time, except that I generally anglicise the "orth. var." to "spelling variation." No need to confuse people. "Nom. nud." I generally translate to "name published without description." Remember the motto: "Eschew obfuscation!"Joseph Laferriere (talk) 23:07, 14 September 2014 (UTC)

Where would we be if taxonomists eschewed obfuscation? A heretical idea, indeed! Peter coxhead (talk) 07:08, 15 September 2014 (UTC)

Are the expression "lichenized fungus" and "lichen" synonymous?

The answer may seem obvious at first, but reliable sources are not consistent. Please contribute to the discussion here. 23:46, 15 September 2014 (UTC)

Species identification

Does anyone know what is the plant species? --Yuriy Kvach (talk) 19:05, 13 September 2014 (UTC)

Were the images taken in a natural habitat? If so, where? What time of year? FloraWilde (talk) 22:45, 13 September 2014 (UTC)

Southern Ukraine, near the sea beach. All the images made at June 2014. --Yuriy Kvach (talk) 07:16, 14 September 2014 (UTC)

I made the description of each file in English. Thank you! --Yuriy Kvach (talk) 07:29, 14 September 2014 (UTC)

It seems to be Zygophyllum fabago. Sminthopsis84 (talk) 17:42, 14 September 2014 (UTC)

Thank You very much!--Yuriy Kvach (talk) 04:58, 18 September 2014 (UTC)

Acacia pycnantha

Australia's floral emblem is at FAC - Wikipedia:Featured article candidates/Acacia pycnantha/archive1 - any input from botanists would be welcome...cheers, Cas Liber (talk · contribs) 14:45, 14 September 2014 (UTC)

Pretty quiet there.....Cas Liber (talk · contribs) 03:03, 20 September 2014 (UTC)

Request for expert review of an edit re holobiont theory of lichens

Is there anyone anyone with expertise on the holobiont theory of lichens who can review this edit, and verify that I correctly summarized the content of the four cited sources? FloraWilde (talk) 19:15, 28 September 2014 (UTC)

Can anyone explain why reddish leaves might protect from intense solar radiation?

Resolved

I made this edit because it is what the RS said, "Many Sierra Nevada alpine plants have reddish or whitish leaves to protect them from damage from intense ultraviolet radiation in the alpine zone". It is plausible that if we could see UV, then UV-colored leaves would indicate protection from UV since it is reflected, but it is not clear why reddish leaves, or even whitish leaves, would. Can anyone explain why reddish leaves might protect from intense solar radiation? What about whitish leaves? FloraWilde (talk) 21:10, 29 September 2014 (UTC)

They protect from UV radiation by absorbing the UV radiation, rather than reflecting it. By absorbing the UV radiation, and transmitting the visible light, they prevent UV from reaching sensitive molecules like DNA, but allow visible light to reach molecules that use it for energy.AioftheStorm (talk) 22:04, 29 September 2014 (UTC)

Thanks, talk. I presume that the UV absorbing anthocyanins are what make these particular plants red, or that it carotenoids and betalains, they similarly absorb UV. I assumed whatever is in the white reflects, not absorbs UV, like the white leaf coating here, but after your answer, I am withholding that assumption, too. FloraWilde (talk) 00:18, 30 September 2014 (UTC)

Comment on the WikiProject X proposal

Hello there! As you may already know, most WikiProjects here on Wikipedia struggle to stay active after they've been founded. I believe there is a lot of potential for WikiProjects to facilitate collaboration across subject areas, so I have submitted a grant proposal with the Wikimedia Foundation for the "WikiProject X" project. WikiProject X will study what makes WikiProjects succeed in retaining editors and then design a prototype WikiProject system that will recruit contributors to WikiProjects and help them run effectively. Please review the proposal here and leave feedback. If you have any questions, you can ask on the proposal page or leave a message on my talk page. Thank you for your time! (Also, sorry about the posting mistake earlier. If someone already moved my message to the talk page, feel free to remove this posting.) Harej (talk) 22:47, 1 October 2014 (UTC)

A euphorb by any other name ...

I have stumbled across a vexing nomenclatural mess that I cannot solve using the on-line resources I have available. I am hoping someone with better literature as her/his disposal might be able to help. Problem concerns what the correct name is for a certain plant. WCSPF calls it "Aparisthmium cordatum." Tropicos, however, says that the genus name Aparisthmium is an illegitimate superfluous name. That means that the author who coined the name listed another name as synonym, thus voiding his own name. I do hope that he got paid for his work anyway. Tropicos says the plant should be in the genus Conceveibum A. Rich. ex A. Juss., and the species should be Conceveiba cordata A. Juss. But wait! Notice the different endings on these two genus names: "-bum" vs "-ba." There is another genus called Conceveiba Aubl. 1775, not the same thing as Conceveibum A.Rich. ex A.Juss. 1824. Are you confused? I am. What do I call this thing?Joseph Laferriere (talk) 22:30, 26 September 2014 (UTC)

I haven't had time to do all the digging, but an 1824 publication in Linnaea (see biodiversitylibrary.org) gives Conceveibum Bl. (not A.Rich.) as a synonym. IPNI ascribes Aparisthmium is Endl. (1840). My guess is that Endlicher validated an earlier name, and there's something wrong with Conceveibum Bl. (but there wasn't much time between Conceveibum A.Rich. and Aparisthmium Garcke & Schlect.) Lavateraguy (talk) 06:25, 27 September 2014 (UTC)

Thanx. The only explanation that makes any sense to me is that someone decided that Conceveibum was a spelling variation on the earlier Conceveiba. But I have not seen anyone say this.Joseph Laferriere (talk) 08:18, 27 September 2014 (UTC)

Ignore the comment about 1824 (should be 1826); I've been mislead by biodiversitylibrary.org - there seems to be an error in the date of publication column. The Linnaea paper is from 1856, and refers to Endlicher as well as Blume. Garcke and Schletchendal (Linnaea) refer to Blume, but Blume refers to A.Richard.

The source of the claim that Aparisthmium is illegitimate is here. Lavateraguy (talk) 18:51, 27 September 2014 (UTC)

Notice that in IPNI, "Conceveibum Rich. ex A.Juss., Euphorb. Gen. 42 (1824). [21 Feb 1824]" is the only occurrence of the genus name Conceveibum – there are no species names. On the other hand there's both a genus and a long list of species if you search for genus=Conceveiba. It does make it look as though "Conceveibum" could have been an orthographic error in a list of Euphorbiaceae genera. Peter coxhead (talk) 19:00, 27 September 2014 (UTC)

Thanx. Someone else sent me some files off-list that address the issue. I have not had time to examine them today but hope to get to them tomorrow. By the way, I found another error apparently made in 1820 and passed down ever since. This involves a South African plant citing a Mexican plant as basionym.Joseph Laferriere (talk) 02:05, 28 September 2014 (UTC)

Okay, very nice discussion of this at https://dl.dropboxusercontent.com/u/26033736/page%2082%20only.pdf . It all boils down to the question of whether the author who published the name Conceveibum in 1824 intended this as a variant spelling of Conceveiba or just happened to pick a similar name. So we need the services of a certain gentleman who travels in a blue British police box to go ask him. Or Aparisthmium can be declared a conserved name, which is what was proposed in this 1994 publication. Does anyone know the outcome of that proposal?Joseph Laferriere (talk) 18:01, 28 September 2014 (UTC)

I think the conservation proposal wasn't properly published; there is no listing for Aparisthmium at Proposals and Disposals. The authors may have thought they had done what was necessary, but it seems that without a publication in the journal Taxon, justifying the proposal, it would not have succeeded. 1994 was when the first set of guidelines about making such proposals was published, and perhaps the authors never saw that. Nicolson, D.H.; Greuter, W. (1994). "Guidelines for proposals to conserve or reject names". Taxon. 43 (1): 109–112.{{cite journal}}: CS1 maint: multiple names: authors list (link) says "When Taxon was initiated in 1951 it was, among other things, to provide a single place for (previously scattered) proposals of nomina conservanda. Yet so far no guidance on how to write such proposals has been provided, and although certain traditions have built up through the years the format and especially the length of proposals have greatly varied." Joseph, I would like to propose your name as a botanist who might like to undertake publishing such a proposal

. Such proposals are all about how disruptive it would be to horticulture and other industries to change the name of a plant, and perhaps sorting out wikipedia could count as a consideration nowadays. (You'd need the latest guidelines, which are here.) Sminthopsis84 (talk) 14:11, 30 September 2014 (UTC)

Sminthopsis84 Wow. I am honored by the suggestion. Let me think about it. I did make a proposal of that sort years ago. Problem now is that I no longer have access to an old-fashioned paper library, so I have to rely on what is on-line.Joseph Laferriere (talk) 02:00, 1 October 2014 (UTC)

Peter coxhead Sminthopsis84 - I am reminded of a short note I saw in a journal many years ago. It was by a prominent and respected botanist whom I would prefer not to name here. Title (TITLE!!!!) of the note was "How absurd can a taxonomic proposal get?" Another botanist had published a conservation/rejection proposal for a generic name. In his arguments, he made the statement "And, besides, if this proposal is not accepted, several recombinations will be required." (A recombination is a short state formally moving a taxon from one genus to another, or else changing its rank, e.g. from variety to species). This note by this prominent botanist went on at some length on how inappropriate it was to use that as justification for such a proposal. Then he said "So, if several recombination statements are required, here they are:" and proceeded to make the formal recombination statements right then and there.Joseph Laferriere (talk) 11:28, 3 October 2014 (UTC)

Yes, I've seen some conservation proposals that go to considerable lengths to demonstrate that it is the best way, that the number of new combinations required would be huge or that angry horticulturists would be brandishing those dangerous tools that they use in their trade. Another advantage of making new combinations rather than a conservation proposal is that the paper could be published just about anywhere, and wouldn't have to wait in the queue for Taxon, which gets rather clogged for a couple of years and then rapidly disgorges just before each International Botanical Congress. Sminthopsis84 (talk) 13:55, 3 October 2014 (UTC)

Question about redirect templates

On the project page are instructions about templates to include in redirects. Which include:

Pseudotsuga menziesii, which is a redirect to Douglas fir, contains the template {{R from scientific name|plant}}. (There should not be many such examples, since this WikiProject's guidelines say that a plant article should only exceptionally be at the English name.)

Since I'm not sure of the uses that these categorizations are put to, I don't know what to do about redirects for synonyms. Linum crepitans, Linum humile, and Linum indehiscens as synonyms of Linum usitatissimum could redirect to Flax, but it is a different situation from the Pseudotsuga menziesii example. Should redirects from these synonyms include the R from scientific name template? Sminthopsis84 (talk) 12:36, 2 October 2014 (UTC)

This is an example of one of the many problems created by using English names as article titles. In an ideal world, the synonyms would redirect to the accepted name which would redirect to the English name. But we can't have double redirects in Wikipedia. The usual approach seems to be to treat these as redirects from a scientific name (which they are), i.e. add {{R from scientific name|plant}}. I suppose there could, in principle, be another redirect template and associated category to deal with redirects from taxonomic synonyms to vernacular names, but I doubt that it's worthwhile. (I'm not really convinced of the need for the R templates in the first place – they seem to be a product of WP:WikiProject Redirect – but if the categories like Category:Redirects from scientific names are to be of any use to us here they need to be broken down by type of organism.) Peter coxhead (talk) 16:51, 2 October 2014 (UTC)

I wonder if it would be best to put in the redirects without a template, because there could be quite a lot of these, such as the various Medicago species that would redirect to Alfalfa. I'm guessing that it might not be helpful to have them clutter Category:Redirects from scientific names of plants if that list could be used in statements about how many plant species pages have a common name as a title. If we decide to omit the template, I'd like to note the decision on the project page, to prevent people becoming inspired to add the templates. Sminthopsis84 (talk) 14:10, 3 October 2014 (UTC)

My feeling on this is that in the case of an non-accepted taxonomic synonym, it should be redirected to the same place that the accepted synonym is redirected. But in the case of two or more accepted species having the same common name, each should have its own page, each with a link to the common name page, not a full redirect.Joseph Laferriere (talk) 16:31, 3 October 2014 (UTC)

@Sminthopsis84: my understanding – which may be wrong – is that WikiProject Redirect really wants all redirects put into "maintenance categories"; see the long list at Wikipedia:Template messages/Redirect pages. Certainly when I've not added an "R" template in the past, one has later appeared, although I haven't usually checked who added it and I try not to keep redirects on my watch list. I don't quite understand this bit of your comment: such as the various Medicago species that would redirect to Alfalfa. Only one accepted species name would redirect to alfalfa, surely? (Which is Joseph's point, I think.) Peter coxhead (talk) 17:38, 3 October 2014 (UTC)

Oh, what I meant was that Medicago sativa is at Alfalfa, but has synonyms Medicago afganica, Medicago alaschanica, Medicago asiatica subsp. sinensis … that could redirect to Alfalfa, and then the number of redirects that would inflate the category is not small, and I'm sure there are quite a lot more that could be found for the unalterably common-name-titled plant articles. Ideally, Alfalfa would be called Medicago sativa and the synonyms would be redirecting there, with the template {{R from alternative scientific name|plant}}. So perhaps we need a new template (I'm in the happy position of being able to state with a smile (

) that I am not a template editor). Sminthopsis84 (talk) 17:52, 3 October 2014 (UTC)

Ah, right. See further below. Peter coxhead (talk) 18:39, 3 October 2014 (UTC)

If I add another row to the table at Wikipedia:WikiProject_Plants#R templates for redirects not involving monotypic taxa, it perhaps clarifies the issue:

		To
		Accepted scientific name	English/vernacular name
From	Accepted scientific name	—	{{R from scientific name\|plant}}
	Alternative scientific name	{{R from alternative scientific name\|plant}}	{{R from alternative scientific name\|plant}} ? {{R from scientific name\|plant}} ?
	English/vernacular name	{{R to scientific name\|plant}}	(not relevant here)

Rather than use one of the two possible existing templates, there could be a new template in the shaded cell (it would have to be called something like "R from alternative scientific name to vernacular name" with a corresponding category), but would it be worthwhile? I'd like to see some more views on this. (It would also need to be put to other relevant WikiProjects; WP:WikiProject Tree of Life should be the forum but seems inactive at present.) Peter coxhead (talk) 18:39, 3 October 2014 (UTC)

As a very rough estimate of how many redirects would be involved, I looked at and counted the synonyms on:

Alfalfa 23

Flax 3

Fraser fir 4

Musk strawberry 1

Okra 9

Rusian knapweed 11

Just looking at these involved updating or adding most of the synonym lists, so a complete survey would involve adding a lot of synonyms without redirects, which I think is disruptive. This quick look convinced me not to proceed until I'm sure of whether and how to add redirects. Sminthopsis84 (talk) 19:31, 3 October 2014 (UTC)

I think I'm responsible for placing probably 90% of the redirects now found in Category:Redirects from scientific names of plants. It was very much my intention that the category should be able to function as a "list [which] could be used in statements about how many plant species [and genus] pages have a common name as a title" (I'm not so interested in the pages where a cultivar group or a hybrid has a common name for a title; clearly nobody is going to suggest that boysenberry should be titled with the scientific name Rubus ursinus × R. idaeus). I played around with a couple different ways of creating said list before arriving on the redirect templates. The most straight-forward way, directly categorizing the common name titled articles probably wouldn't fly; a category on "Maori names for plants" was deleted as it was about an aspect of the article title (apparently not appropriate for a category), rather than a defining characteristic of the article subject. That said, I really don't want to see the category cluttered with dozens of obscure synonyms for Medicago sativa. For the most part, Category:Redirects from scientific names of plants is now a comprehensive list of our common name titled species and genus pages (as the targets of the categorized redirects), although it does have a few hybrids, and a few cases where there are two redirects to the same common name whether because of monotypy or synonymy (I'm not too worried about having both Malus pumila and Malus domestica listed, as there is an outstanding conservation proposal for M. domestica; similarly, Lycopersicon esculentum continues to enjoy currency alongside Solanum lycopersicum as a scientific name for tomatoes).

There are another 48 redirects that I know of which should go into the category eventually (see User:Plantdrew/sandbox#Single_edit_scientific_name_redirects_not_categorized, but otherwise, Category:Redirects to scientific names of plants give us a very good handle on which articles have common name titles. There seem to be less than 400, out of more than 40,000+ plant articles. In spite of common name titles being 1% of the total, almost all of our highly viewed articles (Wikipedia:WikiProject_Plants/Popular_pages)are titled by common name. The presence of Salvia hispanica (#49 most viewed, in spite of the fact that the most likely search term, "chia" is a SIA) shows that readers can still find articles even with scientific name titles (and they're not scared off by our "elitist" use of scientific names). WP:FLORA works!

Getting back on topic, we either need another template for scientific synonyms redirecting to common names, or we could just skip categorizing them for now (with tens of thousands of uncategorized synonym redirects, there's no need to push for categorizing the handful that point to a common name, but I do realize there's no guarantee that somebody won't come along and categorize them anyway). Plantdrew (talk) 21:53, 3 October 2014 (UTC)

It's your last comment that bothers me. (I recently spent some time sorting out plant categories, only to have another editor come along with a different philosophy on categorization and effectively undo much of my work.) I'd prefer to have clearly documented guidance on what should in principle be done, even if no-one actually does it at present.

What would you call the template for alternative scientific names redirecting to vernacular names? (I suggest not using "common names"; this just provides ammunition for those who believe that scientific names aren't WP:COMMONNAMEs and that WP:NCFLORA is wrong.) Peter coxhead (talk) 22:10, 3 October 2014 (UTC)

Addendum: I see that {{R to vernacular name}} is available – {{R from vernacular name}} is a redirect to {{R to scientific name}} – but it's not a self-explanatory title and would be liable to be used for redirects from accepted scientific names to vernacular names. Peter coxhead (talk) 22:17, 3 October 2014 (UTC)

Would someone please explain the purpose of putting redirect pages into categories? Whom does this benefit? One problem is the sheer number of synonyms involved. Estimates of the number of species of flowing plants range from 250,000 to 400,000. Most of them have synonyms, usually only a few but for widespread plants sometimes several dozen. I am guessing here, but the total number of synonyms at the species level must be a few million. Many of these are old names that have not been used for centuries. I have adopted the habit myself that I shall create a redirect page for every generic name I come across, but not for specific names unless there seems to be a good likelihood that someone might search for the name on the internet.Joseph Laferriere (talk) 02:26, 4 October 2014 (UTC)

@Joseph Laferriere: you're making two different points here.

Should we have redirects for every synonym regardless of its usage? I think the clear answer is "no"; they are not of interest or value to readers of a general encyclopedia.
Why should those redirects that are created be categorized? My answer is that the categories are, as stated at Category:Redirects from scientific names of plants for example, purely for administrative purposes. They aren't intended for readers (who anyway will almost never see them since the redirect will automatically go to the target article). They are useful or potentially useful for members of this project. For example, we can check whether the use of vernacular names as article titles is in accord with WP:NCFLORA. Thus looking at Category:Redirects from scientific names of plants I was struck by Lawsonia (plant) which redirects to Henna. Should it? (Not to be discussed here!!)

Peter coxhead (talk) 09:23, 4 October 2014 (UTC)

Peter coxhead - Thanx. I concur.Joseph Laferriere (talk) 10:39, 4 October 2014 (UTC)

Replying to Peter coxhead: {{R to vernacular name}} could work perhaps. It's concise, but that also means it not precise. Just before I first replied on this thread, I moved a bunch of redirects that had been misplaced by a well-meaning editor from "Redirects from scientific names of plants" to the monotypic and alternative scientific name template categories. Redirects from/to monotypic taxa and taxonomic synonyms technically are "redirects from scientific names", but they aren't redirecting to vernacular names as {{R from scientific name}} describes. However well documented the use of redirect templates ends up, it is a complicated subject, and people will end up miscategorizing redirects.

Properly categorizing multiple synonymous scientific name redirects to vernacular names is a pretty trivial concern for plant editors; we have hardly any articles at vernacular names. If there is to be a template for this class of redirects, it will have much broader potential application for animals, which are more often titled by vernacular names. Maybe we should bring this up at Wikipedia talk:WikiProject Animals and Wikipedia talk:WikiProject Tree of Life? Plantdrew (talk) 05:43, 5 October 2014 (UTC)

Sure, although WikiProject Tree of Life posts don't seem to get much response at present. Peter coxhead (talk) 16:34, 5 October 2014 (UTC)

Brainstorming another possibility. This would be one to discuss at Wikipedia talk:WikiProject Redirect, and probably a complicated bit of work for a template editor. I wonder if there could be a pseudo-double redirect template. Maybe it would use a parameter to call another redirect template in a nested fashion, or maybe it would involve a parameter that is the preferred redirect target (as if double redirects to that target were allowed), or maybe it would inolve both parameters. The template could display a message on Medicago afganica something like "This is an [REDIRECT TEMPLATE FROM PARAMETER (in this case, alternative scientific name)] for [DOUBLE REDIRECT TITLE FROM PARAMETER (in this case, Medicago sativa)]". Details of the displayed message and template functionality would need refinement if this approach is worth pursuing.

This approach might have some use outside of organismal nomenclature. For example, lots of pop culture media franchises have the names of minor characters redirecting to a list article. If those characters have alternative names/nicknames, pseudo-double redirects might be useful. For example, Anikin Skywalker redirects to Darth Vader, but it's a misspelling of the redirect Anakin Skywalker. Tagging Anikin with "redirect from misspelling" would be misleading as Darth Vader is a totally different term, not the correct spelling. Plantdrew (talk) 18:16, 5 October 2014 (UTC)

If I understand correctly, your idea is that the target of the redirect should show, instead of "(Redirected from REDIRECT-NAME)" a more complex message. In principle this seems a good idea to me, but I'm pretty certain that the message that appears when a target is reached via a redirect is generated by the MediaWiki software; I don't know any way to alter this via the template language. So it would be an issue to be raised at a much higher level than the Redirect WikiProject. Peter coxhead (talk) 21:59, 5 October 2014 (UTC)

Oh gosh no. I'm really thinking of something that might be appropriate at the Redirect Project level, I guess I'm not just not very aware of which displayed messages come from which code. I'm looking for something where "Anikin Skywalker" could be tagged as a misspelling, while continuing to redirect to "Darth Vader", and "Medicago afganica" would be tagged as an alternative scientific name, but would redirect to "Alfalfa". We could make {{R from alternative scientific name to vernacular name}} and which would cover the concern of this thread, but it really seems like there's a broader issue with cases where MediaWiki's disallowal of double redirects makes the redirect categorization complicated. Category intersection templates like my previous redlink or {{R from misspellings of alternative names for fictional characters}} for Anikin are possible, but there are a massive amount of potnential permutations of category intersections. Perhaps some kind of master template could handle all permutations with what should be double redirects. I'll bring it over to WikiProject Redirect though. Plantdrew (talk)

Okay, wait until you hear this one. I just discovered a page with the common name as the name of the page. The author in the text gave a scientific name. S/he then said that this species was in a monotypic genus, then listed 8 synonymic scientific names. I did a search in the trusty World Checklist to make sure this was accurate. No. The genus is not monotypic, and most of the names he listed as synonyms were not synonyms of the name s/he was using. Yet s/he had made redirect pages directing the genus name and all the alleged synonyms to the common name page. Eeee, gads. I went through and unredirected everything.Joseph Laferriere (talk) 22:33, 5 October 2014 (UTC)

Please help write taxobox and fit article into plant article template, for the "genus with scare quotes" - Dendriscocaulon

Resolved

Please help adding a taxobox and with a WP:BOLD rewrite of the Dendriscocaulon article . FloraWilde (talk) 14:41, 17 September 2014 (UTC) Resolved per article talk page. Thanks. FloraWilde (talk) 02:07, 6 October 2014 (UTC)

Why is Caloplaca albovariegata called variegated ORANGE lichen?

Why is Caloplaca albovariegata commonly called variegated ORANGE lichen?[4] Is some commonly observable feature ever close to being orange? FloraWilde (talk) 23:22, 9 October 2014 (UTC)

It seems that "orange lichen" is the supposed "common" name for every species of Caloplaca; this is then the variegated species of Caloplaca. USDA PLANTS (http://plants.usda.gov/core/profile?symbol=CALOP7 see here) may be the original source of this "common" nomenclature on the internet. Plantdrew (talk) 01:16, 10 October 2014 (UTC)

Thanks. FloraWilde (talk) 12:57, 10 October 2014 (UTC)

Aldrovanda

Question for you good people. I found a genus page for Aldrovanda, which apparently has one living species and several long-extinct species known only from fossils. I placed it in a "monotypic" category as it has only one non-fossil species. Someone reverted this and deleted the category, saying it is not monotypic because of the existence of the fossil species. Who is correct about this? The way I see it, every genus on Earth has extinct species somewhere in the history of the planet, although only a few will have left any fossils good enough to identify. Such is the nature of how fossils are made. Joseph Laferriere (talk) 09:56, 10 October 2014 (UTC)

I have a feeling we've discussed this before, but I can't find it in the archives in a quick search. Personally if the other species are long-extinct I'd treat it as monotypic, i.e. interpret "monotypic" for our purposes to mean "has only one extant or recently extinct member". I've never been sure why we have so many categories for monotypic taxa in the first place, and the concept really makes no sense in paleobotany (is Aglaophyton monotypic because the only species described so far is A. major?). Peter coxhead (talk) 13:39, 10 October 2014 (UTC)

A quick clarification -- the category was not deleted, just removed from the page. I did that because, like Peter, I remembered seeing a discussion here about that but thought the conclusion was the opposite. Joseph may very well be correct that the presence of long extinct lineages that are unnamed make every taxon non-monotypic, thus requiring a different interpretation of the term. But here we actually have named extinct taxa. No editor has yet placed a monotypic category on the article for the genus Ginkgo. And yet again, the application of the term "monotypic" or "monospecific" may be temporary as even new extant species are discovered or the sole species is split apart. Rkitko ^(talk) 13:54, 10 October 2014 (UTC)

(edit conflict, and Rkitko brought up the example I was discussing) Peter, the discussion you're thinking of might have been on the Tree of Life page, here, but nothing really got resolved. I'm happy to call Ginkgo monotypic in spite of multiple fossil species (and if you google "ginkgo" and "monotypic", you'll see thaat plenty of other people use this definition of monotypy). As a reader browsing the monotypic category, I'd be interested in taxa with one living species, and I'd want to see Ginkgo included. As an editor, monotypic categories have a maintenance function, and I wouldn't want to see Ginkgo listed (it's split into separate genus and species articles with good reason). I'm not sure what the best resolution is. Plantdrew (talk) 14:03, 10 October 2014 (UTC)

Mea culpa re imprecise wording. I said "deleted the category" when I meant "deleted the category link from the page." Just trying to save a bit of time. The term "monotypic" is horribly inaccurate and misleading, as a genus may have only one recognized species yet have types for synonyms, subspecies, etc. But there is a difference between species known only from fossils vs those known from old herbarium specimens. I have seen numerous 19th-Century names of taxa not seen in the wild since they were described. Those I simply include in the species list with a dagger (†) in front of the name. The question of whether to include the name in the categories has nothing to do with the biology, everything to do with the question of the purpose of the categories.Joseph Laferriere (talk) 14:32, 10 October 2014 (UTC)

As an editor of fossil plant and insect taxa pages, I would fall into the category of editors that object to monotypic being used for taxa that have more then one described daughter taxa. The term monotypic is used in paleontology literature only when there is not a sister taxon, and rarely have I seen it used for a taxon simply if there is only one living taxon.--Kev min § 02:38, 11 October 2014 (UTC)

Kev Thanx. Please correct me if I am wrong, but the way I read your definition, it seems to exclude any daughter taxon with synonyms or granddaughter taxa. In other words, a genus with one species would not be monotypic if that one species had heterotypic synonyms or subspecies. Is that correct?Joseph Laferriere (talk) 18:42, 11 October 2014 (UTC)

Not responding for Kevmin, but it does raise the question of what precisely "monotypic" means. The Kew Plant Glossary says "(of genera) containing only one species ... (of family) containing only one genus", i.e. it seems to define "monotypic" to mean "with only one taxon at the principal rank immediately below". So a genus with only one species that has subspecies is monotypic because it is monospecific; a family with only one genus that has more than one species is monotypic because it is monogeneric. However I don't know if this is a universally accepted definition. Peter coxhead (talk) 19:34, 11 October 2014 (UTC)

Correct Peter, that is the definition as I have seen it in use. One taxon having only one immediate daughter taxon. For example, when first described Trochodendron was considered monotypic having only one species Trochodendron aralioides, with the description of multiple extinct species, such as †T. nastae and †T. drachuckii, the genus is not monotypic. Even so Trochodendraceae was still consisdered monotypic, only containing the one genus. With the description of two form genera, Nordenskioldia and Zizyphoides, plus the synonymizing of Tetracentraceae, the family is no longer monotypic, however the order Trochodendrales is still monotypic, with only one family. --Kev min § 20:03, 11 October 2014 (UTC)

Agree. The term appears in the code of nomenclature, but that is only because of a special case, when describing a genus and the only species it contains all at once, using a single description. The glossary states "monotypic genus: A genus for which a single binomial is validly published (Art. 38.6) (see also unispecific)." The code therefore is no guide to general usage, even though there would seem to be a connection to Type (biology). I believe that is because it is actually connected to the older meaning of type, meaning the circumscription of a taxon. I agree that monotypic means with only one daughter taxon, living or otherwise. Sminthopsis84 (talk) 21:50, 11 October 2014 (UTC)

Okay. Thanx for the clarification. Joseph Laferriere (talk) 08:31, 12 October 2014 (UTC)

Guava

Advice, please, on the Guava page. The genus name, Psidium, redirects to the common name page. It seems to me that the genus with taxonomic info and a list of species should be on a separate page. I can handle this, but I wanted to check with you good people to be sure that this should be done.Joseph Laferriere (talk) 12:02, 14 October 2014 (UTC)

agree - Psidium should not redirect to common name page guava. The hat note on the guava article says as much "this article is about the fruit", which implies it is not about the genus. Psidium should be its own separate page, with taxonomic info and a list of species, as well as other content standard to wiki articles on plant genera. FloraWilde (talk) 13:41, 14 October 2014 (UTC)

Thanx. That's what I figured, but I wanted to be sure. I'll take care of this right after lunch. Years ago in Colombia, I tasted guavas straight off the tree. Great stuff.Joseph Laferriere (talk) 14:41, 14 October 2014 (UTC)

So you're going for separate articles on Psidium and guava? Do check out Psidium guajava as well for content that might belong in the guava article. I'm not a big fan of having separate article on fruits and the plants that bear them, but it might be the best approach here. The problem is figuring out what content goes in what article. I.e., do cultivars of P. guajava belong in the article on the species, the article on the fruit, or in both articles? Plantdrew (talk) 16:14, 14 October 2014 (UTC)

Thanx for the suggestions. I just finished listing 96 species on the genus page, and need to take a short break before looking at the others. Apparently, P. guajava is not the only cultivated species, further complicating the matter. But the list of the 96 species certainly goes on the genus page.Joseph Laferriere (talk) 16:48, 14 October 2014 (UTC)

Can a "coalesced" lichen have multiple fungal genes in a single lichen "organism"?

Xanthoria is described as "irregularly coalescing". Are there cases here, or in other lichen species, where the "coalescing" involves fungi in the same species, but with different DNA, coexisting in a single lichen "organism"? (This is a different question from a that of a lichenized fungal species taking over the algae from another, e.g. "[Verrucaria bernardinensis is the pale-colored lichen. It is growing out of the brown lichen, Staurothele monicae. Verrucaria bernardinensis steals the green algae from the brown lichen."[5]) FloraWilde (talk) 15:52, 12 October 2014 (UTC)

Yes, this is the standard case of fungal reproduction I learned in school. The genetically distinct products of two different germinated spores come together and form the fruiting body. I either didn't learn about, or had forgotten about homothallic (as opposed to heterothallic) fungi, which are self-fertile. It seems that lichens can be either homo- or hetero-thallic, though I wouldn't be surprised if homothally is more common in lichens than in non-lichenized fungi. Plantdrew (talk) 23:28, 14 October 2014 (UTC)

Should link to genus be in the lead and article, or just in the taxo-box

There is often no link to the genus in plant articles, not in the lead, and not in the body. Conversely, there is almost always a link to the family in the first sentence. (If a user happens to know to look in the taxo-box, and there happens to be a taxo-box, that is the only place to find the genus link.) It is possible to put the link in the genus part of the bold faced binomial name, in the first sentence of the article. Other than producing bicolored binomial names, is there a good reason why this is almost never done? FloraWilde (talk) 22:54, 13 September 2014

This is covered in the guideline MOS:BOLDTITLE "Links should not be placed in the boldface reiteration of the title in the opening sentence of a lead". And I agree, it would be very distracting IMHO.--Melburnian (talk) 00:19, 14 September 2014 (UTC)

Also, promoting having a link to the genus in the first sentence may encourage non-informative and redundant constructions such as:

Fooia communis, also known as the common fooia, is a plant in the genus Fooia.

--Melburnian (talk) 01:25, 14 September 2014 (UTC)

I have seen very few plant pages without a taxobox, and when I do find one, I generally create one. It is very frequently the only place where a link to the genus page can be found, and I think this is entirely adequate. I do not need to go looking through the text to find the link to the genus page, because I know exactly where it is. A sentence such as "Zea mays is in the genus Zea" is stating the obvious. I would much prefer an opening sentence that actually says something.Joseph Laferriere (talk) 02:23, 14 September 2014 (UTC)

Indeed. Thus it's important to botanists where a taxon is placed, but usually of little importance to anyone else. I'm as guilty as anyone else of starting genus articles with information on the family placement, but I am now convinced that the first sentence should usually be descriptive. Peter coxhead (talk) 10:14, 14 September 2014 (UTC)

A few points: 1) So-called "authoritative sources" do make errors. The ICN exists to provide some way of solving dilemmas about which name or which spelling is correct. Imagine if authors could create as many orthographic variants as they want with no way to settle the arguments. 2) The question "Is this orthographic variant worthy of the status of formally recognized synonym?" is different from the question "Should we here at Wikipedia make note of such variant spellings in widely used sources and provide redirect pages to aid the reader in locating the appropriate information?" 3) Most amateur plant lovers do know what a genus is and that the first half of the so-called scientific name is in fact the genus name. Most do pay some attention to families, especially the larger and more distinctive ones such as grasses, palms, cacti, etc.Joseph Laferriere (talk) 12:16, 14 September 2014 (UTC)

"Fooia communis, also known as the common fooia, is a plant in the genus Fooia" is exactly how articles should start. It may be obvious to all of you, but won't be to many readers. Johnbod (talk) 00:20, 16 September 2014 (UTC)

But its only restating what's in the taxobox to the right and doesn't tell the reader anything specific about the plant.--Melburnian (talk) 01:38, 16 September 2014 (UTC)

Agreed. Further, a reader who doesn't know that Fooia communis is in the genus Fooia won't know what a genus is anyway, so will gain nothing by being told this in the first sentence. Whereas, "Fooia communis is a small tree with yellow flowers, native to south eastern Madagascar" says something informative to everyone. For a real example of a good opening sentence, how about "Hyacinthoides non-scripta ... is a bulbous perennial plant, found in Atlantic areas from north-western Spain to the British Isles, and also frequently used as a garden plant." For completeness I'd probably add "with spikes of blue flowers" after "perennial plant". Peter coxhead (talk) 08:33, 16 September 2014 (UTC)

Johnbod's sentence not only has content, it has essential content that should overtly be in the lead wording.
Peter coxhead's first comment above is also right on the mark, a lay-person-description is almost always best to start off with - what kind of plant (tree, shrub, perennial plant, etc.), gross appearance-to-lay-person growth form (low growing, tall, thorny, bushy), lay-person-notable colors (showy yellow flowers, whitish powdery leaves, red bark), and general range and habitat (country/region, mountain range/plains, rain forest/desert, etc.).
But family and genus should be overtly stated in the lead first paragraph, if not the first sentence, since it is also essential content for a large number of plant article readers. There should also be links to the terms "family" and "genus", so a reader unfamiliar with these terms, or who only vaguely recalls them from a long-ago biology class, can quickly get up to speed on them - "Fooia communis (common fooia) is a small, whitish-green tree with showy yellow flowers, that is found in moist, coastal-facing slopes of the western Wikiland mountain range. It is in the Fooia genus of the commoners family (Commonaceae)."
One problem with relying on taxo-boxes (other than that they might not be there at all) is that many casual encyclopedia users are "sentence and paragraph reader-types", who read the words and ignore all of the boxes and tabs appearing all over their screen (the left column Wiki box, the Wiki ad banner box at top, and the taxo-box at right until they know to look there, etc.
Proposal - Add to the plant article template that"

"The genus and family should be overtly stated in the lead first paragraph, with a link to both "genus" and "family", e.g., "It is in the Fooia genus of the commoners family (Commonaceae)."

.

For me, the family is acceptable, but the genus? No, sorry, I don't agree. Peter coxhead (talk) 18:40, 16 September 2014 (UTC)

Re: But its only restating what's in the taxobox: this is not a good reason to keep information out of the main text of the article. The taxobox should be a summary of the structured part of the information from the article; it should not be considered a replacement for that part of the article. —David Eppstein (talk) 19:00, 16 September 2014 (UTC)

Part of the purpose of the opening sentence is to reassure the reader that she or he has located the correct page. A sentence such as "Gardenia is a genus of plants" may seem simplistic and redundant, but it does serve the purpose of informing the reader of the fact that this is not a page on the marine crustacean named Gardenia nor the ancient Roman Province of Gardenia.Joseph Laferriere (talk) 21:20, 16 September 2014 (UTC)

Sure, a genus article needs to say that it's about a genus of plants, but that wasn't quite the point, I think. FloraWilde seems to have been asking about species articles; my reply was directed at these. I don't believe we should say that "X y is a species in the genus X". Peter coxhead (talk) 21:27, 16 September 2014 (UTC)

Yes, I was talking about species articles. At first I suggested linking to the genus from the title, but I changed my proposal after reading Johnbod's comment. Not only should the genus be stated in a species article, but the word "genus" itself should be in the article, with a link. And I fully agree with David Eppstein's comment. FloraWilde (talk) 22:11, 16 September 2014 (UTC)

I haven't created many plant articles (and none recently), but looking at a few (e.g. Rosa fedtschenkoana), I can see that I did state genus and family in the first sentence, my reason being that I was trying to pinpoint exactly what the article was describing. In fact, I often wrote "plant genus" or "plant family", in order to make it as clear as possible to lay readers. However, I remember I was never very happy with this construction, as it seemed inelegant and laboured, and I agree with Peter that it isn't the best approach; readers who are familiar with binomial names won't need to be told which genus a species is in, whereas readers who aren't familiar with them won't understand what a genus is anyway (and linking the terms genus and family in the first sentence could lead to excessively dense linking). Personally I favour Peter's approach of a descriptive first sentence; the taxonomy can be explained later in the article. PaleCloudedWhite (talk) 22:42, 16 September 2014 (UTC)

I don't want to prescribe any particular form of first sentence, but it should not be assumed that readers understand that the genus is part of the species name, nor should readers have to go to the infobox for any information that a general reader might want and that can easily be put in the text (as opposed to technical classification numbers etc). Johnbod (talk) 00:49, 17 September 2014 (UTC)

To clarify, I was objecting to mandating a genus link in the first sentence of a species article which was the opening proposition of this discussion, not precluding a link elsewhere in the article text.--Melburnian (talk) 01:37, 17 September 2014 (UTC)

Modified proposal -

"If possible, the lead first sentence should contain descriptive information in plain English that informs a general reader about the plant, e.g., growth form (tree, shrub, annual), size, flower colors, where it naturally grows, etc. Although stating what the genus is may seem redundant, given it is already in the article title, the genus and family should be overtly stated in the lead first paragraph, with a link to both the term "genus" and the term "family", so that readers unfamiliar with these concepts, or who may have learned them but do not readily recall what they learned, can quickly link to them - e.g., "It is in the Helianthus genus of the sunflower family (Asteraceae)."

. FloraWilde (talk) 03:05, 17 September 2014 (UTC)

Yes, I know that the focus was on species pages, but my previous comment applies to any sort of page.Joseph Laferriere (talk) 09:27, 17 September 2014 (UTC)

Clicking the note at the end of that statement clarifies that the restriction presumes a circular redirect. When the link goes to another page, the circular redundancy doesn't exist. If the link only uses part of the reiterated title, it is splitting the boldface reiteration between two colors that is cautioned against. HTML gives us a possible solution using <span> tags. Consider this example where only the genus is linked: Bambusa oldhamii. Perhaps this approach could quell the concern raised when a term requires only a partial link.—John Cline (talk) 07:55, 16 September 2014 (UTC)

Partial links which don't show up as links because the colour is changed to black are surely an extremely bad idea – how is the reader supposed to know there is a link? I'm always and everywhere strongly opposed to linking part of a binomial. (The worst is where the genus and specific epithet are separately linked, like this: [[Fooia]] [[Fooia barii|barii]] which you occasionally come across.) Peter coxhead (talk) 16:45, 21 September 2014 (UTC)

Agree with Peter coxhead as to no invisible black links, but give John Cline an "A" for HTML skills. Re my modified proposal, in trying to implement it, I found that it is going to take some getting used to, because it feels like redundancy or stating the obvious. But it is not, for those not already handy with "genus". FloraWilde (talk) 16:52, 21 September 2014 (UTC)

Like the modified proposal. Johnbod (talk) 14:07, 21 September 2014 (UTC)
Support the modified proposal, too. It's good to restate (and link to) WP:OBVIOUS information. WhatamIdoing (talk) 22:26, 15 October 2014 (UTC)

Masterwort move request

Please see Talk:Masterwort#Requested_moves to comment on a multiple move request. The vernacular names Masterwort, Spurge Olive and Milk Parsley may refer to multiple plants and it is proposed to move these articles to scientific name titles. Plantdrew (talk) 16:48, 21 October 2014 (UTC)

Great masterwort listed at Redirects for discussion

An editor has asked for a discussion to address the redirect Great masterwort. Please participate in the redirect discussion if you have not already done so. 67.70.35.44 (talk) 01:34, 22 October 2014 (UTC)

RSN Posting

There is a question about the reliability of a source regarding plants (www.plantvillage.com) on WP:RSN here, members of this wikiproject may be helpful with regards to their expertise in this area. Thanks! Yobol (talk) 20:18, 28 October 2014 (UTC)

generic synonyms

I have seen something on several pages that conflict with established botanical practice. The Asteraceae pages in particular seem riddled with this problem. I just thought I would make sure everyone is up to speed on this, so that you can recognize the error if you should come across it. I estimate that for me to go through the entire Asteraceae correcting this problem would take 14.3 years. Issue is generic synonyms. Let me say for example that we have a plant called Planta hypothetica. There are other species in the genus: P. realistica, P. hallucinogenica, P. somnia, etc. You decide that P. hypothetica does not belong in the genus Planta, so you create a monotypic genus Greenthingia. Thus the plant now becomes Greenthingia hypothetica. In creating a genus page for the genus Greenthingia, you list Planta as a synonym for Greenthingia on the grounds that the species now called Greenthingia hypothetica was formerly in Planta. No. This is bass-ackwards. To say that Planta is a synonym of Greenthingia is to say that Planta is no longer recognized as a distinct genus, and the type species of Planta is now included in Greenthingia. If you were to merge the two genera back together, so that the type of Greenthingia reverts to being in Planta, then Greenthingia gets listed as a synonym of Planta.Joseph Laferriere (talk) 12:54, 22 October 2014 (UTC)

Suppose I say that Planta pro parte is a synonym of Greenthingia. In my understanding of the taxonomic use of "pro parte" this means that part of Planta is synonymous with Greenthingia – in your example just one species, but it could be more (we could be a little more precise and say Planta pro minore parte). For a real example of this usage see here: Pectis pro parte is a synonym of Hydropectis because some species have been taken out of Pectis and placed in Hydropectis. So is the only problem that "pro parte" is missing? Of course we could say that pro parte synonyms should not be included (many databases do exclude them – e.g. this one). Peter coxhead (talk) 19:09, 22 October 2014 (UTC)

Peter coxhead That's the old-fashioned (i.e. 19th Century) way of doing it, from before they invited the concept of type species. The generic name follows the type species.Joseph Laferriere (talk) 20:35, 22 October 2014 (UTC)

Possibly a bot could be of assistance here. Look for instances where there is a genus article for a genus listed in a taxobox in a genus article as a synonym. Lavateraguy (talk) 20:42, 22 October 2014 (UTC)

That might work, if you can rig it so that the bot alerts a human to investigate but does not make any changes itself. There are thousands of homonyms lurking around that get listed in taxoboxes while their namesakes are recognized generaJoseph Laferriere (talk) 23:32, 22 October 2014 (UTC)

Plus there are articles on "historically recognized taxa" so the existence of a genus article does not show that it is an accepted genus. Peter coxhead (talk) 07:28, 23 October 2014 (UTC)

@Joseph Laferriere: in your response to me above you inadvertently illustrate my underlying point. There's no such thing as a "type species" in the ICN; the term appears nowhere in the Code. The type of a genus is the type of the species (see Article 10). Nevertheless the term "type species" is widely used by botanists (and indeed is used in some taxoboxes). Similarly "pro parte" synonyms are not defined in the Code, but nevertheless the term is still in use, old-fashioned or not. (For species it's very easy to find lists including p.p. synonyms; here is one from a source I've used in Wikipedia articles.) So for me the question is why the one is acceptable but not the other; it can't be a simple question of the terminology used in the Code.
By the way, presumably Synonym (taxonomy)#Other usage is wrong in your view? Peter coxhead (talk) 07:31, 23 October 2014 (UTC)

Just now, I reread Article 7 of the ICN. You are correct that the phrase "type species" does not occur there, but only because they generalize the wording so that it covers taxa at every level. It does say "A nomenclatural type (typus) is that element to which the name of a taxon is permanently attached." Question for us here is not what the ICN says or what 21st-Century botanists do, but how we should handle this on Wikipedia. Certainly it is appropriate to inform the reader that the species contained in one genus were formerly called by some other name. But simply listing the old name in the taxobox without qualifications is misleading. If you want to use the "pro parte" option, fine.Joseph Laferriere (talk) 10:59, 23 October 2014 (UTC)

Re your comments on "type species" and Article 7.2, see "element" in the Glossary. This appears to support the concept of a "type species" since "element" is said to be "applied to a species name considered as the full equivalent of its type for the purposes of designation or citation of the type of a name of a genus", but it then cites 10.1 which, as I pointed out above, says something different. What this shows, I think, is that the Code is confusing (if not confused).

I'm not personally pushing for the use of "pro parte" synonyms. I haven't added them to articles I've created or substantially edited (so far as I recall). I'd probably agree that (normally) they shouldn't appear in taxoboxes. If they do, I certainly agree that "pro parte" (or "p.p." with a wikilink) is essential.

What we definitely should do is to add something about "pro parte" synonyms to the project page at WP:Plants#"Synonyms" of scientific names. We're very good in this project at discussing issues on this talk page and not recording a decision to guide us in the future. Peter coxhead (talk) 18:17, 23 October 2014 (UTC)

Certainly the ICN is confusing. Such would be true of any rule book written by committee then revised by another committee, then revised again by yet another committee ... My preference on this "pro parte" problem is to leave it out of the taxobox entirely. In the text, you can say "This was formerly considered part of a certain other genus," if and only if the name was done so recently that people are still using books containing the old names. The other problem with "pro parte" is that it is Latin, which many people cannot read. That is especially true on this side of "The Pond." "In part" works fine.Joseph Laferriere (talk) 22:11, 23 October 2014 (UTC)

Any thoughts on what to do with redirects for synonymized genera that were monotypic? Hermodactylus is now treated as a synonym of Iris, but if somebody is searching for Hermodactylus, they'll find more relevant information at Iris tuberosa than at Iris (plant). Should Hermodactylus redirect to the genus or the species? Plantdrew (talk) 18:46, 29 October 2014 (UTC)

To the species, it seems to me – this is where the information is. Peter coxhead (talk) 20:01, 29 October 2014 (UTC)

In general, I would agree, but some of those irises, such as Hermodactyloides are very tangled, so I think it could be a challenge to work out which ones are monotypic. Sminthopsis84 (talk) 23:19, 30 October 2014 (UTC)

Nonsexual speciation

Does anyone know any sources discussing the mechanism of for "Some lichens have lost the ability to reproduce sexually, yet continue to speciate"[6]? FloraWilde (talk) 12:50, 31 October 2014 (UTC)

It doesn't focus on the mechanisms, but this provides a case for speciation within an asexual Lepraria clade. Note the parallel with the asexual bdelloid rotifers. Lavateraguy (talk) 15:54, 31 October 2014 (UTC)

There is a more recent study but it's paywalled. Lavateraguy (talk) 16:08, 31 October 2014 (UTC)

Plants have the same problem. Many of them reproduce asexually yet continue to evolve. As to whether or not these new forms should be called species depends on your definition of the word.Joseph Laferriere (talk) 10:31, 1 November 2014 (UTC)

"प्रत्यक्श्रेणी-tʃən", and other such material found in our plant articles

Many of our English language plant articles start of with characters that few English speakers have ever seen. "प्रत्यक्श्रेणी-tʃən" is a combination of the characters found at the beginning of two articles, Jatropha curcas and lichen. (All I learned in college was that "ʃ" is read "integral of", and "ə" is read "such that", otherwise the symbols are unintelligible to me.) There seems to be a consensus to include such characters in all articles at Wiki, by good-faith special-universal-character-pronunciation-technocrats at the Wiki-pronunciation division of MOS. Few at Wiki:PLANT likely ever participated in forming this consensus. That consensus is inconsistent with the more basic consensus at MOS to use plain English, and is inconsistent with Wikipedia being accessible to English language speakers. I propose adding to the plant article templete:

"Any non-standard characters, such as for pronunciation, should not appear in the lead, so that the lead is accessible to general readers."

FloraWilde (talk) 15:46, 1 November 2014 (UTC)

Pronunciation is a problem for a lot of people, especially in a language with as confused and unphonetic an orthography as English has. Giving the obvious ones seems a straightforward thing to do. They should be in a coherent style and should be well referenced (how do you pronounce lichen? I say something akin to 'likken', not included in the article). I'm sure you realise that "ʃ" and "ə" are phonetic symbols here. My Concise Oxford English dictionary indicates pronunciation by including various obscure superscripts over or after the characters. This is never part of the word in actual use, and the user needs to ignore these when finding the word. I imagine many users will find these essential. I agree there is no reason to include names in other languages in the lead without good reason, which there does not seem to be for Jatropha. Imc (talk) 13:35, 1 November 2014 (UTC)

@Imc: pronouncing "lichen" as /ˈlɪkən/ is interesting (to me anyway!). I wonder if it's a pronunciation shared by others – I haven't yet found it in a dictionary. If it can be sourced it should, of course, be added to the article. Peter coxhead (talk) 23:23, 1 November 2014 (UTC)

Interesting, Jatropha has "The name is derived from the Greek words ἰατρός (iatros), meaning "physician," and τροφή (trophe), meaning "nutrition,"", and I've recently seen the Greek letters being added to various pages. Perhaps the solution in that sort of situation is to move etymology out of the lead to a special section. Sminthopsis84 (talk) 16:59, 1 November 2014 (UTC)

There are two issues here: pronunciation guides and common names of species in other languages. I see no problem with the pronunciation guides as found in lichen, but the foreign language common names are a different beast. The foreign language common names are arguably useful and important, but probably should not be in the first sentence of an article, as is the case with Jatropha curcas. We also have to ask ourselves how important is that foreign language name -- is the plant native to that area? Mimosa pudica is constantly picking up new foreign language names in the article because of its status as a worldwide weed, but I usually revert them as it's not the purpose of en.wiki to chronicle all 20 foreign language common names it has been given; that's what interwiki links are for. Rkitko ^(talk) 22:01, 1 November 2014 (UTC)

I agree entirely with Rkitko; these are two quite distinct issues. (1) Rightly or wrongly (rightly in my view) the use of the IPA is specifically mandated at MOS:IPA so it is required to be used if pronunciation is to be given. There is no better way of indicating pronunciation – re-spelling only works for speakers of the same dialect so is not helpful in an international encyclopedia. The obvious place to give the pronunciation of the article's title is at the start, just as a dictionary would. (2) There's a long list of non-English names towards the end of Jatropha curcas – there's absolutely no reason for a name written in Devanagari to appear at the very start of the article and I've removed it. Peter coxhead (talk) 23:23, 1 November 2014 (UTC)

If you are discussing the pronunciation of scientific names, there is no standard. How you pronounce it depends on who taught you how to pronounce it. Americans tend to anglicize the names, Mexicans hispanicize them, etc. And I have never heard anyone from any country pronounce the so-called Latin names the way that Pliny the Elder would have pronounced them.Joseph Laferriere (talk) 06:31, 2 November 2014 (UTC)

Aconitum

Because of a story in the UK news, a number of editors are adding "toxicology" material to this page based on something speculative said during an inquest. I've been reverting but more expert eyes/views would help, as always ... Alexbrn ^{talk|contribs|COI} 14:29, 7 November 2014 (UTC)

Agree. FloraWilde (talk) 20:25, 7 November 2014 (UTC)

User:Zigzig20s/Petit Gulf cotton

Hello. Is anyone here interested in helping me create a page about Petit Gulf cotton? I have started a userpage. I think this could easily become a start, but I am not an expert at all. It seems very historically significant. Thank you.Zigzig20s (talk) 08:54, 8 November 2014 (UTC)

There's some juicy bits on this in this ref, download the PDF from Stanford Univ. HalfGig talk 17:48, 8 November 2014 (UTC)

There's some stuff in JSTOR too. Do you have access? HalfGig talk 17:51, 8 November 2014 (UTC)

I don't, unfortunately.Zigzig20s (talk) 18:13, 8 November 2014 (UTC)

Btw, the Stanford PDF says, "Please do not cite without permission."Zigzig20s (talk) 18:15, 8 November 2014 (UTC)

If you have access to Jstor though, feel free to expand it. Thank you.Zigzig20s (talk) 03:31, 9 November 2014 (UTC)

You could read the Rhode article for background. I've discovered this: Wikipedia:WikiProject Resource Exchange/Resource Request, where you can request articles you don't have access to. I don't have full JSTOR access but I can tell you that these articles may help you, you can request them at the Resource Exchange link: Cotton Breeding in the Old South, Agricultural Price Control in Pioneer Utah (less likely but it came up in a search). Hope it helps. HalfGig talk 13:15, 9 November 2014 (UTC)

Monocot article

Plant articles on Wikipedia have been upgraded to the latest in evolutionary knowledge except for one of the most important articles. Plants that were once considered dicotyledons link to families, orders, and appropriate unranked clades from APG3, but plants that were considered monocotyledons link to an article about the old concept monocotyledon (as the other half of "monocots and dicots") instead of to the monocot clade. There are articles based on APG3 about all of the unranked clades, except for the monocot clade. Why is such a major clade reduced to its old concept? Even if the morphologies and many of the relationships are sound, compared to the dissolution of the dicots, there should be an article on every unranked APG3 clade. The text of the article that appears in my cell phone includes only one line about the monocot clade, "The APG III system recognises a clade called "monocots" but does not assign it to a taxonomic rank." The full article compares APG3 and other systems, after more interesting information like, "The name monocotyledons is derived from the traditional botanical name "Monocotyledones," and "From a diagnostic point of view the number of cotyledons is neither a particularly useful (as they are only present for a very short period in a plant's life), nor completely reliable characteristic."

This article is very bad. It is hard to improve it because there should be an article about the monocot clade, which this article is attempting to be after a bad start as the monocotyledons article. This is not about that monocotyledons are monocots; it's about helping someone who can't make sense of the monocot clade from this article. — Preceding unsigned comment added by 50.250.153.211 (talk) 03:34, 2 November 2014 (UTC)

Well, it is a poor article, I agree. This edit way back in March 2011 added material apparently automatically translated from the Spanish article which has never since been properly copy-edited or had its references sorted out.

On the other hand, unlike dicots, historical monocots and modern monocots are the same taxon, so the content is actually not way out. Peter coxhead (talk) 20:41, 7 November 2014 (UTC)

Is that a dismissal? The other references I looked at had this information and an article about the clade, not the historical concept for one clade and the apg clades for the others like Wikipedia. It is like you rewrote modern science out of old books for one article, a very important article, and used modern sources for the rest. 50.250.153.211 (talk) 04:25, 9 November 2014 (UTC)

It's not a "dismissal" – we agree it's a poor article. My point was simply that molecular phylogenetics has upheld the monocots as a natural group, which it hasn't for the historical dicots, so information like circumscription is essentially still correct. Peter coxhead (talk) 07:54, 9 November 2014 (UTC)

I am not expressing myself well. I know this. I found this out by going to the Missouri Botanical Garden's website.

From Wikipedia I learned: "The APG III system recognises a clade called "monocots" but does not assign it to a taxonomic rank."

And that "The name monocotyledons is derived from the traditional botanical name "Monocotyledones", which derives from the fact that most members of this group have one cotyledon, or embryonic leaf, in their seeds. In contrast, the traditional dicotyledons typically have two cotyledons. From a diagnostic point of view the number of cotyledons is neither a particularly useful (as they are only present for a very short period in a plant's life), nor completely reliable characteristic."

I was searching for information on apg clades, a major area of knowledge that seemed modern and appropriate for an up to date encyclopedia.There is an apg cladogram on Wikipedia, somewhere. You could link all the clades to articles. Except for the monocots, because the "circumscription is essentially still correct for monocotyledons", so why bother, so Wikipedia ignores the monocot clade. It does not address Wikipedia ignoring a major article while having an article on half of an outdated concept (monocots and dicots) because the monocots were circumscribed well, mostly. It does not address the uselessness of this article when someone wants to know about the monocots clade mentioned in all this apg material and in every monocot article on Wikipedia.

I hoped my last sentence in my ip would make it clear I already knew this, so I could find a way to deal with the problem instead of hearing that it does not matter because smart people already know. Many things that I already know are found in encyclopedia articles. 75.171.247.94 (talk) 07:03, 10 November 2014 (UTC)

Hardy palms article changed to "List of hardy palms"

This makes no sense. When and why did the Hardy Palms article become "List of hardy Palms"? The article is quite a bit more than just a list: http://wiki.riteme.site/wiki/List_of_hardy_palms 173.73.232.183 (talk) 00:25, 10 November 2014 (UTC)

It was moved on 3rd January 2014 (see article history). Lavateraguy (talk) 07:38, 10 November 2014 (UTC)

Request for review of lichen genus article style and format

I am starting to fill out the articles on lichen genera, from A-Z, then on species within the genera. The plant template does not quite fit when it comes to lichens. Also, I am finding variations from article to article on the format for lichen genera aricles, e.g., on lists of species being partial "selected" lists in the article body, being collapsed lists in the article body, being collapsed lists entirely contained in the taxobox and not the article body, and being their own articled that is linked from the genus article. I just did some work on Acarospora. I would appreciate it if someone could review it and make suggestions or comments for improvements, then I will use the resulting formatting and style for other lichen genus articles. (I already know one improvement is to use more sources, which I will do, especially dispositive sources on the genus. FloraWilde (talk) 20:08, 8 November 2014 (UTC)

Well, the lichen articles aren't within the scope of this project, so there's no reason they should follow our template. However, WP:WikiProject Fungi seems pretty inactive at present, so maybe it is sensible to ask here, although you should certainly also ask there. I note that the Fungi project page suggests Psilocybe as one of its "template" examples – it seems to follow the Plants template fairly well, except for discussing species at the end, which I think is quite wrong. The Distribution and habitat section is bound to require some mention of species. In most cases the biochemistry and pharmacology will also require information at the level of species. The history, uses and ethnography certainly do. So Taxonomy, including subdivisions of taxa, belongs before these other sections.

Collapsed lists are controversial; I've noticed experienced editors (Stemonitis is one) uncollapsing them on the grounds that information shouldn't be hidden from users. If they are present, then I think they should be the exception, not the rule.

Finally, I'd strongly suggest looking at some of the WikiProject Fungi Featured Articles. Peter coxhead (talk) 23:08, 8 November 2014 (UTC)

Thanks, Peter coxhead. I posted the same notice on the WP:WikiProject Fungi talk page. I will make a habit of looking at featured articles there, and elsewhere. FloraWilde (talk) 23:21, 8 November 2014 (UTC)

To clarify, the guidance on scrolling or collapsible items is that they may be used, but only where they are "consolidating" (i.e. repeating) information already presented in the article. That means that a long list of synonyms in a taxobox (one of the more frequent [mis-]uses) should not be collapsed, unless the list is included or expanded upon elsewhere in the article. In the case of Acarospora, I see no reason at all to collapse the list in the text, although an additional list in the taxobox could be collapsed (for argument's sake; that's probably not actually a desirable addition). Incidentally, I notice that several of the listed species have articles in Category:Lecanorales rather than Category:Acarosporales; they should probably all be in the same place, although I don't have the expertise to say which.

In my experience, lists of "Selected species" result from a lack of knowledge – especially a lack of reliable, comprehensive sources – rather than because there's any advantage to omitting some species. It is inevitable that this will sometimes occur, but it is not something to aspire to. Very long lists of species can be farmed out to separate articles if they would make the original article cumbersome. There used to be an informal limit of 32 kb on articles, but that is becoming increasingly irrelevant. Anything up to a couple of hundred species I would keep in the main article; other editors might put the threshold at a different value.

As you have realised, the most important thing is to get the content right; it's quite easy to modify the layout afterwards. I, for one, think it is more important to make the articles informative and reliable than to make them adhere rigidly to a particular format. You asked for a review: I think what you have done at Acarospora is excellent. Keep it up! --Stemonitis (talk) 08:49, 9 November 2014 (UTC)

I'm glad to hear someone speak up for emphasizing substance over format. As for "selected species" lists, in my experience, there are two reasons for this: 1) the list includes only those species of interest to the person doing the selecting, e.g., an American listing only American species; 2) Someone creating a page for a large genus might not want to spend the time it takes to list a large number of species. Lists of accepted species are indeed available for many taxa, if you know where to look. But some genera have over 1000 species.Joseph Laferriere (talk) 13:05, 10 November 2014 (UTC)

Style guidelines?

Does the Plant project "officially" have an opinion on articles that resemble field guides, e.g. short sentence fragments like "Leaves: lanceolate, 5 cm . Fruits: 3 cm spherical." See for instanceMeconopsis lancifolia. I feel this should be politely discouraged, since Wikipedia is an encyclopedia not a field guide or plant identification manual. If there is a guideline, and other people feel this field guide structure is too common, perhaps the guidelines should be more prominent on the Project Page. Cheers.--Animalparty-- (talk) 21:47, 10 November 2014 (UTC)

In my case, I simply convert those to sentence form e.g.

The leaves are around 5 cm (2.0 in) in length, and are lance-shaped (lanceolate). The fruits are spherical, approximately 3 cm (1.2 in) in diameter.

I disagree that plant identification is not important to Wikipedia though. They're pretty essential when describing the plant, especially when there is no or only partial photos of the plant.-- OBSIDIAN†SOUL 02:33, 11 November 2014 (UTC)

I think the relevant guideline here is MOS:JARGON and WP:TECHCONTENT. Information for expert readers should not be a reason for WP:Content removal, but effort should be taken to make them understandable to the general reader.-- OBSIDIAN†SOUL 02:43, 11 November 2014 (UTC)

I'm not saying plant identification is unimportant, I am simply addressing the style in which the information is presented. Complete sentences and paragraphs should be encouraged; encyclopedias and field guides are different beasts, even if they have the same information.--Animalparty-- (talk) 06:36, 11 November 2014 (UTC)

Oh I definitely agree with that.-- OBSIDIAN†SOUL 08:14, 11 November 2014 (UTC)

I think it's quite clear that Wikipedia articles should be written in continuous prose; the MOS notes in several places the need for an "encyclopedic style". However, so long as it is sourced, poorly styled content is still better than no content. To echo Joseph's comment above, we mustn't appear to emphasize format over substance. Peter coxhead (talk) 09:49, 11 November 2014 (UTC)

I have looked at hundreds, perhaps a few thousand, of plant pages and found very little consistency in such matters. Style and content depend largely on who created the page. Each author adds whatever information s/he has in her/his field. I have no problem with this myself, provided that the content is intelligible and free of factual errors. I view these pages as a group effort. I add the information that I have available, leaving to others to inject information outside my own area of expertise. So any page you see is a work in progress.Joseph Laferriere (talk) 12:24, 11 November 2014 (UTC)

I have tended to use both (technical and plain English). The Flora summary style or "Floralese", with its abbreviations and shorthand understood by botanists though, is by no means standard, Kubitsky being especially idiosynchratic.

eg (Narcissus) in Flora of North America -

Herbs perennial, scapose, from ovoid, tunicate bulbs. Leaves (1–)several; blade linear to ligulate, flat to semiterete, fleshy. Inflorescences umbellate in clusters of 2–20, or solitary, spathaceous; spathe 1-valved, enclosing buds, membranous or papery. Flowers pedicellate or sessile, erect or declinate, often fragrant; tepals 6, connate proximally, distinct and reflexed to ascending distally, yellow and/or white; perianth tube surmounted by a cupular to trumpetlike corona with margins often frilled; stamens 6, epitepalous, often of 2 lengths; filaments separate from corona; anthers basifixed; ovary inferior, 3-locular; style often exserted; stigma minutely 3-lobed. Fruits capsular, 3-locular, papery to leathery, dehiscence loculidical. Seeds numerous, subglobose, often with elaiosomes; testa black.

But in all cases it must be accompanied by an easily readable plain English description. The other related issue that usually comes up in reviews is the use of technical terms such as 'scapose' above, whether they should be used at all, the degree to which they should be explained, or merely linked. If there is not a good explanation in the Glossary of botanical terms (which can be linked, at least as far as the first letter), add it. Also if the term falls under the description of a part, eg leaf ligulate, make sure that ligulate is explained on the leaf page, when linking to it. I think there is a place for the inclusion of such words that users may come across on reading other sources, but they should always be explained or linked when used. The question is to what degree is linking alone enough. I don't want to to have to explain 'ligulate' every time it appears! And there are some terms difficult to explain without introducing yet more technical terms. --Michael Goodyear (talk) 13:27, 11 November 2014 (UTC)

The other problem with explaining technical terms every time they are used is that such explanations make the descriptions longer and more difficult to read. People do not want to have sift through a long list of explanations to find the useful information they need. I generally to use a term in plain English if one is available, otherwise a link.Joseph Laferriere (talk) 13:43, 11 November 2014 (UTC)

I think that how far we should go to explain or gloss technical terms depends on the topic. An article about an species or taxon likely to be of interest only to someone with some botanical or horticultural knowledge is different from an article about a well-known garden plant or food source. So, for example, I wouldn't expect to write about Lophospermum scandens or Roscoea tumjensis in exactly the same style as Schlumbergera or Cactus. But maybe this is just a personal view. Peter coxhead (talk) 14:41, 11 November 2014 (UTC)

Well said, Peter. The vast majority of plant species have no uses, no common names, no economic value, and no interest to the lay public except for plant-lovers seeking to take photos of rare species. They will be of interest only to taxonomists and conservationists.Joseph Laferriere (talk) 17:31, 11 November 2014 (UTC)

Stems, stalks and such like

One problem I've encountered is how to be consistent in converting botanical terminology to plain English in those articles in which it is appropriate. For example, I was originally quite inconsistent in my use of "stem" and "stalk", which seem to me to be more-or-less synonymous in ordinary language, although not in botanical terminology.

Eventually I decided to base my usage on The Kew Plant Glossary. It defines "stalk" as "any support of an organ that has length". In its terminology, a leaf has a "stalk" (a "petiole"), a single flower has a "stalk" (a "pedicel"), an inflorescence has a "stalk" (a "peduncle"). A naked peduncle arising from the ground is a "scape". A "stem", on the other hand, would be expected to have at least internodes, and usually also leaves and perhaps flowers. So I've tried, doubtless not always successfully, to gloss "petiole", "pedicel", "peduncle" and "scape" from botanical sources as "stalk" in Wikipedia rather than "stem", using "stem" in the stricter botanical sense.

The botanical terminology for inflorescences is tricky to translate into plain English, in my experience. I seem to remember being taken to task (rightly I think) by Joseph Laferriere for accepting "flower head" as a gloss for the "umbel" of an Allium species. I've glossed "raceme" in the past as "flower spike", but "spike" has a narrower botanical use.

We'd probably find it hard to agree on some "standard translations" although I believe they would be useful. Peter coxhead (talk) 22:54, 11 November 2014 (UTC)

Peter coxhead Thanx for the nice compliment. I remember that. I was not trying to "take you (or anyone else) to task on that issue, just remarking that the use of "head" to refer to an umbel runs counter to formal botanical usage. Most of the time, common usage and technical usage will coincide. Show anyone a maple tree, and I am sure the botanist and the layperson will agree on what is a stem and what is a leaf. The problem arises when the two lexicons disagree, not uncommon with words of Anglo-Saxon derivation. We could use Latinesque terms instead, such as "capitulum" instead of the Anglo-Saxon "head." That would be technically correct although it would send the layperson scurrying for the dictionary.Joseph Laferriere (talk) 23:20, 11 November 2014 (UTC)

I think that sometimes we try too hard, and should just try and think what the average reader would understand by a word such as 'stem'. Illustrations and diagrams are a great help too! --Michael Goodyear (talk) 02:31, 12 November 2014 (UTC)