User talk:Larry Sanger

Larry Sanger

Current talk page

1, 2, 3, 4, 5, 6, 7, 8, 9, 10
11

Definitions: what are they and why do we need them?

Excuse me for being stupid, but nowhere in all these discussions in various Forums and User Pages do I find a *clue* as to *why* we want a "definition" or as to *what* it is. All I can glean is that if an article such as Ray Casey currently has a Def. tab at the top, that means that there is *no* "definiton" and that one should therefore be written on the Def. tab page.

• Once this is written, apparently, in a truly existential act (or non-act) the Def. tab disappears!
  • If the Def. tab is now invisible, then what good is it?
  • What does the new definition (invisible, remember) accomplish? Something, apparently, or all this discussion about it would not be underway. But for a guy like me, who just wants to write simple-minded articles about Backhand (tennis) and Spareribs (barbecued), what am I missing? Hayford Peirce 12:41, 12 May 2008 (CDT)

Well...we decided to have definitions etc. back when we instituted subpages. Their purpose can be ascertained on CZ:Related Articles: they make those subpages much more usable. They have only recently become visible because Chris had the bright idea of how to move definitions to subpages from their current locations.

Hmm, yes, we know that the def tab disappears. That's its designed behavior (you should talk to User:Chris Day about this). It is interesting that you find this disconcerting. Tell this to Chris! If you find it disconcerting, so do I. --Larry Sanger 15:29, 12 May 2008 (CDT)

Two problems seem to be emerging here. One, the def tab is not liked by all, even as a reminder. Two, the noinclude code at the top of the definition subpage is causing confusion. One solution might be to axe the tab and the code at the top and go with a definition subpage that does not include the subpages template. After all if there is no tab link then readers will not surf onto that page, it will essentially be invisible until someone want to edit the definition. All we would lose would be a category that can show us our definition subpages that are not as part of a cluster.

If we are going with a hidden def subpage then maybe we should just go with it being in the metadata? In the long term i envisage that the user interface with the metadata page will be very user friendly and adding the definition there will be as easy as typing into a text box. If that is likely to be the case it might solve future problems to have the definition there from the start? Do you have a strong reason for having it on its own subpage? Basically, neither place is perfect, so I wonder if we need to think more long term. Maybe a computer expert is the right one to ask for an opinion on this? Chris Day 22:00, 12 May 2008 (CDT)

I agree that if editing the definition in the metadata were just as easy as typing it into its own text box, then I would support that change. But...it isn't as easy. And, it probably won't become as easy anytime soon. I'm not sure what future problems this might solve. And, after all, when we do have a more automated metadata solution, presumably we'll have a lot more programming help and so we'll be able to switch the location then. Sure, consult all relevant experts! I'm just concerned about keeping it maximally simple to use.

I don't mind removing the def tab. As long as it's on the talk page, as it is now, that ought to be enough for our purposes. But--and this is something worth thinking and discussing some more--there is one decided advantage to keeping the def tab there. It is that it is obviously a little "itch" that contributors have been "scratching." And it's an itch that has been needed to be scratched. So, if we were to remove the def tab, there would be both good and bad: on the one hand, we would simplify the subpage templates (for definitionless articles); on the other hand, we would not produce quite as many definitions (how many fewer, it's hard to say). I'd leave this up to you, Chris... --Larry Sanger 12:39, 13 May 2008 (CDT)

What about the removal of the noinclude code and subpages template from the definition subpage? Is there any good reason for keeping it? Without a tab for the definition page in the cluster then no readers will be browsing the definition subpage.

Personally, i think the tab serves a useful role in causing an itch. I wonder whether we should keep that and the To-do list reminder for now.

Another reason for not going the metadata location route is that the pre include size of the R template will increase, potentially by a lot. Chris Day 14:15, 13 May 2008 (CDT)

Good points. Yes, I don't mind removing {{subpages}} from the Definition subpages. No point to having it there if it's not going to be viewed by users.

OK I'm just going to play devil's advocate--I don't care, but maybe users would like to see a Definition page. Want a single simple definition, that's all? There it is. Want more info? Click the tabs. By the way, it wouldn't be a bad idea to have a little graphic (which we can take down after some months?) advertising the existence of more content, when it exists. "Look above --> for more content on this topic." And after all, sometimes people do search for definitions. If we have a page titled "Term > Definition" we'll probably bring in traffic just from that. At least there could be such a graphic/message on the Definition subpage.

If we did have a non-disappearing Definition tab, I'm thinking that writing out "Definition" would be better than "Def" -- the former is clearer and more user-friendly rather than contributor-friendly. But it would make me worried that, as on articles like Life, there would be too many tabs! I'm sure you have worried about wrapping tabs. Remember, I warned this would be a problem with horizontal display of subpage links!!!

I predict that if we don't include {{subpages}} on the Definition subpages, some people will put it there not realizing that those subpages are used as templates, and will proceed to screw up Related Articles pages. I don't know how serious a problem this would be, but it probably would be an annoying little problem at least. --Larry Sanger 14:26, 13 May 2008 (CDT)

Since i developed both I abstained from the horizontal/vertical vote since I didn't want my endorsement to color the debate. :) Often I will push both sides of a debate just to get feedback and make sure i have seen all the possible solutions. Besides we can always switch back to vertical if articles like life becomes a real problem, that is more about aesthetics than function.

I had not thought about people entering from an external search. That is a good a reason to keep tabs on the definition page. Obviously anything on that page, other than the definition, has to be within noinclude tags so if we went with a graphic we might as well go the whole hog with the the subpages template. I think you are also correct that it might be tempting for people to add the subpages template to the definition template if one is not there. And that would really mess up the related articles pages. How about we leave everything as it is for a while and see how people respond after a month. In summary:

1. I'll make the red tab name read "definition" but keep its disappearing property once the defintion exists.
2. I'll keep the subpages template between the noinclude tags
3. I'll keep the to-do list reminder.
4. I'll tweek the definition pre-load text to try and make it more informative.

Chris Day 14:55, 13 May 2008 (CDT)

1CE

I solved that problem there was a template in the wrong place. Not sure how I missed it. Chris Day 22:02, 12 May 2008 (CDT)

disambig strategy

I think this got archived before you got a chance to respond to it, so I'll put a copy here...

Hi, I've finally gotten around to writing a draft proposal. You can see it at CZ:Proposals/Disambiguation mechanics‎; comments appreciated. J. Noel Chiappa 12:02, 13 May 2008 (CDT)

Merciless editing

Hi, maybe it's time to change that "If you don't want your writing to be edited mercilessly and redistributed at will, then don't submit it here" that we inherited from Wikipedia? See Talk:Central Intelligence Agency‎#Huge deletions not justified for what brought this to mind. (The message is MediaWiki:Copyrightwarning if you need the location.) J. Noel Chiappa 10:28, 16 May 2008 (CDT)

yeah, I removed stuff quoting a nonexistent government report that probably was a hoax and certainly fails all reliability tests. (ie quotes from a "document" that archivists have searched for and not found, indeed there is no evidence it existed in the first place.) Only one person claims to have seen this "official government document," and he lost his notes. The section removed had some quotes from the supposed document, but mostly was about its mystery status. A famous historian did make the quotes, but his citation was to the Kennedy papers and the Kennedy archivists say it never was there; the historian (Schlesinger) says he lent out his notes and never got them back and has no copies. If reliability means anything, this scores a 2 on a scale 1 to 100. Richard Jensen 10:37, 16 May 2008 (CDT)

I think I wrote the "edited mercilessly" bit back in 2001--amazing that it is still around. I went ahead and changed it.

Richard, my response is going to be the same as in so many other cases: you might have good reasons for doing what you do. But CZ is a collaborative enterprise, and that means indulging in some discussion before making dramatic edits. If making large deletions without prior discussion upsets other people in the project, as it usually does, it does not matter how well justified the deletions are (and I would agree that, if there is not another legitimate side to this issue, we probably don't want to include the material you deleted). Besides, as you must know as well as anyone, we have a policy that specifically forbids unexplained deletions. In fact, you can be banned for it after a warning. --Larry Sanger 12:06, 16 May 2008 (CDT)

P.S. I don't mean to make any decision or ruling or anything about the particular case in question; perhaps there was adequate discussion in advance in this case. I suspect that this is a case yet again where what is called for is an intelligent compromise with CZ:Neutrality Policy in mind. Without such compromises, we'll always be fighting. Intelligent compromise is the heart and soul of intelligent collaboration. --LMS

Gentle guidance

Maybe it is time to remind long-time editors about the gentle guidance clause, especially when dealing with authors who joined only 3 weeks ago. I hate to see new people driven away, especially prolific ones. David E. Volk 10:46, 16 May 2008 (CDT)

Hi David, could you give me a pointer to what you mean, by e-mail? But such a reminder is probably a good idea on general principles. --Larry Sanger 11:54, 16 May 2008 (CDT)

Bug

Larry i just want to alert you to a bug I found. The same problem exists in wikipedia too so this is nothing the new processor will improve. Basically in the current format the definitions cannot be used as a template directly, only as part a more convoluted template such as {{R}} (More here). The problem is that the line break we currently have on the definition page does not appear in the R template but does when the definition subpage is transcluded on its own. Below is an examples.

{{R|Biology}}

• Biology [r]: The science of life — of complex, self-organizing, information-processing systems living in the past, present or future. ^[e]

*{{:Biology/Definition}}

The science of life — of complex, self-organizing, information-processing systems living in the past, present or future.

This is not a major problem since at present we only use definitions as part of a template. And possibly in the future too? However, if you have plans to use the transcluded form directly from the definition subpage we need to remove the line break so that it is in the form of either:

<noinc1ude>{{Subpages}}</noinc1ude><!--
-->Definition here.

Or go with the following:

<noinc1ude>{{Subpages}}</noinc1ude>Definition here.

Rather than what we currently have:

<noinc1ude>{{Subpages}}</noinc1ude>
Definition here.

Two ways forward here. Either change CZ:Definitions so that is does not suggest transcluding the defintion page directly or remove the line break from all definitions and rewrite the preload to reflect this policy. I favor rewriting CZ:Definitions and only using the definitions with a tempalte like {{R}} or similar. Chris Day 11:10, 16 May 2008 (CDT)

As you see I just went ahead with this and wrote the {{Def}} template. Seems like a no brainer in retrospect. So for the /Defintion subpages we can keep the current format. Chris Day 12:45, 16 May 2008 (CDT)

Sounds good. (I knew what you meant.) --Larry Sanger 12:46, 16 May 2008 (CDT)

Regarding Bibliographies

Hi Larry,

Saw your post on the CIA article regarding bibliographies and just thought I should pop my head up (As usual!) Generally the task is to get as much information on the article itself. It is as much psychological as anything else to have the bibliographies on the article page at one time; it is under the principle that when the entire article is finished, then the bibliography can be moved to the subpage. Furthermore, a small 'further reading' section containing parts of the bibliography is useful within an article, and sometimes its just easier to leave the entire bibliography there until the article gets to the stage of polishing up things; such as leaving a 'further reading' section. Just thought I should let you know this is my (And probably Richards, from my observations and dealings with him) method for writing articles and why I don't fill out the subpages straight away. I hope this makes sense. (Beginning to feel like it doesn't) Denis Cavanagh 19:38, 16 May 2008 (CDT)

As long as you don't mind it when others move your bibliographies to bibliography subpages, and don't ask others not to move them, that's fine with me. It would be easier, however, if you just started the bibliographies on the subpages--or, of course, you could propose to make your practice standard practice...since you are defending your behavior, it looks like you want to do that (i.e., change our standard practices).  :-) Anyway, I'd rather not try to force people to change their behavior if they're doing a lot of good work, even if their behavior is against our rules, unless they really make a nuisance of themselves.  :-) --Larry Sanger 13:08, 19 May 2008 (CDT)

I agree with Denis. When we're drafting an article it's much easier to have the bibliog at the botton so we can keep track of what is covered. When the article is mostly done then move to its separate page.Richard Jensen 13:24, 19 May 2008 (CDT)

I was going to suggest the 'Further Reading' thing (i.e. selecting a few of the best things which one would suggest for a novice looking to take their next steps ina field, and sticking that at the bottom of the article) as a policy change, but it's mired in my ToDo list somewhere... :-) J. Noel Chiappa 13:34, 19 May 2008 (CDT)

Well, the articles are written for readers, and if they see bibliographies in two different places, they'll be confused. So I have a suggestion: open another window!  :-)

I'm not opposed to "Further Reading" and making that distinct from the bibliography; I'm not even opposed to having that as part of the main article. But actually, it would be best to keep "further reading" fairly short and include extensive annotations, if its function really is indicated by the description "further reading" (these are a few pointers we'd give to someone who we pretend really intends to read more about the topic now), and is distinct in function from that of bibliography. It would serve the purpose of a brief, beginner's introduction to the literature on the topic. If it were annotated and in prose form, then there is no inconsistency with the idea that other kinds of information can be found on subpages: this is prose general information about the topic, i.e., it's a prose description of the best sources to learn more about the topic. And, that would be a great thing to make a proposal out of, you know... --Larry Sanger 13:57, 19 May 2008 (CDT)

Its too small an issue to get the EC council involved in; Is there a specific article policy that doesn't allow a further reading section? Denis Cavanagh 14:02, 19 May 2008 (CDT)

Denis, about whether the Editorial Council needs to be involved, you are guessing; and you don't need to guess about how a proposal is decided on if you use CZ:Proposals. Nope, there is no policy that doesn't allow such a section. If you want to add such a section, do so. However, I don't believe anyone has been doing so. And, for the sake of uniformity and "least surprise," it would be good to make such a good idea "official policy." --Larry Sanger 19:43, 19 May 2008 (CDT)

Larry, what you propose is pretty much what I'd like to see. You can see one that's starting down that road at Michael Faraday/Draft#Further reading, although some entries aren't deeply annotated yet (I don't have all these works). Can it be an annotated list, as there, or do you really prefer prose? I would think prose really would look ugly if we include things like publisher, ISBN's, etc.

I would like to make it formal policy because I'd like to see all (well, as near as practical) our articles eventually include a really nice Further Reading section like that. J. Noel Chiappa 14:25, 19 May 2008 (CDT)

I stand corrected, then, about whether anyone has added "Further reading" sections yet! But in this case, I agree--this "Further reading" is not really prose, but just looks like an annotated bibliography, and we have an already-established place for those (CZ:Bibliography subpages :-) ).

Let me be clear. What I am trying to prevent from happening is strong-willed editors and authors (you know who you are) from just going off on their own, potentially duplicating effort, or doing things that, when our work is taken all together, prove to be essentially incoherent. I am largely in favor of people doing what they want, when they want, and trying new approaches to formatting. But at some point, for the sake of usability, we should make an effort to articulate a uniform policy.

Basically, as I see it, in the long run, people (both users and contributors) will understand very well what the difference is between an article and what belongs on subpages, but in order for that to happen, we must get clearer on the distinction. Here is how I make the distinction in my own mind: the stuff that goes on an article page is a general prose introduction to the topic, of a general encyclopedic sort, together with any supporting notes. The stuff that goes on subpages is all other types of information. I assume that some reasonably clear distinction can be drawn between prose encyclopedic introductions, on the one hand, and information that is in the form of lists, tables, images, charts, diagrams, other media, raw data, and so forth.

Given this general distinction, which I hope I am not alone in making, it follows that anything that takes the form of a mere list of books really belongs on the Bibliography page. A prose introduction to the literature, as one sometimes finds at the end of chapters of some textbooks, could be reasonably construed as part of "a general prose introduction to the topic." Merely annotated bibliographic entries are exactly what we want completed, well-developed bibliographies to contain, after all. (I see that Chris is saying something like this below.)

If we think that "Further reading" sections are better cast as merely annotated bibliographies, then there is no reason that they cannot be standard first sections in bibliographies. We simply begin all our bibliographies with sections titled "Further Reading" or perhaps "Essential Literature" or something like that. --Larry Sanger 19:43, 19 May 2008 (CDT)

I see no reason why bibliographies cannot be like that too. After all, if editors are taking time to select various sources, rather than the bibliography being a comprehensive list, I think it would be useful to see some reasoning that led to the editorial decision. The best review articles in biology even bullet the articles they cite that have a high impact on the field, along with a brief explanation for the bullet status. While I like the further reading to compliment to the potentially larger bibliography we must be careful that they do not become overlong. Chris Day 14:34, 19 May 2008 (CDT)

Oh, I want to see more info in Bibliographies too! Organized into article/books/original sources, annotations on each entry, yadda-yadda! (That was to be in the proposal too.) But I take your point about 'not too long' - is a fixed limit on the number of entries (say, a half-dozen) the way to go; or what kind of guideline can we give? J. Noel Chiappa 14:48, 19 May 2008 (CDT)

A case by case, but common sense approach might be the best route to go here. But I think three to six is a reasonable limit. Chris Day 14:53, 19 May 2008 (CDT)

I agree with some such limit too. --Larry Sanger 19:43, 19 May 2008 (CDT)

Eduzendium: General Microbiology

The CZ:Biol 201: General Microbiology experiment seems to have been a success. Most of the students have completed excellent posts on microbes. I was pleasantly surprised with the participation. All pages are now open to edits from the broader community (and some pages need cleanup). I'll probably try this again next Spring when Microbiology 201 resumes. --John J. Dennehy 11:14, 19 May 2008 (CDT)

This is excellent! I'm so glad! You have made my day!

You would be doing us a great service by posting something (even as short as what you have above) on Citizendium-L and Citizendium-Editors. A little testimonial on CZ:Eduzendium or another (new? CZ:Eduzendium Testimonials?) page would also be a great service. --Larry Sanger 12:22, 19 May 2008 (CDT)

Eduzendium Testimonials--John J. Dennehy 16:29, 19 May 2008 (CDT)

Thanks, John. --Larry Sanger 19:47, 19 May 2008 (CDT)