Commons:Administradors

interfície en català Administradors en altres llengües: Alemannisch | asturianu | български | brezhoneg | català | dansk | Deutsch | English | español | فارسی | suomi | français | magyar | italiano | 日本語 | 한국어 | Lëtzebuergesch |

Shortcut: COM:A· COM:ADMIN

Administrators as of June 2013 [+/−]

Listing by language Listing by date

Number of Admins: 272 1Veertje, nl, en-4, de-1, fr-1 32X, de, en-2, hsb-1, ru-1 99of9, en (bureaucrat) á, fi, en-2, sv-2 A.Savin, ru, de-4, en-2 Adrignola, en AFBorchert, de, en-3 Ahonc, uk, ru-4, en-2, de-1 Aka, de, en-3 Alan, es, eu-3, en-2 Ala z, pl, en-2, ru-1 ALE!, de, en-3, es-3, fr-1, it-1 Alhen, es, en-2 Alison, en, ga-3, fr-2, gd-1 Alno, fr, en-3, es-2, pt-1 Alpertron, es, en-3 Amada44, de, en-3, fr-1 Angr, en, de-4, fr-2, ga-2, la-2, cy-1 AnRo0002, de, en-2, fr-2, es-1 Anthere, fr, en-3 Aude, en, ar-3 Avenue, en, de-1, fr-1, it-1 Avraham, en, he-2 (oversighter, steward) AVRS, ru, en-2, eo-2 Axpde, de, en-4, es-1, fr-1, it-1, nl-1 AzaToth, sv, en-4 Badseed, el, en-3, it-1 Bapti, fr, en-3, de-2 Barcex, es, en-2, fr-1 Bastique, en, fr-3, es-2, la-2, ga-1 Bdk, de, en-2 Bencmq, zh, en-3 (steward) Benoit Rochon fr, en-4 Beria, pt, en-2, es-2 Bidgee, en Billinghurst, en (steward) Blackcat, it, en-3, fr Blacklake, ru, en-2 Blurpeace, en, es-1 Butko, ru, uk-2, en-1 Cambalachero, es, en-3 Captain-tucker, en Cecil, de, en-3, fr-2, es-1, fi-1 (bureaucrat) Chatama, ja, en-1 Chris 73, de, en-3, ja-1 ChrisiPK, de, en-3, fr-1 ChristianBier, de, en-3 Ciell, nl, en-2, de-1 Cirt, en, es-2 Common Good, en CommonsDelinkerHelper (bot) Cookie, es, en-2 Courcelles, en, es-2, fr-2 Coyau, fr, en-1 DaB., de, en-1 Dantadd, it, pt, en-3, es-3, fr-3, gl-3, ca-2, ro-1, el-1 Darwinius, pt, en-3, es-2, fr-2, gl-2, ca-1, it-1, oc-1 Davepape, en David Levy, en Dcoetzee, en, fr-2, et-1, af-0 Denniss, de, en-2, fr-1 Dereckson, fr, en-3, de-1, nl-1 Didym, de, en-2, fr-2 D-Kuru, de, en-2, it-1 Dschwen, de, en-3, fr-1 (bureaucrat) Edgar181, en, de-1, fr-1, es-1 Effeietsanders, nl, en-3, de-1, fr-1, la-1 Ejdzej, pl, en-2 Elcobbola en, de Elitre, it, en-3, fr-2 Elya, de, en-3, uk-2, ru-1 EPO, da, en-3, de-1 Érico Júnior Wouters, pt, en-2, es-2 Esby, fr, en-3, de-1 EugeneZelenko, ru, be, en-2, bg-1, pl-1 (bureaucrat) EVula, en Ezarate, es-3, en-1 Fanghong, zh, en-2, fr-1 Fastily, en, fr-2, zh-2 Flominator, de, als, en-3 Foroa, vls, nl, en-3, fr-2 Funfood, de, en-2, bar-1 FunkMonk, da, en-4, no-3, fo-2, sv-2, de-1, es-1 Geagea, he, ka-3, en-3, ru-1 Geni, en George Chernilevsky, ru, uk-3, de-2, en-2, bg-1, la-1, be-1, fr-1 GeorgHH, de, en-1 Gestumblindi, als, de, en-3 Gmaxwell, en (checkuser) Gnangarra, en Golbez, en, ja-2 Greudin, fr, en-2, de-1 grin, hu, en-3, de-1 Gruznov, ru, en-1, fr-1 guillom, fr, en-3, de-1 Heb, da, en-2 Hekerui, de, en-4 Hesperian, en High Contrast, de, en-3, fr-1 HJ Mitchell, en Howcheng, en, ja-2 Hystrix, de, en-1 H-stt, de, en-4, fr-1 INeverCry, en, es-1, ru-1 Infrogmation, en, es-1 JDavid, pl, en-2, de-1 J Milburn, en Jafeluv, fi, en-4, fr-3, de-2, ru-2 Jameslwoodward, en, fr-1 (checkuser) January, en Jaqen, it, en-2 Jarekt, pl, en Jastrow, fr, en-3, de-1, it-1 Jcb, nl, en-3, es-3 Jcornelius, de, lt-2, la-2, en-2, pt-2, fr-1 Jdforrester, en Jean-Frédéric, fr, en-4, es-1 JeremyA, en JGHowes, en, fr-2, de-1 Jmabel, en, es-3, ro-2, de-1, ca-1, it-1, pt-1, fr-1 Joergens.mi, de, en-3 John Vandenberg, en Juliancolton, en (bureaucrat) Julo, pl, en-2, de-1, ru-1 JuTa, de, en-2, fr-1 Jusjih, zh, en-3, fr-1 (bureaucrat, steward) Kaldari, en Kallerna, fi, en-3, sv-2, de-1 Kanonkas, no, en-4, nn-3, da-2, sv-2, de-1 (bureaucrat) Killiondude, en, es-3, ru-1 King of Hearts, en, zh-4, es-3 Klemen Kocjancic, sl, en-3, de-2, hr-1, bs-1 Krd, de, en-3 Krinkle, nl, en-3, de-2 Krzysiu, pl, en-2, szl-2 KTo288, en, zh-4 Kved, es, en-3 Kwj2772, ko, en-2 Kyro, fr, de-3, en-2 Leit, de, en-3, fr-1 Léna, fr, en-3, es-1 Letartean, fr, en-3 Leyo, gsw, de, en-3, fr-3, es-1, la-1 Lobo, es, ca-2, en-2 Logan, en, es-3 Lokal Profil, sv, en-4, pt-2, fr-1 LtPowers, en, es-1 Ludmiła Pilecka, pl, en-2, ru-1 Ludo29, fr, en-2 Lupo, de, en-3, fr-2, es-1, it-1 Luxo, gsw, de-4, en-1, fr-1 Lymantria, nl, de-2, en-2, fy-2, fr-1, zea-1 Magister Mathematicae, es, en-4, pt-1 (checkuser) Magnus Manske, de, en-2 Magog the Ogre, en, es-2 Maire, pl, en-4, es-2, fr-2, de-2, ru-1 MarcoAurelio, es, en-2, fr-2 (steward) Marcus Cyron, de, en-1 Mardetanha fa, az, en-3, tr-2, ar-1 (checkuser, steward) Martin H., de, en-2 (checkuser) Masur, pl, en-3, de-1 Matanya, en, he (steward) Materialscientist, en-4, ru-4, nl-3, fr-1, es-1 Matt314, de, en-3, fr-2, es-1, zh-1 Mathonius, nl, en-3, fr-1, de-1 (steward) Mattbuck, en, fr-1, la-1 Maxim, ru, en-3, fr-2 MBisanz, en (steward) McZusatz, de, en-3, es-1, la-1 swg-1 Mentifisto, en, mt, it-2 (steward) MGA73, da, en-3, de-2, sv-1, no-1 MichaelMaggs, en, fr-1 (bureaucrat) Micheletb, fr, en-3, it-1, es-1 Mitchazenia, en, es-2 Miya, ja, en-2 Mmxx, fa, en-3 Mono, en Moogsi, en, la-2, fr-1, grc-1 Morgankevinj, en, es-1, la-1 Mormegil, cs, en-2, de-1 Morning Sunshine, vi, en-3 M0tty, fr, en-1 MPF, en, da-2, de-1, fr-1 Multichill, nl, en-3, de-1, fr-1 Mys 721tx, zh, en-3 Nagy, de, en-3, fr-2, es-1, sv-1 Neozoon, de, en-4, nl-4, fr-2 Nilfanion, en, fr-1 NordNordWest, de, en-3 notafish, fr, en-4, de-3, es-2, it-2 O, zh, en-4, zh-wuu-2, zh-hu-3, yue-1 fr-1 odder, pl, en-3, de-2 (oversighter) Okki, fr, en-2 Otourly, fr, en-2, it-1 PeterSymonds, en, de-1 (steward) Pharos, en, fr-1 Philosopher, en, es-1, zh-1 PierreSelim, fr, en-3, es-1 Pitke, fi, en-4, sv-2 Platonides, es, en-2, fr-1 Podzemnik, cs, en-2 Polarlys, de, en-2, fr-1, no-1 Powerek38, pl, en-4, fr-2, es-1, de-1 Pruneau, fr, en-4, de-1 PumpkinSky, en, de-2 Putnik, ru, en-2 ~Pyb, fr, en-2 Pymouss, fr, en-3, de-2, it-2, he-1 Ragesoss, en, de-1, fr-1 Ra'ike, de, en-2 Rama, fr, en-3, de-2, la-2, es-1, it-1, ja-1 (oversighter) Rastrojo, es, en-3, fr-2, eo-1 Raul654, en, es-1 Raymond, de, en-3, nl-1 (oversighter) Rd232, en, de, es-2, fr-1 Rehman, en, si-1 Reinhard Kraasch, de, en-3 Rillke, de, en-2, fr-1 Rimshot, de, en-4, fr-2, it-1 Romaine, nl, en-3, de-2, af-1, fr-1 Ronhjones, en, fr-1 Rosenzweig, de, en-3, fr-1, la-1 Royalbroil, en, es-1 Rubin16, ru, tt, en-3 Rüdiger Wölk, de, en-2 Russavia, en, ru-3 (bureaucrat) Sanandros, als, de, en-3, fr-1 Sandstein, als, de, en-4, fr-3, it-1 SarahStierch, en SatuSuro, en, id-1 Sfu, pl, en-2 Shizhao, zh, en-1, ru-1 (steward) Siebrand, nl, en-3, fr-1, de-1 Skeezix1000, en, fr-2 Spiritia, bg, en-3, ru-2, mk-2, de-1 Sreejithk2000, ml, en-3, hi-3, ta-1, kn-1 Steinsplitter, tir, de-4, it-3, en-1 Steven Walling, en Stifle, en, ga, fr-2, de-1 Sven Manguard, en Tabercil, en Tarawneh, en, ar, de-1 Techman224, en TheDJ, nl, en-3, de-1, fr-1 Thuresson, sv, en-3, no-2 Tiptoety, en (checkuser, oversighter) Tom, en, es-1 Trijnstel, nl, en-4, de-1, fr-1 (checkuser, steward) Trixt, it, en-2, fr-1 tsca, pl, en, da Túrelio, de, en-3, es-1 VIGNERON, fr, de-2, en-2, zh-1 Waldir, pt, en-3 Whym, ja, en-2 Wikitanvir, bn, en-3, as-2, bpy-1 (steward) WJBscribe, en, fr-3, de-1 Wknight94, en Wpedzich, pl, en-4, de-2 (steward) Wsiegmund, en, fr-1, es-1 Wutsje, fy, nl, en-3, de-2, fr-1 Wuzur, de, en-3 wvk, de, en-4, fa-3, fr-2 Yann, fr, en-3, hi-2, gu-1 Yarl, pl, en-2, de-1, ru-1 Yuval Y, he, en-3 Zirland, cs, pl-3, en-3, sk-2, eo-2 Zolo, fr, en-4, de-2, zh-2 Zscout370, en, ja-3 Zyephyrus, fr, en-3, la-3, el-2 Zzyzx11, en, es-1, fr-1 KrinkleBot, Bot account; temporary adminship for testing, see also Commons:Bots/Requests/KrinkleBot (2). Brion VIBBER, Temporary adminship: "Temporary enable to look into UW campaign setup". No exact expiry date. The system currently recognizes 272 administrators. If that is not the last number in the list above, there is an error in the list.

Aquesta pàgina presenta tota la informació essencial sobre els administradors de Wikimedia Commons així com les candidatures i els vots per a administrador, buròcrata, checkuser i oversight. També s'inclouen les sol·licituds per a marca de bot.

Si el que voleu és demanar l'ajuda d'un administrador, feu-ho a Commons:Administrators' noticeboard.

Què és un administrador?

L'accés a administrador es concedeix als membres de la comunitat que són coneguts i de confiança i que estan familiaritzats amb les polítiques de Wikimedia Commons. No es tracta d'un reconeixement per l'aportació destacada d'un col·laborador sinó només d'una eina addicional per la gent que mostra interès pel manteniment. L'experiència mostra que els col·laboradors destacats redueixen la seva valuosa aportació quan esdevenen administradors degut a l'increment de tasques de manteniment, i això no és el que volem. Per tant, contribuïu amb les vostres millors habilitats i considereu que hi ha moltes formes d'obtenir el reconeixement de la comunitat, a part de ser administrador (si us agrada el manteniment, endavant; si contribuïu fent fotos impressionants, repenseu-vos-ho). Accedir a administrador no significa obtenir autoritat editorial en el projecte. Un administrador és simplement un usuari de confiança que pot:

• protegir i desprotegir pàgines
• esborrar i restaurar pàgines
• esborrar imatges i altres arxius carregats
• bloquejar i desbloquejar a usuaris
• editar la interfície i altres pàgines protegides.

A més, el buròcrates poden:

• fer administradors a altres usuaris
• canviar els noms d'usuari (vegeu Commons:Changing username)
• marcar o desmarcar comptes com a bot

Els administradors amb funció checkuser poden, a més, verificar si un usuari ha utilitzat més d'un compte (comptes titella).

Què s'espera d'un administrador?

Podeu sol·licitar ser administrador a Commons si compliu els següents condicions:

• No sou completament novell als projectes de Wikimedia. Heu estat editant al menys durant dos mesos i enteneu i accepteu l'abast del projecte.
• Teniu una pàgina d'usuari a Commons, heu col·laborat com a mínim amb 200 edicions (incloses càrregues) i esteu interessat en ajudar a la comunitat de Commons. Tingueu en compte que la gent pot tenir els seus propis criteris més exigents que això.
• Accepteu seguir les polítiques bàsiques i respectar el consens dels usuaris de Commons.
• Activitat. Igual que la política de Meta, als administradors inactius se'ls podrà retirar la seva funció. A Commons, es considera inactiu un administrador amb menys de 5 accions administratives en els últims sis mesos. Un administrador inactiu pot tornar a sol·licitar l'accés pel procés normal. Eina per comprovar l'activitat dels administradors. Es pot trobar més informació a Commons:Administrators/De-adminship.

Suggeriments per als administradors

• És útil subscriure's a la llista de correu commons-l si voleu estar al corrent. Podeu fullejar el seu arxiu.
• Afegiu la informació Babel en la vostra pàgina d'usuari perquè els altres usuaris puguin saber quines llengües enteneu.
• Llegiu Commons:Guia de supressió i les instruccions de les sol·licituds de supressió.
• Instal·leu MediaWiki:Quick-delete.js, així podreu marcar ràpidament imatges sense origen o sense llicència amb les plantilles corresponents i avisar a l'usuari amb un sol clic. (Recomanable: és molt útil)
• Poseu aquestes pàgines a la vostra llista de seguiment: Commons:Help desk, Commons talk:Licensing, Commons:Administrators' noticeboard i les seves subpàgines: Vandalisme, Atenció, Problemes amb usuaris, Blocatges i proteccions i Disputes.
  • Encara que no sigueu actiu, hi pot haver un moment on el vostre coneixement sigui important! Especialment si coneixeu altres llengües a part de l'anglès.
• Lleguiu Commons:Guide to adminship.

...si coneixeu altres llengües a part de l'anglès

• Participeu a La taverna de la vostra llengua. És un dels pocs llocs on els usuaris poden demanar ajuda en la seva pròpia llengua. Si existeix una versió de Commons:Help desk en la vostra llengua, ajudeu-hi també.
• Com a mínim doneu una ullada al Commons:Centre de coordinació de traduccions.

Candidatures per a administrador

• Les candidatures normalment duren set dies per recollir els vots i comentaris. S'accedirà a administrador amb una majoria mínima del 75% i un mínim de 4 vots de suport. En aquest cas, la sol·licitud s'ha de dirigir a un buròcrata perquè la faci efectiva.
• Tingueu en compte que en aquesta pàgina també es poden sol·licitar altres permisos, per exemple, la marca de bot abans d'engegar un robot.
• Les candidatures anteriors es troben a l'arxiu.

Com completar una candidatura

Administradors

Useu la caixa de sota substituint username pel vostre nom d'usuari:

Vegueu: Commons:List of administrators, Commons:List of bureaucrats

Checkuser

Useu la caixa de sota substituint username per vostre nom d'usuari:

Vegeu: Commons:List of checkusers

Marques de bot

Useu la caixa de sota substituint BotName pel nom del compte del bot:

Vegeu Commons:Bots/Requests for flags per al procés complet

Següent pas

• Després de crear la subpàgina, afegiu-vos a Candidatures i vots, al principi de la secció.
• Si algú altre us ha proposat, en lloc de fer-ho vós mateix, heu d'acceptar la candidatura afegint "I accept", o alguna cosa similar, i signant a sota. Això us registra com a acceptat i la data de la signatura és l'inici de la candidatura (així no es tancarà prematurament per error).

Candidats

Refresca la pàgina Useu l'enllaç d'edició de més avall per a editar la subpàgina corresponent.

This is the requests and votes page, a centralized place where you can keep track of ongoing user requests, and where you can comment and leave your vote. Any user is welcome to comment on these requests, and any logged in user is welcome to vote.

When requesting rights that do not need the support of the community (e.g. filemover) please go to Commons:Requests for rights‎!

How and where to apply for additional user rights on Commons

• Administrator: Commons:Administrators/Requests
• Bureaucrat: Commons:Bureaucrats/Requests
• Checkuser: Commons:Checkusers/Requests
• Oversighter: Commons:Oversighters/Requests
• Bot: Commons:Bots/Requests

All applications made on the above pages are automatically transcluded onto this page.

How to comment and vote

Any logged-in user is welcome to vote and to comment on the requests below. Votes from unregistered users are not counted, but comments may still be made. If the nomination is successful, a bureaucrat will grant the relevant rights. However, the closing bureaucrat has discretion in judging community consensus, and the decision will not necessarily be based on the raw numbers. Among other things, the closing bureaucrat may take into account the strength of any arguments presented and the experience and knowledge of the commenting users. For example, the comments and votes of users who have zero or few contributions on Commons may at the bureaucrat's discretion be discounted.

It is preferable if you give reasons both for  Support votes or  Oppose ones as this will help the closing bureaucrat in their decision. Greater weight is given to argument, with supporting evidence if needed, than to a simple vote.

Purge the cache. Use the edit link below to edit the transcluded page.

Requests for adminship

watch

When complete, pages listed here should be archived to Commons:Administrators/Archive.

• Please read Commons:Administrators before voting here. Any logged in user may vote, although those who have few or no previous edits may not be fully counted.

Requests for bureaucratship

watch

When complete, pages listed here should be archived to Commons:Bureaucrats/Archive.

• Please read Commons:Bureaucrats before voting here. Any logged in user may vote, although those who have few or no previous edits may not be fully counted.

Requests for CheckUser

watch

When complete, pages listed here should be archived to Commons:Checkusers/Archive.

• Please read Commons:Checkusers before posting or voting here. Any logged in user may vote although those who have few or no previous edits may not be fully counted.

INeverCry

Vote

Links for INeverCry: INeverCry (talk · contributions · deleted user contributions · recent activity · logs · block log · global contribs · SULinfo)

NOTE: CU requests at Commons run for 2 weeks minimum, this request will end no earlier than 29 June 2013 (UTC)

The rationale - People may wonder whether we need more checkusers. The simple answer is yes. We could use 1, maybe even 2, extra checkusers. We have 7 checkusers right now. We had 8, but our most active CU quit recently (Herby). To illustrate the big hole he left: I've looked at the statistics of the last 12 months & compiled a table which shows the activity of the checkusers. As you can see I'm the most active CU now, but Herby was more than twice as active as me. Martin H. does a lot, but never responded on the request page the past year. Which leaves Jim as the last active CU (& I love his help), but he never checks spambots and stuff & hardly replies on the CU mailing list. The other four are either semi-active or simply inactive as a CU.

My nominee - I've discussed with Herby about CU candidates and a few names came up. But we shared INeverCry in our list of candidates. INeverCry is an admin here since August 2012 and has been very active ever since. He frequently blocks users (in a good way of course ;)) which is very important to me as that's what checkusers do most of the time: deciding whether or not you should block someone. INeverCry has a good sense in discovering sockpuppets as he requested me and Herby multiple times to perform a CU. He is also an admin on the English Wikipedia so he's also aware of the global overview (cross-wiki) and possible problems. IMHO INeverCry is a very good admin overall and more than competent to be a CU.

Last but not least: CU is all about trust and INeverCry can certainly be trusted imho. I hope the community agrees with me. Trijnstel_talk 20:00, 15 June 2013 (UTC)

Acceptance: I gratefully accept the nomination. INeverCry 20:36, 15 June 2013 (UTC)

Votes

1.  Support as nom. Trijnstel_talk 20:00, 15 June 2013 (UTC)
2.  Support. Strong candidate. -- Cirt (talk) 20:43, 15 June 2013 (UTC)
3.  Support. Trusted colleague. --Túrelio (talk) 20:50, 15 June 2013 (UTC)
4.  Support good candidate. --Rschen7754 21:21, 15 June 2013 (UTC)
5.  Support - Jmabel ! talk 21:29, 15 June 2013 (UTC)
6.  Support Of course! --Didym (talk) 21:30, 15 June 2013 (UTC)
7.  Support I may as well voice my support, it's a comparison-based support, I would still like my concerns properly addressed though. Penyulap ☏ 21:58, 15 June 2013 (UTC)
8.  Support russavia (talk) 22:05, 15 June 2013 (UTC)
9.  Support good candidate--Steinsplitter (talk) 22:16, 15 June 2013 (UTC)
10.  Support, per nom. Savh^ñ 22:24, 15 June 2013 (UTC)
11.  Support --MichaelMaggs (talk) 22:28, 15 June 2013 (UTC)
12.  Support I don't always support requests for higher wiki office, but when I do, I drink Dos Eq..., err I mean, I make sure they are very good candidates. Magog the Ogre (talk) (contribs) 23:22, 15 June 2013 (UTC)
13.  Support Alan ^(talk) 23:27, 15 June 2013 (UTC)
14.  Support. Mathonius (talk) 01:12, 16 June 2013 (UTC)
15.  Support -FASTILY 01:16, 16 June 2013 (UTC)
16.  Support. Érico Wouters ^msg 02:36, 16 June 2013 (UTC)
17.  Support JKadavoor Jee 04:47, 16 June 2013 (UTC)
18.  Support of course. TCN7JM 09:15, 16 June 2013 (UTC)
19.  Support --Stryn (talk) 11:26, 16 June 2013 (UTC)
20.  Support --EugeneZelenko (talk) 14:18, 16 June 2013 (UTC)
21.  Support--Canoe1967 (talk) 16:38, 16 June 2013 (UTC)
22.  Support Taivo (talk) 17:12, 16 June 2013 (UTC)
23.  Support Excellent choice - thanks for helping - despite Marcus's comments the spambot invasion/attacks require continuous work sadly. --Herby ^{talk thyme} 18:30, 16 June 2013 (UTC)
24.  Support Trusted, responsive and very diligent user. -- Rillke^(q?) 20:23, 16 June 2013 (UTC)
25.  Support I have done some work with INeverCry and he/she seems responsive in deleting clear copyright violations. I think we do need a new active CU after Herby retired and that perhaps Gmaxwell and Mardetanha should resign as CUs--from the very low level of their activity here. --Leoboudv (talk) 08:20, 17 June 2013 (UTC)
26.  Support --Hedwig in Washington ^(mail?) 20:51, 17 June 2013 (UTC)
27.  Support MoiraMoira (talk) 10:21, 18 June 2013 (UTC)

Votes not related to the candidate, but instead related to the position in general

Bureaucrat Note: I have refactored this section to highlight that the rationale used in these votes is not about the candidate, but is explicitly about the position in general or external factors. If any of you wish to make comments about the candidate, you are welcome to add them and move your vote back into the other section. RfX is not the place for policy reform, nor is it for attacking those currently or formerly serving in the position. --99of9 (talk) 22:35, 18 June 2013 (UTC)

1.  Oppose - Commons already has much too much Checkusers. There should be only very few very trusted Authors with these rights. I don't see a cause for a new one. Sorry @ Trijnstel - but only to write we need some is not enough for me.But your Statistics tells me, we should take away the Rights from Gmaxwell and Mardetanha. And we have to talk about the extensive use of this "last to use" tool! About 8.500 CUs is pure horror. I don't know if we can argue against Pipa, Sopa and Acta - and PRISM - and use this tool so unbeleavable often! Marcus Cyron (talk) 17:51, 16 June 2013 (UTC)

   Because of this reply of Marcus Cyron, I believe I should clarify a few things:

   1) Yes, I believe we should take away the right from Gmaxwell & Mardetanha too. I even asked them both if they would drop the tool themselves: here and here.

   2) Regarding the "extensive use" of the tool; maybe it helps if I say I use it 90% of the time for checking spambots (the other 10% are regular requests etc.)? Also (I know I shouldn't mention it maybe, but still it's important imo), on the English Wikipedia the tool is used even more... So frankly we *do* need more checkusers now Herby quit.

   And yes, we should take it away from inactive ones, but that doesn't mean INeverCry shouldn't be a great asset for the team. Trijnstel_talk 18:29, 16 June 2013 (UTC)

   The terible often use at en:WP is not a cause for me. A de:WP we have only very few uses. I hate the Big-Brother-Structure here and I don't feel safe any longer with you handling this tool so extensive. Marcus Cyron (talk) 09:26, 17 June 2013 (UTC)

   If you don't do anything wrong that might look like sockpuppetry, I have absolutely no reason to CU you (and I never have either ofc). :) Trijnstel_talk 12:17, 17 June 2013 (UTC)

   Sorry - but here's my problem: If you don't do anything wrong that might look like sockpuppetry - I never ever use Sockpuppets. But what happens if you think it looks like? You decide to Checkuser. But "I think there could be something" is for me not enough. The possibility "there could be something" is not enough for a CU. We need real good causes - because it's a very hard way into the privacy of the people who work here - in a free project. They are volunteers! Until we checkuser them, really a lot has to happen. Marcus Cyron (talk) 00:02, 18 June 2013 (UTC)

   That's a very poor argument. It's like "If you do'nt have to hide anything, you could show us pictures of your bedroom and of your underwear drawer in the closet". If you do not care of another privacy, you should publish your name and your full address on your user page and your usual IP address, otherwise you apply double standards for me. But you did'nt do that all until now. Your privacy seems to be "worthy" than others. Morty (talk) 14:18, 17 June 2013 (UTC)

   I never said I don't care about the privacy of others (which I do care about ofc). I only said I won't CU without a valid reason. Trijnstel_talk 14:24, 17 June 2013 (UTC)

2.  Oppose - Until there is no control of his acting. Morty (talk) 14:21, 17 June 2013 (UTC)

   I don't get this statement. Are you talking about me or INeverCry? Trijnstel_talk 14:24, 17 June 2013 (UTC)

   It's not personal. But i miss any independent control and/or public accessible log file of the commons CUs. And until there is no check and balance i deny to vote pro to any candidate. Morty (talk) 14:27, 17 June 2013 (UTC)

   Right, well, we're not dewiki which logs everything, but we control eachother. And in case you don't trust us, you always have the OC. Trijnstel_talk 14:30, 17 June 2013 (UTC)

   Please tell me: Is there a list of provable reasons why a CU is made or is such a decision is commonly based on a simple feeling in the stomache? I am a little bit scared of the enormous amount of 8.500 CUs in a year. That looks to me as if there is no self-imposed barrier to use this instrument of controlling the community. Morty (talk) 15:06, 17 June 2013 (UTC)

   I guess you came here because of the post of Marcus on dewiki? If so, yes, I would be frightened too if someone just gives a number without any background. But I'm happy you've asked for a clarification. Yes, there is a list of reasons: see the CU policy. I stick to that. And again: we're not dewiki which requires a consensus to be able to CU. It's a tool to fight vandalism and I use it that way. Here I obviously only use CU to check for sockpuppetry, that is *abusing sockpuppets*. As I said before, 90% of my checks are spambots or attack accounts. The spambots are mostly from China and have a clear pattern. So I definitely don't randomly check accounts. And the attack accounts are pretty clear too (can't go into detail). Sadly Commons receives a lot of spam and an abuse filter alone won't help. I am a steward thus I also cross-wiki check them and afterwards I globally block the IP so other projects won't be affected by the spam from that IP anymore either. I've never checked a regular editor and won't do that either unless I have a very strong reason to do so. I don't understand why people are so scared to be CU'd. CU is just a tool to fight vandalism. It's not something we use to 'control the community' as you suggest. Trijnstel_talk 15:44, 17 June 2013 (UTC)

   Well said, Trijnstel. I never afraid of the tools; only those who operates. Honestly, many admins are not very trustable. But here your choice is good. :) JKadavoor Jee 17:06, 17 June 2013 (UTC)

3.  Oppose --Hubertl (talk) 02:07, 18 June 2013 (UTC) as Morty and Marcus. If the discussion about possible excessive misuse of data should begin here, then it is not the wrong place.
   •  Comment A discussion about possible misuse of CU data is appropriate on another forum. Not on an existing CU request. Besides, if there are not enough CU's, then Commons risks being inundated by spammers and copyright violating accounts. Who wouldn't want to upload copyvios or spam on a highly visited website like Commons or Wikipedia? When a spammer or copyright violater finds one account is blocked, he/she immediatedly creates another. No one can tolerate this situation--unless we want to risk a lawsuit from the real copyright owner. That is why we need a more active Check User in the first place--now that Herby who did half this task has retired and Mardetanha almost never uses this tool. The possible misuse of CU data I cited on another thread was on English wikipedia, not WikiCommons. I respect INeverCry's judgment. He follows Commons procedures. Even when I pointed out a massive copy vio account case on his talkpage, he waited almost 7 days here before acting. To me, this was a speedy delete case. That tells me a lot on this Admin's respect for Commons laws. Regards, --Leoboudv (talk) 03:23, 18 June 2013 (UTC)
4.  Support Can't compare Commons with the German Wikipedia.--Stanzilla (talk) 10:29, 18 June 2013 (UTC)

Comments

Trijnstel suggests that "INeverCry has a good sense in discovering sockpuppets[...]", perhaps can you tell me did you see anomalies in the contributions of this editor ? If so, why were you silent, if not, why would you be good at the job ? What does 'turning a blind eye' mean to you ? Penyulap ☏ 21:17, 15 June 2013 (UTC)

Without commenting about Moogsi (don't know much about him), but having sockpuppets itself isn't forbidden. *Abusing* sockpuppets is wrong. Trijnstel_talk 21:23, 15 June 2013 (UTC)

If you can't spot them in the first place it's a moot point isn't it. Ditto being happy to vote them into positions of trust without knowing who they are. Penyulap ☏ 21:30, 15 June 2013 (UTC)

Moogsi indicated that he hasn't edited with any other accounts. I see no indication that Moogsi has done anything but constructive editing. I assumed good faith in regard to his RFA, and so far I haven't seen him do anything but good work as an admin. When looking for sockpuppets, I look for direct evidence of disruptive editing, as can be seen in cases like this, or this, or with most of the cases brought to COM:RFCU, COM:AN/U, etc. If somebody comes to me with credible evidence of disruptive socking, or if I see it, I have done and will continue to do my best to deal with it in the appropriate way, through discussion with other editors, and with blocks when necessary. INeverCry 22:21, 15 June 2013 (UTC)

Well, I won't give my own thoughts on that editor in public, and I won't call you particularly great at spotting socks, but I will commiserate with you that you'll be doing the lion's share of the drudgery in both the CU and DR departments. Say it with me, "Woo Hoo", come on, say it with me, give me a "Woo".... just a "Woo" erm, yes, never mind.

Let me be the first to say "Sorry to hear you got stuck with even more work to do". hmm. Wait a sec, I know something I can say that is sure to cheer you up ! "I'll shut up now." Penyulap ☏ 22:33, 15 June 2013 (UTC)

You are one interesting person. Killiondude (talk) 07:01, 16 June 2013 (UTC)

general discussion about CU/Commons:

• User:Marcus Cyron wrote the following at de:Wikipedia:Kurier (the de-Wikipedia equivalent for the Sign Post). I think everyone here, and especially the candidate has a right to know what he wrote there, thereof, here is a rough (and possibly not always correct) translation which Marcus is welcome to improve:
  • Currently there is a Checkuser-election at Commons. It is arguable whether the writer of these lines is right with his demand keeping the number of people who have access to these sensitive right low. He is more interested or even alarmed by the statistics of the eight checkusers at Wikimedia Commons during the past year: About 8.500 check user actions were performed. Half of them during the last half year. Especially two collaborators — of which one just threw in the towel (retired) — excelled with a four digits number of actions, each. And it doesn't grasp to the author [of these lines] how such a thing could happen. Are there really so many violations that have to be treated with a CU (where there is hardly a Community with “socking”) – or are the buttons carelessly used? And how can we then complain about spying by ACTA, SOPA, PIPA and PRISM, if we ourself created such a surveillance structure in our project. A comment by M.C. //
• Note by the translator: The checkuser policy at de.wp is stricter. Also, I am going to add a translation of Trijnstel's reply to the Kurier. -- Rillke^(q?) 20:01, 17 June 2013 (UTC)

•  Comment: I support INeverCry's request to be a CU because he is reasonable and looks at the evidence before acting but I agree with Trijnstel that a user with 2 accounts should Not be blocked unless there is evidence of abusive sockpuppetry/spamming. So, I think I understand Marcus Cyron's concerns about the CU process. In this English wikipedia case, a user was temporarily blocked for 1 week because he had 2 user accounts, not because of any abusive sockpuppetry. The user appealed the block and it was lifted Later on, the person who lifted the block Admitted/Admitted 2 that he didn't know why the user was blocked in the first case when there was no evidence of abuse on either account. (just something to do with English wiki policy) That is why I believe Trijnstel's standard should be Common's standards here--act only if there is clear evidence of abusive sockpuppetry or spamming. Regards, --Leoboudv (talk) 00:40, 18 June 2013 (UTC)

Requests for Oversight rights

watch

When complete, pages listed here should be archived to Commons:Oversighters/Archive.

• Please read Commons:Oversighters before voting here. Any logged in user may vote, although those who have few or no previous edits may not be fully counted.

Requests for permission to run a bot

watch

Before making a bot request, please read the new version of the Commons:Bots page. Read Commons:Bots#Information on bots and make sure you have added the required details to the bot's page. A good example can be found here.

When complete, pages listed here should be archived to Commons:Bots/Archive.

Any user may comment on the merits of the request to run a bot. Please give reasons, as that makes it easier for the closing bureaucrat. Read Commons:Bots before commenting.

YiFeiBot (talk · contribs) (2)

Operator: Zhuyifei1999 (talk • contribs • recent activity • count • block log • rights log • upload log • SUL)

Bot's tasks for which permission is being sought: mark broken redirects as speedy deletion as requested in Commons:Bots/Work_requests#Broken redirects.

Automatic or manually assisted: Automatic

Edit type (e.g. Continuous, daily, one time run): hourly

Maximum edit rate (e.g. edits per minute): 6 edit per minute, and should seldom or never happen that fast.

Bot flag requested: (Y/N): Y

Programming language(s): pywikipedia, modified script

Zhuyifei1999 (talk) 11:14, 11 June 2013 (UTC)

Noaabot (talk · contribs)

Operator: Fæ (talk • contribs • recent activity • count • block log • rights log • upload log • SUL)

Bot's tasks for which permission is being sought: Uploading of archives of images from the National Oceanic and Atmospheric Administration.

These are public domain and the background of the initial request and project can be found at Commons:Batch_uploading/Weather_maps#Coordination. In addition to the initial batch upload of around 20,000 images providing maps from September 2002 to the current day, there may be categorization and formatting changes as needed that can run from this account. Beta test images consisting of weather maps for the first year of the archive and the most recent month of maps, can be found at 2002 NCEP weather maps (610 maps) and 2013 NCEP weather maps (ongoing with the most recent weather maps being uploaded each day; these appear to be released after 2pm EST for the previous day's maps).

Partial supervision for archive. Beta testing then monitored runs would be expected, with unmonitored runs once uploads or changes are seen to be stable (i.e. 1,000 or more uploads or changes). Daily or weekly updates would be automatic with some regular oversight or in response to questions.

Automatic or manually assisted: Automatic.

Edit type (e.g. Continuous, daily, one time run): One time runs for the past 11 years of archive maps and then a daily or weekly automatic update. For the NCEP weather, 5 types of maps are made available each day and a weekly summary pdf is derived from these. The maps are published as gifs and Noaabot is converting these to pngs before uploading.

Maximum edit rate (e.g. edits per minute): Approximately 4 per minute.

Bot flag requested: (Y/N): Y

Programming language(s): Python

Fæ (talk) 11:12, 22 May 2013 (UTC)

Discussion

• Not sure if the template is correct—the images do not come directly from NOAA, but from NCEP (National Centers for Environmental Prediction) — other than that, I'm quite OK with the way files are uploaded. odder (talk) 12:21, 22 May 2013 (UTC)

  Categories now changed from using "NOAA" to "NCEP". In theory the NCEP is a child of the "National Weather Service" (previously "Weather Bureau") which itself is a child of "NOAA". I would suggest avoiding making the category tree over-hierarchical until it starts to appear over-loaded or might be misleading. --Fæ (talk) 06:11, 24 May 2013 (UTC)

• Looks OK for me. --EugeneZelenko (talk) 14:35, 22 May 2013 (UTC)
• Files should have more categories. A category for the day and a category for the type. Also, are you going to upload the Daily Weather Map Weekly PDF Files? The pdfs contain vectorized maps.Smallman12q (talk) 00:58, 24 May 2013 (UTC)
  • The categories can be added quickly enough. The types are selected in the ingestion template and I will tweak it to include a NOAA weather map type category automatically. I am less certain about the value of a day category, my original thoughts on this were that the files are strictly named, with ISO format date at the beginning, so any particular month or day's worth of images (there are 5 types for each day) can be easily found by scrolling through the alphanumerically sorted category of the year, and a breakdown further than year would be superfluous. I'm happy to include day categories if the benefits of doing so are a bit clearer to me. In the longer term I would like a navigation template (possibly automated as part of the ingestion template) to provide a link to the other map types for the day, yesterday and tomorrow's image. I am deferring this until either I get to grips with Lua, or another volunteer can take a look at it; certainly it is a more long term improvement that can be worked out once the archive backlog is uploaded (one of the benefits of using an ingestion template is that tweaks like this can happen on the template rather than across 20,000 files ).

     Done Type categories now added to the ingestion template as:

    Category:NCEP daily surface weather maps

    Category:NCEP black and white daily max-min temperature maps

    Category:NCEP daily max-min temperature maps

    Category:NCEP daily 500-millibar height contour maps

    Category:NCEP daily precipitation maps

  • Yes, the weekly pdfs can be uploaded from the pdf page—hopefully the NCEP will stick to the recently changed naming scheme so updates can be part of the batch upload. There are not that many, as they are only available from the last week of November 2012. It would be great if these were decomposed at some point, so that the embedded vector maps are available in addition to pngs, so having the pdfs on Commons is a good start.

     Done Category:NCEP weekly weather maps and Category:NCEP weekly color weather maps. --Fæ (talk) 12:42, 24 May 2013 (UTC)

• Just as an outside thought, I believe that a category for each day is just too much, but I would support creating monthly categories; there should be around 150 files in each category, which would make them quite useful. odder (talk) 12:44, 24 May 2013 (UTC)
  • Looking at the yearly categories for single map types is useful for seeing weather patterns over the seasons, so we might actually put them both in annual and monthly categories. I think this could be done again by adapting the ingestion template rather than sticking these on every file. I'll see if I can come up with a template inclusion solution. --Fæ (talk) 12:49, 24 May 2013 (UTC)
    • Categorisation by template is a Bad Idea™ (as I learnt not very long ago). I'd rather just add those categories to directly to file descriptions pages, so to let people use existing tools (CatScan, Cat-a-lot) when necessary. odder (talk) 12:55, 24 May 2013 (UTC)
      • Okay, easy enough once a scheme is put up. Could you think about how the hierarchy would best work and make a suggestion here? I can then ensure future uploads fall in line, and we can easily fix the 'beta test' uploads so far. Thanks --Fæ (talk) 12:58, 24 May 2013 (UTC)
        • File:2013-05-06 Color Max-min Temperature Map NOAA.png shows how — in my opinion — those images should be categorised: by type (Category:NCEP daily surface weather maps), by year (Category:2013 NCEP weather maps), by month (Category:NCEP weather maps for May 2013), and by year and type (Category:2013 NCEP daily surface weather maps). This was it should be easy to do category intersection and perform other actions necessary for good maintenance of categories and files. I also set up a whole new category tree at Category:NOAA maps. odder (talk) 20:23, 24 May 2013 (UTC)
          • It all looks useful and commonsense, I'm happy to implement all these automatically in the batch upload once the bot gets flagged. --Fæ (talk) 21:01, 24 May 2013 (UTC)
• Why did bot upload images from USA military? --EugeneZelenko (talk) 14:17, 27 May 2013 (UTC)
  • Classic human error. I was testing out some complicated checks for non-identical duplicates for Department of Defense batch uploads and ran the upload from the wrong terminal. I killed the process as soon as I noticed my error 6 minutes later, by which time a total of 6 public domain photographs had been uploaded out of a planned batch of more than 500. --Fæ (talk) 17:38, 27 May 2013 (UTC)
• I'd much prefer not to have them in both year and month, per COM:OVERCAT. Scrolling through is not much of an argument, because there are 5 different types in the year category, so you can hardly remember what it was 5 files back. Also I think a daily category would actually be useful for weather, because some people like comparing today's weather with last year's on the same day. --99of9 (talk) 18:48, 27 May 2013 (UTC)
  • The current directories provide a directory per year by type (example), so you do not have to browse the full year with all 5 map types. I am unsure what your expectation of a day category means. Is this something like "day 42" of all years (leap years being a problem), or "Monday", or something else? Any of this is do-able, but I feel a lot could be done with category intersections rather than hard categories, or by a user searching by dates. --Fæ (talk) 18:54, 28 May 2013 (UTC)
    • Yes, 2002_precipitation is a good category for browsing. But the files in there, are also in the parent cat Category:2002_NCEP_weather_maps, which if this convention is followed, will eventually have 5*365 files in it. I think they should be removed from that, since they can be immediately and directly placed in any relevant subcats at the time of upload. --99of9 (talk) 11:21, 30 May 2013 (UTC)
    • Sorry I didn't properly explain the daily category idea. What I mean is similar, but more user-friendly than "day 42". My category titles would be something like Category:NCEP weather maps for 11 September (although I can understand the argument for having the date the other way around for USA weather, current Commons date categorization is this way: Category:Days_in_September). I can think of a few things people might use these categories for (e.g. historical event research; or "wasn't it warmer last year?"). I don't think many users are sophisticated enough to do cat-intersects, and since it's easy to do, I'm not sure why we can't do it for them now? (On the other hand, I don't think "Monday" is correlated with weather patterns, so I don't think it's useful.) --99of9 (talk) 11:21, 30 May 2013 (UTC)
      • Okay, let me ponder it. The most recent uploads for days this week include the month category and it is easy enough in Python to name a category by the day of the month. I'll think about setting up an example day, and then uploading the maps for the full 11 years for that one day of the year, so we can see it in "action" before making a mare's nest of categories. Obviously "29 February" will end up a little sparse. --Fæ (talk) 11:27, 30 May 2013 (UTC)
        • Yes, 29 Feb will get a raw deal, as it usually does. My scheme only adds 366 subcategories, which is nothing if you've got ~20k files. --99of9 (talk) 11:36, 30 May 2013 (UTC)
          • I have set up Category:NCEP weather maps for 20 May as a little test. Currently for years 2006-2013. This was manual, but it can be easily automated for future uploads. --Fæ (talk) 12:23, 30 May 2013 (UTC)
            • That looks fine to me. Personally, if I were the uploader, I would further subcat by type, but it seems that you and odder prefer larger cats (or dislike complex subcategory trees more) than me. --99of9 (talk) 13:38, 30 May 2013 (UTC)

• I have gone along with your suggestions and implemented them in the upload, namely dropping the year category with all types and breaking down the day category with types. This will mean a bit of category emptying later on, and quite a bit of category creation (which I have not automated yet, but will ponder it). In the example of the file I just uploaded, File:2006-05-20 Max-min Temperature Map NOAA.png this means the following categories were added: --Fæ (talk) 15:40, 30 May 2013 (UTC)

Category:NCEP black and white daily max-min temperature maps - this can be switched off in {{NOAA-dailywxmap}}

Category:2006 NCEP black and white daily max-min temperature maps

Category:NCEP weather maps for May 2006

Category:NCEP black and white daily max-min temperature maps for 20 May

I think the first can be cut out because it's a parent of the second, and I doubt anyone will want to do a slideshow of over 12 years of files. Depending if you think people would prefer to scan a whole year or a month at a time, you could cut it down to just (with even more category creation):

Category:NCEP black and white daily max-min temperature maps for May 2006

Category:NCEP black and white daily max-min temperature maps for 20 May

If you need help with the category creation I have some scripts that might help. --99of9 (talk) 15:51, 30 May 2013 (UTC)

A Python code snippet (by email) might be helpful. Were I writing it, as I have the generated category name, I just need to call something to check "does this exist?" and if not, then I'll write the initial contents (which I have the basics already in the code to write in). For the existence check, rather than a failed page connection, a commons API call might be a quicker way of doing it. I'm not really stuck on this, it's just time to look it up and test it out. The '12 year' type cat is easily switched off in the template. I disagree with dropping the year of a type cat, this is rather useful for seeing the seasonal patterns over the year which would be much harder to do if broken into 12 month categories; though I'm not against having both.

Consider it pondered. It is easy enough to do a call like this and check for the 'missing' flag. I'm assuming this is slightly quicker than getting the category page, which I can do if this existence test fails. I'll add this in before running a bit more testing.

Category existence/creation routines now added, I am running through files for Category:NCEP weather maps for 21 May to check. Creating categories this way means they only get created when there is a file to populate them. --Fæ (talk) 10:06, 31 May 2013 (UTC)

Autobot (talk · contribs)

Operator: BokicaK (talk • contribs • recent activity • count • block log • rights log • upload log • SUL)

Bot's tasks for which permission is being sought: Transfering images from sr.wiki.

Automatic or manually assisted: manually assisted

Edit type (e.g. Continuous, daily, one time run):

Maximum edit rate (e.g. edits per minute):

Bot flag requested: (Y/N):

Programming language(s):

 Bojan  Talk  03:50, 19 May 2013 (UTC)

Discussion

Which task are you willing to run? --Ricordisamoa 09:42, 19 May 2013 (UTC)

Sorry, I didn't noticed that field. My intentions are moving images from sr.wiki that were uploaded by trusted users -- Bojan  Talk  14:05, 19 May 2013 (UTC)

Sometimes duplicated license tags need clean-up. {{self}} is not appropriate. --EugeneZelenko (talk) 14:39, 22 May 2013 (UTC)

I'll clean it (if I get bot flag). I don't understand the latter. -- Bojan  Talk  03:33, 23 May 2013 (UTC)

Bot is not photographer. So only license tags without {{self}} wrapper should be used. --EugeneZelenko (talk) 14:35, 23 May 2013 (UTC)

It is not my script - I'm running Magnus's script imagecopy.py that utilise CommonsHelper. {{Self}} would be ignored if redirect Template:Дуална лиценца wasn't created. -- Bojan  Talk  23:20, 23 May 2013 (UTC)

SamoaBot 3 (talk · contribs)

Operator: Ricordisamoa (talk • contribs • recent activity • count • block log • rights log • upload log • SUL)

Bot's tasks for which permission is being sought: internationalize file description pages, using apposite templates (like {{original upload log}}) and MediaWiki system messages (like {{int:license-header}})

Automatic or manually assisted: automatic unsupervised

Edit type (e.g. Continuous, daily, one time run): intermittently, at the operator's discretion

Maximum edit rate (e.g. edits per minute): 20-25 EPM

Bot flag requested: (Y/N): N (already flagged)

Programming language(s): Python (with PWB)

--Ricordisamoa 01:53, 14 May 2013 (UTC)

Some test edits: Revision of File:Signator.jpg and Revision of File:Emerald spring in yellowstone.jpg --Ricordisamoa 05:02, 14 May 2013 (UTC)

Another: Revision of File:Hospital-quiron-san-sebastian.jpg (at the moment I'm checking every single diff before saving, later I could run it "bot-like") --Ricordisamoa 05:44, 14 May 2013 (UTC)

Discussion

• The edits look fine to me. I know other bots do work like this, but I don't see much harm in redundancy, especially since you're making a few changes at once. Which portion of the file database do you plan to run it on? --99of9 (talk) 12:49, 14 May 2013 (UTC)

For example I can start from a search, or from pages that transclude {{ImageUpload}}: most times they are old, low-frequency-edited pages, and often contain superseded/superfluous syntax structures. --Ricordisamoa 13:36, 14 May 2013 (UTC)

Ok, that's fine by me. --99of9 (talk) 13:40, 14 May 2013 (UTC)

• Looks OK for me, but will be good idea to borrow other trivial clean-ups ideas from similar bots. Like {{Location}} place, etc. --EugeneZelenko (talk) 14:21, 14 May 2013 (UTC)

Upd: another test edit. What do you mean with "{{Location}} cleanup"? --Ricordisamoa 13:18, 18 May 2013 (UTC)

I meant that {{Location}} should be near {{Information}} (I usually place it before). --EugeneZelenko (talk) 14:16, 18 May 2013 (UTC)

Above or below? PS: another test edit --Ricordisamoa 14:59, 18 May 2013 (UTC)

Above. Please not that removing 1= from language templates may cause problem when description contains URL with with some special characters. --EugeneZelenko (talk) 14:17, 19 May 2013 (UTC)

I know, but it checks for them, and it's always been working. --Ricordisamoa 16:53, 19 May 2013 (UTC)

But then if someone puts a link in later, they have to also know to put the 1= in as well? That sounds like it will make life difficult. --99of9 (talk) 19:00, 19 May 2013 (UTC)

So should I avoid doing that? Removing "1=" only breaks the template if the text contains another "=". --Ricordisamoa 21:05, 19 May 2013 (UTC)

I don't have a strong opinion. But I can imagine another user coming here and applying for a bot that puts the 1= in... and I certainly don't want to see bot wars. So maybe just leave them untouched if Eugene (and others?) think that's best. --99of9 (talk) 22:09, 19 May 2013 (UTC)

Smallbot (talk · contribs)

Operator: Smallman12q (talk • contribs • recent activity • count • block log • rights log • upload log • SUL)

Bot's tasks for which permission is being sought: To upload ~500k files from the US National Archives and Records Administration based on a database dump provided in partnership with the Digital Public Library of America.

Example

JSON source

{ "id": "nara--1693425", "key": "nara--1693425", "value": { "rev": "1-a8e9cee50a8cea9d1724c12a0d0d69e5" }, "doc": { "_id": "nara--1693425", "_rev": "1-a8e9cee50a8cea9d1724c12a0d0d69e5", "hasView": [{ "url": "http://media.nara.gov/Public_Vaults/14755_2006_001_a.jpg", "format": "image/jpeg" }, { "url": "http://media.nara.gov/nwl/berryman/H-009_7-1-1928_Yes_We_Have_No_Ambitions_print.pdf", "format": "application/pdf" } ], "sourceResource": { "date": { "begin": "1928-07-01", "end": "1928-07-01", "displayDate": "07/01/1928" }, "description": "This cartoon plays off a line from a popular 1923 song (\\" Yes, We Have No Bananas!\\") to characterize car maker Henry Ford\'s Presidential ambitions--or lack thereof. Ford blames his busy schedule for his hesitation to jump into the \\" Presidential contest pool, \\" while eager supporters encourage him to \\" come on in !\\" Berryman was correct in his prediction: Ford chose not to pursue the Presidency.", "title": "Yes, We Have No Ambitions Today!", "rights": "Restrictions: Unrestricted; Use status: Unrestricted", "collection": { "@id": "http://dp.la/api/collections/15e82b12ef89a63d03737461e2440df8", "id": "15e82b12ef89a63d03737461e2440df8", "title": "Records of the U.S. Senate, 1789 - 2011" }, "stateLocatedIn": { "name": "DC" }, "creator": "U.S. Senate. Office of Senate Curator.\\t(? -)", "isPartOf": "Series: Berryman Political Cartoon Collection, 1896 - 1949", "type": "image" }, "object": "http://media.nara.gov/Public_Vaults/14755_2006_001_t.jpg", "ingestDate": "2013-04-11T21:27:25.187803", "originalRecord": { "access-restriction": { "specific-access-restrictions": null, "restriction-status": "Unrestricted" }, "contributors": { "contributor": { "contributor-display": "Berryman, Clifford Kennedy, 1869-1949", "contributor-record-type": "PER", "contributor-type": "Artist", "standard": "Y", "num": "1", "contributor-id": "3119843" } }, "hierarchy": { "hierarchy-item": [{ "hierarchy-item-inclusive-dates": "1896 - 1949", "hierarchy-item-id": "306080", "hierarchy-item-lod": "Series", "hierarchy-item-title": "Berryman Political Cartoon Collection, 1896 - 1949" }, { "hierarchy-item-id": "375", "hierarchy-item-lod": "Record Group", "hierarchy-item-title": "Records of the U.S. Senate, 1789 - 2011", "hierarchy-item-record-group-number": "46" } ] }, "production-dates": { "production-date": "07/01/1928" }, "created-timestamp": "1/20/2013 4:36:49", "arc-id": "1693425", "use-restriction": { "specific-use-restrictions": null, "use-status": "Unrestricted" }, "title": "Yes, We Have No Ambitions Today!", "title-only": "Yes, We Have No Ambitions Today!", "general-records-types": { "general-records-type": { "num": "1", "general-records-type-desc": "Photographs and other Graphic Materials", "general-records-type-id": "4237050" } }, "scope-content-note": "This cartoon plays off a line from a popular 1923 song (\\" Yes, We Have No Bananas!\\") to characterize car maker Henry Ford\'s Presidential ambitions--or lack thereof. Ford blames his busy schedule for his hesitation to jump into the \\" Presidential contest pool, \\" while eager supporters encourage him to \\" come on in !\\" Berryman was correct in his prediction: Ford chose not to pursue the Presidency. ", "parent": { "parent-title": "Berryman Political Cartoon Collection, compiled 1896 - 1949", "parent-lod": "Series", "parent-id": "306080" }, "edited-timestamp": "[g_x128_110, g_x32_443, g_x64_221, g_x2_7090, g_x16_886, g_x8_1772, g_x4_3545, b_x1_14180]", "objects": { "object": [{ "thumbnail-url": "http://media.nara.gov/Public_Vaults/14755_2006_001_t.jpg", "object-sequence-number": "1", "file-size": "579687", "mime-type": "image/jpeg", "num": "1", "file-url": "http://media.nara.gov/Public_Vaults/14755_2006_001_a.jpg" }, { "description": "Download PDF", "object-sequence-number": "2", "file-size": "209895", "mime-type": "application/pdf", "num": "2", "file-url": "http://media.nara.gov/nwl/berryman/H-009_7-1-1928_Yes_We_Have_No_Ambitions_print.pdf" } ] }, "title-date": "07/01/1928", "subject-references": { "subject-reference": { "subject-type": "SRT", "display-name": "cartoons (humorous images)", "num": "1", "subject-id": "4170951", "standard": "Y" } }, "level-of-desc": { "level-id": "NAVI", "lod-display": "Item" }, "physical-occurrences": { "physical-occurrence": { "media-occurrences": { "media-occurrence": { "num": "1", "media-type": "Paper" } }, "reference-units": { "reference-unit": { "city": "Washington", "fax": "202-357-5911", "name": "Center for Legislative Archives", "ref-id": "36", "address2": "Room 8E, 7th and Pennsylvania Avenue NW", "summary": "true", "phone": "202-357-5350", "state": "DC", "num": "1", "postcode": "20408", "address1": "National Archives Building", "mailcode": "LL", "email": "legislative.archives@nara.gov" } }, "copy-status": "Preservation-Reproduction-Reference" } }, "creators": { "creator": { "creator-id": "1107050", "standard": "Y", "num": "1", "creator-record-type": "ORG", "creator-type": "Most Recent", "creator-display": "U.S. Senate. Office of Senate Curator.\\t(? - )", "summary": "true" } }, "variant-control-numbers": { "variant-control-number": { "mlr": "false", "variant-number": "NWL-46-BERRYMAN-H009", "num": "1", "variant-type": "NAIL Control Number", "variant-number-desc": "NWL-46-BERRYMAN-H009" } }, "arc-id-desc": "1693425", "indexable-dates": { "date-range": "[b_x16_120, b_x8_237, g_x64_30, b_x4_486, b_x16_119, g_x128_14, g_x32_59, g_x128_15, g_x16_118, g_x8_243, g_x32_60, g_x64_29, b_x2_974, b_x8_242, g_x16_121, g_x4_487]" }, "parent-control-group": { "parent-control-title": "Records of the U.S. Senate, 1789 - 2011", "parent-control-lod": "Record Group", "parent-control-id": "46" }, "_id": "1693425" }, "isShownAt": "http://research.archives.gov/description/1693425", "provider": { "@id": "http://dp.la/api/contributor/nara", "name": "National Archives and Records Administration" }, "@context": { "begin": { "@id": "dpla:dateRangeStart", "@type": "xsd:date" }, "@vocab": "http://purl.org/dc/terms/", "hasView": "edm:hasView", "name": "xsd:string", "object": "edm:object", "dpla": "http://dp.la/terms/", "collection": "dpla:aggregation", "edm": "http://www.europeana.eu/schemas/edm/", "end": { "@id": "dpla:end", "@type": "xsd:date" }, "state": "dpla:state", "aggregatedDigitalResource": "dpla:aggregatedDigitalResource", "coordinates": "dpla:coordinates", "isShownAt": "edm:isShownAt", "stateLocatedIn": "dpla:stateLocatedIn", "sourceResource": "edm:sourceResource", "dataProvider": "edm:dataProvider", "originalRecord": "dpla:originalRecord", "provider": "edm:provider", "LCSH": "http://id.loc.gov/authorities/subjects" }, "ingestType": "item", "dataProvider": "Center for Legislative Archives", "@id": "http://dp.la/api/items/02b4f072d067494f67b08d6a4100f143", "id": "02b4f072d067494f67b08d6a4100f143" } }

File

Yes, We Have No Ambitions Today! - Nara - 1693425.jpg

Description	English: This cartoon plays off a line from a popular 1923 song ("Yes, We Have No Bananas!") to characterize car maker Henry Ford's Presidential ambitions--or lack thereof. Ford blames his busy schedule for his hesitation to jump into the "Presidential contest pool," while eager supporters encourage him to "come on in!" Berryman was correct in his prediction: Ford chose not to pursue the Presidency.
Author	Berryman, Clifford Kennedy, 1869-1949
Date	1 July 1928
Current location	National Archives and Records Administration  Native name National Archives and Records Administration Location Washington, D.C. (headquarters), and many regional facilities and presidential libraries nationwide in the USA Coordinates 38° 53′ 34.01″ N, 77° 1′ 22.71″ W    Established 1934 Website www.archives.gov Authority control VIAF: 132254586 LCCN: n84176101 GND: 00605336X BnF: cb12182396f WorldCat
Record ID	This media is available in the holdings of the National Archives and Records Administration, cataloged under the ARC Identifier (National Archives Identifier) 1693425. This tag does not indicate the copyright status of the attached work. A normal copyright tag is still required. See Commons:Licensing for more information. Record group: Record Group 46: Records of the U.S. Senate, 1789 - 2011 (ARC identifier: 37) Series: Berryman Political Cartoon Collection, 1896 - 1949 (ARC identifier: 306080) NWL-46-BERRYMAN-H009
Source	U.S. National Archives and Records Administration
Permission (Reusing this file)	This work is in the public domain in the United States because it is a work prepared by an officer or employee of the United States Government as part of that person’s official duties under the terms of Title 17, Chapter 1, Section 105 of the US Code. See Copyright. Note: This only applies to original works of the Federal Government and not to the work of any individual U.S. state, territory, commonwealth, county, municipality, or any other subdivision. This template also does not apply to postage stamp designs published by the United States Postal Service since 1978. (See 206.02(b) of Compendium II: Copyright Office Practices). It also does not apply to certain US coins; see The US Mint Terms of Use. This file has been identified as being free of known restrictions under copyright law, including all related and neighboring rights.
Other versions	Please do not overwrite this file: any restoration work should be uploaded with a new name and linked in this page's "Other versions =" parameter, so that this file represents the exact file found in the NARA catalog record to which it links. The metadata on this page was imported directly from NARA's catalog record; additional descriptive text may be added by Wikimedians to the template below with the "descriptions =" parameter, but please do not modify the other fields. (Note: Editors who post this notice are strongly encouraged to add details explaining how it applies to this file.)

	The metadata on this page was imported directly from NARA's catalog record; additional descriptive text may be added by Wikimedians to the template below with the "Description=" parameter, but please do not modify the other fields.
	Please help us by reporting errors! This may include misidentifications, erroneous images, typos in the metadata, possible copyright issues, and poor-quality images needing rescanning. (Be aware that, for documentary purposes, NARA often retains the original image captions, which may be erroneous, biased, or even misspelled.)

Automatic or manually assisted: Automatic

Edit type (e.g. Continuous, daily, one time run): One time

Maximum edit rate (e.g. edits per minute): 10-15, as fast as it uploads

Bot flag requested: (Y/N): No

Programming language(s): Python 3.2

Will use metadata from DPLA bulk download for NARA. The metadata is in json, and is converted formatted to the template by the bot.

Smallman12q (talk) 23:41, 8 May 2013 (UTC)

Discussion

For reference, a previous NARA batch upload was approved at Commons:Bots/Requests/US National Archives bot.Smallman12q (talk) 23:41, 8 May 2013 (UTC)

• Yeah sure, looks good to me. --Dschwen (talk) 21:21, 9 May 2013 (UTC)

Usual suggestion: please use language template for Author/Source/Record ID fields. --EugeneZelenko (talk) 13:44, 11 May 2013 (UTC)

• Please can you put a deeplink in the "source" field, as that is where most editors will look. I tried to get the original of this example, but apparently "The Online Public Access (OPA) system will be down for maintenance from May 10 to May 25.", so we may not be able to thoroughly test this for a couple of weeks. --99of9 (talk) 13:01, 14 May 2013 (UTC)

Yes, I recently heard some details about that as well. I'll try to keep updated on the status. Bdcousineau (talk) 14:50, 16 May 2013 (UTC)

• What kind of label is: "NWL-46-BERRYMAN-H009"? It might help to add the name of this kind of identifier. --99of9 (talk) 13:02, 14 May 2013 (UTC)

That is an old catalog number used by NARA. It is no longer in use, but since it is in the current template used by NARA on Commons, it has been included. It most likely refers to the "NAIL" database, which was the in use prior to ARC/OPA, the current database. For a sample, see File:Football team on the field, Haskell Institute, Lawrence, Kansas, 1914 - NARA - 519149.jpg. Better removed? Bdcousineau (talk) 14:50, 16 May 2013 (UTC)

I'd suggest leaving it in there, but having the template do nothing with it (i.e. not display it). That way we can easily reintroduce it if someone thinks it is useful later. --99of9 (talk) 15:36, 16 May 2013 (UTC)

• 500k files! Wow, this is huge, congratulations and good luck! --99of9 (talk) 13:09, 14 May 2013 (UTC)

• Great start! Since this is a large set, and since the metadata will not be perfect (never is for a transfer of this size): are you thinking of staging this? Say, a few hundred to start, then 1k, then 10k, with pauses to see what sort of cleanup is needed? --SJ+ 22:40, 15 May 2013 (UTC)

 On hold-As stated at Online Public Access, access to records is suspended from the 10th to the 25th. (2 weeks is a loong roll out). Once access is restored, will do an initial batch upload of 100, 1000, then auto after that. Will also make source available once upload starts.Smallman12q (talk) 00:06, 24 May 2013 (UTC)

• Online Public Access online again. Bdcousineau (talk) 11:06, 29 May 2013 (UTC)

Can someone explain the process here? What does this have to do with DPLA (which does not host NARA images)? If you are just planning on copying the mostly low-resolution images from the catalog, I think we should slow down and concentrate on acquiring more of the high-resolution TIFF files like we did for the first mass upload. Also, with a separate mass upload based on a different set of source files, how are you planning to prevent uploading tens of thousands of duplicates? Dominic (talk) 16:37, 4 June 2013 (UTC)

Rybecbot (2) (talk · contribs)

Operator: Rybec (talk • contribs • recent activity • count • block log • rights log • upload log • SUL)

Bot's tasks for which permission is being sought: Sometimes when files are transferred from Flickr by a bot, the tags on Flickr lead the bot to add inappropriate categories. For example, this photo of some rocks in shallow water was given the unhelpful categories Commons, Facebook, Flickr, Google, News, Pic, Wallpaper, Wiki, Wikipedia and Photographs. Mass importation of files causes a need for mass removal of categories, which is what this request is for.

Automatic or manually assisted:automatic with some supervision

Edit type (e.g. Continuous, daily, one time run):occasional

Maximum edit rate (e.g. edits per minute):4

Bot flag requested: (Y/N):Y

Programming language(s): Python (standard pywikipedia category.py or replace.py script)

Rybec (talk) 02:14, 31 March 2013 (UTC)

Discussion

• Test edits have been done: 50 files were removed from the News category. Rybec (talk) 06:33, 31 March 2013 (UTC)

• So do you remove every image in this kind of category, or only those from Flickr, or??? --99of9 (talk) 13:13, 31 March 2013 (UTC)

I think you could make better edit summaries, like Removing [[Category:News]]. Also will be good idea to remove from several categories at once edit when applicable. --EugeneZelenko (talk) 14:22, 31 March 2013 (UTC)

• The bots that import images from Flickr don't create new categories, but only add images to categories that already exist, so my intention is not to get rid of the categories entirely. When a category should contain no images but only subcategories, then I would want to empty it of images, but typically there would be some images which belong and others which don't. My intention is to manually identify the ones which don't belong, make a list of them, then have the script make the changes.

I've done another three test edits to show removal of multiple categories in a single edit with a non-default edit summary: [1] [2] [3]. Rybec (talk) 21:09, 31 March 2013 (UTC)

Looks OK for me, but I think will be good idea to use link to categories in edit summary. --EugeneZelenko (talk) 14:36, 3 April 2013 (UTC)

I don't object to doing that. Rybec (talk) 00:48, 4 April 2013 (UTC)

I’ve have had the same kind of trouble with stuff bot-uploaded from Flickr being piled up in Category:Lisbon (a much more specific category than those above, of course), which is a pain to clean up manually. There’s a few things that the importing tool could do automaticly, like avoiding over-categorization (e.g. if a photo is under Category:Streets in Lisbon is should not be also under Category:Lisbon), but more or less human input and manual work is going to be needed sooner or later. A big problem is how to tell apart what media really belong in a given category from those that should be further moved to more detailed subcategories within the same tree. I’d really like to have separate "(cleanup)" subcategories for all categories afflicted by this kind of flooding, really. -- Tuválkin ✉ 20:18, 5 April 2013 (UTC)

SamoaBot 2 (talk · contribs)

Operator: Ricordisamoa (talk • contribs • recent activity • count • block log • rights log • upload log • SUL)

Bot's tasks for which permission is being sought: detecting and logging (in a user subpage) SVG images without a proper xmlns declaration on the root <svg> element: those images aren't viewable at all in some browsers, and should be properly fixed (this can be done later, either manually or automatically)

Automatic or manually assisted: automatic, supervised

Edit type (e.g. Continuous, daily, one time run): intermittently

Maximum edit rate (e.g. edits per minute): about 1 edit per minute (max)

Bot flag requested: (Y/N): N (already flagged, see [[../SamoaBot]])

Programming language(s): JavaScript, with Ajax (own code, will be published soon)

Ricordisamoa 04:56, 26 March 2013 (UTC)

Discussion

Here can be seen the log of all images detected so far.--Ricordisamoa 06:02, 26 March 2013 (UTC)

• How hard would it be for your bot to fix them and reupload? --99of9 (talk) 23:42, 26 March 2013 (UTC)

  It is currently written in JavaScript (I plan to switch to Python in a few weeks), and Ajax upload isn't tested yet, but I will try to do as much as possible. In the meantime, it could however log these files. --Ricordisamoa 02:52, 27 March 2013 (UTC)

I think will be good idea to add maintenance template to image page too.

Edit summary for log action could be just file name with a link, log page name is self-explanatory.

EugeneZelenko (talk) 14:44, 27 March 2013 (UTC)

Does a proper template exist for these cases? (and I'll work on edit summary) --Ricordisamoa 06:14, 28 March 2013 (UTC)

{{BadSVG}} may be adapted for this purpose, or {{Cleanup image}} may be used. --EugeneZelenko (talk) 14:47, 28 March 2013 (UTC)

•  Info In Firefox, you can use the sendAsBinary() method of your XHR-instance to upload the SVG. This avoids encoding issues (while some SVGs also work with the send method, this will screw up others). Downloading is very easy through a GET since the cross-origin-issue is resolved.
• I created a sample that works with FF 19 (tested): User:Rillke/fastTransfer.js. It downloads and uploads a file immediately when invoked. You have access to the raw data in function _gotFile so you can manipulate that data. -- Rillke^(q?) 20:43, 28 March 2013 (UTC)

• I had a look with Firefox 19. It displayed two of the nine files on the list.

(E)-pent-2-ène.svg does not display

(Z)-pent-2-ène.svg does not display

(±)-Ethyl-2-methylbutyrate_Structural_Formulae_V.1.svg has been re-uploaded several times; version of 13:06, 26 March 2013 does not display and Mediawiki did not generate a thumbnail for it; other versions okay

1-Chlornaphthalin.svg displays correctly

1-jpg.svg Mediawiki says there's an error in the file; does not display in browser

1025arud.svg Mediawiki says there's an error in the file; does not display in browser

10th_Panzer_Division_logo_1.svg has been re-uploaded, but both versions displayed correctly

1422_Zeta_in_the_Serbian_Despotate_after_death_Balsa_III.svg does not display

1885ArmenianFlag.svg has since been re-uploaded; original file did not display

Rybec (talk) 22:21, 28 March 2013 (UTC)

OK, now I'm going to run a fixed version of the script; let's see... --Ricordisamoa 23:16, 28 March 2013 (UTC)

• I tried to view the new additions to the list, with similar results: most of the files did not display, but one did. I don't know enough about the subject to say definitively that there are false positives.

1969_draft_lottery_scatterplot.svg file has been replaced; old version did not display in Firefox

1988_Illinois_Constitutional_Convention_Vote_pie_chart.svg file has been replaced; old version did not display in Firefox

1st_Panzer_Division_logo.svg displays correctly in Firefox

2-propil-amine.svg does not display in Firefox

201globe.svg file has been replaced; old version did not display in Firefox

250x250Feld.svg does not display in Firefox

2NOGCMOS.svg does not display in Firefox

Even with the possible false positives, the usefulness of this list is apparent. If making the list is all that this request covers, I fully support it (if the request is also about automatically fixing the problems that are found, I don't support that part: some unneeded changes might be made, and test edits fixing the SVG files haven't yet been done). Rybec (talk) 23:55, 30 March 2013 (UTC)

After 1st_Panzer_Division_logo.svg I changed the code, so it should work well now. --Ricordisamoa 10:54, 31 March 2013 (UTC)

I  Support this request, but I'm leaning against applying the bot flag. If it's only editing one page, and even that only once per minute, I don't see it as necessary. Am I missing a reason you need the flag? --99of9 (talk) 11:10, 31 March 2013 (UTC)

The purpose of the bot flag is to avoid flooding RCs (if the bot's speed is out of control)... anyway, there's also the first request. --Ricordisamoa 13:57, 31 March 2013 (UTC)

What is final functionality? Will bot re-upload fixed files, or only log problematic files? If last is true, will be clean-up template added to file page? --EugeneZelenko (talk) 14:26, 31 March 2013 (UTC)

In case it is only logging, I can try to write a JavaScript-Bot which fixes the issue that does not need any other host than a compatible browser to run. IMHO a logging-bot does not need a bot-flag but it would be great if we could combine this functionality (detection and fixing). Then, we also do not need to log each occurrence or adding a template. -- Rillke^(q?) 09:16, 1 April 2013 (UTC)

You get my {{support}} --Ricordisamoa 11:15, 1 April 2013 (UTC)

I need your source code. -- Rillke^(q?) 09:54, 2 April 2013 (UTC)

→ User:Ricordisamoa/XMLNSense.js --Ricordisamoa 10:23, 2 April 2013 (UTC)

┌─────────────────────────────────┘
Thank you. → User:Rillke/MwJSBot.SVGXmlNSFixer.js. Log and continue-params are written to my user space by default but this can be customized by creating an own instance of window.SVGXmlNSFixer. Detection of svg root in its own svg namespace like for this file has to be fixed.

• Files processed so far by the script:
  • File:A-weighting, ISO 226 and ITU-R 468.svg
  • File:5 inch floppy.svg
  • File:2NOGCMOS.svg
  • File:(E)-pent-2-ène.svg
  • File:(Z)-pent-2-ène.svg

-- Rillke^(q?) 20:35, 3 April 2013 (UTC)

So could you operate a real bot for this task? --Ricordisamoa 20:52, 3 April 2013 (UTC)

I've no dedicated server/computer for this task, if that is your question. But I think if I or someone else continue(s) running this JavaScript over all 666,540+ SVG files, it would be a good idea to ask whether other issues with SVG files should be considered as well. Also the speed/bandwidth is not really sufficient… -- Rillke^(q?) 16:58, 4 April 2013 (UTC)

I meant "a flagged bot account"; BTW, I got the flag (for another task). --Ricordisamoa 18:47, 4 April 2013 (UTC)

I've no flagged bot account where the task would be appropriate to run under. -- Rillke^(q?) 20:18, 4 April 2013 (UTC)

Would your script work on Chromium/Chrome? --Ricordisamoa 21:16, 4 April 2013 (UTC)

It seems so. At least the loop runs and the parser does its job. Not entirely sure whether the upload will work but it's very likely (it's using the usual XHR.send() as SVGs are UTF-8 encoded). -- Rillke^(q?) 22:00, 5 April 2013 (UTC)

Should I continue running the script (e.g. under RillkeBot (not flagged)), would you like continuing running it, or do we want to split the load, are there questions left? -- Rillke^(q?) 20:44, 14 April 2013 (UTC)

For me it's ok, but you should get a bot flag; I'm thinking it may be better to swich to Pywikipediabot, though. --Ricordisamoa 13:30, 15 April 2013 (UTC)

How many files are we approximately looking at? If it is of the order of a hundred or less then I suggest to just go ahead with it. --Dschwen (talk) 21:26, 9 May 2013 (UTC)

It would have to check all files on the Commons, and upload at least several hundred images... However, I have PWB installed, and will starting coding something tomorrow. --Ricordisamoa 21:54, 9 May 2013 (UTC)

First of all you'll have to check all SVG files. Secondly, when you code please make sure to do a http range request! Try downloading just the first kilobyte of each file you are analyzing. This should speed things up. Let me know if you need help with that in python, I've implemented it before. --Dschwen (talk) 22:38, 9 May 2013 (UTC)

Rybecbot (talk · contribs)

Operator: Rybec (talk • contribs • recent activity • count • block log • rights log • upload log • SUL)

Bot's tasks for which permission is being sought: re-uploading photos which have been cropped to remove watermarks and editing accompanying text to indicate the watermark has been removed

Automatic or manually assisted: automatic, lightly supervised

Edit type (e.g. Continuous, daily, one time run): one time run

Maximum edit rate (e.g. edits per minute): 2 when uploading files, 4 when changing text

Bot flag requested: (Y/N): Y

Programming language(s): Python (the Pywikipediabot upload.py script with minor changes and the replace.py script with no changes)

Rybec (talk) 05:29, 22 March 2013 (UTC)

Discussion

• Badly needed. Please execute a batch of runs as an example. --Foroa (talk) 06:54, 22 March 2013 (UTC)
• I'm having trouble doing the test edits because the newly-created bot account doesn't have reupload permission (just reupload-own)--I checked here. Rybec (talk) 12:18, 22 March 2013 (UTC)
  • Yes it's very nasty for new bot accounts. Should work now! -- Rillke^(q?) 18:10, 22 March 2013 (UTC)

    Thank you! I've done the test edits. I only prepared 24 files to replace instead of the suggested 30 to 50. Rybec (talk) 20:42, 22 March 2013 (UTC)

Please do not continue until the bot preserves Metadata and please repair this for all edits done so far by the bot. Example where data is lost at File:047-1211 Enschede 125.JPG (before after processing). Please also include a meaningful upload/edit summary (like "image cropped to remove watermark"). Thank you! -- Rillke^(q?) 21:55, 22 March 2013 (UTC)

 Question Which software do you use for cropping the file? Is it lossless? -- Rillke^(q?) 22:02, 22 March 2013 (UTC)

• Thanks for the review! I used jpegtran, which is lossless. I hadn't noticed the problem with the EXIF data; I don't know why that happened. Rybec (talk) 22:19, 22 March 2013 (UTC)
  • ExifTool is, for example capable copying (nearly) all metadata from the original file to the edited one. This way you could ensure they are never lost. -- Rillke^(q?) 10:38, 23 March 2013 (UTC)
• I've reverted my test/example edits. Rybec (talk) 22:34, 22 March 2013 (UTC)
  • Thank you. -- Rillke^(q?) 10:38, 23 March 2013 (UTC)

• Great demand exists for automated removal of watermarks, and this pioneering bot is brilliant :D I would say the exif is less important at the moment especially if the information is still made available with the older version. If it inspires people to make exif copying bots, all the better. I believe it is not long before we see watermark removal bots that mend the picture rather than crop, but for the time being, in these chaotic times where trigger fingers are blocking people for good contributions, Rybec's bot would help bring some badly needed relief and order. Rybec certainly seems responsive, capable, and I recommend flagging his bot forthwith ! I can't see maintenance and improvements being a problem. Penyulap ☏ 05:59, 23 March 2013 (UTC)
  • In this case they contained copyright and camera information and it is quite bad if they aren't visible any more at the file description page. -- Rillke^(q?) 10:38, 23 March 2013 (UTC)

•  Question: Does your bot automatically detect the watermarks or are you manually instructing what to crop? -- Rillke^(q?) 10:38, 23 March 2013 (UTC)

  I was just using the identify command from Imagemagick to get the pixel size of downloaded images, subtracting 138 from the height, scripting jpegtran to crop to that size, and the only function of the bot is the re-uploading. I agree that the metadata is important. The problem was that I didn't use the "copy all" option to jpegtran. I've manually uploaded to File:1210_Turnhout_029.JPG one example of a file cropped with the "copy all" option. Its EXIF data is preserved. I also learned how to do an edit summary with the script: [4]. I've started another test run, with the metadata and the edit summaries. Rybec (talk) 11:51, 25 March 2013 (UTC)

• Someone pointed out the need to remove {{watermark}} and the category Category:Uploads by Microtoerisme with watermarks. I was thinking that could be done with VisualFileChange.js. Rybec (talk) 12:47, 25 March 2013 (UTC)

Not remove "watermark", but change it to "watermark removed". ("watermark removed" is appropriate for these uploads) – JBarta (talk) 13:01, 25 March 2013 (UTC)

I've done a second test run, changing {{watermark}} to {{watermark removed}} and removing [[Category:Uploads by Microtoerisme with watermarks]] as described by Jbarta. The files can be seen at Special:ListFiles/Rybecbot. I've changed my request to add the use of the standard replace.py script for the textual changes. Rybec (talk) 21:41, 28 March 2013 (UTC)

Results look good to me. --VanBuren (talk) 21:52, 1 April 2013 (UTC)

• Suggestion - Howdy. I suggest using {{Attribution metadata from licensed image}} instead of {{watermark removed}} because the latter redirects to the former. Also, I suggest checking to see if one of those templates is already on the page. When you made this edit, the template was already on the page.--Rockfang (talk) 10:53, 6 April 2013 (UTC)

I wasn't even aware that "Attribution metadata from licensed image" existed. Might I suggest that "watermark removed" is more used, more intuitive and easier to spot than the other? The resulting template on the image description page is the same either way. Just a thought. – JBarta (talk) 11:36, 6 April 2013 (UTC)

Assuming Jarry1250's Toolserver Template transclusion count tool is correct, {{Attribution metadata from licensed image}} is transcluded 6,192 times while {{Watermark removed}} is transcluded 3,422 times. If an image license doesn't require attribution, then {{Metadata from image}} can be used.--Rockfang (talk) 13:35, 6 April 2013 (UTC)

• The mistaken edit found by Rockfang is one I did manually. When doing the textual replacements, the bot will look for the specific text "{{watermark}}" (by which I mean, enclosed in curly brackets) and change it. Only if {{watermark}} appeared twice already, or together with {{watermark removed}} would it make the same mistake I did. If it encounters "{{watermark removed}}" it does not do any replacement. In other words, it's not inserting {{watermark removed}} but rather changing {{watermark}} to {{watermark removed}}. For the text replacement task I want to use the standard replace.py script from pywikipedia. I don't especially mind using {{Attribution metadata from licensed image}} rather than {{watermark removed}}, although the latter is more succinct. On Wikipedia, using redirects in a similar manner is considered okay. Is it the same here? Is the redirect likely to be deleted? If not, it seems to me like a matter of indifference. Rybec (talk) 22:05, 6 April 2013 (UTC)

UWCTransferBot (talk · contribs)

Operator: Ahonc (talk • contribs • recent activity • count • block log • rights log • upload log • SUL)

Bot's tasks for which permission is being sought: I wrote a bot using php for transfering free images from Ukrainian Wikipedia to Commons. It is an alternative to CommonsHelper, as CommonsHelper often generates bad descriptions and they are to be checked and fixed, and my bot is better adjusted for it. Images will be checked by local sysops before transfer.

Automatic or manually assisted: automatic

Edit type (e.g. Continuous, daily, one time run): one time per day

Maximum edit rate (eg edits per minute): 5-10

Bot flag requested: (Y/N): Y

Programming language(s): PHP, based on Chris G's botclasses framework.

Anatoliy (talk) 21:52, 18 March 2013 (UTC)

Discussion

Looks like human review before transfer is good idea (example: File:Вп станция сихов.jpg). Also better author attribution is possible (File:Врубель Серафим.jpg, File:Бівуак. Чатир-Даг..JPG). As well as better categorization (File:Голосіїв.jpg).

EugeneZelenko (talk) 14:18, 19 March 2013 (UTC)

Situation like in first example is fixed. Such images will not transfered from uk-wiki. They should be transfered from original wiki (in this example Russian). Categories for Commons are taken from template 'Move to Commons' in file description in local wiki.--Anatoliy (talk) 12:00, 8 May 2013 (UTC)

• Please can you internationalize the headings to save us having to do this [5] --99of9 (talk) 13:26, 14 May 2013 (UTC)

  Fixed. Changes will be applied during next run.--Anatoliy (talk) 17:02, 14 May 2013 (UTC)

• I still think more human participation in images preparations on Ukrainian Wikipedia is necessary. If it will not done there, chances of fixing problems is less likely here. --EugeneZelenko (talk) 14:41, 28 May 2013 (UTC)

JAnDbot (talk · contribs)

Operator: JAn Dudík (talk • contribs • recent activity • count • block log • rights log • upload log • SUL)

Bot's tasks for which permission is being sought: replacing text, recategorization, maybe more

Automatic or manually assisted: both

Edit type (e.g. Continuous, daily, one time run): Sometimes

Maximum edit rate (eg edits per minute):

Bot flag requested: (Y/N): Yes (global bot)

Programming language(s): pywikipedia

JAn Dudík (talk) 10:29, 21 February 2013 (UTC)

Discussion

Could you be a bit more specific please about what you intend to do with your bot? --Dschwen (talk) 14:37, 21 February 2013 (UTC)

Since there was zero further input from the requester I will close this as stale soon. --Dschwen (talk) 23:13, 12 March 2013 (UTC)

I want to use bot mainly for mass recategorization or mass replacing of text, see contributions. Maybe, when Wikidata will be able to store links to commons, I'll work on this field too. JAn Dudík (talk) 07:12, 13 March 2013 (UTC)

You mean the several thousand edits your bot made without having a flag? Please don't do that or we will have to block the bot. Recategorizations are already performed by User:Category-bot. And I won't give out a bot flag for a maybe job. I'll close this one. You are welcome to reopen a request if and when you have a specific task (that is not already covered by an existing bot). --Dschwen (talk) 15:26, 13 March 2013 (UTC)

Although I agree that the unapproved volume was inappropriate, the 23 Feb URL format changes like this look useful. So if you can give us a clear, more focused/limited scope, I'd potentially support. --99of9 (talk) 22:44, 13 March 2013 (UTC)

Maybe we could create a template for "URL REKOS", to prevent all those bot edits. --Ricordisamoa 22:23, 25 March 2013 (UTC)

Sorry, I am not daily editor of commons, but sometimes I (or somebody else from cs.wiki) need to do more edits - and looking for somebody with bot, then translate request... Bots are for helping, but this looks to me like bureocracy :-( JAn Dudík (talk) 18:28, 30 May 2013 (UTC)

We need to know what you will be doing (more specifically than "mass recategorization... maybe more"). That's even more important if you're not a regular commons user. I'm sorry if you don't like the bureaucratic nature of these requests, but, think of it as a conversation. Bots are powerful tools, and it's important for the community to have their say about what you propose to do. --99of9 (talk) 18:55, 30 May 2013 (UTC)

Neuchâtel Herbarium (talk · contribs)

Operator: Chandres (talk • contribs • recent activity • count • block log • rights log • upload log • SUL)

Bot's tasks for which permission is being sought: Upload of the pictures created by the commons:Neuchâtel Herbarium project

Automatic or manually assisted: semi automatic, I launch the script manually for a fixed number of picture to upload , but once it's started the process is automatic

Edit type (e.g. Continuous, daily, one time run):around 40 000 pictures remain to be upload, by batch when I'm available to control the upload process, no full automatic work

Maximum edit rate (eg edits per minute):4-5 upload per minute

Bot flag requested: Y:

Programming language(s):

Chandres (talk) 14:27, 13 February 2013 (UTC)

Discussion

It might be a good idea to respect the capitalisation of the categories. So far, I renamed the categories of the majority of your uploads. --Foroa (talk) 14:56, 13 February 2013 (UTC)

Thanks for the warning , we update the script and I will correct the already upload pictures.--Chandres (talk) 15:01, 13 February 2013 (UTC)

I think will be good idea to use Bot in account name. Why Template:Information is not used? --EugeneZelenko (talk) 15:46, 13 February 2013 (UTC)

It's not really a bot account, it's always me behind, but used with a script. --Chandres (talk) 18:05, 20 February 2013 (UTC)

Well, using [[tl|Specimen}} is probably some sub-project policy which we could argue against until we are blue in the face... The sourcecode of the description page is formatted in a very confusing way. It took me 3 minutes to figure out where the closing template braces are and to realize that {{Information field}} is uses within the description field. This needs to be made clearer. --Dschwen (talk) 16:26, 13 February 2013 (UTC)

 {{Specimen
 |taxon=Abies alba
 |authority=
 |institution={{Institution:University of Neuchâtel}}
 |description=
 {{en|1=Neuchâtel Herbarium - ''[[:en:Abies alba]]''}}
 {{de|1=Neuchâtel Herbarium - ''[[:de:Abies alba]]''}}
 {{fr|1=Neuchâtel Herbarium - ''[[:fr:Abies alba]]''}}
 {{it|1=Neuchâtel Herbarium - ''[[:it:Abies alba]]''}}
 |date=
 |source={{own}}
 |author=[[User:Neuchâtel Herbarium|Neuchâtel Herbarium]]
 |permission=
 |other_versions=
 |other_fields={{Information field|name={{Occupation|1=Botanist}}|value=?}}
 }}

Actually it is a minor miracle that the old version doesn't produce invalid HTML. If you want to use {{Information field}} please add it to the other_fields parameter. --Dschwen (talk) 16:34, 13 February 2013 (UTC)

Is this being adressed? --Dschwen (talk) 17:06, 19 February 2013 (UTC)

Yes, if , see below :-)--Chandres (talk) 18:05, 20 February 2013 (UTC)

Do we need the "description" ? It seems redundant with other parameters. I have proposed an alternate layout at File:Neuchâtel Herbarium - Abies alba - NEU000003665.tif. --Zolo (talk) 20:09, 14 February 2013 (UTC)

The actual description field is important for the project by the providing the links to the wikipedia articles in several language, especially the swiss one. But if anybody has ideas on how improving this information part, I will be more than happy! --Chandres (talk) 08:35, 18 February 2013 (UTC)

You mean, in this case, the link to en:Abies alba. There is a link to the corresponding category in the header. I would also prefer a link to Wikipedia, but we should be able to have that once wikidata: is deployed to Commons (hopefully, in a few months). Personnally, I find it unintuitive and rather confusing to have two different links just a few lines away from each other, without clear rationale why one links to Wikipedia and the other to Commons. --Zolo (talk) 05:06, 19 February 2013 (UTC)

I find that the link the the commons category give less information than a link to the wikipedia article, but maybe we could improve the wording of the description to be more explicit. The idea of having the link to wikipedia article is "reader oriented", whereas commons category is really "wikimedian oriented". I don't want to wait for Wikidata deployment, we never what will happend, and we can always run a bot to correct that afterwards. --Chandres (talk) 18:05, 20 February 2013 (UTC)

• I would like a more expansive description for those who stumble across a file and don't want to read the background of the whole project. My suggested change is here. In some of the test uploads (e.g. File:Neuchâtel Herbarium - Asplenium Viride - NEU000000475.tif there is no description at all!) --99of9 (talk) 23:55, 26 March 2013 (UTC)

The addition of "dried pressed specimen" is ok in english, but would complicated ,without benefice, the script in other language. I will control after upload if all description are present.--Chandres (talk) 06:51, 3 May 2013 (UTC)

• I don't completely understand your answer. Do you mean that you do not know the translation for "dried pressed specimen" in the languages you plan to use, or do you mean that it would be hard to add the words to each language? (Sorry for the slow reply) --99of9 (talk) 13:13, 14 May 2013 (UTC)

sorry for the slower reply :-D In french italian and german, we struggled to find a sentence that do not change according to the first letter of the species. But we managed and now we found a good alternative: http://commons.wikimedia.org/wiki/File:Neuch%C3%A2tel_Herbarium_-_Isoetes_lacustris_-_NEU000020015.tif --Chandres (talk) 11:44, 3 June 2013 (UTC)

That looks good to me! --99of9 (talk) 13:40, 3 June 2013 (UTC)

For the record the actual template is the following, any improvement is welcome:

=={{int:filedesc}}==

{{Specimen
|taxon=<TMPL_VAR NAME=GENIUS> <TMPL_VAR NAME=SPECIE>
|authority=
|institution={{Institution:University of Neuchâtel}}
|description=
<TMPL_IF NAME=IWEN>{{en|1=Dried pressed specimen of ''[[:en:<TMPL_VAR NAME=IWEN>]]''}}</TMPL_IF>
<TMPL_IF NAME=IWDE>{{de|1=Getrocknete und gepresste Einzelprobe aus ''[[:de:<TMPL_VAR NAME=IWDE>]]''}}</TMPL_IF>
<TMPL_IF NAME=IWFR>{{fr|1=Spécimen de plante séchée et pressée de l'espèce ''[[:fr:<TMPL_VAR NAME=IWFR>]]''}}</TMPL_IF>
<TMPL_IF NAME=IWIT>{{it|1=Esemplare di pianta essiccata e pressata della specie ''[[:it:<TMPL_VAR NAME=IWIT>]]''}}</TMPL_IF>

|date=<TMPL_VAR NAME=DATE>
|source={{own}}
|author=[[User:Neuchâtel Herbarium|Neuchâtel Herbarium]]
|permission=
|other_versions=
|other_fields= {{Information field
|name={{Occupation|1=Botanist}}|value=?}}
}}


{{Neuchâtel Herbarium}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}


[[Category:<TMPL_VAR NAME=GENIUS_UCFIRST> <TMPL_VAR NAME=SPECIE>]]

--Chandres (talk) 07:33, 5 June 2013 (UTC)

• Is the botanist known for any of your items? The ones I've randomly checked have all been "?". If they're nearly all unknown, I'd suggest leaving that field out for those where the botanist is unknown. --99of9 (talk) 10:04, 5 June 2013 (UTC)

• we will fill this parameter afterwards, it's part of another project. --Chandres (talk) 09:03, 10 June 2013 (UTC)

Categories

Please don't create thousands of red and/or invalid categories. I'v put some in Category:Neuchâtel Herbarium Project categories to be classified for further correction/classification. --Foroa (talk) 09:41, 10 June 2013 (UTC)

Hello, I'm aware of this, and it's planned to fix all the categories at once per batch. At the origin the ""XX (herbarium specimen)" was not planned, but because people start to change the categorization without coordination herbarium sheet, herbarium, herbarium specimen, etc, we move to a standard categorization that will assure the coherency, but for that we need to create first the red categories.--Chandres (talk) 09:53, 10 June 2013 (UTC)

Smallbot (talk · contribs)

Operator: Smallman12q (talk • contribs • recent activity • count • block log • rights log • upload log • SUL)

Bot's tasks for which permission is being sought: To upload files related to Commons:Batch uploading/ECGPedia The files that will be uploaded can be found at User:Smallbot/source/Cardionetworks

This is based on OTRS Ticket#2011102310008874 . The ticket is a year old.

Related discussions:

• w:Wikipedia:Village_pump_(proposals)/Archive_76#Attribution_of_images
• w:Wikipedia_talk:WikiProject_Medicine/Archive_22#Offer_to_share_images

Automatic or manually assisted:automatic

Edit type (e.g. Continuous, daily, one time run): One time run...though there may be future uploads

Maximum edit rate (eg edits per minute): depends on upload speed (10)

Bot flag requested: (Y/N): N

Programming language(s): VBScript (Javascript, XMLHTTP, MSHTML, XMLDOM, COM).

Smallman12q (talk) 16:56, 1 December 2012 (UTC)

Discussion

A lot of the files lack a description. Also, how should author information be handled? There are a number of .swf, a format that will never be supported on commons Bugzilla: 26269, that could be converted to a supported video format. The .avi could be converted to a supported video format.Smallman12q (talk) 16:56, 1 December 2012 (UTC)

Please make test uploads. --EugeneZelenko (talk) 15:42, 2 December 2012 (UTC)

First, I need to verify the OTRS ticket and make the relevant template. I've asked at Commons:OTRS/Noticeboard#Cardio_Networks.Smallman12q (talk) 17:33, 2 December 2012 (UTC)

The answer from another OTRS volunteer on that page:

License template exist at Template:Cardionetworks permission that provides the relevant details. Regards -- KTC (talk) 18:14, 2 December 2012 (UTC)

Hope this helps, if not, don't hesitate to remove the {{section resolved}} template and ask further! Trijnstel_talk 18:57, 2 December 2012 (UTC)

Thanks. Didn't know the template was already made. Will do upload later this week.Smallman12q (talk) 20:39, 2 December 2012 (UTC)

Wonderful. Will these images all be put together in a single category? Do you need anything further from my end? James Heilman, MD (talk) 18:34, 13 December 2012 (UTC)

I don't see the test uploads yet. Also can you supply links to a few swf files? If they are either static or videos they could be converted as well. Do you have a solution for converting the avi videos yet? --Dschwen (talk) 00:46, 16 January 2013 (UTC)

Working-I'm going to do this upload this week..was busy with Commons:Gerald R. Ford Presidential Library and Museum but they seem to be stuck in a bureaucratic quagmire. The .swf files have an equivalent .avi file (my guess is the .swf is just a flash wrapper for those who can't play .avi but have flash). The .avi will be converted to the webm format(which the commons now supports) before upload. I am in the process of downloading the files... probably around 10GB + for each wiki. I've written a script that will download all files, the file history table for each file, and text of the file for a wiki so this may be handy for future uploads. A lot of the files lack any text so I'm not sure what to put for these. Any thoughts are welcome.Smallman12q (talk) 00:41, 28 January 2013 (UTC)

What are some examples of fills missing text? James Heilman, MD (talk) 01:02, 28 January 2013 (UTC)

There are quite a few files missing text. Have a look at User:Smallbot/source/Cardionetworks/Example to see how the uploads will look (including those missing text). Let me know if it looks okay.Smallman12q (talk) 17:18, 29 January 2013 (UTC)

Yes that is okay. We will need to go through and add this after the fact. James Heilman, MD (talk) 02:01, 31 January 2013 (UTC)

A few peculiarities

• Afib_ecg.jpg (and a few more) == Description == inside the description value in the Information template.
• 2072.jpg this description is not useful (maybe tag everything with a description of less then 10 chars as needing description)
• Course.jpg this is most likely a copyright violation (stock image, compare to this image or do google image search or tineye.

That last point makes me a bit uneasy about the whole task. --Dschwen (talk) 21:39, 31 January 2013 (UTC)

I've uploaded ECGpedia at Category:Media from CardioNetworks ECGpedia. I fixed the description issue I believe. I will go back and add {{Description missing}} to descriptions with less than 10 characters. I've requested speedy-delete for File:Course (CardioNetworks ECGpedia).jpg I'll do uploads of the other pediass tmrw.Smallman12q (talk) 03:49, 1 February 2013 (UTC)

Sure so 2) the HR = 32 means that the heart rate is 32, standard shorthand and useful 3) I have sent a note to the up loader there and we will figure out who has copied from who. Does look like it is from here though [6]. The point is the ECGs though and not the clip art. James (log in appears broken)

Ok, so it was probably a fluke. I suggest you go ahead and do a few more test uploads. We should be able to resolve this quickly if you have time. --Dschwen (talk) 02:49, 2 February 2013 (UTC)

@Dschwen Resolve what exactly? I'll do echopedia.org next.Smallman12q (talk) 19:32, 2 February 2013 (UTC)

This bot request. --Dschwen (talk) 15:23, 3 February 2013 (UTC)

┌─────────────────────────────────┘
For Echopedia, a lot of the files have no description, I will see if I can get some from the template on case files pages.Smallman12q (talk) 02:32, 5 February 2013 (UTC)

I have had a look at both ECGpedia and Echopedia and am sceptical as to the usefulness of this bot approach. What it does on the Commons end (i.e. after spidering the source side) is (1) upload the files with (2) information on source, author and licensing, (3) add maintenance categories. For most of the files, this leaves Commons users with the tasks of (4) providing descriptions, (5) providing content categories and (6) renaming the files to Commons standards. That is a lot to ask for, and so I would personally favour an approach more akin to Flickr2Commons, in which individual Commons users import selected materials, and thus take responsibility for them here. Another thing I noticed is that the image pages over there link to "description pages" on Commons, which never exist because the files have the " (CardioNetworks ECGpedia)" suffix here. Has that anything to do with their collaboration with us or is this simply an error in their MediaWiki configuration? -- Daniel Mietchen - WiR/OS (talk) 22:38, 8 February 2013 (UTC)

I tend to agree with Daniel here. There hasn't been a lot of discussion whether this stuff should be imported. I can see that some of the files can provide educational value, but this is largely dependent on good descriptions. Is there an anticipated use for those file on Wikimedia projects? Ie. Wikiversity cardiology? ;-) --Dschwen (talk) 23:01, 8 February 2013 (UTC)

An obvious use case would be WikiProject Medicine but the usefulness certainly depends on the quality of the descriptions and discoverability by way of categories (or perhaps file names). -- Daniel Mietchen - WiR/OS (talk) 23:05, 8 February 2013 (UTC)

For the stuff already imported, I suggest adding specific (rather than things like {{Description missing}}) maintenance categories that address the points 4-6 in my comment from an hour ago, i.e. something like Category:Media from CardioNetworks ECGpedia missing descriptions (for which an alternative would be CatScan), Category:Media from CardioNetworks ECGpedia missing categories (these have not been tagged at all, by the way, since Category:Media from CardioNetworks ECGpedia had not been marked as hidden and thus counted as a content category) and Category:Media from CardioNetworks ECGpedia needing file name review. This way, people interested in helping out with ECGpedia can dive right in and do not have to spend time searching for files in need of their help. -- Daniel Mietchen - WiR/OS (talk) 23:25, 8 February 2013 (UTC)

In terms of converting multimedia files to OGG, it may be worthwhile to have a look at media.py. Adding WebM support to that is easy. -- Daniel Mietchen - WiR/OS (talk) 23:02, 8 February 2013 (UTC)

For converting to .webm, I'll be calling w:FFmpeg in a subprocess from python. Daniel Mietchen's description above is fairly accurate as my bot is spidering and then uploading whatever info it can get...which isn't that much. The links to commons from the pedia pages are non-existent (it's a bug). I could add a custom description missing template and whatnot. So far, none of the files are being used...so I'm not sure if I should upload more files for Echopedia. I will post a note to WikiProject Medicine as to whether this upload is worthwhile.Smallman12q (talk) 22:37, 14 February 2013 (UTC)

I plan to go through the ECGs, add descriptions and than add many of them to the appropriate Wikipedia article. James Heilman, MD (talk) 01:37, 15 February 2013 (UTC)

I've uploaded ECHOpedia to Category:Media from CardioNetworks ECHOpedia. I could do animated gifs for the videos, but most would fall in the 25-30 million total pixel range and currently only less those with 25 million will be rendered.Smallman12q (talk) 17:19, 18 February 2013 (UTC)

Upload videos as videos. It makes no sense to convert them into animated GIFs nowadays. --Dschwen (talk) 22:20, 18 February 2013 (UTC)

Animated

Thumbnail not animated

The videos are 1-2 second clips. Here's what a gif version would look like.Smallman12q (talk) 22:39, 18 February 2013 (UTC)

Five times the file size, conversion loss, and no apparent advantage. Why on earth would you convert to anmated GIF?! --Dschwen (talk) 23:33, 18 February 2013 (UTC)

Gifs may be easier to use in some places and can loop by default. Anyhow, it's probably not worthwhile. PCIpedia is up next...it's ~200 files.Smallman12q (talk) 01:06, 19 February 2013 (UTC)

Smallbot (talk · contribs)

Operator: Smallman12q (talk • contribs • recent activity • count • block log • rights log • upload log • SUL)

Bot's tasks for which permission is being sought: To upload the NOAA Office of Response and Restoration Photo Collection. 4000 files of high-res JPG and PCD. I plan to convert PCD to 2048*3072 JPG for upload.

See User:Smallbot/source/NOAA Office of Response and Restoration Photo Collection for more details.

Automatic or manually assisted: Automatic

Edit type (e.g. Continuous, daily, one time run): one time run

Maximum edit rate (eg edits per minute): 5-10 (depends on upload speed)

Bot flag requested: (Y/N): N

Programming language(s): VBScript (Javascript, XMLHTTP, MSHTML, XMLDOM, COM).

Source: User:Smallbot/source/NOAA Office of Response and Restoration Photo Collection

Smallman12q (talk) 22:52, 21 November 2012 (UTC)

Discussion

The extracted metadata is limited the galleries 1,2, and 3. (See the xml files of User:Smallbot/source/NOAA Office of Response and Restoration Photo Collection). I'm not sure how to name the files where there is no metadata.Smallman12q (talk) 22:52, 21 November 2012 (UTC)

Can you give examples of how the file names will be constructed, and can you point us to an example of missing metadata? --Dschwen (talk) 08:02, 24 November 2012 (UTC)

I've posted a table here. Some of the items have no description, some have a vague description ("??Oregon somwhere"), some have conflicting descriptions ("Roebling Steel, Roebling, NJ 4/4/90 Water treatment facility located on the banks of the Delaware River." and "Roebling Steel, Roebling, NY 4/4/90 Water treatment facility located on the banks of the Delaware River.") Should I upload with multiple descriptions?

Some are very good. From gallery 4, they follow this pattern: <incident>, <place>, <State>, <Date>. <Description>. such as "Powell Duffryn chemical storage tank incident, Savannah, Georgia, April 1995. Data from a berm chracterization overhead used during the Powell Duffryn incident."Smallman12q (talk) 20:05, 24 November 2012 (UTC)

I suggest the bot includes all descriptions, and humans can work out which one is true. It looks like the directory structure has some info when there is no description. So how do you propose to construct filenames? --99of9 (talk) 11:39, 3 December 2012 (UTC)

┌─────────────────────────────────┘
Gallery 4 is the most complete. I've created a table here. I'll take the first 230 characters of the description as the filename.Smallman12q (talk) 02:45, 11 December 2012 (UTC)

I'm happy to approve the gallery 4 upload. For the others, especially those without descriptions, I'd like to see an example of the proposed filenames before upload. --99of9 (talk) 11:29, 7 March 2013 (UTC)

• Maybe we're all waiting for each other here. Would the bot operator like to comment on plans for galleries 1-3? Or should I just close with approval of gallery 4? You're a very experienced operator, so I trust whatever you decide to go with. --99of9 (talk) 12:53, 22 May 2013 (UTC)

Requests for comment

Centralized discussion
Request for comment on amending licence policy for uploads to "appropriately licensed" media (e.g., no longer accepting GFDL as a sole licence) (15 June 2013) Request for comment about remembering the people we miss. (15 June 2013) Request for comment on FoP Mexico and licenses. (11 June 2013) Request for comment on enabling the DynamicPageList extension on Wikimedia Commons. (21 May 2013) Request for comment on enabling "article feedback" functionality for selected Commons images. (18 March 2012) Request for comment on creating a page to allow users to request others to upload files on their behalf. (14 March 2013) Request for comment on clarifying Commons' Project Scope, as laid down in COM:SCOPE. (11 March 2013) Request for comment on making Commons:Username policy an official Wikimedia Commons policy. (26 January 2013) There is a Request for Comment on hard category redirects #REDIRECT. (1 January 2013) Please help by translating these messages into other languages. Note: inactive discussions, closed or not, should be archived.
Archive  • Discussion • Edit • Page history • Watch