568:
which, if you put ~~~~ at the end of each post when you post on a talk page, the software will automatically sign it for you so people know who made it.) The thing is, there are quite a few people around here who know how to format a taxobox or which categories to add or where to put the bold at the beginning of an article, so you don't need to sweat the small stuff. Once your article is out there, people will come in and tweak the little things like that.
572:
plant article.) Then, pull some sources together. You can probably get some from Google
Scholar. Start by looking for the more general, descriptive articles. You don't want to get bogged down in a lot of highly technical papers describing some obscure plant-insect interaction where your species is one of many getting studied. Sometimes those papers will include a useful short description, though (like the one I linked at
273:
591:
formatting nice. Once an article is in the main space of the encyclopedia (out of the sandbox), you can create a talk page for it and add {{WikiProject Plants}} at the top. That will let the WikiProject Plants people know there's a new article that needs to be assessed. Usually we can spot plants articles even before that, though, because a bot runs every few days and generates a list of
433:
361:
332:
576:) and you can use that and not worry about the rest. You have better library/journal access than I do, so you might want to see what you can find there. If you have access to some floras covering Chile and that part of South America, they should have descriptions of the plant, its habitat, and distribution.
590:
That's the key, really. You and your classmates should be the experts on whatever plant you've chosen: focus on getting that knowledge across, together with the sources so other people can verify it. When you've managed to do that, it's easy enough to get help tidying up the references and making the
571:
As far as how to write an article that will look good and won't get banged around, I suggest approaching it a bit like a short paper. First, figure out what things you want to include—draw up a sort of an outline. (That plant article template gives a good idea of what sections you'd usually find in a
535:
Ah, OK. The thing about the pictures is that if you have permission to use them here, Knowledge needs a central way to track that the copyright holder gave their permission. (In other words, they want to hear directly from the copyright holder in a specific way, so they don't have to deal with person
599:
if you need to flag down a
Knowledge-active botanist or ask a botanical question. I'd better go now (long post, and I have a botanical club trip tomorrow), but pass this on to your classmates. We're unlikely to see their articles until they get them out of their sandboxes, and if there's a big issue
548:
I'll be back afterwards with some more tips on writing and source use. By the way, which college or university do you attend, if you don't mind my asking? I think I've helped with a few articles from your class. And thanks for coming to the talk pages to discuss this—a lot of people just write their
563:
Well, the Flickr upload bot doesn't seem to be working right now, but I'll try to get those backup photos on later in the weekend. One of my former students is graduating from Stony Brook this year, but I think he's a premed, so I'm not sure you'd know him—Nikhil
Sonalkar. I know Dr. Raleigh in the
579:
Once you have some sources on hand, sit down and tackle a section. Look over your sources, and then write a paragraph or two summarizing them. Write as if you were explaining things to a classmate, so they could understand where the plant lives or what it would look like if you were out collecting
582:
and give the reference where people can look up the information in that sentence, so they know it's true. Wait! You don't have to have a reference after every single sentence--if you have several sentences or a paragraph that all came from the same reference, just put the reference at the end. If
544:
In the meantime, I'm going to request that FlickrUploadBot move some of those freely-licensed images onto
Commons so that we have some images for your article while the OTRS ticket works its way through the system. You can use your original image once the copyright issues get sorted, but that way
567:
I know what you mean about
Knowledge being more complicated than it looks. I've been here about seven years (!) now, and it was a going concern when I arrived, and in Internet time, that's more than long enough to build an elaborate civilization and lots of twisty rules and customs. (Speaking of
540:
describes the process. The person who has copyright does have to release the images under a free license, and not just for use on
English Knowledge alone. See the "When permission is confirmed" section on that page for what to do when you have a written release from the copyright
586:
later on and it will duplicate the footnote. Just keep doing that for each section. Some sections, like the description of the plant, will probably be longer and harder to write, while things like the distribution will probably be fairly quick and
580:
and so on. It's OK to use some technical terms (after all, you've all been taking plant systematics!), but the more obscure ones should get wikilinked with ]. Then, add your references. For each sentence, after the period, put <ref: -->
513:.) In my experience, the best way to avoid that is to have more than one source, and maybe make yourself an outline of what you want to write into the article so you're not spending too long drawing from any single source.
508:
It's OK, I've removed the tag since you removed the copy-and-pasted content. Just make sure you're writing articles in your own words. (You don't want to follow the sentence structure of the source too closely, either; see
536:
A saying "Person B said I could use this," and 6 months later Person B shows up and denies giving permission and gets all bent out of shape.) Fortunately, there is a central clearinghouse called OTRS to handle this.
395:
However, for textual content, you may simply consider rewriting the content in your own words. While contributions are appreciated, Knowledge must require all contributors to understand and comply with its
28:
488:
Administrators will look at your reasoning before deciding what to do. For further help about the deletion, you could contact the user who first placed the tag or a
310:
If you believe that the article or image is not a copyright violation, or if you have permission from the copyright holder to release the content freely under the
287:
text or images obtained from other web sites or printed material, without the permission of the author(s). This article or image appears to be a direct copy from
537:
341:
36:
200:
300:
600:
with the article (copyright, medical claims, etc.), they're going to want us to spot that and tell them sooner rather than later. Good night!
592:
514:
51:
or by typing four tildes (~~~~); this will automatically produce your username and the date. Also, please do your best to always fill in the
583:
you're going to use a source multiple times in the article, you can give it a name the first time you use it: <ref name="some name": -->
492:
who is willing to help with deletion. This message was left by a bot, so please do not contact the bot about the deletion. Thank you, -
224:
110:
549:
articles and disappear, and that's a little frustrating for the active editors here. (It feels like we're shouting into the void...)
439:
to
Knowledge, thank you for taking the time to create a page here. It might not have been your intention, but you recently removed a
596:
48:
47:
41:
455:. Please do not continue to remove the deletion tag, instead, if you disagree with the deletion, you can follow these steps:
381:
133:
42:
517:
is good for helping organize botanical articles. If you'd like me to help you with this article, please leave a note on my
489:
151:
510:
105:
476:
This will take you to the talk page, where you can make your case by explaining why the page does not meet
Knowledge's
573:
386:
355:
If you hold the copyright to the material: send an e-mail from an address associated with the original publication to
349:
323:
205:
440:
229:
405:
377:
312:
296:
156:
64:
288:
462:
452:
436:
424:
304:
292:
280:
266:
180:
100:
95:
348:
If a note on the original website states that it is licensed under the CC-BY-SA license, leave a note at
497:
234:
397:
284:
185:
240:
190:
59:
246:
128:
605:
554:
526:
518:
493:
413:
52:
307:
has been tagged for deletion, and may have been deleted by the time you see this message.
371:
477:
448:
444:
195:
595:
that might be about plants. (That's how I found yours.) And the WikiProject has a
322:
If you have permission from the author, leave a message explaining the details at
601:
550:
522:
409:
400:. Knowledge takes copyright concerns very seriously, and persistent violators
289:
http://www.chileflora.com/Florachilena/FloraEnglish/HighResPages/EH0472.htm
609:
558:
530:
501:
417:
69:
564:
chem dept. too, although it's been a long time since we talked.
443:
tag from a page you created yourself. Because
Knowledge policy
585:
and then you just have to put <ref name="some name" /: -->
55:. Below are some useful links to facilitate your involvement.
271:
467:
447:
the creator of the page to remove deletion tags, an
316:(CC-BY-SA) then you should do one of the following:
313:Creative Commons Attribution/Share-Alike License
451:has replaced the deletion tag you removed from
167:
82:
19:
8:
352:with a link to where we can find that note.
283:, please note that Knowledge cannot accept
469:Click here to contest this speedy deletion
465:. Once there, select the button that says
538:Knowledge:Requesting copyright permission
342:Knowledge:Requesting copyright permission
326:and send an email with the message to
208:– a Wizard to help you create articles
279:Hello. Concerning your contribution,
7:
545:we'll have a stopgap image in there.
385:, and note that you have done so on
581:text of reference here</ref: -->
14:
431:
359:
330:
46:
40:
584:text of reference</ref: -->
1:
101:The five pillars of Knowledge
78:
15:
511:Knowledge:Close paraphrasing
478:criteria for speedy deletion
291:. As a copyright violation,
111:Intuitive guide to Knowledge
37:sign your name on talk pages
574:Talk:Aristolochia chilensis
461:Go to the page by clicking
408:from editing. Thank you.
387:Talk:Aristolochia chilensis
350:Talk:Aristolochia chilensis
324:Talk:Aristolochia chilensis
201:New contributors' help page
630:
610:04:35, 28 April 2012 (UTC)
559:01:47, 28 April 2012 (UTC)
531:00:10, 28 April 2012 (UTC)
502:21:56, 27 April 2012 (UTC)
418:21:41, 27 April 2012 (UTC)
181:Frequently asked questions
70:03:01, 27 April 2012 (UTC)
360:
331:
225:Contributing to Knowledge
152:How to develop an article
370:a postal message to the
301:speedy deletion criteria
265:Copyright problems with
295:appears to qualify for
191:Where to ask a question
120:Finding your way around
453:Aristolochia chilensis
425:Aristolochia chilensis
305:Aristolochia chilensis
293:Aristolochia chilensis
281:Aristolochia chilensis
276:
267:Aristolochia chilensis
275:
29:Welcome to Knowledge!
25:Hello, Ab022688, and
372:Wikimedia Foundation
134:Department directory
423:Removing Speedy at
241:Knowledge etiquette
35:Please remember to
490:highly active user
374:permitting re-use
277:
235:Join a WikiProject
106:How to edit a page
53:edit summary field
449:automated program
344:for instructions.
262:
261:
258:
257:
254:
253:
164:
163:
129:Table of contents
77:
76:
621:
472:
435:
434:
398:copyright policy
366:
364:
363:
362:
337:
335:
334:
333:
274:
230:Community Portal
216:How you can help
168:
143:Editing articles
83:
79:
67:
62:
50:
44:
20:
16:
629:
628:
624:
623:
622:
620:
619:
618:
466:
441:speedy deletion
432:
428:
358:
356:
329:
327:
272:
270:
217:
173:
157:Manual of Style
144:
121:
88:
87:Getting started
73:
65:
60:
58:Happy editing!
12:
11:
5:
627:
625:
617:
616:
615:
614:
613:
612:
588:
577:
569:
565:
546:
542:
482:
481:
474:
445:does not allow
427:
421:
393:
392:
391:
390:
357:permissions-en
353:
346:
328:permissions-en
269:
263:
260:
259:
256:
255:
252:
251:
250:
249:
243:
237:
232:
227:
219:
218:
215:
212:
211:
210:
209:
206:Article Wizard
203:
198:
193:
188:
183:
175:
174:
171:
165:
162:
161:
160:
159:
154:
146:
145:
142:
139:
138:
137:
136:
131:
123:
122:
119:
116:
115:
114:
113:
108:
103:
98:
90:
89:
86:
75:
74:
61:SwisterTwister
23:
13:
10:
9:
6:
4:
3:
2:
626:
611:
607:
603:
598:
594:
589:
578:
575:
570:
566:
562:
561:
560:
556:
552:
547:
543:
539:
534:
533:
532:
528:
524:
520:
516:
512:
507:
506:
505:
504:
503:
499:
495:
491:
485:
483:
479:
475:
471:
470:
464:
460:
459:
457:
456:
454:
450:
446:
442:
438:
426:
422:
420:
419:
415:
411:
407:
403:
399:
388:
384:
383:
379:
373:
369:
365:wikimedia.org
354:
351:
347:
345:
343:
336:wikimedia.org
325:
321:
320:
319:
318:
317:
315:
314:
308:
306:
302:
298:
294:
290:
286:
282:
268:
264:
248:
244:
242:
238:
236:
233:
231:
228:
226:
223:
222:
221:
220:
214:
213:
207:
204:
202:
199:
197:
194:
192:
189:
187:
184:
182:
179:
178:
177:
176:
170:
169:
166:
158:
155:
153:
150:
149:
148:
147:
141:
140:
135:
132:
130:
127:
126:
125:
124:
118:
117:
112:
109:
107:
104:
102:
99:
97:
94:
93:
92:
91:
85:
84:
81:
80:
72:
71:
68:
63:
56:
54:
49:
43:
38:
33:
32:
31:
30:
22:
21:
18:
17:
593:new articles
487:
486:
484:
468:
458:
430:
429:
401:
394:
375:
367:
339:
311:
309:
278:
172:Getting help
96:Introduction
57:
39:by clicking
34:
27:
26:
24:
494:SDPatrolBot
285:copyrighted
376:under the
299:under the
196:Help pages
186:Cheatsheet
597:talk page
519:talk page
515:This page
463:this link
245:Practice
378:CC-BY-SA
297:deletion
247:civility
541:holder.
437:Welcome
406:blocked
239:Follow
602:Choess
551:Choess
523:Choess
410:Choess
587:easy.
606:talk
555:talk
527:talk
498:talk
414:talk
402:will
382:GFDL
380:and
340:See
66:talk
404:be
45:or
608:)
557:)
529:)
521:.
500:)
416:)
368:or
338:.
303:.
604:(
553:(
525:(
496:(
480:.
473:.
412:(
389:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
