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 May 2013 [+/−]

Listing by language Listing by date

Number of Admins: 271 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 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 Herbythyme, en, fr-2, es-1, it-1 (checkuser) 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 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 Micheletb, fr, en-3, it-1, es-1 Micki, sr, bs-4, hr-3, en-2 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 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 271 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.

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.

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": "[email protected]" } }, "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 original files: 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. (Please note: this template is not yet part of an official guideline or policy)

	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)

PereBot2 (talk · contribs)

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

Bot: PereBot (talk • contribs • recent activity • count • block log • rights log • upload log • SUL)

Bot's tasks for which permission is being sought: Fixing a mistake on description some images I've just uploaded with Commonist.

Automatic or manually assisted: No confirmation for every change, but random check of diffs.

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

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

Bot flag requested: (Y/N): Existing bot without flag. I suppose I still don't need it.

Programming language(s): Python.

Pere prlpz (talk) 23:17, 4 May 2013 (UTC)

Discussion

More information:

• The program is this one:

# -*- coding: utf-8 -*-

import sys
sys.path.append('C:\pywikipedia')
import wikipedia,catlib
import re

# El programa comença aquí.
lloc=u"Images from Wiki Loves Public Art 2013 in an unknown country"
sitecommons=wikipedia.getSite('commons','commons')
l=catlib.Category(sitecommons,lloc).articlesList(recurse=False)
#l=l[:2]
for page in l:
    text=page.get()
    if u"{{Wiki Loves Public Art 2013|ct-es}}" in text:
        text=text.replace(u"{{Wiki Loves Public Art 2013|ct-es}}",u"{{Wiki Loves Public Art 2013|es-ct}}")
        text=text.replace(u"[[Category:Public art in Sant Martí, Barcelona]]",u"")
        page.put(text,u"Bot fixing template in own images")
wikipedia.stopme()

• I'm running a 108 edits test. I hope I won't need to run the program again after the test ends, but I could make the same mistake again and need the bot to fix it.
• I suggest amending the bot policy not to waste bureaucrat's time in such a meaningless request, which under current policy is mandatory.--Pere prlpz (talk) 23:17, 4 May 2013 (UTC)

  Looks OK for me. For one time requests you could ask other bot owner to perform a job. --EugeneZelenko (talk) 14:19, 5 May 2013 (UTC)

  Another bot owner would have needed to ask permission for this particular job. I'm a bot owner, with permission to do another job. Then, asking anybody else wouldn't have made it easier. It would have just meant spending the time of one person more.--Pere prlpz (talk) 14:43, 5 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 fulfill Commons:Batch_uploading#VOA_pronunciation_sound_files. Uploading ~6500 pronunciation files from http://names.voa.gov

Automatic or manually assisted: Automatic

Edit type (e.g. Continuous, daily, one time run): Initial one run, followed by monthly run

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

Bot flag requested: (Y/N): No

Programming language(s): Python3.2 w/ requests, beautifulsoup4. ffmpeg for conversion.

Source

#!/usr/bin/env python3.2 # -*- coding: utf-8 -*- #For uploading files from names.voa.gov to commons from bs4 import BeautifulSoup import requests from subprocess import call import os.path import traceback from PyRWiki import Wiki #Requests based wrapper for api from p import p DEBUG=False #http://stackoverflow.com/questions/1752662/beautifulsoup-easy-way-to-to-obtain-html-free-contents #http://stackoverflow.com/questions/10993612/python-removing-xa0-from-string #http://stackoverflow.com/questions/2077897/substitute-multiple-whitespace-with-single-whitespace-in-python def textOf(soup): return ' '.join(''.join(soup.findAll(text=True)).replace('\xa0', ' ').strip().split()) #make first letter of word Upper if after space or "-", only single space/- def fixname(oldname): oldname=oldname.strip() fixed="" lastwasspace=True#Make first letter upper for i in oldname: if lastwasspace: fixed += i.upper() lastwasspace=False else: if i == " " or i == "-": lastwasspace = True else: lastwasspace = False fixed += i.lower() return fixed def log(stuff): print(stuff) #Log in commons = Wiki("https://commons.wikimedia.org/w/api.php","Smallbot") commons.login('Smallbot',p.bP) commons.setEditToken() counter= 2 #starts at 2 log('Checking for last id.') if os.path.isfile('last.txt'): with open('last.txt', 'r') as content_file: counter = int(content_file.read()) log('Last id found: ' + str(counter)) else: log('No prior id found. Starting at 2.') session=requests.session() if DEBUG: session.proxies = {'http': 'http://localhost:8888'} session.headers = {'Referer': 'https://commons.wikimedia.org/wiki/Commons:Batch_uploading/VOA_pronunciation_sound_files'} reached404=False try: while not reached404: r = session.get('http://names.voa.gov/modal.phrasedetail.php?id=' + str(counter)) if r.status_code == 404: reached404 = True else: soup=BeautifulSoup(r.content) soupbody=soup.select('div.modal-body')[0] name=textOf(soupbody.select("h2")[0])[15:-1] # remove "How do you say" and '?' name=fixname(name) pronounce= textOf(soupbody.select('p')[0]) region=textOf(soup.select('h4')[0].findNext('p'))#('h4 + p')[0]) #Adjacent sibling selector r=session.get('http://names.voa.gov/sounds/' + str(counter) + '.mp3') r.raise_for_status() #should be no errors log('---------------------------------') log('ID: ' + str(counter)) log('Name: ' + name) log('Pronounce: ' + repr(pronounce)) log('Region: ' + region) log(str(len(r.content)) + ' bytes') with open('data.mp3','wb') as voamp3: voamp3.write(r.content) filedesc="{{Information\n" +\ "|description= {{VOA pronunciation|term=" + name + "|region=" + region + "|transliteration=" + pronounce + "}}\n" +\ "|date= 2013\n" +\ "|source= VOA pronunciation guide: [http://names.voa.gov/modal.phrasedetail.php?id=" + str(counter) + " " + name + "]\n" +\ "|author= Jim Tedder\n" +\ "|permission= {{PD-USGov-VOA}}\n" +\ "|other_versions=\n" +\ "}}\n" if os.path.exists('data.webm'): os.remove('data.webm') call(['avconv', '-i', 'data.mp3', '-acodec', 'libvorbis', '-aq', '7', 'data.webm']) commons.upload(title=name + ' from ' + region + ' pronunciation (Voice of America).webm', filelocation='data.webm', text=filedesc, comment='[[Commons:Bots/Requests/Smallbot 9]]: Uploading Voice of America pronunciation files from http://names.voa.gov', uploadifduplicate=True) #TODO-upload data.webm as file counter += 1 except: traceback.print_exc() finally: # with open('last.txt','w') as lastfp: lastfp.write(str(counter)) log('Done.')

Smallman12q (talk) 20:45, 2 May 2013 (UTC)

Discussion

What should the file description be? Should I use {{pronunciation}}? Smallman12q (talk) 20:45, 2 May 2013 (UTC)

Looks like this template is not popular, but it's good idea to standardize media files class descriptions. BTW is this source so unique and Commons doesn't have such pronunciations? :-) --EugeneZelenko (talk) 14:39, 3 May 2013 (UTC)

I don't believe Commons has these pronunciations. Is there some standard pronunciation template? I'll probably make one for the VOA files.Smallman12q (talk) 03:09, 4 May 2013 (UTC)

The template would read:

Voice of America pronunciation of <term> from the region of <region>. Transliteration: <transliteration>

Is that fine? It'll also auto-categorize by region and first letter of the first name so "AL-HALQI, WAEL" would be "WAEL AL-HALQI" and categorized by W. Is the letter/region categorization needed?Smallman12q (talk) 19:51, 4 May 2013 (UTC)

Well... this should clearly be marked as an american pronounciation recommendation. At least for the few german names I have checked this is certainly not the gold-standard for pronounciation (Erik Honnecker, Frantz Muntefering, and many more). --Dschwen (talk) 16:49, 3 May 2013 (UTC)

there is contact info, i'm sure they would be open to your feedback. [1] (or refer them to our local Goethe institute) - the value is that it is a currently maintained public domain source of pronunciations. Slowking4⇔ †@1₭ 13:03, 4 May 2013 (UTC)

I've uploaded a few to Category:Terms from Voice of America pronunciation guide. Is it good to go?Smallman12q (talk) 14:03, 8 May 2013 (UTC)

It'll be good idea to include these files into some pronunciation categories. --EugeneZelenko (talk) 14:27, 8 May 2013 (UTC)

I could add them to Category:English pronunciation and also prepend the names with En-us so it'd be "File:En-us Abadilla from Philippines pronunciation (Voice of America).webm"? Would that be all?Smallman12q (talk) 23:17, 8 May 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: [2] [3] [4]. 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)

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: [5]. 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)

Hazard-Bot (talk · contribs)

Operator: Hazard-SJ (talk • contribs • recent activity • count • block log • rights log • upload log • SUL)

Bot's tasks for which permission is being sought: Category replacements

Automatic or manually assisted: Automatically

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

Maximum edit rate (eg edits per minute):

Bot flag requested: (Y/N): No

Programming language(s): Python

There are cases when more help is wanted for category replacements. Now is an example. User:CommonsDelinker/commands has a backlog with, I believe, no bots working on it at the moment, so I'd like to be able to help out in such cases.  Hazard-SJ  ✈  01:36, 19 March 2013 (UTC)

Discussion

• There has been some recent issues with SieBot recently that makes COM:CDC to be backlogged. I'd welcome very much a clone for performing those category moves when SieBot is not working. I support approval (with flag). —MarcoAurelio (talk) 15:20, 19 March 2013 (UTC)
• Please make a test run if this is not standard bot. --EugeneZelenko (talk) 14:28, 20 March 2013 (UTC)
• If this is not a standard bot, one has to care that nothing inside <nowiki><!-- --> or <source> is replaced. -- Rillke^(q?) 17:46, 22 March 2013 (UTC)
• I planned to use CategoryMoveRobot in category.py (PyWikipedia trunk). Originally, I was planning to manually start the bot for each request, but I could create an on-wiki page for the bot (or use the one currently in use) to use so I wouldn't have to manually start it each time. I'd still integrate the CategoryMoveRobot class into it, though. Would that be preferred? (P.S. SieBot is back up so there isn't much of a rush now.)  Hazard-SJ  ✈  00:27, 23 March 2013 (UTC)

  I think will be good idea to use User:CommonsDelinker/commands for list of requests and proceed automatically. --EugeneZelenko (talk) 14:30, 24 March 2013 (UTC)

  • In such a case, however, the completed requests won't be removed until someone comes along to do so manually, as my bot cannot edit that page.  Hazard-SJ  ✈  04:18, 26 March 2013 (UTC)

    • If you create a separate account for the task, that account could be admin-flagged so that it can edit the page. The task is important and it would be best to integrate a supplementary bot into the existing structure as neatly as possible. Rd232 (talk) 10:55, 3 April 2013 (UTC)

      Even if I'm not an admin myself (as is the current case)?  Hazard-SJ  ✈  23:09, 13 April 2013 (UTC)

      • Many moves require still manual intervention as many items cannot be bot moved and in some cases a redirect is created, otherwise deleted; I don't think that can be handled by a bot anyway. (I spend on average 2 minutes per category move on cleaning up). --Foroa (talk) 11:06, 3 April 2013 (UTC)

        Yes, moving categories it technically impossible, so without admin access it wouldn't be able to do the deletions, but rather, create the new category and request deletion of the old one.  Hazard-SJ  ✈  23:09, 13 April 2013 (UTC)

        • Ideally, the bot should be able to update the Wikidata structures as for example in d:Q1144392. --Foroa (talk) 11:11, 3 April 2013 (UTC)

          I agree: this is a very good idea. Conveniently, I'm already approved to do this on Wikidata.  Hazard-SJ  ✈  23:09, 13 April 2013 (UTC) This can't be done until Wikimedia Commons is somehow integrated into Wikidata.  Hazard-SJ  ✈  03:56, 21 April 2013 (UTC) It's currently not possible to search for values of D:P:P373 via the API. The only way to get to the relevant Wikidata item would be, considering there is a (correct) link in a template on the category page (such as in {{w}}), go to the Wikipedia page, then the item (if there is one), then change the value of p373.  Hazard-SJ  ✈  04:42, 21 April 2013 (UTC)

• For the record, SieBot is, again, down, so I've gone ahead and coded the bot. I've ran a 16-edit trial with it here, doing four requests in all. Of course, as I already mentioned, the bot isn't able to edit the queue page, since the current one is fully protected. Also, for now, I'm just marking the old category as a category redirect to the new one.  Hazard-SJ  ✈  03:56, 21 April 2013 (UTC)

• We need at least one other bot looking at the commands. SieBot is asleep way too often. However
  1. If the bot behaves differently from SieBot, it should replace it and not work alongside it
  2. If the bots are to work concurrently, you would have to account for more than one bot picking up the same request (as neither can edit User:CommonsDelinker/commands to remove a request before they start executing it).

If the bot doesn't behave like SieBot, can you specify in the request how it differs? Does the bot alter the old category for example (afaik SieBot does not)? –⁠moogsi (blah) 02:40, 28 April 2013 (UTC)

As for working concurrently, the only (if not, main) problem if they're working on the same category at the same time would be an edit conflict, which is already handled. Specifically, the bot currently creates the new category page if it doesn't exist (attributing the authors in the summary, or on the talk page if the list is too long), then moves the categories. After it determines that the category is empty, it replaces the content of the old category page with {{Category redirect|"new category name"}}. All that can be seen from the trial I made. As for behaving differently, I think the main difference is the implementation, and probably that my bot actually edits the old category afterwards (not sure if SieBot does that).  Hazard-SJ  ✈  02:56, 28 April 2013 (UTC)

{{Move}} requests have to be stripped during the transfer, no need to remove it from the delinker queue as it needs manual inspection (5 % of moves need manual intervention or category restructuring). --Foroa (talk) 16:08, 29 April 2013 (UTC)

I can implement that.  Hazard-SJ  ✈  02:25, 30 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: semiautomatic

Edit type (e.g. Continuous, daily, one time run): now run manually, in future it will run one or several times per day (if I'll get toolserver account)

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)

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)

Unauthorized Bot (talk · contribs)

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

Bot's tasks for which permission is being sought:

The bot uploads public domain newspapers, journals and books and does the categorization for them.

So far it has uploaded:

• about 20,000 Romanian newspaper issues published between 1850-1918. - PD due to copyright expiration for anonymous works 70 years. The articles are signed only with pseudonyms, and the only name in clear being of the editor-in-chief (such as Ion Luca Caragiale (1852-1912), Alexandru Beldiman (1832-1898), whose work expired due to life + 70). Sample: German-language Bucharest newspaper Category:Bukarester Tagblatt.
• about 10,000 issues of the official gazette of the Romanian Parliament (which publishes laws and administrative decrees) - PD due to inelligibility according to the Romanian copyright law
• about 850 Romanian language books and booklets (all of them by en:Nicolae Iorga, categorized in Category:Books by Nicolae Iorga) - PD due to copyright expiration (life + 70)
• categories for the newspapers and journals (not yet complete, there are still some batches of categories to be created)

The sources for the scans are generally local libraries (Bucharest Metropolitan Library, Cluj University Library, etc).

Automatic or manually assisted: automatic

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

Maximum edit rate (eg edits per minute): 6

Bot flag requested: (Y/N): Y

Programming language(s): Python

Bogdan (talk) 13:15, 16 February 2013 (UTC)

Discussion

I think will be good idea to find more meaningful bot name. Is it possible to provide precise URL for each file? --EugeneZelenko (talk) 15:48, 16 February 2013 (UTC)

For some it's not possible because they don't have permalinks. I'll try to add them whenever possible.Bogdan (talk) 18:49, 16 February 2013 (UTC)

This bot has been blocked, and rightfully so. Thousands of uploads goes well beyond a test run (and even that was not discussed yet). --Dschwen (talk) 16:51, 19 February 2013 (UTC).

I don't think the bot did any damage at all to be blocked. All its uploads respected the rules regarding to copyright, file description and categorization, so what's the problem with it? Bogdan (talk) 08:57, 22 February 2013 (UTC)

I reported the bot; the problem I saw was that it was editing very quickly, had a unique username, and was not approved. Mono 00:41, 24 February 2013 (UTC)

You also stated your bot would make a maximum edit rate of 6 edits per minute, your bot only followed that maximum edit rate on its first 5 edits (three of which you made) Riley Huntley (talk) 10:02, 24 February 2013 (UTC)

• What is the relationship between User:Unauthorized Bot and User:Botul prietenos? Both seem to be unapproved bots operated by the same person uploading the same kind of files. --Stefan4 (talk) 21:11, 2 March 2013 (UTC)
• Could you please reconfirm the copyright status of the newspapers? You are claiming that all authors are anonymous or pseudonymous and that the pseudonyms can't be matched to any real person. Are you really sure that this is the case? For example, File:Familia 1906-12-03, nr. 39.pdf contains a translation of a text attributed to someone called Stefan Bársony, which I take is hu:Bársony István (író) (1855-1928). Also, the same magazine contains photos of sculptures by Alexandru Liuba (1875-1906[6]). These works are luckily in the public domain, but there are lots of names in the magazines, and I can't tell if the rest of the names are unidentified pseudonymes or if some of the names in fact are real names. I take it that the newspapers from the 1850s are in the public domain because all of the authors died more than 70 years ago, but this is less clear when you get to 1918. --Stefan4 (talk)

Is there any need to keep this request open? --Dschwen (talk) 14:55, 25 April 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)

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 [7]. 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)

タチコマ robot (talk · contribs)

Operator: とある白い猫 (talk • contribs • recent activity • count • block log • rights log • upload log • SUL)

Bot's tasks for which permission is being sought: Bot will tag featured pictures from other wikis (main concern is ar.wikipedia) using {{Assessments}}.

Automatic or manually assisted: Automatic, unsupervised after the generation of the list of pages to be edited.

Edit type (e.g. Continuous, daily, one time run): infrequent runs to tag new promotions/demotions

Maximum edit rate (eg edits per minute): 60

Programming language(s): AWB, bot already has a flag

-- とある白い猫 ^ちぃ？ 07:36, 24 September 2012 (UTC)

Discussion

• Please make a test run. --EugeneZelenko (talk) 14:55, 24 September 2012 (UTC)
  • Certainly. -- とある白い猫 ^ちぃ？ 14:31, 6 October 2012 (UTC)
    • It seems like someone has already manually tagged the images. I can demonstrate with another wiki if you approve. -- とある白い猫 ^ちぃ？ 15:06, 6 October 2012 (UTC)
      • A small test run from any wiki would help us to evaluate this. --99of9 (talk) 03:55, 11 October 2012 (UTC)
• I don't quite understand this request. Is this about extending the scope of a previously approved bot request? For the description it sounds like this is a small one time task. Does this warrant a request? --Dschwen (talk) 15:23, 2 November 2012 (UTC)
  • I doubt it would be one-time, since other wikis are going to be periodically featuring pictures and not marking them here. But it does seem like it would be infrequent. – Philosopher ^{Let us reason together.} 12:41, 1 December 2012 (UTC)
    • @Dschwen: It's quite common sense that small one time tasks (or small few times task) don't warrant a request, and I think such request basically give more work to bureaucrats, who have already a lot of work - judging by this page. Anyway, as far as I can see, bot policy is very strict about bots running without requesting, and there are no written exceptions in policy. IMO, providing some clear exceptions for low volume tasks would benefit bureaucrats, bot users and the project.--Pere prlpz (talk) 16:05, 11 December 2012 (UTC)
• Four months and still no report of a test run. I will close this as stale within the next few days. --Dschwen (talk) 17:19, 27 February 2013 (UTC)
  • What exactly am I supposed to test? I am merely trying to understand the nature you want me to run. How many edits would be sufficient? My plan is to grab a category off a wiki that has featured pictures and use a regex to apply it to the assessments template (or add the template if it isn't present). -- とある白い猫 ^ちぃ？ 23:58, 2 April 2013 (UTC)
    • 30-50 edits per step III of Commons:Bots/Requests. --99of9 (talk) 00:08, 3 April 2013 (UTC)
      • I might not be able to generate 30 edits due to people manually tagging which is why I was asking. I am processing all 3,345 files from and hopefully I have enough to reach that mark. -- とある白い猫 ^ちぃ？ 16:08, 6 April 2013 (UTC)
        • Yeah I only have 17 edits (edit summary: "adding enwiki fa assessment, replaced: {{Assessments| → {{Assessments|enwiki=1|)"). It is a simple regex in AWB. Is this sufficient? -- とある白い猫 ^ちぃ？ 19:09, 6 April 2013 (UTC)
• Also, please note that 60 edits per minute is much higher than the normal maximum. --99of9 (talk) 00:09, 3 April 2013 (UTC)
  • This has been discussed before. Is there any reason why we have to worry about such an arbitrary number bot operators disregard? It artificially creates a massive backlog as 1000 edits would take 16.66 hours to complete. I have placed a remark on the talk page of the policy to avoid duplication. -- とある白い猫 ^ちぃ？ 15:30, 6 April 2013 (UTC)

1000 edits would take 100 minutes with recommended maximum bot speed. I think that is a reasonable speed fot this kind of task. Bots can make errors and if they do they should not do it at to high speed. This bot needs to be fixed so that it links to correctly named nomination pages at English Wikipedia, like this. It also needs to make sure that the pictures it tags really are featured pictures, eg File:Eastern Screech Owl.jpg does not seem to ever have been featured and File:Ebony Bones backup performer.jpg seems to have been delisted as featured picture. /Ö 19:59, 6 April 2013 (UTC)

FA Page ghosts on en.wikipedia
  Eastern_Screech_Owl.jpg
  Ebony Bones-01.jpg

Linking to nomination pages is a later issue. Not all of them are marked on en.wikipedia or on commons and crawling for them is a non-trivial task. That is a future task I hope to tackle.

The idea is also to sync enwiki (and other wikis) delistings with commons. The bot has no way of verifying if a file is actually featured or if it tagged without even being nominated. It can however check if files are in the en:Category:Featured pictures or not. The two mentioned files were in the category or at least en.wikipedia reported them as such (Eastern_Screech_Owl.jpg doesn't exist as a page on en.wikipedia despite appearing on category, Ebony Bones-01.jpg is a redirect on en.wikipedia to Ebony Bones backup performer.jpg which is the matching image which again shouldn't appear on category). On my second sweep I'd run a similar regex to en:Category:Wikipedia former featured pictures. Also not everything is nicely marked so catching problematic images is again a future development task.

The restriction is no faster than 1 edit/10sec according to the linked policy page. Simple math is 10sec*1000=10,000secs, 10,000/60=166.66... minutes, 166.66.../60=2.77... hours, provided bot does not spend any time doing anything. I do not want to add a 10 second counter between edits which would serve no purpose than waste my time. I do not see the point of a speed limit for bots. It was thrown in as an idea that servers couldn't handle such speeds. Developers disagreed and did not see a problem. The quicker the bot edits the better as edits would be rolled out quicker. That way I can change the parameters to work on the next wiki. This script would probably check for about 20 wikis that have featured pictures - of which most don't have that many files or new files. This task would take probably no more than 20 edits per month after the initial run. I do not believe the speed limit is based on consensus mind you. Let's discuss bot speeds on Commons talk:Bots as its a more general question if this is worth tracking and enforcing.

-- とある白い猫 ^ちぃ？ 02:36, 7 April 2013 (UTC)

Please notify me on my talk page if there are any developments here. I cannot watch a page forever. :/ -- とある白い猫 ^ちぃ？ 22:56, 20 April 2013 (UTC)

Requests for comment

Centralized discussion
Request for comment on enabling the Translate extension on Wikimedia Commons. (28 April 2012) Request for comment on enabling the UniversalLanguageSelector on Wikimedia Commons. (24 April 2012) 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