2421:
separate articles seems the best solution for nearby stars likely to be in many lists - if you think about how best to present the information in a way that is easy for a reader to navigate. What other solution is there that works as well as that? Plus the separate article is easier to read than a Simbad entry for a non professional astronomer and if you really know your way around SIMBAD you can find e.g. that Gliese 146 is a member of the hyades supercluster, but is not obvious from its entry that it is, and once you are in Simbad you no longer have cross linking back to wikipedia while if you stay in wikipedia then go to Gliese 146 and you can then just click on the link to get to the entry on the Hyades supercluster or the entry on habitability of dwarft stars etc. The separate articles are not meant to confer notability on these stars as entities, certainly not saying they deserve an astronomical article, just make it easier to organise the content.
1624:. The wikipedia entry is easier to read for the average reader, and is also more informative, it has a few details not in the SIMBAD entry such as its galactic orbit, that it's a member of the Hyades moving cluster (which is mentioned elswehere in SIMBAD but for some reason not in its star article itself). Another benefit over the SIMBAD database entry is that it also has the cross links to other wikipedia articles on habitability of orange dwarf stars and to other nearby stars in the "See also" section. As new lists are made that include these nearby stars, then you can add cross links to those lists as well e.g. to a list of other nearby orange dwarf stars which I'd like to add some time.
696:
same time totally agreeing that if someone adds an entry for an insignificant tenth magnitude star chosen at random from SIMBAD, then this serves no value at all in wikipedia, as we are not trying to build a star catalogue. There seem to be occasional users who do that, and their star articles are rightly deleted, but many of the star articles are contributed by users who have chosen the star for the article because they consider the star to be interesting, e.g. in an interesting class of nearby stars, even though it doesn't have a paper devoted to it. And that's not OR since it is simply collating together material from many different online sources to provide the star article.
922:(Edit conflict) I agree with StringTheory11, Graeme Bartlett, et al that these should be deleted and merged into a list article (in case it wasn't clear above). As noted repeatedly, they plainly don't meet the notability criteria which are well established, project-wide, for good reason. Knowledge (XXG) is not an indiscriminate collector of information, and all the data about these stars that users note is important is better suited to true astronomical databases like SIMBAD, unless reliable sources indicate that there's something interesting about a particular star. We can't synthesise or determine importance ourselves when no reliable source does. —Alex (
1987:
significant coverage to build an article, or it doesn't. However, I'll go a little beyond
Robertinventor and say that even some articles that have more than one line of text are not suitable. Some of the recent examples that were debated are just multiple lines of terse fact-stating, essentially rehashing what's in the info box. I don't agree with the sentiment from other editors above that an encyclopedic article can be made by cobbling together little bits of physical parameters from large survey papers or bulletins. The spirit of NASTRO (and the General Notability Guideline) is to favor objects that have
1078:: should Knowledge (XXG) eliminate or reduce the need for significant coverage of individual people to allow stub articles on any individual. A phone book lists names of people, along with their phone numbers. An internet search can even turn up an address in many cases. A search for the basic Facebook profile can yield even more information about an individual. This is bound to be useful for somebody out there - we cannot predict who it will be useful for. Surely if NASTRO is to be modified to allow astronomical object articles without the need for significant coverage, then we should do the same with
1459:. Once one or more appropriate lists (e.g., List of members of the Hyades moving group, List of stars at 10 to 20 parsecs distance) are identified, I would include the star's name, whatever properties are decided to be included in the list itself, and a link to its SIMBAD page ... and nothing more, until some datum more demanding of individual attention arises about that particular star. Umbrella articles about the moving group, or about the local star population, etc., should be used to provide the overview for the larger category (the forest, in the trees-vs-forest analogy). In effect, I apply a
1034:
guideline. The community decided to explicitly exclude the creation, or maintenance, of individual articles for astronomical objects which cannot be developed beyond a stub. There's not many ways for editors to know which articles can be developed beyond a stub, but the best way is to judge the individual coverage in 3rd party sources. None of the objects we're discussing here have significant coverage. If they did, they would meet the common sense criteria of NASTRO. The objects at the heart of this current discussion don't meet the "spirit" of
884:
then compile the lists the verifiable data that exists. I do not agree that creating new, or keeping existing, articles for non-notable objects is necessary. I am not particularly convinced all this data needs to be culled in lists, though. As well, an inconsequential stub doesn't help anybody - the random person who does happen to look for information on a non-notable star is likely a professional, or an advanced amateur astronomer - in that case they have other, better databases to consult. From NASTRO: "It is not the job of
Knowledge (XXG) to
1690:, in your argument you seem to conflate "notable" with "interesting", "remarkable", "exceptional" or something semantically in the same ballpark. That is not how WP notability works. Notability is, instead, roughly speaking, a measure of "do we have the conditions to write an article about this?" - The subject does not need to be exceptional at all. What it needs, summing it up very quickly, is enough reliable material published about it that we can assemble in an article. So, when you say that an article existence
1599:
jump to the star article and then from the information there find out about other lists it belongs to (e.g. Gleise 146 belongs to at least three potential lists possibly more), and helps to avoid repetition in articles that refer to them. And unlike most AfD discussions, these articles add information to wikipedia that is uncontroversial, accurate, and backed up by citations, and they are more readable for the average reader than the SIMBAD database entry for the star, and can include details not in SIMBAD
1760:, you have correctly represented my interpretation of "notable", and that interpretation will continue to govern what I choose to add and edit into WP, and by extension, what I think ought to be in general. I recognize that is a much stricter policy than present consensus even under the existing NASTRO, but as long as I refrain from putting debatable things up for deletion and don't beat people up for acting otherwise, it governs only my own contributions and is of no further concern. Happily,
1768:... I see those comments were a product of my own interpretation of "notable" coupled with the act of choosing to create WP articles based on the results of correlating data in catalogs; the OR is not in the content of the articles themselves, but rather in the selection of what gets created. I know from personal acquaintance with those who did it that correlating data from different surveys and looking for anomalies and outliers was in fact the first step in their research. That is the way
1514:. But each of those are, or were for some time, key example objects of particular classes (which makes them Mid-level importance under WP:AST's importance scheme). I would heartily endorse keeping an article like the QWERTY 467 example above; it feels like the same level of notability as the real articles I've linked, a key individual case in a larger phenomenon. Ideally its article should highlight those features of the star that are important for understanding the class it exemplifies.
2504:
changes. But one could argue that having so many minor planet articles makes consistent maintenance all but impossible. It is very easy for a vandal to make a modification to a stub page that may not be caught for years. In the overall scheme of things on
Knowledge (XXG), I've reached the perspective that it is better to focus on quality rather than quantity. Having 500 high quality asteroid pages is better than having 500,000 uninformative stubs. Regards,
1888:. So if all 1400 of the stars within 50 light years were added then your chance of coming across one of them in a random search would be about 1 in 3000. Probably only a few hundred of them will ever get articles, so that would be 1 in 15,000 chance or less of coming across those articles. The number of star articles sent for AfD recently is quite large of the order of dozens, but not hundreds and that includes a few that everyone agreed should be deleted.
1914:
to make quite a substantial small article as there is so much material about them in the databases, also in articles studying various small classes of nearby stars. For more distant stars, would have to be a very interesting type of star. Still, if there happens to be lots of information about those types of stars, and not just a list of figures all in a single database but something worth collating into an article, then they could be worth inclding too.
31:
575:". However, I currently do not have the time to compile such a list due to real-life and other on-wiki commitments. If consensus goes that we should create these lists, I'd be happy to help in the writing as much as I can. However, for now, these stars do not pass either the GNG or NASTRO, and thus have to go. There's no reason to make an exception for these stars, anymore than there is for some random star that doesn't have an article yet.
2431:
make wikipedia better for the average reader. There is a bit more to it I think than first meets the eye which is why it became such a long thread. And these star articles have been in wikipedia for years, is only recently that the issue came up when someone started PRODing them, is not a new policy direction in that sense. I am not sure you have resolved it though it is good to have a fresh eye on it.
353:. I also stated very clearly in my first post that articles which just parrot catalogues are not worth of keeping. I am speaking of a different kind of beast, namely objects where one can build an informative article well beyond a simple catalogue entry, due to multiple studies, reported in reliable sources (peer-reviewed papers, for example) having determined things about them, and that fulfill the
990:-this is hardly a provable assumption. We do not have to care about who is likely to look for the article or not, and where they tend to hang around. Knowledge (XXG) is there to provide information, not to worry about who and how will look for it. The point is not that I like articles on stars, or that we have to serve the amateur astronomer community. The point is that these articles meet the
2219:
of objects of interest for search for debris disks or in the
Horologium constellation. If you try and put all the information from the article into a list type article it will leave most of the information out, or else will be almost unreadable and each entry in the list would have a separate set of bibliography entries, and "see also" sections. And the lists would have duplicate information.
167:, particularly the significant coverage component of it. They are only interesting because they are in a class of objects (nearby late-type main sequence stars) that is interesting for habitable planet searches. Therefore, their content should either be deleted or merged to a list of stars in that class. Thus, I see no problem with the astronomical object notability guideline. —Alex (
662:"Too many insubstantial stubs dilutes the overall useful information" This is exactly where I disagree. I mean not with what you say of course, but whether it applies here. In most areas of wikipedia yes, that would be true, but here, the only way that any reader is going to come across e.g. a separate article on Gliese 146 is because they are interested in that particular star.
1429:
now-inactive-in-research astronomer. I am a little leery of Robert Walker's argument; deciding a star is notable because its collective data from 20 or more survey papers (each of which has hundreds or more stars' data, and none of which single out the star under discussion for specific mention) assembles to an interesting combination ... this is in fact a violation of
1316:
1406:
50 or 100 papers, and in databases, rather than collected together in a single article. The total amount of information available in the literature for a nearby star, say, within 50 light years, is typically, I'd say, at least for the orange dwarfs, more than the amount of information you would have in a typical paper devoted to just that star.
530:, I participate in AfD since a long time). My issue is: some of that information doesn't appear to be easily mergeable in a list. If this is indeed possible and there are suitable merge targets, this is perfectly satisfying: I do not care so much about the individual article, but of having the information available somewhere. But in this case
2048:. The point is that stars and other astronomical objects happen to be an exception: you can have plenty of information to build an article even without one source significantly covering it. If the spirit of NASTRO is to prevent perfectly fine, informative, encyclopedic articles, then then spirit of NASTRO is at odds with the project. --
1581:
about the star. Also these articles don't confer notability on the object. There is no implication that a star deserves to be singled out for special study as a separate object of its own in an astronomical paper, just because someone took the care to collate some of the easily available data about it into a separate entry in wikipedia.
2473:.) He simply has an agenda to remove as many asteroid-stubs as he can. Asteroids numbered below ~2000 should not be aggressively targeted since they are fairly large and easily observed by amateurs with small telescopes. Make a honest guide and there will always be someone in the group that will try to take advantage of it. --
1455:'s infamous "All science is either physics or stamp collecting" comment goes in the same direction, though I am closer to the "stamp collectors" he was backhanding. My deletionist tendencies stem from a belief that after the first few, the forest is what is notable, not the individual trees in it. I would, by myself, delete
1694:, you're getting it wrong. The existence of an article suggests nothing of the sort -we're not a collection of the exceptional, we're a collection of knowledge, in general. We have tons of articles on extremly specialistic stuff, in all disciplines, which is nonetheless notable by far and large according to our standards.
768:
whole page, so end up with a page with lots of distinct reference lists in it. Same also for the external links, to have a list of all the relevant external links for all the stars on the page at the end of the page, can't see that working, so they also would be separate for each section in the merged list.
2272:
It's like - the only reason for presenting this information in list form in a big long list or several lists is to comply with the notability criterion for the star as a separate object. It doesn't benefit the reader of wikipedia to do it this way. But the notability criteria are meant to be there to
2218:
The problem with lists is that a star can belong to many lists. Plus the references are different e.g. take Gliese 146 again as example it can be in a list of K dwarfs within 50 light years, or a list of members of the Hyades supercluster, or list of objects between 40 and 50 light years, or the list
1350:
In this case, there is plenty of information about the object that makes it possible to create a substantial article, even if no study is specifically about the object. Collating of these sources requires no original research: it's simply a listing of independent facts. This is the kind of edge cases
1103:
It would greatly depend on what information we deign to include on the suggested new list, since I would assume it would include the common name, position, magnitudes, distance, constellation, stellar classification. And that any merger would also merge the star to the lists of stars by constellation
802:
Also many of the stars in the lists may have separate star articles already, because someone has written a paper about them as individual stars, so presumably your notes page wouldn't duplicate that material and would only list the stars that don't have articles yet. Then as time goes on you would be
689:
It is much more straightforward, to avoid burdening any long list with unnecessary information to have separate articles for each star - for ones that are near enough to have information about them available in dozens of different surveys. So e.g. for my idea of a list of all the nearby orange dwarfs
463:
Its speed relative to the sun is 38.1 km/second, and its galactic orbit ranges between 20,800 and 25,400 light years form the center of the Galaxy. Its a suspected variable star. It belongs to the Hyades supercluster of stars It is one of 155 K type stars within 50 light years. It is one of 500 stars
403:
It is obvious that this user is just arguing from religious devotion to inclusionism. They clearly haven't investigated the cited "sources" for Gliese 146, otherwise they would realize the sources are superficial websites that parrot each other and provide no substantial coverage. Gliese 146 wouldn't
1792:
link, I find it annoying to have to do this repeatedly to get past the one-sentence stubs about
English footballers, German railway stations, popular music artists, etc., and adding lots of nameless minor planets, stars and galaxies to that would only make it worse. (Looking at the talk page, I see
1580:
As for original research, if someone did a paper about a star then they would gather information in order to study it to find out more about it, and the OR would be whatever they add that is over and above what is already known. These articles don't do that and just collate already known information
1405:
The requirement that there should be a separate article about that star seems a bit artificial nowadays, when there is enough information in all the catalogues and studies of types of stars to make an article about the star. The only difference really is that the information is spread out over maybe
1351:
I am talking about. Is it clearer now? I don't want to open the floodgates to all sorts of random catalogue-like entries. When there is more than a blip on a database, and the star happens to be included in studies here and there, we go beyond that. The only issue is that no individual study tackled
695:
As
Cyclopia said, deleting these individual star articles, as far as I can see doesn't benefit the reader of wikipedia in any way at all. They don't dilute the searches since you have to search specifically for the individual star to find its article. I think those are all great points. While at the
548:
I am agreeing with
Astrocog to some extent, but with the variation that the merge may not just be to a list article, but may also be to a section in an article about a category of objects. Many of these stars may have a bit more to say than makes sense in a table. A box in a table with a paragraph
503:
clearly encourages instead of deleting the information. Everything in your quote box above could be placed into a table on a list article with greater utility than a stand-alone stub. A reader, either amateur or professional, would benefit more from having a table of data for grouped similar objects
308:
It seems to me that you're suggesting that topics which have no established notability should be included in
Knowledge (XXG); if so, that's a fairly radical change to practice which would require a much wider discussion. Having articles which essentially parrot SIMBAD for every nearby star fragments
148:
Again, just to be clear: I agree many articles about stars or other objects (e.g. minor planets) contain little information and can thus be merged in appropriate lists or linking to the appropriate catalogue. But some, even if they have never been the subject of a full paper, have enough information
2430:
We all agreed that it is not the task of
Knowledge (XXG) to become a new directory of stars, and that star articles that are little more than a brief database entry of distant stars should be deleted, this is just for eg. nearby stars with lots of information available, and is to do with helping to
2061:
If all that can be stated is from a handful of survey data, what is wrong with summing up that knowledge in a list, or a table within a section of a larger article, where context is better provided and a general reader can compare to related objects. My assertion is that is more advantageous. There
1913:
I totally agree that it would be an act of vandalism to try to turn wikipedia into a star catalogue. One line entries + a star box - no problem deleting those - unless there is a good chance they will be expanded. For objects within 50 light years, then there is a good chance they could be expanded
1236:
I do not think merging to a class-object article is such a good idea, such lists grow rather large, and have to be split off anyways, so instead, should be listed by class-object-type, it should start as a list of those, and not as a section of the class-object article. We should only list the very
494:
and carefully writing it. The purpose of NASTRO as an accepted guideline is to provide a tool to evaluate articles for inclusion related to astronomical objects - I'll briefly summarize the main rationale for not including every object in
Knowledge (XXG): doing so doesn't increase the usefulness of
469:
This is much more than a simple location-and-spectral type one-sentence kind of entry. It seems to me perfectly decent, good and reliable coverage. Even if no single source devotes itself to the star only, we can build a reasonable entry from lots of reliable, neutral sources. To meet conditions to
1991:
coverage. Coverage doesn't have to be singular in an article, but it should be substantial and not trivial (e.g. the object is listed with 1000 others, and its mass is stated). I also don't yet see a compelling reason to arbitrarily include stars within 50 light years (what's special about 50? Why
1836:
during my last stay in Germany, and obviously pop music artists are important to many people, even if maybe not us two. Your problem about kickstarting yourself is easy -just click again the random article link until you find something that you like. Much better than excluding content which can be
1544:
Thanks for sharing your view on the star articles. Most of it is a matter of what you think wikipedia is for, and though we have many guideline, still those have to be interpreted and as Cyclopedia said the main aim is to create an encyclopaedia useful to the reader. Guidelines like notability are
1446:
Second, I believe that in the absence of other interest-piquing evidence, possessing extreme brightness, velocity, color, what have you ... does not make an object notable. There is a Fritz Zwicky anecdote (which is from my education rather than my reading, so I cannot provide a citation) where a
1177:
Intersection articles do not look good, it seems a trivial intersection. Also, what of objects that belong to more than one class -this would require duplication of entries, which is nightmarish. It would also be difficult to justify a duplication with the current lists by constellations. If there
1137:
This seems an interesting suggestion, however I am unsure of how it would look like. Any examples of similar types of articles, to have an idea? Also, an object can belong to several classes, depending on how it is classified: do we want a list/article by spectroscopy? By distance to Sun? Articles
1051:
As an aside, I'll briefly defend NASTRO criteria #1, which was attacked above. Of the roughly 10,000 (my order of magnitude estimate) objects visible to the naked eye, probably a small fraction have individual articles. NASTRO grandfathers these objects in for article inclusion, because an article
677:
E.g. almost all the information about Gliese 146 would be left out in a merge - its exact spectral type, constellation, apparent magnitude, that it's a suspected variable star, that it belongs to the Hyades supercluster, its alternate names, details of its galactic orbit and motion relative to the
1986:
is perfectly capable of handling all the cases and examples that have been mentioned. The onus is always on the article creator/editors to establish notability in questionable or borderline cases. I have yet to see a compelling reason to modify the guideline. Either an astronomical object has the
1747:
raised the kind of argument I was trying to make, though not quite in the same way. My number was exaggerating for emphasis; in principle that represents what I perceive as the logical conclusion of the inclusionist spirit, one article per star that has ever been cataloged in any way, and I feel
1598:
I still stand by my original view that since Knowledge (XXG) is not a paper encyclopedia and these star articles don't turn up in searches unless you search for the star itself by name, then they don't dilute or pollute wikipedia. They also make it easier to cross reference between lists, you can
1562:
Just a couple of observations. First, where do you get your 10 from? I make it that there are about 9000 naked eye stars. For stars within 50 light years so possible to have similar amounts of information about them as Gleise 146, there are 1400 of those. So if you added a blanket approval of all
1480:
a disservice to an encyclopedia user: it wrongly suggests that there's something to that object that anyone other than a specialist might bother with. Similar to AstroCog above, I have made (and I stand by) the uncharitable comment that the extreme-inclusionist attitude naturally produces a very
1395:
Yes I agree, all good points. I think one of the things that have changed in the last few years is the increasing interest in nearby stars that are not visible to naked eye. There's the increase in the amount of information available about just about every nearby star. Also there is the increased
1373:
it makes lots of sense as a guideline. It is simply, in my opinion, that at the time such edge cases weren't taken into account, and quite reasonably so: one cannot hope to get everything right at the start. Also remember that consensus is not fixed in stone: guidelines are subject to change, and
1060:
to have significant coverage in independent sources. If an object in that list doesn't have the necessary sourcing, we could have a common sense discussion on whether to create a stub for it (I would actually vote "no"). I would gladly revisit this criteria if it could be shown that a significant
892:. Arguing that stars with no substantial individual coverage merit individual articles, because they belong to an interesting class, or because they are within some arbitrary distance, goes against one of the foundational principles of NASTRO: notability is not inherited. Just because a few users
883:
Merging to appropriate lists is the way to go, if preserving the information is wanted. It doesn't matter if there is more than one list, e.g. "List of nearby stars..." and "List of solar analogs..." that have the same objects on them. If you, or other editors, are so interested in these objects,
701:
In short, for nearby stars with a lot of information available about them, then to avoid overburdening the reader, I think putting that into separate star articles is a better way to organize the material than to attempt to put it all into one big article. It's not to do with an attempt to confer
683:
It would completely overburden any list to put all the information from the individual star articles into one huge list of say 100 stars or whatever. Also the same star may appear in several different lists, and if you attempt to include this information in any lists that mention that star, that
144:
choose to search WP for some of these objects: for example I may want to parse categories of solar twins, or of fast-proper motion stars, to look around. This is not as far-fetched as someone apparently thinks. But even if such occurrence is very low, still is a disservice to the few readers that
2420:
First, I appreciate your input especially as a professional astronomer. But interested to know, then, what is your solution to the lists issue? You say it should be considered separately, but I'm not sure the lists issue is separate from this question of notability of nearby stars. Keeping these
767:
What about the references and external links, do you put them all at the end of the whole page - or put them at the end of each section? Makes more sense if the references are about that individual star to put the references at the end of the section for that star rather than have a list for the
2366:
To address the counter-arguments presented by cyclopia: 'It is one of 500 stars...' is clearly neither notable nor relevant; 'Its speed relative to the sun is 38.1 km/s' simply repeats information available on SIMBAD (wrongly) and 'Its a suspected variable' does the same (again wrongly, it's a
2137:
and create one. If a list exists, but without a column to house an important piece of information an editor wants to include, that editor can be bold and make a new column. The choice of list to merge stub information is more within the scope of the object or list's talk page, but if you have a
616:
a list is set up be an idea? I am happy to collaborate in starting such lists as soon as possible, asking to relevant wikiprojects for help (even if I created/edited some astronomy articles, I'd prefer to have some expert input on this). At that point, I could also help in the cleanup by simply
276:
I am applying common sense. If there is no reliable source that focuses on an object, that object is not notable. I think that any other standard is unreasonable. I also see no reason to make an exception for the particular stars in question here. Please point to a reliable source that suggests
124:
unlike Earth-based geographic features, arbitrary astronomical objects are unlikely to be visited or run across by a general reader of Knowledge (XXG). Therefore, unless an astronomical object has significant coverage in the media or published sources, the likelihood that a general reader would
2503:
It seems to be a fact of life on Knowledge (XXG) that there are a number of people performing fussy activities that aren't particularly beneficial for either the readers or the editors. I see that type of behavior almost every day; just witness all the recent fuss about astronomy category name
1033:
be developed into an article, and do not provide for topics that cannot. Your proposal to water down NASTRO so that it will include these inconsequential objects in individual articles goes against the consensus of many months of debate on NASTRO, and the subsequent debate on its adoption as a
312:
I don't generally like slippery slope arguments, but one does apply here. If we make up a guideline that doesn't use reliable sources to establish notability, where does it stop? I think we all agree that we don't need an article for every star that's in a table in some paper, and I think both
965:
than mere database duplication, but where the information is fragmented among many studies and sources instead of having a single source full deep coverage. I agree we should not start from arguments of intrinsic notability (even if NASTRO explicitly allows it for many objects, e.g. naked-eye
2631:
I was going to start with something simple such as asteroid 182016 (1999 XF255) and changing "beyond its discovery in 1999." to say, "since it is a less than 5km in diameter main-belt asteroid of which hundreds of thousands of such small main-belt asteroids are known." I assume such a simple
1656:
is interesting, is not a consensus, and there are several Delete votes but also several Keep votes and clearly there are quite a few wikipedians who agree with me and Cyclopedia on the benefits of including these articles about nearby stars. The result of the discussion was "no consensus"
94:
I see that there is an ongoing effort at deleting several articles about stars. While I agree an article containing just a star location and spectral type (for example) can be safely deleted, it seems that NASTRO allows failures like allowing for the deletion of objects like (for example)
1428:
Let me admit up-front I have strong exclusionist/deletionist tendencies, though I haven't made any RfD's myself: for example, my personal preference would be that naked-eye brightness is insufficient for a star to have its own article, in the absence of other interesting data; and I am a
2488:
Thanks for keeping up with him. I think with any guideline, there will be those who abuse its recommendations, as you said. I think we'll just have to take Chrisrus on a case by case basis unless he does something extremely disruptive, in which case administrator help may be warranted.
114:
allows for deletions which are not in the interest of the readers or the encyclopedia. The articles there discussed are not mere catalogue entries: they contain encyclopedic,accurate and neutral information, and cannot be easily merged: there is no way therefore removing them actually
1396:
interest in nearby stars generally, because they could have detectable planets or debris disks, and so are targets to look at for that reason. So it is now easier to write a fair amount about a nearby star than it was a few years ago, and there is also more interest in these stars.
1122:
Well I am not really proposing merge to a list, but merge to an article on the class of object. Which article names would depend on what reliable sources write topics on. Such an article would no jsut be a table, but could ahve paragraphs on each of the non notable objects.
611:
This "shooting first, merging later" approach makes it harder to recover the information for the list by deleting stuff and then having to painstakingly ask for userfying/sending copies of deleted articles to recreate the list. Would a 1-2 weeks moratorium of nominations
2396:
Robert Walker raises a valid point about list-type articles, and the possibility of multiple redundant ones being created just because of NASTRO. I suggest this issue is considered separately, as it is important and not really related to the issues which started this
2043:
articles are made by cobbling together stuff. The significant coverage criteria is usually necessary because it usually implies that otherwise there is little or no information about the subject available to build an article. That's the spirit of GNG, as explained in
1756:, one article per object, with the data from that survey, with only the data from SDSS with the rationale that other editors can fill in other things if they want. I would consider that an act of vandalism. It seems that others would feel otherwise. Second, to
816:
It just seems a bit unwieldy, and I don't see why it is better to do things this way. It is for simplicity really, seems simpler and a better way to organize the material to have separate articles for each star even though the individual articles would be rather
2062:
isn't any prohibition against summing up this knowledge on WP. I disagree that astronomical objects are an exception to the GNG, as have many other editors in the process of creating this guideline. I think stubby information is best served by lists. Cheers,
1699:
its collective data from 20 or more survey papers (each of which has hundreds or more stars' data, and none of which single out the star under discussion for specific mention) assembles to an interesting combination ... this is in fact a violation of
103:. Both articles contain reasonably encyclopedic information about the object which is well sourced and unlikely to be controversial. Not all of this information cannot be brought to a suitable merge target, as far as I can see, thus failing somehow
2615:
not the change he is proposing? Looks like it locks for a week due to edit warring, fairly typical, not a beef against any one editor. I like the idea of not starting more than 10 AfDs in a day. That's a reasonable number, we are all volunteers
979:
As well, an inconsequential stub doesn't help anybody - the random person who does happen to look for information on a non-notable star is likely a professional, or an advanced amateur astronomer - in that case they have other, better databases to
1939:
In the recent spate of deletions there were a few stars like that, ones that were e.g. 14th magnitude distant stars hundreds of light years away, and just info copied over from the SIMBAD database. Everyone I think agrees those should be deleted.
1821:
is about the content, not about what one decides to create. There is no original research involved in deciding to create an article about a star (unless in the hypothetical circumstance one has discovered that star and publishes it first on WP).
1265:. I answer here for the sake of other readers of this discussion. I feel, from your rhetorical device, that there is still some misunderstanding instead. Perhaps I can try three toy examples to show what I mean by "watering down" the guidelines.
690:
within 50 light years, the list would just give its distance from the sun and its apparent magnitude perhaps, and say of each one whether it has planets detected yet, or debris disks, and then link to the stars individually for more information.
998:, are of service (at least potentially) to readers, and as such should be merged or kept. That guidelines disallow that means that guidelines have to be fixed, or that at least a solution to fully preserve the information has to be found. --
617:
redirecting and merging, without even passing through AFD, I suppose (in case the star is notable, the redirect can easily be reverted). It seems this makes everyone happy: no more non-notable articles, all information happily preserved. --
803:
continually moving stars off your list into separate star articles as papers are written about them, or as planets are discovered in the case of the nearby orange dwarfs. Many of them will probably eventually be found to have planets.
896:, doesn't mean we should make a mockery of the community's notability guideline with arbitrary special cases. The "unwieldy" scenario in which individual articles are created as significant coverage is made of individual objects is
2335:
for comments from an uninvolved editor, started reading, and simply ran out of steam after the first few thousand words. Have you really written a dissertation-length discussion on (what appears to me) a straightforward issue?
504:
than from having to hunt around individual stubs. Many of these cases at AfD end in merging to lists, and not pure deletion. AfD is just the standard way of going about this process currently. I encourage you to carefully read
185:
My point is that instead of following guidelines robotically we should think about our readership, and how these actions help actually readers of the encyclopedia and/or the encyclopedia itself. The sources are enough to avoid
1344:
QWERTY 467 is a G0 star in the constellation Aquila. It has been characterized spectroscopically as exceptionally metal poor . Nevertheless, it possibly has a debris disk . It belongs to the Twinkle Twinkle moving group .
384:
lacking sources that allow building an article beyond a simple catalog entry. If sources existed, they would meet point 3 of the astronomical object notability criteria. So I remain unclear how the guideline fails. —Alex
495:
the encyclopedia, it actually decreases it. Too many insubstantial stubs dilutes the overall useful information. Far more useful is to gather the trivial data and parameters for non- or marginally-notable objects into
1748:
that that is not what should come about, and the existing NASTRO correctly prevents. To take a more concrete and possible case, it ought to be possible for someone to program a bot to populate WP from the entries in
1702:- That's not how OR works. OR requires you to do your own research or to reach conclusions not stated in the sources. That's not what happens here. Collating facts from sources is exactly how every article is made. --
571:(and if you look, you'll notice that I have withdrawn all my nominations of stars which have been demonstrated to meet the GNG). Anyways, I would support a list much in the style of the minor planet lists, such as "
1481:
lengthy (ultimately, on the order of 10) series of articles about stars that, prior to the creation of their articles, were notable only for their being the brightest star not to have its own dedicated WP article.
1181:
Perhaps instead the constellation lists should be able to accomodate the information, as previously was (almost) agreed? If the "Notes" entry of the constellation lists allows that, it's a start -for objects like
2403:: I see no problem with NASTRO as currently written, at least in the arguments I read above (which wasn't all of them). There's no need to change it. Now can we all go back to applying it and writing articles?
489:
I apologize for my unwarranted assumption. I do appreciate your passion for having useful information on Knowledge (XXG). None of us would be here if we didn't share that passion. We spent many months debating
215:
aren't in dispute here. This is about notability. Something has to be notable to merit its own Knowledge (XXG) article, and these stars aren't notable (as defined by the sensible Knowledge (XXG) policy). —Alex
258:
are met by the articles above. Thus, a normally sensible guideline seems to fail for some edge cases -and it's fine, one cannot think of all possible cases when drafting a guideline. It seems thus that either
974:). In this case we have, given the particular nature of the topic, the capability to realize such articles even in cases that are accidentally excluded by the guidelines. Thus the guidelines need rethinking.
474:
is met, even if the technicality is not. Removing these articles seems to be of no help to either readers or the encyclopedia. That's why I call it a failure of NASTRO (or even of GNG, if you may wish so).
2527:
753:
but am not sure that compromise solution would work. Would you have a lot of sections with headers, like the individual star pages and edit each section just as at present people edit the individual star
534:
is not required: all the nominators should do is simply merge and redirect, which does not require deletion. And I would appreciate if possible merge targets are given explicitly. Does this make sense?
2273:
improve the encyclopedia for its readers, that's their purpose. So they seem to be failing in their purpose if when you apply them has the effect of making the information harder to read and organize.
1797:. I perceive that's what is trying to be initiated here. Like a couple of others have previously commented, and I am happy with the present NASTRO, and I do not see a need to alter it at this time.
1447:
student wanted to study a particular galaxy merely because it was the brightest galaxy in its cluster, and Zwicky's response was to the effect, some galaxy had to be the brightest in the cluster, why
1138:
can be at the intersection of several categories; a merge target needs instead to choose one overarching feature to classify for. I'm not saying "no" to the proposal, only it raises some questions. --
321:
represent good thought and consensus about the kinds of topics that are useful to readers to have their own articles, and I think that logic applies well to the particular stars we're discussing here.
2531:
2470:
2466:
81:
76:
64:
59:
447:, and while I happily call myself an inclusionist, my argument is no more "religious devotion" to it than yours is religious devotion to deletionism. If it were so, I would go around challenging
2037:
I don't agree with the sentiment from other editors above that an encyclopedic article can be made by cobbling together little bits of physical parameters from large survey papers or bulletins.
1433:. That is how some of my professional colleagues select individual stars for original research study; it is an act of individual research, correlating disparate data to identify something new.
1451:
that one? The point is that an object which is an outlier among its fellows in one of its properties need not be an object worthy of study, i.e., that doesn't make it notable by itself.
1378:. That's the point of the friendly discussion here. I understand you spent lots of energies and love into the guideline, but it doesn't mean it should now be regarded as immutable. --
1772:
was originally selected for inclusion in a research program, as hinted at in the "Spectral Type" section of that article. This is closest to, but not quite, the issues hinted at in
1545:
not to be followed blindly for their own sake but to help improve the encyclopaedia. For these star articles particularly, I doubt if it can ever become an "open and shut case".
1992:
not 60, 75, or 100?). Many of those will have coverage - but I think it's reasonable at this point to just expect the article creator/editor to include such evidence. Cheers,
47:
17:
2138:
reasonable proposal for a merging recipe that could be incorporated into the "Dealing with..." section of this guideline, then this is a good place to consider it. Cheers,
2039:- Why? You keep rehashing what NASTRO currently is, but you don't explain why it is an advantage for the public, nor how does it advance WP goal of summing up knowledge.
1780:-land. Fourth, I do see dilution of WP with one-line-plus-starbox articles of no interest as being an issue, in one concrete if trivial case. As someone who sometimes
672:
The problem with merging is that you can't merge all the information about all the stars in your list. You can't do a star box for every star in the list for instance.
1563:
stars within 50 light years then that's only 1400 max new star articles, most of which would probably never be created just as for the naked star sky articles.
785:, GL146 is in the list), but would also be in a list of the members of the Hyades supercluster, if someone decided to put a list like this one into wikipedia
1826:
I find it annoying to have to do this repeatedly to get past the one-sentence stubs about English footballers, German railway stations, popular music artists
324:
Again, I think merging the content into a single list of nearby stars would be useful, and there's no reason not to keep the star page as a redirect. —Alex (
1518:, by contrast, does not and cannot do this, from the data which exists in the astronomical literature now, and for that reason I would support deleting it.
125:
choose to search Knowledge (XXG) for an arbitrary astronomical object is quite low. This is not a matter of dubious predictions; it is just common sense.
1476:
Cluttering up an encyclopedia with thousands (or more) of articles of not even trivial/stub-class interest on astronomical objects which are unremarkable
149:
from academic literature to build a meaningful article. I think we should think about what to do with these articles, and possibly amend the guideline. --
1178:
were examples of articles that work in the same way (articles which contain a number of paragraphs about separate entries) this could help me understand.
2532:
Knowledge (XXG) talk:WikiProject Astronomical objects/Archive 22#Feedback requested for Knowledge (XXG):Bots/Requests for approval/Helpful Pixie Bot 50
563:
Yes, I think merging to a list is probably the best idea in this scenario. As has been explained by ASHill and AstroCog above, these stars do not pass
549:
of text is not as good as just a paragraph of text. However I do agree with Cyclopia that too much content is just being deleted without being merged.
2381:
Knowledge (XXG) is an encyclopaedia. As such, it is not its purpose to collate entries in catalogues or databases, simply to save someone a SIMBAD or
667:
Can you think of any way that extra individual star articles dilute the overall useful information in other articles in wikipedia for the readers?
1237:
significant examples in the class-article (such as the archetype, prototype, nearest, usual examples of the class)Â ; remember we already have a
609:
However, for now, these stars do not pass either the GNG or NASTRO, and thus have to go. There's no reason to make an exception for these stars.
572:
2632:
explanation for the casual editor is beneficial. Asteroid 9418 Mayumi was the first main-belt asteroid discovered that was similar in size. --
632:
Don't get too worried about making a new list after deletion, just remember the names of the articles and I will assist when anyone is ready.
1029:"a set of conditions that allow the topic to develop into an article". They are a set of minimum of conditions that provide for topics that
584:
295:
Repeating "it's not notable" is not really an argument. Can you explain how removing these articles helps our readers? That's the point. --
2462:
2347:
has no demonstration of non-trivial coverage in reliable sources, has no particular claim to fame I can see, and simply consists of the
1242:
1109:
594:
363:, the guidelines seem to be at odds with their own stated goals, and the general goal of helping the encyclopedia. Is it clearer now? --
1793:
I may be able to filter out stub-class articles with a .js file, something I hadn't known until now, sigh.) Fifth, Cyclopia mentioned
1151:
The suggestions I have seen are by constellation (for which we have lists), by radial distance from the sun, and by type of object eg
2454:
1463:
argument to any astronomical object article I see, and if I can't find a reason that satisfies, I'd be willing to support a delete.
1885:
263:
needs amend, or some explanation must be had of what is the help to our readers and the encyclopedia in removing these articles.--
957:
There is a misunderstanding here. We're not arguing that the stars pass GNG or NASTRO in their current form. We are arguing that
728:
there is a, say, "Notes" or "Features" entry where one can put all the published non-standard information about each object. --
526:
I appreciate your answer. What you said makes a lot of sense in general, and I agree in general (I am also very well aware of
1494:
This may seem like a divergence from my personal activities, creating or expanding articles on obscure individual stars like
1186:, which are interesting for one thing only, seems a good compromise. For others, I'm less sure, but I'd like to hear more. --
970:
foundational principle of notability: Notability is a set of conditions that allow the topic to develop into an article (see
2526:
The primary list of the 4862 minor planets being considered for re-direction to generic Knowledge (XXG) lists is located at
1204:
2641:
2625:
2606:
2588:
2569:
2543:
2515:
2498:
2482:
2440:
2411:
2290:
2165:
2147:
2084:
2071:
2056:
2001:
1949:
1845:
1806:
1710:
1666:
1633:
1527:
1415:
1386:
1363:
1250:
1215:
1194:
1172:
1146:
1132:
1117:
1091:
1006:
935:
909:
864:
839:
736:
711:
641:
625:
602:
588:
558:
543:
521:
483:
417:
398:
371:
337:
303:
290:
271:
229:
202:
180:
157:
931:
786:
394:
333:
286:
225:
176:
856:
Your points make sense -having an article would be easier and clearer indeed. Let's see what the others above think.--
1982:. I'm not going to wade into the random article discussion, which I think is beside the point of this entire thread.
1056:
be developed beyond a stub article. Criteria #1 is hardly an arbitrary cutoff - indeed, the set includes the objects
781:
Also, if the same star is in several different lists, e.g. Gliese 146 would be in a list of the nearby K type stars (
408:, so complaining about the "failure" of NASTRO is not just beside the point, it's light years away from it. Cheers,
2553:
38:
1160:
2458:
1168:
1128:
637:
554:
130:
This seems an exceptionally poor criterion for notability. The likelihood that I'll walk in the neighbourhood of
2326:
Section break to save lots of scrolling, and because this section is too big and slow for my syntax highlighter!
1082:, since there's only 7.1 billion people, but the number of astronomical objects is, well, astronomical. Cheers,
119:
readers, and it is clearly encyclopedic information. I am especially worried by this wording in the guideline:
2436:
2286:
2278:
1979:
1945:
1749:
1662:
1629:
1411:
835:
707:
580:
1829:
607:
The merging suggestion in a list as the one above is excellent. However the current approach seems backwards:
1692:
wrongly suggests that there's something to that object that anyone other than a specialist might bother with.
1156:
2409:
2360:
1284:
1246:
1113:
598:
2332:
1369:
Also: I have read the discussion that brought to NASTRO promotion as a guideline, and others. I agree that
1152:
1816:
the OR is not in the content of the articles themselves, but rather in the selection of what gets created.
1207:, even if it doesn't contain the full info that is at its own article. It seems a good example however).--
1105:
1017:
There's no misunderstanding here. I see what is being proposed, and I don't agree with it. You referenced
2579:
Why is the NASTRO page locked? Or am I being singled out? Another step backwards for Knowledge (XXG). --
2557:
2386:
2352:
2337:
2076:
We've been through that. In principle I'd agree but the problem is: which list? See above discussion. --
1238:
2471:
Knowledge (XXG) talk:WikiProject Astronomical objects/Archive 22#Straw poll: Automated stub redirection
2153:
104:
1653:
1052:
for an object that is visible to the naked eye (brighter than, say, 5 or 6 apparent magnitude) likely
2356:
1802:
1523:
1164:
1124:
633:
550:
893:
2432:
2282:
2274:
2152:
I'll point out that most of my suggestions above are taken care of in the "Special cases" section:
1941:
1740:
1736:
1658:
1625:
1407:
1075:
831:
721:
703:
576:
2390:
1983:
1789:
885:
568:
505:
500:
491:
260:
111:
2602:
2494:
2404:
2161:
2143:
2082:
2067:
2054:
1997:
1843:
1708:
1384:
1361:
1213:
1192:
1144:
1087:
1004:
952:
905:
862:
734:
623:
541:
517:
481:
413:
369:
301:
269:
200:
155:
1079:
496:
194:
concerns, so meaningful articles can be built. I fail to see the advantage in such deletions. --
2375:
1617:
96:
2637:
2584:
2565:
2539:
2478:
1507:
1452:
966:
objects! so it's hardly a "foundational principle"). We should instead start from what is the
789:(Gliese 146 is the entry HD 22496]. A star might easily end up in two or more lists like this.
359:
behind our notability guidelines. What makes it hard to keep these articles is the fact that,
2134:
2045:
1761:
1035:
1018:
995:
971:
527:
509:
355:
350:
314:
255:
247:
212:
191:
2509:
2133:
Whichever list is most appropriate for the object. If one doesn't exist, then an editor can
1288:
1200:
1183:
927:
390:
329:
282:
221:
172:
1794:
1777:
1773:
1375:
1062:
1039:
889:
564:
531:
440:
405:
318:
164:
1881:
1798:
1687:
1519:
1328:
XYZ 123456 is a star in the constellation Musca. It is a very far K2 star. (database ref)
342:
Sigh. I must have a weird curse that makes it impossible for me to explain myself clearly.
1818:
1765:
1430:
246:
it helps the encyclopedia and our readers. It usually does, for the reasons explained at
208:
187:
2393:
simply reflects that. I think the way it does so is reasonable, consistent and useful.
2618:
2596:
2490:
2157:
2139:
2077:
2063:
2049:
1993:
1838:
1757:
1744:
1703:
1511:
1379:
1356:
1277:
1262:
1208:
1187:
1139:
1083:
999:
901:
857:
750:
729:
702:
notability on the star. It is just to do with a better way to organize the material.
618:
536:
513:
476:
409:
364:
296:
264:
195:
150:
2633:
2580:
2561:
2535:
2474:
136:
1021:
to support your argument, but failed to see that every line of it is an argument
2505:
1296:
923:
888:." I have seen no compelling case that stars such as Gliese 146 merit a pass by
386:
325:
278:
217:
168:
46:
If you wish to start a new discussion or revive an old one, please do so on the
2344:
1837:
informative for many just because it isn't what you want for your breakfast.--
1781:
1621:
1515:
1456:
782:
724:
above, however for the sake of a compromise I think that a list-merge is fine
455:
377:
131:
100:
1769:
1499:
1495:
2355:. It should be deleted and redirected to a relevant list article, perhaps
240:
it is best treated with common sense, and occasional exceptions may apply.
1785:
1503:
1292:
309:
editor attention and makes useful information harder for readers to find.
1832:
argument -for example I perused articles about German railway stations
830:
What do you think about these points? Does what I say here make sense?
508:, its adoption thread (from the talk page), and especially this page:
464:
selected for the SCUBA-2 All Sky Survey for stars with debris disks.
2382:
2348:
1300:
145:
could be interested, and it carries no obvious contrasting benefit.
2528:
Knowledge (XXG):WikiProject_Astronomy/Candidates for redirection new
2467:
Wikipedia_talk:WikiProject_Astronomical_objects/Archive_21#Step_TWO
1280:
1287:
in the night sky and the second brightest star in the northern
1336:
Here we all agree that this star should not be in an article.
1304:
725:
243:
25:
1886:
4,331,285 articles in wikipedia with 198,285 added last year
242:. As all guidelines, it makes sense to apply it, in general,
1276:(α Lyr, α Lyrae, Alpha Lyrae) is the brightest star in the
1884:
Okay first about the random articles, there are currently
1776:. That is probably not likely to become an issue here in
1163:
but I suspect this does not follow reliable source usage.
977:
Also please don't make assumptions about readership as in
573:
List of stars within 26–30 light-years of the solar system
470:
do this is the purpose of notability guidelines, and this
1784:
his brain in the morning by browsing WP over his morning
110:
The point is that it seems, judging from the above, that
593:
We already have lists of stars by IAU constellation. --
2613:
1764:
is something I find easy. Third, about my comments on
1753:
349:, notability guidelines make sense for the reasons at
18:
Knowledge (XXG) talk:Notability (astronomical objects)
1460:
163:
I think that the two stars you mention plainly fail
1074:As a rhetorical device, let me ask a question from
1743:, subheading Extrapolation from number of stars.
140:. It is actually a dubious prediction that I will
1342:
1326:
1271:
886:needlessly duplicate content in these databases
461:
122:
2378:, has already been deleted so I can't comment.
2343:For what it's worth, I don't see any problem.
961:We're talking exactly of cases where there is
238:, not policy. Which is prefaced by this text:
1061:fraction of this set of objects doesn't meet
8:
2594:How about we discuss the changes you want? ―
1752:, 930,000 galaxies and 120,000 quasars from
1299:from Earth, and, together with Arcturus and
1741:Observable universe#mass of ordinary matter
1295:. It is a relatively close star at only 25
959:guidelines should be fixed so that they do.
376:The two stars you mentioned (particularly
1159:. We could do intersections of these eg
1025:your proposal. Notability guidelines are
134:is zero: so is the one that I will pet a
2351:entry turned into words, which violates
1303:, one of the most luminous stars in the
454:Now, the issue is that for example, for
1735:Thank you for the comments! First, to
2374:The other example given at the start,
2036:
1825:
1815:
1698:
1691:
1205:List of unconfirmed extrasolar planets
978:
608:
510:arguments to avoid in deletion debates
239:
44:Do not edit the contents of this page.
2385:search. This is enshrined in policy (
783:K stars between 40 and 50 light years
7:
2530:and is currently being discussed at
2455:Knowledge (XXG):I just don't like it
1978:I agree with much of the above from
1313:
250:. The issue here is that basically
2554:Talk:List of minor planets#Delete?
1339:Issues appear with article three:
1080:the notability criteria for people
900:what should be happening. Cheers,
24:
2281:) 14:52, 21 September 2013 (UTC)
1314:
1261:Thank you for your reply above,
1063:the general notability guideline
890:the general notability guideline
451:notability guideline. I don't.
29:
996:under our concept of notability
443:, I have no religious devotion
2441:15:40, 27 September 2013 (UTC)
2412:19:57, 23 September 2013 (UTC)
2291:14:52, 21 September 2013 (UTC)
2166:18:09, 20 September 2013 (UTC)
2148:18:05, 20 September 2013 (UTC)
2085:15:21, 20 September 2013 (UTC)
2072:15:14, 20 September 2013 (UTC)
2057:14:37, 20 September 2013 (UTC)
2002:14:05, 20 September 2013 (UTC)
1950:00:12, 20 September 2013 (UTC)
1846:18:11, 19 September 2013 (UTC)
1807:17:59, 19 September 2013 (UTC)
1711:11:40, 19 September 2013 (UTC)
1667:09:06, 19 September 2013 (UTC)
1634:08:36, 19 September 2013 (UTC)
1528:21:46, 18 September 2013 (UTC)
1:
2331:I came here via a request on
1654:AfD discussion for Gliese 146
1312:We all agree this is notable
986:doesn't mean it doesn't help
2570:16:23, 12 October 2013 (UTC)
2453:I see Chrisrus is up to his
1161:M type binaries in Capricorn
1618:Simbad entry for Gliese 146
1416:15:34, 30 August 2013 (UTC)
1387:14:56, 30 August 2013 (UTC)
1364:14:51, 30 August 2013 (UTC)
1251:13:36, 30 August 2013 (UTC)
1216:12:24, 30 August 2013 (UTC)
1195:12:19, 30 August 2013 (UTC)
1173:12:08, 30 August 2013 (UTC)
1147:11:17, 30 August 2013 (UTC)
1133:10:28, 30 August 2013 (UTC)
1118:04:16, 30 August 2013 (UTC)
1092:14:23, 30 August 2013 (UTC)
1007:20:43, 29 August 2013 (UTC)
982:- That a stub doesn't help
936:20:36, 29 August 2013 (UTC)
910:20:23, 29 August 2013 (UTC)
865:19:57, 29 August 2013 (UTC)
840:19:47, 29 August 2013 (UTC)
737:16:55, 29 August 2013 (UTC)
720:I agree with the spirit of
712:16:04, 29 August 2013 (UTC)
642:20:26, 28 August 2013 (UTC)
626:17:58, 28 August 2013 (UTC)
603:04:47, 28 August 2013 (UTC)
589:21:14, 27 August 2013 (UTC)
559:20:30, 27 August 2013 (UTC)
544:18:09, 27 August 2013 (UTC)
522:13:34, 27 August 2013 (UTC)
484:13:13, 27 August 2013 (UTC)
458:, we are able to say this:
418:12:59, 27 August 2013 (UTC)
399:12:51, 27 August 2013 (UTC)
372:12:24, 27 August 2013 (UTC)
338:11:46, 27 August 2013 (UTC)
304:11:19, 27 August 2013 (UTC)
291:11:15, 27 August 2013 (UTC)
272:11:05, 27 August 2013 (UTC)
230:11:00, 27 August 2013 (UTC)
203:10:49, 27 August 2013 (UTC)
181:10:47, 27 August 2013 (UTC)
158:09:54, 27 August 2013 (UTC)
2658:
2544:16:44, 15 April 2012 (UTC)
2516:16:41, 12 April 2012 (UTC)
2499:12:24, 21 March 2012 (UTC)
2483:08:37, 21 March 2012 (UTC)
1333:
684:means a lot of repetition.
2459:User:Anomie/Asteroid list
2371:variable). I could go on.
2321:Comments by Modest Genius
1739:... my 10 number is from
2642:17:44, 21 May 2015 (UTC)
2626:17:31, 21 May 2015 (UTC)
2607:17:17, 21 May 2015 (UTC)
2589:16:00, 21 May 2015 (UTC)
1984:Our notability guideline
90:NASTRO possible failures
1157:stars with debris disks
361:in these specific cases
2361:List of Gliese objects
1347:
1330:
1309:
1106:List of stars in Pyxis
466:
127:
2549:List of minor planets
1239:list of nearest stars
1153:K class solar analogs
42:of past discussions.
2357:List of nearby stars
1795:consensus can change
1376:consensus can change
1289:celestial hemisphere
1285:fifth brightest star
345:I stated above that,
2463:request for tagging
1307:'s neighborhood...
1076:reducio ad absurdum
787:Hyades supercluster
722:User:Robertinventor
439:Please remember to
277:notability. —Alex (
234:Sensible wikipedia
1750:SDSS-I and SDSS-II
347:generally speaking
254:points covered by
2624:
2461:. He made a wiki
2340:appears to apply.
2327:
1508:BD Camelopardalis
956:
441:assume good faith
87:
86:
54:
53:
48:current talk page
2649:
2623:
2605:
2599:
2325:
2080:
2052:
1841:
1706:
1382:
1359:
1319:
1318:
1317:
1211:
1190:
1142:
1002:
950:
894:like these stars
860:
732:
621:
539:
479:
367:
299:
267:
198:
190:, there are not
153:
73:
56:
55:
33:
32:
26:
2657:
2656:
2652:
2651:
2650:
2648:
2647:
2646:
2597:
2595:
2577:
2551:
2524:
2451:
2323:
2078:
2050:
1839:
1788:by hitting the
1704:
1380:
1357:
1348:
1331:
1315:
1310:
1209:
1188:
1165:Graeme Bartlett
1140:
1125:Graeme Bartlett
1000:
858:
730:
678:sun, and so on.
634:Graeme Bartlett
619:
551:Graeme Bartlett
537:
477:
467:
365:
297:
265:
196:
151:
128:
92:
69:
30:
22:
21:
20:
12:
11:
5:
2655:
2653:
2645:
2644:
2610:
2609:
2576:
2573:
2558:forum shopping
2550:
2547:
2523:
2522:Mass redirects
2520:
2519:
2518:
2501:
2450:
2447:
2446:
2445:
2444:
2443:
2425:
2424:
2423:
2422:
2415:
2414:
2398:
2394:
2379:
2372:
2364:
2341:
2322:
2319:
2318:
2317:
2316:
2315:
2314:
2313:
2312:
2311:
2310:
2309:
2308:
2307:
2306:
2305:
2304:
2303:
2302:
2301:
2300:
2299:
2298:
2297:
2296:
2295:
2294:
2293:
2245:
2244:
2243:
2242:
2241:
2240:
2239:
2238:
2237:
2236:
2235:
2234:
2233:
2232:
2231:
2230:
2229:
2228:
2227:
2226:
2225:
2224:
2223:
2222:
2221:
2220:
2191:
2190:
2189:
2188:
2187:
2186:
2185:
2184:
2183:
2182:
2181:
2180:
2179:
2178:
2177:
2176:
2175:
2174:
2173:
2172:
2171:
2170:
2169:
2168:
2150:
2108:
2107:
2106:
2105:
2104:
2103:
2102:
2101:
2100:
2099:
2098:
2097:
2096:
2095:
2094:
2093:
2092:
2091:
2090:
2089:
2088:
2087:
2017:
2016:
2015:
2014:
2013:
2012:
2011:
2010:
2009:
2008:
2007:
2006:
2005:
2004:
1980:Robertinventor
1963:
1962:
1961:
1960:
1959:
1958:
1957:
1956:
1955:
1954:
1953:
1952:
1926:
1925:
1924:
1923:
1922:
1921:
1920:
1919:
1918:
1917:
1916:
1915:
1900:
1899:
1898:
1897:
1896:
1895:
1894:
1893:
1892:
1891:
1890:
1889:
1867:
1866:
1865:
1864:
1863:
1862:
1861:
1860:
1859:
1858:
1857:
1856:
1855:
1854:
1853:
1852:
1851:
1850:
1849:
1848:
1830:WP:IDONTLIKEIT
1790:Random Article
1754:their web page
1737:Robertinventor
1722:
1721:
1720:
1719:
1718:
1717:
1716:
1715:
1714:
1713:
1695:
1676:
1675:
1674:
1673:
1672:
1671:
1670:
1669:
1643:
1642:
1641:
1640:
1639:
1638:
1637:
1636:
1607:
1606:
1605:
1604:
1603:
1602:
1601:
1600:
1589:
1588:
1587:
1586:
1585:
1584:
1583:
1582:
1571:
1570:
1569:
1568:
1567:
1566:
1565:
1564:
1553:
1552:
1551:
1550:
1549:
1548:
1547:
1546:
1535:
1534:
1533:
1532:
1531:
1530:
1487:
1486:
1485:
1484:
1483:
1482:
1469:
1468:
1467:
1466:
1465:
1464:
1439:
1438:
1437:
1436:
1435:
1434:
1421:
1420:
1419:
1418:
1400:
1399:
1398:
1397:
1390:
1389:
1355:that object.--
1341:
1325:
1270:
1260:
1258:
1257:
1256:
1255:
1254:
1253:
1229:
1228:
1227:
1226:
1225:
1224:
1223:
1222:
1221:
1220:
1219:
1218:
1203:is covered at
1179:
1099:
1097:
1096:
1095:
1094:
1069:
1068:
1067:
1066:
1046:
1045:
1044:
1043:
1015:
1014:
1013:
1012:
1011:
1010:
1009:
975:
939:
938:
919:
918:
917:
916:
915:
914:
913:
912:
874:
873:
872:
871:
870:
869:
868:
867:
847:
846:
845:
844:
843:
842:
823:
822:
821:
820:
819:
818:
809:
808:
807:
806:
805:
804:
795:
794:
793:
792:
791:
790:
774:
773:
772:
771:
770:
769:
760:
759:
758:
757:
756:
755:
742:
741:
740:
739:
715:
714:
698:
697:
692:
691:
686:
685:
680:
679:
674:
673:
669:
668:
664:
663:
659:
658:
657:
656:
655:
654:
653:
652:
651:
650:
649:
648:
647:
646:
645:
644:
577:StringTheory11
460:
437:
436:
435:
434:
433:
432:
431:
430:
429:
428:
427:
426:
425:
424:
423:
422:
421:
420:
401:
343:
322:
310:
121:
91:
88:
85:
84:
79:
74:
67:
62:
52:
51:
34:
23:
15:
14:
13:
10:
9:
6:
4:
3:
2:
2654:
2643:
2639:
2635:
2630:
2629:
2628:
2627:
2621:
2620:
2614:
2608:
2604:
2600:
2593:
2592:
2591:
2590:
2586:
2582:
2574:
2572:
2571:
2567:
2563:
2559:
2555:
2548:
2546:
2545:
2541:
2537:
2533:
2529:
2521:
2517:
2513:
2512:
2507:
2502:
2500:
2496:
2492:
2487:
2486:
2485:
2484:
2480:
2476:
2472:
2468:
2465:. (See also:
2464:
2460:
2456:
2448:
2442:
2438:
2434:
2433:Robert Walker
2429:
2428:
2427:
2426:
2419:
2418:
2417:
2416:
2413:
2410:
2408:
2407:
2406:Modest Genius
2402:
2399:
2395:
2392:
2388:
2384:
2380:
2377:
2373:
2370:
2365:
2362:
2358:
2354:
2350:
2346:
2342:
2339:
2334:
2330:
2329:
2328:
2320:
2292:
2288:
2284:
2283:Robert Walker
2280:
2276:
2275:Robert Walker
2271:
2270:
2269:
2268:
2267:
2266:
2265:
2264:
2263:
2262:
2261:
2260:
2259:
2258:
2257:
2256:
2255:
2254:
2253:
2252:
2251:
2250:
2249:
2248:
2247:
2246:
2217:
2216:
2215:
2214:
2213:
2212:
2211:
2210:
2209:
2208:
2207:
2206:
2205:
2204:
2203:
2202:
2201:
2200:
2199:
2198:
2197:
2196:
2195:
2194:
2193:
2192:
2167:
2163:
2159:
2155:
2151:
2149:
2145:
2141:
2136:
2132:
2131:
2130:
2129:
2128:
2127:
2126:
2125:
2124:
2123:
2122:
2121:
2120:
2119:
2118:
2117:
2116:
2115:
2114:
2113:
2112:
2111:
2110:
2109:
2086:
2083:
2081:
2075:
2074:
2073:
2069:
2065:
2060:
2059:
2058:
2055:
2053:
2047:
2042:
2038:
2035:
2034:
2033:
2032:
2031:
2030:
2029:
2028:
2027:
2026:
2025:
2024:
2023:
2022:
2021:
2020:
2019:
2018:
2003:
1999:
1995:
1990:
1985:
1981:
1977:
1976:
1975:
1974:
1973:
1972:
1971:
1970:
1969:
1968:
1967:
1966:
1965:
1964:
1951:
1947:
1943:
1942:Robert Walker
1938:
1937:
1936:
1935:
1934:
1933:
1932:
1931:
1930:
1929:
1928:
1927:
1912:
1911:
1910:
1909:
1908:
1907:
1906:
1905:
1904:
1903:
1902:
1901:
1887:
1883:
1879:
1878:
1877:
1876:
1875:
1874:
1873:
1872:
1871:
1870:
1869:
1868:
1847:
1844:
1842:
1835:
1831:
1827:
1824:
1823:
1820:
1817:
1814:
1813:
1812:
1811:
1810:
1809:
1808:
1804:
1800:
1796:
1791:
1787:
1783:
1779:
1775:
1771:
1767:
1763:
1759:
1755:
1751:
1746:
1742:
1738:
1734:
1733:
1732:
1731:
1730:
1729:
1728:
1727:
1726:
1725:
1724:
1723:
1712:
1709:
1707:
1701:
1696:
1693:
1689:
1686:
1685:
1684:
1683:
1682:
1681:
1680:
1679:
1678:
1677:
1668:
1664:
1660:
1659:Robert Walker
1655:
1651:
1650:
1649:
1648:
1647:
1646:
1645:
1644:
1635:
1631:
1627:
1626:Robert Walker
1623:
1619:
1615:
1614:
1613:
1612:
1611:
1610:
1609:
1608:
1597:
1596:
1595:
1594:
1593:
1592:
1591:
1590:
1579:
1578:
1577:
1576:
1575:
1574:
1573:
1572:
1561:
1560:
1559:
1558:
1557:
1556:
1555:
1554:
1543:
1542:
1541:
1540:
1539:
1538:
1537:
1536:
1529:
1525:
1521:
1517:
1513:
1512:RR Telescopii
1509:
1505:
1501:
1497:
1493:
1492:
1491:
1490:
1489:
1488:
1479:
1475:
1474:
1473:
1472:
1471:
1470:
1462:
1458:
1454:
1450:
1445:
1444:
1443:
1442:
1441:
1440:
1432:
1427:
1426:
1425:
1424:
1423:
1422:
1417:
1413:
1409:
1408:Robert Walker
1404:
1403:
1402:
1401:
1394:
1393:
1392:
1391:
1388:
1385:
1383:
1377:
1372:
1368:
1367:
1366:
1365:
1362:
1360:
1354:
1346:
1340:
1337:
1334:
1329:
1324:
1323:Article two:
1321:
1308:
1306:
1302:
1298:
1294:
1290:
1286:
1282:
1279:
1278:constellation
1275:
1269:
1268:Article one:
1266:
1264:
1263:User:Astrocog
1252:
1248:
1244:
1243:76.65.128.222
1240:
1235:
1234:
1233:
1232:
1231:
1230:
1217:
1214:
1212:
1206:
1202:
1199:(By the way,
1198:
1197:
1196:
1193:
1191:
1185:
1180:
1176:
1175:
1174:
1170:
1166:
1162:
1158:
1154:
1150:
1149:
1148:
1145:
1143:
1136:
1135:
1134:
1130:
1126:
1121:
1120:
1119:
1115:
1111:
1110:76.65.128.222
1107:
1102:
1101:
1100:
1093:
1089:
1085:
1081:
1077:
1073:
1072:
1071:
1070:
1064:
1059:
1055:
1050:
1049:
1048:
1047:
1041:
1037:
1032:
1028:
1024:
1020:
1016:
1008:
1005:
1003:
997:
993:
989:
985:
981:
976:
973:
969:
964:
960:
954:
953:edit conflict
949:
948:
947:
946:
945:
944:
943:
942:
941:
940:
937:
933:
929:
925:
921:
920:
911:
907:
903:
899:
895:
891:
887:
882:
881:
880:
879:
878:
877:
876:
875:
866:
863:
861:
855:
854:
853:
852:
851:
850:
849:
848:
841:
837:
833:
832:Robert Walker
829:
828:
827:
826:
825:
824:
815:
814:
813:
812:
811:
810:
801:
800:
799:
798:
797:
796:
788:
784:
780:
779:
778:
777:
776:
775:
766:
765:
764:
763:
762:
761:
752:
751:User:Cyclopia
748:
747:
746:
745:
744:
743:
738:
735:
733:
727:
723:
719:
718:
717:
716:
713:
709:
705:
704:Robert Walker
700:
699:
694:
693:
688:
687:
682:
681:
676:
675:
671:
670:
666:
665:
661:
660:
643:
639:
635:
631:
630:
629:
628:
627:
624:
622:
615:
610:
606:
605:
604:
600:
596:
595:76.65.128.222
592:
591:
590:
586:
582:
578:
574:
570:
566:
562:
561:
560:
556:
552:
547:
546:
545:
542:
540:
533:
529:
525:
524:
523:
519:
515:
511:
507:
502:
498:
497:list articles
493:
488:
487:
486:
485:
482:
480:
473:
465:
459:
457:
452:
450:
446:
442:
419:
415:
411:
407:
402:
400:
396:
392:
388:
383:
379:
375:
374:
373:
370:
368:
362:
358:
357:
352:
348:
344:
341:
340:
339:
335:
331:
327:
323:
320:
316:
311:
307:
306:
305:
302:
300:
294:
293:
292:
288:
284:
280:
275:
274:
273:
270:
268:
262:
257:
253:
249:
245:
241:
237:
233:
232:
231:
227:
223:
219:
214:
210:
206:
205:
204:
201:
199:
193:
189:
184:
183:
182:
178:
174:
170:
166:
162:
161:
160:
159:
156:
154:
146:
143:
139:
138:
133:
126:
120:
118:
113:
108:
106:
102:
98:
89:
83:
80:
78:
75:
72:
68:
66:
63:
61:
58:
57:
49:
45:
41:
40:
35:
28:
27:
19:
2617:
2611:
2578:
2556:Chrisrus is
2552:
2525:
2510:
2452:
2405:
2400:
2387:WP:DIRECTORY
2368:
2353:WP:DIRECTORY
2338:WP:DEADHORSE
2324:
2040:
1988:
1833:
1477:
1448:
1370:
1352:
1349:
1343:
1338:
1335:
1332:
1327:
1322:
1311:
1273:
1272:
1267:
1259:
1098:
1057:
1053:
1042:, or NASTRO.
1030:
1026:
1022:
991:
987:
983:
967:
962:
958:
897:
613:
567:, much less
471:
468:
462:
453:
448:
444:
438:
381:
360:
354:
346:
251:
235:
147:
141:
137:Velociraptor
135:
129:
123:
116:
109:
93:
70:
43:
37:
2575:Page locked
2154:WP:NASTHELP
1989:significant
1828:- That's a
1782:kick starts
1297:light-years
1058:most likely
356:motivations
105:WP:PRESERVE
36:This is an
2401:Conclusion
2345:Gliese 146
1882:BSVulturis
1799:BSVulturis
1688:BSVulturis
1622:Gliese 146
1520:BSVulturis
1516:Gliese 146
1457:Gliese 146
1453:Rutherford
1371:in general
512:. Cheers,
456:Gliese 146
445:whatsoever
404:even pass
378:Gliese 146
132:Gliese 146
101:Gliese 146
2391:WP:NASTRO
2376:HD 142093
1770:HD 122563
1500:HD 140283
1496:HD 122563
1461:"So what"
754:articles?
569:WP:NASTRO
506:WP:NASTRO
501:WP:NASTRO
492:WP:NASTRO
261:WP:NASTRO
236:guideline
112:WP:NASTRO
97:HD 142093
82:Archive 5
77:Archive 4
71:Archive 3
65:Archive 2
60:Archive 1
2619:Milowent
2612:Is this
2598:Padenton
2491:AstroCog
2449:Chrisrus
2333:WT:ASTRO
2158:AstroCog
2140:AstroCog
2079:cyclopia
2064:AstroCog
2051:cyclopia
1994:AstroCog
1840:cyclopia
1786:Cheerios
1758:Cyclopia
1745:Astrocog
1705:cyclopia
1652:BTW the
1616:Compare
1504:SN 1972e
1381:cyclopia
1358:cyclopia
1293:Arcturus
1291:, after
1210:cyclopia
1189:cyclopia
1141:cyclopia
1084:AstroCog
1001:cyclopia
980:consult.
932:contribs
902:AstroCog
859:cyclopia
731:cyclopia
620:cyclopia
538:cyclopia
514:AstroCog
499:, which
478:cyclopia
410:AstroCog
395:contribs
366:cyclopia
334:contribs
298:cyclopia
287:contribs
266:cyclopia
226:contribs
197:cyclopia
177:contribs
152:cyclopia
2634:Kheider
2616:here.--
2581:Kheider
2562:Kheider
2536:Kheider
2475:Kheider
2397:thread.
2135:be bold
2046:WP:WHYN
1036:WP:WHYN
1023:against
1019:WP:WHYN
988:anybody
972:WP:WHYN
898:exactly
528:WP:AADD
472:purpose
351:WP:WHYN
315:WP:ANOT
256:WP:WHYN
248:WP:WHYN
213:WP:NPOV
192:WP:NPOV
39:archive
2457:using
2389:) and
2383:VizieR
2349:SIMBAD
1778:WP:AST
1774:WP:SYN
1700:WP:OR.
1301:Sirius
1283:, the
1201:WASP-9
1184:WASP-9
1040:WP:GNG
992:spirit
924:ASHill
817:short.
565:WP:GNG
532:WP:AFD
406:WP:GNG
387:ASHill
326:ASHill
319:WP:GNG
279:ASHill
218:ASHill
169:ASHill
165:WP:GNG
2560:. --
2534:. --
2369:known
1834:a lot
1819:WP:OR
1766:WP:OR
1697:Also
1431:WP:OR
1108:) --
1104:(ie.
1038:, or
749:Yes,
614:until
449:every
209:WP:OR
188:WP:OR
117:helps
16:<
2638:talk
2585:talk
2566:talk
2540:talk
2511:talk
2495:talk
2479:talk
2469:and
2437:talk
2287:talk
2279:talk
2162:talk
2144:talk
2068:talk
1998:talk
1946:talk
1803:talk
1762:that
1663:talk
1630:talk
1620:and
1524:talk
1412:talk
1353:only
1281:Lyra
1274:Vega
1247:talk
1169:talk
1129:talk
1114:talk
1088:talk
968:real
963:more
928:talk
906:talk
836:talk
708:talk
638:talk
599:talk
555:talk
518:talk
414:talk
391:talk
330:talk
317:and
283:talk
222:talk
211:and
207:But
173:talk
2506:RJH
2359:or
2041:All
1880:Hi
1449:not
1320:.
1305:Sun
1241:--
1155:or
1054:can
1031:can
1027:not
994:of
726:iff
382:are
252:all
244:iff
142:not
107:.
99:or
2640:)
2622:•
2587:)
2568:)
2542:)
2514:)
2497:)
2481:)
2439:)
2289:)
2164:)
2156:.
2146:)
2070:)
2000:)
1948:)
1805:)
1665:)
1632:)
1526:)
1510:,
1506:,
1502:,
1498:,
1478:is
1414:)
1249:)
1171:)
1131:)
1116:)
1090:)
984:us
934:)
930:|
926:|
908:)
838:)
710:)
640:)
601:)
587:)
583:•
557:)
535:--
520:)
475:--
416:)
397:)
393:|
389:|
380:)
336:)
332:|
328:|
289:)
285:|
281:|
228:)
224:|
220:|
179:)
175:|
171:|
2636:(
2603:✉
2601:|
2583:(
2564:(
2538:(
2508:(
2493:(
2477:(
2435:(
2363:.
2285:(
2277:(
2160:(
2142:(
2066:(
1996:(
1944:(
1801:(
1661:(
1628:(
1522:(
1410:(
1245:(
1167:(
1127:(
1112:(
1086:(
1065:.
955:)
951:(
904:(
834:(
706:(
636:(
597:(
585:c
581:t
579:(
553:(
516:(
412:(
385:(
216:(
50:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.