Welcome to mapoid.com on July 5 2009.
This is an internet experiment running to monitor browsing habbits of individuals through wikipedia contents.

Wikipedia:Bot requests

From Wikipedia, the free encyclopedia

Jump to: navigation, search
Shortcuts:
WP:BOTREQ
WP:BOTR
WP:BTR

This is a page for requesting work to be done by bots per the bot policy. This is an appropriate place to simply put ideas for bots. If you need a piece of software written for a specific article you may get a faster response time at the computer help desk. You might also check Wikipedia:Bots/Status to see if the bot you are looking for already exists, in which case you can contact the operator directly on their talkpage.

If you have a question about one particular bot, it should be directed to the bot owner's talk page or to the Bot Owners' Noticeboard. If a bot is acting improperly, a note about that should be posted to the owner's talk page, to the Administrators' Noticeboard. A link to such a posting may be posted at the Bot Owners' Noticeboard.

If you are a bot operator and you complete a request, note what you did, and archive it. {{BOTREQ}} can be used to give common responses, and to make it easier to see at-a-glance what the response is.

There are a number of common requests which are regularly denied, either because they are too complicated to program, or do not have consensus from the wikipedia community. Please see Wikipedia:Bots/Frequently denied bots for a list of such requests, and ensure that your idea is not among them.

If you are requesting that a bot be used to add a WikiProject banner to the talkpages of all articles in a particular category or its subcategories, please be very careful to check the category tree for any unwanted subcategories. You might not expect Category:World War II to be a subcategory of Category:Thailand, but it actually is, and a bot will find it! It is usually safer to give a complete list of categories that should be worked through individually, rather than one category to be analysed recursively. Compare a successful request with a similar one that made a mess.

Commonly Requested Bots
Newsletter delivery · Talkpage Archiving · Template substitution ·
WikiProject tagging  · Article autoassessment

Archives (Index)
Archive 1 Archive 2 Archive 3
Archive 4 Archive 5 Archive 6
Archive 7 Archive 8 Archive 9
Archive 10 Archive 11 Archive 12
Archive 13 Archive 14 Archive 15
Archive 16 Archive 17 Archive 18
Archive 19 Archive 20 Archive 21
Archive 22 Archive 23 Archive 24
Archive 25 Archive 26 Archive 27
Archive 28 Archive 29


Contents

[edit] Bot to judge suitability of potential admins

As outlined at WT:RfA#WT:RfA.

This bot would take a user and look through the things which are considered in an RfA (so for example: What areas they take part in, block log, how much interaction they have with other users, how many AN/I threads there have been about them ;), what (if any) warnings they have received, etc. etc.) and then give the user a "score" of how good an admin they would make, it could also find the average score of failed/successful noms over the past month(s) and compare the user to that.

The way to do this which seems best (as we don't want the results to be public), is to have a page where users can request to be reviewed (optionally) and the bot will then email their results to the user via Special:EmailUser.

There is also talk about having a bot "fail" users before they go for RfA. It seems to be a bad idea to add this immediately, but it would be nice to have the bot save data about whether it would have failed them, if it was allowed to. - Kingpin13 (talk) 08:37, 17 June 2009 (UTC)

I guess the hardest part of this would be to work out all the metrics, if you intended to have an overall conclusion. - Jarry1250 (t, c) 09:50, 17 June 2009 (UTC)
Aye. But this should be possible through trial and improvement. By comparing results of past candidates. - Kingpin13 (talk) 10:16, 17 June 2009 (UTC)
What a horrible idea! Having sacks of bolts to pass judgement on human behaviour and hand out scores? Who in the world would have access to the results if they were not public? The small bunch of people who hangs at RfA? If the data is available upon request, who decides who has access? If it's no one, then the data is public, despite you saying otherwise. By querying the bot? Then what's to stop people from using it on non RfA candidates? I mean there's problems with the RfA process and the RfA folks, but this is something else. If you're getting too lazy to go through {{usercheck-full}} (which compiles everything you could possibly know about the user, with links to searchs at ANI and all these other alphabet soup location) or a variant of it yourself, don't !vote at RfA! Headbomb {ταλκκοντριβς – WP Physics} 13:38, 17 June 2009 (UTC)
It's for he use of potential candidates to use to gain confidence/not go for RfA and avoid the disappointment of failure. The results are emailed to the user who requests them, so to find out someone else's score you would have to hack into their account or email. You seem to think it's designed for !voters, that's not the idea. - Kingpin13 (talk) 13:44, 17 June 2009 (UTC)
Ah, well if that's the case, then disregard my previous remarks. Although I would worry about giving them false hopes of success. Headbomb {ταλκκοντριβς – WP Physics} 14:13, 17 June 2009 (UTC)
  • Comment As I stated at WT:RFA, I feel this is an excellent idea. It's not going to be a simple thing to code, though, as there are a lot of factors to figure out and weight. Enigmamsg 16:54, 17 June 2009 (UTC)
  • As a completely opt in private assessment bot, there really is nothing to object to. However, getting a reasonable accurate score would be quite a programming task. More specifically, while a number of disqualifiers can be identified (insufficient edit history, recent blocks, lack of edits it certain areas, etc), it will struggle in accurately assessing candidates that don't have any obvious problems. The reason is that assuming someone meets all the unofficial criteria, they will pass or fail based on subjective (and realistically incomplete) information gathered from their edit history. That is, the pass or fail will depend on what is unearthed about their past and how that information is viewed. --ThaddeusB (talk) 21:00, 17 June 2009 (UTC)
  • I think I had a hand in starting this idea off, there could be some truly terrible results from this or something really useful - depending on how it was setup and run. At one extreme a black boxed set of software that predicted whether or not someone would pass RFA based on the last 12 months RFAs would soon prompt questions such as What was your score on RFAbot? and of course would risk all sort of positive feedback loops as it came to influence who passed RFA. On the other hand an RFA bot that judged how a candidate fared against a set of criteria that each RFA voter could tweak would be of useful, but it would have to be parameter driven - eg a hypothetical criteria, variables marked in italics:
  1. clean block log for at least 12 months
  2. At least 300 edits last month and in at least two other months in the last 5
  3. No warnings in the last three months and show me any in the last 6 months
  4. No civility or npa warnings in the last 18 months.
  5. At least 3,000 edits disregarding 90% of minor or automated edits.

ϢereSpielChequers 18:26, 25 June 2009 (UTC)


It should be noticed that this proposal is just to determine how accurate a bot is compared to a bureaucrat in "closing" and RfA. The data would be compiled over the course of 6-12 months, and then reviewed. Whatever the outcome, the data would be useful and would also either shoot down the idea of a bot doing it or support it. ···日本穣? · Talk to Nihonjoe 23:35, 22 June 2009 (UTC)

Comment This sounds like people want a statistical analysis done of past RFA decisions, as in a logit regression analysis, or a neural net prediction model. Creating such a prediction model would be an easy analysis for anyone knowledgeable who has a statistical software package, if the candidate variables were collected in a table for a bunch of past RFA decisions, but it is not the same a running a bot! doncram (talk) 01:25, 29 June 2009 (UTC)

90% sounds like too much for minor edits, about right for automated, but I think minor edits should be about 75% - Kingpin13 (talk) 13:06, 1 July 2009 (UTC)

[edit] Accessdate formatting bot

Could we have a bot edit the accessdate parameter in templates such as {{Cite book}} from something like 2006-02-07 to something like 7 February 2006? Numbers and dashes look messy, in my opinion, and the dates used to be linked before the delinking thing, so they were never intended to look like they do now. It Is Me Here t / c 18:04, 25 June 2009 (UTC)

Agreed that the dashed format is bad, but I don't think that a bot can really do this unless it detects what date formatting style (DMY or MDY) is used in the rest of the article. –Drilnoth (T • C • L) 18:14, 25 June 2009 (UTC)
I love the pseudo-ISO format, unambiguous, multilingual, and short. If anything I'd change pages to using the pseudo-ISO format for accessdate. However, auto-formatting is actually support with {{#formatdate:}}, no idea what it isn't implemented to the citation template. — Dispenser 19:20, 25 June 2009 (UTC)
OK, in that case, if you can provide me with the exact code to edit Template:Cite web (etc.), then I shall boldly do so. It Is Me Here t / c 20:18, 25 June 2009 (UTC)
The citation templates have been combined into a single core at Template:Citation/core. From discussions their the issue seem to be somewhat complex. Non-linked autoformatting might be banned from the discussion and Arbcom ruling over linked autoformatting. Disputes over which of the three formatting should be used and that doing it automatically is not a good idea. I also remember reading a proposal to have date standardization function similar to {{DEFAULTSORT:}}, but I don't think anything come of it yet. However, one thing seems to be clear that the article should have consistent formatting. So I am wrong with my previous bot assessment.
The bot would convert from ISO if all dates are pre-2009, when the ISO format was a techinal requirement. It would also have to convert dmy and mdy to the dominate format used (lets say 80%). — Dispenser 23:34, 25 June 2009 (UTC)
I believe bug 17905http://bugzilla.wikimedia.org/show_bug.cgi?id=17905 is related to the DEFAULTSORT-like proposal. As for the bot request, IMO it's Not a good task for a bot Anomie 11:23, 26 June 2009 (UTC)
I have created {{DEFAULTDATEFORMAT}} for use by bots until the bug gets resolved. — Dispenser 20:47, 28 June 2009 (UTC)

[edit] Poop Patrol

Hi, every now and then I patrol various parts of the pedia for particular words that are either commonly misused or an indicator of vandalism/attacks. But for those with a high proportion of false positives its a complete pain to search again a few months and have to trawl the whole lot to find a few new errors. What I would like to be able search for are for example articles containing the word "poop " but not containing the words "poop deck" or "poop cabin" and that didn't contain that word on "dd/mm/yyyy". However if that isn't too practical could I have a bit of code that lets me specify a word or phrase, whether I'm looking though article space user space or user talk and a sandbox to write it to. Provided the query refreshed the sandbox with a list of the resulting article names in square brackets and in alpha order I think I can do the rest simply by looking at what has changed since last time the query was run, though it would be even better if the list contained article links and the date they were added to the sandbox, and were in date order.

I've tried searching for "posses " and written the search to User:WereSpielChequers/posses, but they don't come up as clickable. However it does give an idea as to what I'm searching for. ϢereSpielChequers 19:25, 25 June 2009 (UTC)

The best way to scan the 'pedia quickly for complex combinations of words is to get a dump and use AWB's database scanner gizmo, I always think. Unfortunately I can only just squeeze 512mbits/sec fom the copper wiring, so I've never tried it myself. - Jarry1250 [ humourousdiscuss ] 19:39, 25 June 2009 (UTC)
Just realised I didn't actually read what you wrote. Oh well. I'll leave that ^ there anyway just in case it's handy to others. - Jarry1250 [ humourousdiscuss ] 19:40, 25 June 2009 (UTC)
Related. – Quadell (talk) 20:08, 25 June 2009 (UTC)
Thanks guys, to give a simpler example, when I search for "posses " there are over a hundred articles that legitimately contain that word, it would save a lot of faff if a bot could help me ignore the ones I've patrolled before. Is that technically possible? ϢereSpielChequers 21:30, 28 June 2009 (UTC)

[edit] Bot to remove {{popcat}} from categories which it is not needed

I've started a discussion at Category talk:Underpopulated categories#The Underpopulated categories cat is Overpopulated! regarding how to de-populate that category. My idea is to have a bot systematically clean up that category by removing {{popcat}} from all those categories that either:

a.) already are populated with a certain numbered amount of articles, and/or

b.) have been tagged with {{popcat}} for a certain amount of time, or that fall within a certain date period (in which case a date= parameter may be needed?)

Is it possible to have a bot be able to automatically determine these things? -- œ 19:17, 27 June 2009 (UTC)

Looks pretty simple. A date parameter will probably not be needed, because the bot could determine when the template was added from the history. I assume that you want arbitrary numbers for the two things you mentioned above; what do you think they would be? The Earwig (Talk | Contribs) 19:25, 27 June 2009 (UTC)
That I'm not so sure about and would like more input from the community, but I suggest 10+ articles with the tag being in place for at least a year. -- œ 12:47, 28 June 2009 (UTC)

[edit] bio-photo-bot

As part of a larger project to address the list of requests for photographs I would like assistance creating a bot script to sort out photo requests of people. I have no experience of Python or similar script languages. I started the task using AWB but it became clear it would take me a couple of years to complete it with that method. See User:Traveler100/bio-photo-bot for details. Traveler100 (talk) 09:06, 28 June 2009 (UTC)

OK no one interested, could someone point me in the direction of some Python source code examples of replacing text in articles so I can see if I can work this out myself.Traveler100 (talk) 13:49, 4 July 2009 (UTC)
That's not a good idea, you shouldn't be removing the tags from the WikiProject banners, they have these for a reason, you should simply add the banner later on in the page if need be. Although a bot to go though those lists and remove any that have images would be a good idea because last time I had a look all the ones I clicked on had images. Peachey88 (Talk Page · Contribs) 14:17, 4 July 2009 (UTC)
The tag in the WikiProject is no longer of any use, there are thousand are requests in each of the current titles and are mixed up with with articles from many other projects. The reason for removing and not just added a new tag is track how complete the process would be.Traveler100 (talk) 15:01, 4 July 2009 (UTC)
I don't believe a bot to remove ones that have pictures is a good idea. A bot cannot tell what a picture is of so it cannot determine if a given picture satisfies the request. For example, a biographical article may have a picture of something else, but be missing a picture of the person. I suppose it could be limited to pictures in infoboxes, but even that I think would be prone to false positives. Generating a list for human review is a better option. -- JLaTondre (talk) 14:31, 4 July 2009 (UTC)
It turns out there is already a bot who checks for this. PhotoCatBot adds articles to Category:Articles which may no longer need images if they have images. -- JLaTondre (talk) 14:44, 4 July 2009 (UTC)
there is a tool check if articles in these categories have images. You have to go through manually, which I have been. All 10,000 articles in people needed image are valid requests.
Traveler100 (talk) 14:59, 4 July 2009 (UTC)
Given PhotoCatBot is already classifying image requests (in addition to listing ones with pictures), you may wish to directly ask Twp if he wants to take this on. -- JLaTondre (talk) 15:10, 4 July 2009 (UTC)

[edit] NRHP banners

This is a long request, hope that it is composed properly! I would most appreciate a bot to be run to add WikiProject NRHP banner to many articles that have been created in the last year without banners, perhaps 1,000-4,000 in number, adding to the 20,000 articles in the wikiproject. This request reflects feedback on format of bot request from Wikipedia:Bot requests/Archive 28#Advance questions for a WikiProject NRHP banner placement bot.

I am hoping it would show results before July 4, so as to inform some press-release type announcements on that day or a day or two before, but will be glad to get any help. Thanks in advance! doncram (talk) 01:19, 29 June 2009 (UTC)

Part 1. Request that all articles in wikipedia whose titles begin with "National Register of Historic Places listings in" be tagged with this banner, {{WikiProject National Register of Historic Places|class=list}}, retaining existing assessments if any. Unless the article is a redirect, then do not add any banner.

Part 2. Request that all articles in the following NRHP categories be tagged with this banner, {{WikiProject National Register of Historic Places}}, retaining existing assessments if any. Unless the article is a redirect, then do not add any banner.

Doing... Anomie 03:56, 29 June 2009 (UTC)
Thanks, and it looks basically good. But I notice for List of Registered Historic Places in Wexford County, Michigan and others, it is adding banners for redirects, contrary to the bot request. I am not sure if / how much this is a problem, as i was unsure beforehand about whether redirects should be tagged or not, so I don't expect it is worth going back to undo all of those. But I did try to ask for the bot request to exclude them. :) doncram (talk) 14:22, 29 June 2009 (UTC)
In fact, since i think the bot is halfway through the state categories lists, i think it is best for it to continue as it is, tagging the redirects that have NRHP categories. To be considered by the wikiproject as a group, not a bad thing. doncram (talk) 14:57, 29 June 2009 (UTC)
Doh! I set the bot up to skip redirects, and then I changed it around and forgot to re-set it. Anomie 17:04, 29 June 2009 (UTC)
It looks done. Total for wikiproject went from 20,400 at start to 23,372 now, adding about 700 list-articles among a total of 3,000 added. Plus about 100 redirects added (not counted as wikiproject articles). Others seem to be busy categorizing the new, unassessed ones. Thanks so very much! doncram (talk) 23:41, 30 June 2009 (UTC)

[edit] Prep element infoboxes for update of master template

Bot request no longer needed.

If anybody is interested, please complete this bot request. Add the below parameters to each element infobox, which are all in Category:Periodic table infobox templates. |namecap= |number3=

At the same time, create some values. Values for namecap will be capitalized versions of what is already in the name field. For template:Infobox copper the name value is copper so the corresponding namecap value should be Copper

Values for number3 should be the 3 digit version of what is already in the number field. For copper, the number value is already 29 and the number3 value should therefore be 029. Of course, any element that already has a three digit value in the number field should just have that value copied over to number3. Like so: |namecap=Copper |number3=029

Also, please replace spaces between words in the values given for crystal structure with plain old ascii hyphens (-). Example, cubic face centered becomes cubic-face-centered. You will find oddball values - that's fine, we know that there will be manual clean-up and will do that ourselves.

Addendum: Put .jpg at the end of each value given in the image name field. Note that not all fields have values. Once the bot run is over, replace the text at Template:Elementbox with the text at User:Mav/Sandbox/Elementbox. Project members will manually fix any oddities.

All of the above per discussion on WikiProject Elements' talk page. Thanks for any help you can provide! :) --mav (talk) 01:24, 29 June 2009 (UTC)

While you are at it, please also add |image ext=.jpg to each infobox. Thanks. --mav (talk) 01:42, 29 June 2009 (UTC)

Is there any particular reason not to use {{ucfirst:{{{name}}}}} and {{padleft:{{{number}}}|3|0}} as needed in the template code instead of creating the two extra parameters? And any reason (besides breakage for a few minutes while the bot runs) the .jpg can't just be included in the image name? Anomie 02:25, 29 June 2009 (UTC)
I was not aware of those templates. I'll test them. Avoidance of breakage was the intent of having a separate param for the extension. But having a single param is cleaner. Let's put this request on hold for now. --mav (talk) 03:13, 29 June 2009 (UTC)
Test successful. Thank you so much for the pointers! :) Addendum and strikeouts above. --mav (talk) 03:42, 29 June 2009 (UTC)
I had to strike the space to hyphen part too. Is there a way to accomplish the same thing w/o changing the values? The purpose is to create image links to images of the crystal structures (all such images have hyphens instead of spaces). --mav (talk)
No, the devs are strongly opposed to giving us useful string manipulation functions for some reason. About all you could do is a #switch to translate the "normal" values into image names. Or go back to the idea of having the bot change them. Anomie 04:02, 29 June 2009 (UTC)
The number of cases is small, so I think #switch will work nicely as project members manually fix the broken infobox parts. Thanks again! Way past time for bed - I'd like to create some cases before the bot does its thing, so if possible please hold this request until then. You have been most helpful. :) --mav (talk) 04:30, 29 June 2009 (UTC)

For what it's worth, most elements don't use Template:Elementbox. It's a tedious conversion process and it's been on my to-do list for ... awhile. --MZMcBride (talk) 04:54, 29 June 2009 (UTC)

There probably should be a bot run just to prevent all the hacks that are being suggested. Anyway a hack for images lacking .jpg extension is {{{image name}}}{{#ifexist:{{{image name|}}}.jpg|.jpg}}. — Dispenser 07:43, 29 June 2009 (UTC)
#ifexist doesn't work for images on Commons; I believe it checks for the existence of the the file description page and not the file itself, and Commons images of course have no local description page. What are the hacks you're complaining of? Surely not the use of core functions like ucfirst or padleft for the exact purpose they are intended? Anomie 12:12, 29 June 2009 (UTC)
#ifexist does work with external repos (like Commons) if you use Media: as I recall ({{#ifexist:Media:Foo.jpg|...}}). I'm not really sure I see a need for bots anywhere here. It's like thirty pages that use {{Elementbox}}.... --MZMcBride (talk) 13:38, 29 June 2009 (UTC)
"Media:" works? Nifty, I'll have to remember that. Anomie 17:02, 29 June 2009 (UTC)

Hm. Seems like the remaining conversion issues could just as easily be done with a tabbed browser due to the fact that only 30 elements use the elementbox template. Please cancel the bot request and accept my gratitude for all the great advice and pointers to improve the template. :) --mav (talk) 00:15, 30 June 2009 (UTC)

43 mainspace pages transclude {{Elementbox}}, 44 templates. Anomie 01:36, 30 June 2009 (UTC)
All fixed manually. I think all is well now - thanks again! --mav (talk) 03:40, 30 June 2009 (UTC)

[edit] db-author and db-self bot

Is there any interest in a bot that would handle non-controversial db-author and db-self chores?

What I had in mind:

  • Check if requester is blocked, if yes, do not delete
  • Check if the page has had any kind of protection on it recently, if yes, do not delete.
  • For db-author, check to see if page has any edits by other editors, if yes, do not delete.
  • For db-user, check to see if page is in the correct user: space. If not, do not delete.
  • For both, check move history to make sure it has never been moved. If moved, do not delete.
  • Delete if okay to delete.
  • If deleted, notify the requester and give the requester instructions to shut off the bot and request restoration if there was a problem.
  • If not deleted, add a template indicating bot refused to delete. Administrators can watch the category that the template adds.
  • Log the results.

The primary issue is that this would be an admin bot. It would only be useful if the benefits of the bot outweighed the risk of a snafu and that this wasn't seen as "admin bot creep," which is always something to watch out for. Good code review should make snafus almost unheard of. davidwr/(talk)/(contribs)/(e-mail) 00:38, 30 June 2009 (UTC)

I'd be willing to devote a little bit of my time to writing this. Coding... (X! · talk)  · @092  ·  01:12, 30 June 2009 (UTC)
Good. Now all we need is consensus that this is a good idea. davidwr/(talk)/(contribs)/(e-mail) 14:28, 30 June 2009 (UTC)
Just a quick Q - is {{db-author}} ever used when no one else has edited? Normally it is added after a third party has edited the article to point out it doesn't meet our guidelines (by adding a notability template/speedy tag) and the original author realizes their error. --ThaddeusB (talk) 19:15, 30 June 2009 (UTC)
User:SDPatrolBot curretly tags pages which creators blank after they have been tagged for deletion - Kingpin13 (talk) 19:19, 30 June 2009 (UTC)
Db-author is sometimes used where db-user would also be appropriate. I would assume it's also used if an author changes his mind on his own or after being notified off-page, such as on a talk page or by email. However, your point is a good one, many db-authors will be bypassed by the proposed bot. davidwr/(talk)/(contribs)/(e-mail) 14:48, 1 July 2009 (UTC)
Yes, I agree that g7 is nearly always added by another user (a point I was trying to illustrate with my bot). But I think this could be useful in cases where a user recreates a page when tagging it for deletion (this normally happens with Twinkle), and then they are the only editor, and they quickly change to g7. - Kingpin13 (talk) 14:55, 1 July 2009 (UTC)
  • Please don't automate this. The load of {{db-author}} requests isn't very high and isn't overwhelming C:CSD, and there are often reasons to keep a page around (say, somebody else links to it or transcludes the page). Better to leave this to humans. Kusma (talk) 15:25, 1 July 2009 (UTC)
    • I agree with Kusma. The actual deletion shouldn't be automated because there are so many things that need to be checked (although automated tagging of author-blanked pages would be good). –Drilnoth (T • C • L) 16:05, 1 July 2009 (UTC)
      That's what User:SDPatrolBot does, so no need for another bot (although I don't object to there being one). Also, I think the things which would be checked are pretty good, and I the bot would probably make 0.5% mistakes, and not make the same one twice (so long as the code was updated), so we could get it pretty good. But I don't think there is a huge need for this bot (although again I really don't mind if there is), as admins keep this area well under control - Kingpin13 (talk) 16:15, 1 July 2009 (UTC)
    The bot should skip if the page is being transcluded by others. –xenotalk 16:18, 1 July 2009 (UTC)
    Good point, similar to that, if it's a category, you may want it to check if there are any pages in it - Kingpin13 (talk) 16:22, 1 July 2009 (UTC)
  • Once more, this bot is not needed. There is no problem that it solves that is worth even an (optimistic) error rate of 0.5%. In particular, the bot won't be able to check whether the incoming links indicate that the page should be kept despite the author's wishes. WP:CSD#G7 is done as a courtesy, having their page deleted is not an author's right. Kusma (talk) 16:49, 1 July 2009 (UTC)

[edit] CAS and EC Nos

Most chemicals in Wikipedia have a CAS No. listed, but most do not have the corresponding EC No.

the template:chembox, the field to fill in is "EINECS".

By using a CAS No. in the following url, e.g. http://ecb.jrc.ec.europa.eu/esis/index.php?GENRE=CASNO&ENTREE=124-38-9 where the CAS No. is 124-38-9, you can identify the corresponding EC No. and then insert it into the Wikipedia article.

Any takers?—Preceding unsigned comment added by 86.166.233.138 (talkcontribs)

This is less simple than it looks. A) is the CASNo that is listed correct (we are working on that, but the majority of the 9000 boxes is not checked), B) is the EINECS listed correct against the CASNo. I would not suggest this automated, but manual using a carefully selected database. --Dirk Beetstra T C 19:30, 2 July 2009 (UTC)
And it would be much better to get the whole list of numbers in one file for the bot to process, rather than having a bot submit 9000 queries into their website. Anomie 20:01, 2 July 2009 (UTC)
If this is done in some way (Anomie's way is thé way forward), please do this together with Wikipedia:WikiProject_Chemicals/Chembox_validation. They have access to a lot of verified data. --Dirk Beetstra T C 08:20, 3 July 2009 (UTC)
Personal tools

Visit joltnews for the latest headlines
Visit bloit.com for company information
Geed Media does computer consulting on long island.
This page viewed times. See Logs