User talk:AlessioMela

From Wikidata
Jump to navigation Jump to search

Benvenuto[edit]

Benvenuto su Wikidata, AlessioMela!

Wikidata è la base di conoscenza libera e collaborativa che tu puoi migliorare! Può essere letta e modificata da umani e macchine allo stesso modo, e tu puoi aiutare a farlo. Vai ora alla pagina di un qualsiasi elemento e contribuisci alla crescita sempre continua dell'archivio!

Per favore, dai un'occhiata alle pagine seguenti. Potrebbero dimostrarsi utili se sei nuovo di qui:

  • Come contribuire - Spicciole dritte per contribuire
  • CreaElemento - Crea un nuovo elemento
  • Bar - Discussioni sul progetto
  • Glossario - Terminologia di Wikidata
  • Strumenti - elenco di strumenti (script) per lavorare su Wikidata in modo più confortevole

Se hai domande, non esitare a contattarmi nella mia pagina di discussione. Spero ti troverai subito bene qui e diventerai un ottimo redattore di Wikidata.

Tante buone cose, -- DangSunM (T · C) 00:02, 14 November 2012 (UTC)[reply]

Video esplicativo sull'editing[edit]

Grazie mille, sono due mesi che cerco di capire come fanno (quelli che lo fanno) e soprattutto con che lo fanno. La domanda al bar.. e certo che non la capisci! ci manca tutto un pezzo che non ho detto! Se per caso ti sorgessero dubbi su qualche aspetto nella modifica di Wikidata che pensi si possa meglio chiarire attraverso una linea guida non aver paura di proporla. Non ti fare scrupolo che le pagine si sviluppano dalla versione inglese. Stando qui su Wikidata dal 30 ottobre ho visto che le linee guida o le pagine non è che li crea il super amministratore ma l'utente qualsiasi a cui viene in mente quella cosa. Finora la maggior parte delle pagine create è stata creata senza una discussione alla maniera wikipediana ma semplicemente scrivendo quello che uno pensa in una pagina e collegandola con le altre. Come si suol dire "be bold". Per esempio la pagina Wikidata:Glossary l'ho creata io in italiano e gli inglesi l'hanno tradotta in inglese (strano ma vero) e poi vabbè le strade si sono divise. Potrai per esempio notare la differenza sostanziale tra Wikidata:Tools e Wikidata:Strumenti, oppure il sistema del Bar diverso dagli altri. Quindi se qualcosa non ti piace (in questo senso) o vedi una mancanza che ritieni doverosa basta che ti fai sentire o la crei. Gli altri ti diranno: il progetto si sviluppa dall'inglese e poi gli altri copiano, ma è una sciocchezza e non ascoltare: il progetto lo sviluppa chi ha voglia di dare il suo contributo e migliorare le cose e non per forza deve essere scritto subito in inglese. Per esempio Help:Description e le altre (tranne quella francese) sono tutte traduzioni dall'italiano. In questo senso intendevo "avresti delle cose che si potrebbero migliorare?" 'n po' lunghetto sto msg, vè! mi dispiace. --Raoli (talk) 01:15, 22 November 2012 (UTC)[reply]

problemi con la funzione merge[edit]

Salve, volevo unire i due item identici Q526178 e Q17566534 ma mi chiede di risolvere un conflitto di descrizione En, ma quando cerco di modificare la descrizione mi dice che non può salvare perchè identica all'altro item. Moolto schizofrenogenico! Sai come si fa? O a chi posso chiedere? --Demostene119 (talk) 11:19, 20 October 2014 (UTC)[reply]

@Demostene119: Visto che Alessio non ti ha ancora risposto, lo faccio io: ho provato a unirli e a creare un redirect e non ho avuto problemi. Per il merge usi il gadget Merge? (lo trovi negli accessori, come prima voce) --ValterVB (talk) 18:04, 20 October 2014 (UTC)[reply]
@ValterVB: grazie! --AlessioMela (talk) 14:56, 23 October 2014 (UTC)[reply]

Wikidata:WikiProject Authority control/Status[edit]

Lo stato del passo 5 "embed" su itwiki potrebbe aver bisogno di aggiornamenti. --Ricordisamoa 14:24, 27 July 2015 (UTC)[reply]

@Ricordisamoa: Sì probabilmente ne mancano qualche migliaia. Tuttavia il passo 5 non è un continuo work in progress? Come facciamo a mettere "fatto"? --AlessioMela (talk) 08:16, 28 July 2015 (UTC)[reply]
Già, solo T.seppelt sembra avercela fatta (come?). Ma anche chiarire il ruolo di AlessioBot, aggiungere collegamenti a discussioni, esempi, ecc. sarebbe sufficiente. --Ricordisamoa 13:27, 28 July 2015 (UTC)[reply]
@Ricordisamoa: Probabilmente ha fatto un giro completo, tuttavia è un lavoro in continua evoluzione visto che arrivano sempre nuove voci e sempre nuovi codici. Appena sistemo il codice del bot e lo pubblico su github, aggiorno anche descrizioni e faq qua in giro. --AlessioMela (talk) 12:52, 16 August 2015 (UTC)[reply]

Borse Alessio Guidetti per Wikimania 2016[edit]

Ciao, un messaggio dalla Commissione Borse Alessio Guidetti

Ciao, come forse saprai quest'anno Wikimania, il raduno annuale delle comunità Wikimedia, si terrà a Esino Lario (Lecco) dal 22 al 28 giugno.

Come per le scorse edizioni dell'evento, anche per il 2016 l'associazione Wikimedia Italia intende rendere disponibili alcune borse di partecipazione.
Potete trovare il bando di partecipazione con tutti i dettagli a questo link.
La scadenza è il 30 aprile 2016, ore 23:59 CEST.

Trovate invece tutte le informazioni su Wikimania Esino Lario sul sito ufficiale dell'evento
Grazie, e un sincero augurio di buon lavoro e buon divertimento sull'enciclopedia libera :-)

per non ricevere più questa tipologia di messaggi rimuovi il tuo nome da queste liste

Alexmar983 13:24, 24 April 2016 (UTC)[reply]

Merging[edit]

Hallo AlessioMela,
When you merge items, you may want to use the merge.js gadget from help page about merging. It helps with merging, nominating, gives the option to always keep the lower number (which is older, so preferable in most cases) and makes it a lot easier for the admins to process the requests.
With regards,- cycŋ - (talk • contribs • logs) 06:38, 22 July 2016 (UTC)[reply]

New property proposal: Coinage of the Roman Republic Online ID[edit]

I just kick started a new property proposal, you may like to check: Wikidata:Property proposal/Coinage of the Roman Republic Online ID --FedericoMorando (talk) 22:46, 6 October 2017 (UTC)[reply]

Structured Commons newsletter, October 25, 2017[edit]

Welcome to the newsletter for Structured Data on Wikimedia Commons! You can update your subscription to the newsletter. Do inform others who you think will want to be involved in the project!

Community updates
Things to do / input and feedback requests
Presentations / Press / Events
Audience at Structured Commons design discussion, Wikimania 2017
Team updates
The Structured Commons team at Wikimania 2017

Two new people have been hired for the Structured Data on Commons team. We are now complete! :-)

  • Ramsey Isler is the new Product Manager of the Multimedia team.
  • Pamela Drouin was hired as User Interface Designer. She works at the Multimedia team as well, and her work will focus on the Structured Commons project.
Partners and allies
  • We are still welcoming (more) staff from GLAMs (Galleries, Libraries, Archives and Museums) to become part of our long-term focus group (phabricator task T174134). You will be kept in the loop of the project, and receive regular small surveys and requests for feedback. Get in touch with Sandra if you're interested - your input in helping to shape this project is highly valued!
Research

Design research is ongoing.

  • Jonathan Morgan and Niharika Ved have held interviews with various GLAM staff about their batch upload workflows and will finish and report on these in this quarter. (phabricator task T159495)
  • At this moment, there is also an online survey for GLAM staff, Wikimedians in Residence, and GLAM volunteers who upload media collections to Wikimedia Commons. The results will be used to understand how we can improve this experience. (phabricator task T175188)
  • Upcoming: interviews with Wikimedia volunteers who curate media on Commons (including tool developers), talking about activities and workflows. (phabricator task T175185)
Development

In Autumn 2017, the Structured Commons development team works on the following major tasks (see also the quarterly goals for the team):

  • Getting Multi-Content Revisions sufficiently ready, so that the Multimedia and Search Platform teams can start using it to test and prototype things.
  • Determine metrics and metrics baseline for Commons (phabricator task T174519).
  • The multimedia team at WMF is gaining expertise in Wikibase, and unblocking further development for Structured Commons, by completing the MediaInfo extension for Wikibase.
Stay up to date!

Warmly, your community liaison, SandraF (WMF) (talk)

Message sent by MediaWiki message delivery - 14:26, 25 October 2017 (UTC)[reply]

Structured Commons newsletter, December 13, 2017[edit]

Welcome to the newsletter for Structured Data on Wikimedia Commons! You can update your subscription to the newsletter. Do inform others who you think will want to be involved in the project!

Community updates
Things to do / input and feedback requests
A multi-licensed image on Wikimedia Commons, with a custom {{EthnologyItemMHNT}} Information template. Do you also know media files on Commons that will be interesting or challenging to model with structured data? Add them to the Interesting Commons files page.
Presentations / Press / Events
Presentation about Structured Commons and Wikidata, at WikimediaCon in Berlin.
  • Sandra presented the plans for Structured Commons during WikidataCon in Berlin, on October 29. The presentation focused on collaboration between the Wikidata and Commons communities. You can see the full video here.
Partners and allies
  • We are still welcoming (more) staff from GLAMs (Galleries, Libraries, Archives and Museums) to become part of our long-term focus group (phabricator task T174134). You will be kept in the loop of the project, and receive regular small surveys and requests for feedback. Get in touch with Sandra if you're interested - your input in helping to shape this project is highly valued!
Research
  • Research findings from interviews and surveys of GLAM project participants are being published to the research page. Check back over the next few weeks as additional details (notes, quotes, charts, blog posts, and slide decks) will be added to or linked from that page.
Development
  • The Structured Commons team has written and submitted a report about the first nine months of work on the project to its funders, the Alfred P. Sloan Foundation. The 53-page report, published on November 1, is available on Wikimedia Commons.
  • The team has started working on designs for changes to the upload wizard (T182019).
  • We started preliminary work to prototype changes for file info pages.
  • Work on the MediaInfo extension is ongoing (T176012).
  • The team is continuing its work on baseline metrics on Commons, in order to be able to measure the effectiveness of structured data on Commons. (T174519)
  • Upcoming: in the first half of 2018, the first prototypes and design sketches for file pages, the UploadWizard, and for search will be published for discussion and feedback!
Stay up to date!

Warmly, your community liaison, SandraF (WMF) (talk)

Message sent by MediaWiki message delivery - 16:32, 13 December 2017 (UTC)[reply]

Structured Data on Commons Newsletter - Spring 2018[edit]

Welcome to the newsletter for Structured Data on Wikimedia Commons! You can update your subscription to the newsletter and contribute to the next issue. Do inform others who you think will want to be involved in the project!

Community updates
  • Our dedicated IRC channel: wikimedia-commons-sd webchat
  • Several Commons community members are working on ways to integrate Wikidata in Wikimedia Commons. While this is not full-fledged structured data yet, this work helps to prepare for future conversion of data, and helps to understand how Wikidata and Commons can work better together.
Things to do / input and feedback requests
Discussions held
Events
Partners and allies
  • We are still welcoming (more) staff from GLAMs (Galleries, Libraries, Archives and Museums) to become part of our long-term focus group (phabricator task T174134). You will be kept in the loop of the project, and receive regular small surveys and requests for feedback. Get in touch with Sandra if you're interested - your input in helping to shape this project is highly valued!
Research
Development
  • Prototypes will be available for Multilingual Captions soon.
Stay up to date!

-- Keegan (WMF) (talk)

Message sent by MediaWiki message delivery - 19:48, 3 April 2018 (UTC)[reply]

Phone numbers formatting[edit]

Hello and thank you for your upload of the WLM database to Wikidata. the phone number property states that phone numbers should be formatted according to RFC 3966 without the "-" prefix (e.g. using "-" instead of spaces). There is a great library ported for a lot of programming languages to do such phone number validation and formatting. May you apply it for your future importations? Tpt (talk) 10:14, 4 July 2018 (UTC)[reply]

@Tpt: hello! Thanks for the library suggested! I'll use it in my next release :) --AlessioMela (talk) 14:46, 4 July 2018 (UTC)[reply]
Great! Thanks! Tpt (talk) 15:33, 4 July 2018 (UTC)[reply]
Hello! Running my phone number formatting bot I have seen that you sometime output phone numbers like "+39 390114992333". (list). May you check if they are valid (I am not very familiar with the Italian numbering plan). Tpt (talk) 09:19, 5 July 2018 (UTC)[reply]
@Tpt: No they are not valid :( probably some dirty numbers from source. There is a "39" too much. Thanks for the tip! --AlessioMela (talk) 09:42, 5 July 2018 (UTC)[reply]
An other detail: it seems that you output now phone numbers like "+39 055 262 5961". The RFC 3966 prefers to use "-" instead of spaces in order to generate valid URIs like in "+39-055-262-5961". Tpt (talk) 09:23, 5 July 2018 (UTC)[reply]
@Tpt: Now I'm using the library you suggest me (thanks again!). I'm in "international" mode because the RFC3966 mode returns numbers without spacing (nor the "-"). Do you know why? --AlessioMela (talk) 09:42, 5 July 2018 (UTC)[reply]
It's maybe because you are using a smaller library that does not bother to add hyphens in RFC 3966 URIs (they are optionals). What you could do is use the "international" mode and replace spaces with hyphens (and no need to remove tel: anymore). Tpt (talk) 10:50, 5 July 2018 (UTC)[reply]

Here is a list of some Italian wrong numbers. Most of them seems to come from your importation. May you have a look at it (there are maybe some patterns you could fix in your bot code)? Tpt (talk) 18:02, 5 July 2018 (UTC)[reply]

phone number (P1329)[edit]

  • Q3867939: +39 011309011501176048811517: The string supplied is too long to be a phone number.
  • Q55371757: +39 011311245833922272283336020192: The string supplied is too long to be a phone number.
  • Q55391376: +39 0125641238900120014001700: The string supplied is too long to be a phone number.
  • Q55390798: +39 01615902620161590259: The string supplied is too long to be a phone number.
  • Q55390454: +39 0173386697017356277: The string supplied is too long to be a phone number.
  • Q55391553: +39 017439182701825550990171631399: The string supplied is too long to be a phone number.
  • Q55391859: +39 02894005550365546023: The string supplied is too long to be a phone number.
  • Q55391866: +39 03643443010364344858: The string supplied is too long to be a phone number.
  • Q55375895: +39 0364747617404252321989: The string supplied is too long to be a phone number.
  • Q55386308: +39 0365714490365745007: The string supplied is too long to be a phone number.
  • Q54087655: +39 036585537036585556: The string supplied is too long to be a phone number.
  • Q55340471: +39 0427803233661687906: The string supplied is too long to be a phone number.
  • Q3868325: +39 0541913715913750913791: The string supplied is too long to be a phone number.
  • Q55360120: +39 06678620906697645599: The string supplied is too long to be a phone number.
  • Q55360190: +39 066893051066787864: The string supplied is too long to be a phone number.
  • Q55163724: +39 070201010702010302: The string supplied is too long to be a phone number.
  • Q55163727: +39 070201010702010361302: The string supplied is too long to be a phone number.
  • Q55378139: +39 07167782236071679043: The string supplied is too long to be a phone number.
  • Q55378560: +39 07217863020721786107: The string supplied is too long to be a phone number.
  • Q55378519: +39 07335126480733501240733506566: The string supplied is too long to be a phone number.
  • Q55378522: +39 073795200073795421: The string supplied is too long to be a phone number.
  • Q55388370: +39 0781821053897962114: The string supplied is too long to be a phone number.
  • Q55379264: +39 07839902510783996017: The string supplied is too long to be a phone number.
  • Q55375721: +39 079226508079227016: The string supplied is too long to be a phone number.
  • Q55385464: +39 08040562980804056538: The string supplied is too long to be a phone number.
  • Q55369272: +39 08054124202223242627: The string supplied is too long to be a phone number.
  • Q55376996: +39 08355685293299636664: The string supplied is too long to be a phone number.
  • Q3868057: +39 08590682070859068207: The string supplied is too long to be a phone number.
  • Q55192537: +39 086293840433911044733338089883: The string supplied is too long to be a phone number.
  • Q55193840: +39 0864691140864212962: The string supplied is too long to be a phone number.
  • Q55385513: +39 0871330740854462757: The string supplied is too long to be a phone number.
  • Q3867910: +39 087182117087183114: The string supplied is too long to be a phone number.
  • Q122476: +39 09174048900916166621: The string supplied is too long to be a phone number.
  • Q55378106: +39 092446540092446277: The string supplied is too long to be a phone number.
  • Q55359755: +39 09327112393338138648: The string supplied is too long to be a phone number.
  • Q55359781: +39 09327710483281683213: The string supplied is too long to be a phone number.
  • Q55359556: +39 09573060290957306018: The string supplied is too long to be a phone number.
  • Q55375636: +39 3288789521078534273: The string supplied is too long to be a phone number.
  • Q55340774: +39 33312532993356275763: The string supplied is too long to be a phone number.
  • Q55359610: +39 33850233613392002463: The string supplied is too long to be a phone number.
  • Q55387946: +39 34023283310781806077: The string supplied is too long to be a phone number.
  • Q3662455: +39 34915640233497428014: The string supplied is too long to be a phone number.
  • Q55351907: +39 390472847399393487747339: The string supplied is too long to be a phone number.
  • Q55351806: +39-0039047142964: The phone number is not valid
  • Q16621503: +39-00390917404822: The phone number is not valid
  • Q55388799: +39-00390917409188: The phone number is not valid
  • Q55388733: +39-00390918431605: The phone number is not valid
  • Q55388726: +39-00390918431606: The phone number is not valid
  • Q55388680: +39-00390922590371: The phone number is not valid
  • Q55388772: +39-0039092530111: The phone number is not valid
  • Q55388759: +39-0039092530216: The phone number is not valid
  • Q55390346: +39-00390933989056: The phone number is not valid
  • Q55390361: +39-00390935567095: The phone number is not valid
  • Q55388784: +39-0039093585185: The phone number is not valid
  • Q3662761: +39-0039095690374: The phone number is not valid
  • Q55388742: +39-00393204778523: The phone number is not valid
  • Q55388767: +39-00393666712832: The phone number is not valid
  • Q55388779: +39-0039916820522: The phone number is not valid
  • Q55388714: +39-0039918351033: The phone number is not valid
  • Q21552138: +39-0039941919068: The phone number is not valid
  • Q2201144: +39-01181011138101150: The phone number is not valid
  • Q55372151: +39-01248548484463: The phone number is not valid
  • Q55350004: +39-018786507539: The phone number is not valid
  • Q55375901: +39-0336-410877: The phone number is not valid
  • Q55387035: +39-0337-217689: The phone number is not valid
  • Q55359953: +39-0368-288844: The phone number is not valid
  • Q55340542: +39-040327240327124: The phone number is not valid
  • Q55340675: +39-040821244830792: The phone number is not valid
  • Q55340701: +39-043263611674068: The phone number is not valid
  • Q55360199: +39-0644250072060608: The phone number is not valid
  • Q55360193: +39-065990381416: The phone number is not valid
  • Q55360087: +39-0667102475060608: The phone number is not valid
  • Q55360062: +39-0667103058060608: The phone number is not valid
  • Q3867515: +39-0721387541474: The phone number is not valid
  • Q3868265: +39-073422935032: The phone number is not valid
  • Q55378312: +39-07348592798196372: The phone number is not valid
  • Q15812268: +39-07898340181066: The phone number is not valid
  • Q55375641: +39-07898340181066: The phone number is not valid
  • Q55387929: +39-07898340181066: The phone number is not valid
  • Q55387933: +39-07898340181066: The phone number is not valid
  • Q55387942: +39-07898340181066: The phone number is not valid
  • Q55387952: +39-07898340181066: The phone number is not valid
  • Q55387964: +39-07898340181066: The phone number is not valid
  • Q55360321: +39-0825787191789933: The phone number is not valid
  • Q55385613: +39-0848-281: The phone number is not valid
  • Q55351472: +39-08747728292824: The phone number is not valid
  • Q16336138: +39-0949-67005: The phone number is not valid
  • Q30889812: +39-09625106251069: The phone number is not valid
  • Q55377289: +39-0977-9050: The phone number is not valid
  • Q55385652: +39-193-275-2897: The phone number is not valid
  • Q55385913: +39-33327009: The phone number is not valid
  • Q55351814: +39-471945702: The phone number is not valid
  • Q55352668: +39-473615590: The phone number is not valid

fax number (P2900)[edit]

  • Q55360188: +39 (+39)0654221673: The string supplied did not seem to be a phone number.
  • Q55369057: +39 -: The string supplied did not seem to be a phone number.
  • Q55388799: +39 003909162309580039091610776: The string supplied is too long to be a phone number.
  • Q55376013: +39 0375200251-0373/65632: The string supplied is too long to be a phone number.
  • Q55340661: +39 040575519-0405582156: The string supplied is too long to be a phone number.
  • Q55340832: +39 0427808136(comune);ufficioTuristico0427809610: The string supplied did not seem to be a phone number.
  • Q55340734: +39 0433727821(ufficioturistico): The string supplied is too long to be a phone number.
  • Q55360403: +39 0813330288(ComunediLaccoAmeno): The string supplied is too long to be a phone number.
  • Q55193986: +39 0858572358-0858572132: The string supplied is too long to be a phone number.
  • Q55385381: +39 097288643;097280111(comune): The string supplied did not seem to be a phone number.
  • Q55360478: +39 temporaneamenteinattivo: The string supplied did not seem to be a phone number.
  • Q55388680: +39-0030922401450: The phone number is not valid
  • Q55351806: +39-00390471412979: The phone number is not valid
  • Q16621503: +39-00390916890527: The phone number is not valid
  • Q55388742: +39-00390918460108: The phone number is not valid
  • Q55388726: +39-00390918889893: The phone number is not valid
  • Q55388733: +39-00390918889894: The phone number is not valid
  • Q55388767: +39-00390923860143: The phone number is not valid
  • Q55388759: +39-0039092530216: The phone number is not valid
  • Q55388772: +39-0039092531170: The phone number is not valid
  • Q55388784: +39-00390935546299: The phone number is not valid
  • Q55388793: +39-00390935643119: The phone number is not valid
  • Q3662761: +39-0039095690374: The phone number is not valid
  • Q55388779: +39-0039916814156: The phone number is not valid
  • Q55360914: +39-00523737833: The phone number is not valid
  • Q55385449: +39-0053381234: The phone number is not valid
  • Q55378977: +39-008133433865: The phone number is not valid
  • Q3868061: +39-0178-222-4013: The phone number is not valid
  • Q55375962: +39-039026458772: The phone number is not valid
  • Q55353011: +39-0467-83315: The phone number is not valid
  • Q55368353: +39-052493112507: The phone number is not valid
  • Q55378574: +39-0721470799266863: The phone number is not valid
  • Q55378562: +39-0721720972266863: The phone number is not valid
  • Q55378231: +39-0736812456818760: The phone number is not valid
  • Q55375699: +39-0793489643406006: The phone number is not valid
  • Q55386413: +39-0928-649478: The phone number is not valid
  • Q55360489: +39-0944-981113: The phone number is not valid
  • Q30889812: +39-09625106251069: The phone number is not valid
  • Q3803675: +39-55-229-9809: The phone number is not valid
  • Q3867941: +39-55-646-6532: The phone number is not valid

Structured Data on Commons Newsletter - Summer 2018[edit]

Welcome to the newsletter for Structured Data on Wikimedia Commons! You can update your subscription to the newsletter and contribute to the next issue. Do inform others who you think will want to be involved in the project!

Community updates
  • Our dedicated IRC channel: wikimedia-commons-sd webchat
  • Since our last newsletter, the Structured Data team has moved into designing and building prototypes for various features. The use of multilingual captions in the UploadWizard and on the file page has been researched, designed, discussed, and built out for use. Behind the scenes, back-end work on search is taking place and designs are being drawn up for the front-end. There will soon be specifications published for the use of the first Wikidata property on Commons, "Depicts," and a prototype is to be released to go along with that.
Things to do / input and feedback requests
Discussions held
Wikimania 2018
Partners and allies
Research

Two research projects about Wikimedia Commons are currently ongoing, or in the process of being finished:

  1. Research:Curation workflows on Wikimedia Commons—a project that seeks to understand the current workflows of Commons contributors who curate media (categorize it, delete it, link to it from other projects, etc.).
  2. Research:Technical needs of external re-users of Commons media—soliciting feedback from individuals and organizations that re-use Commons content outside of Wikimedia projects, in order to understand their current painpoints and unmet needs.
Development
  • Prototypes will be available for Depicts soon.
Stay up to date!

-- Keegan (WMF) (talk)

Message sent by MediaWiki message delivery - 21:07, 6 July 2018 (UTC)[reply]

Structured Data Newsletter - Research link fix[edit]

Greetings,

The newsletter omitted two interwiki prefixes, breaking the links on non-meta wikis as you might see above. Here are the correct links:

  1. m:Research:Curation workflows on Wikimedia Commons—a project that seeks to understand the current workflows of Commons contributors who curate media (categorize it, delete it, link to it from other projects, etc.).
  2. m:Research:Technical needs of external re-users of Commons media—soliciting feedback from individuals and organizations that re-use Commons content outside of Wikimedia projects, in order to understand their current painpoints and unmet needs.

My apologies, I hope you find the corrected links helpful.

- Keegan (WMF) (talk) 21:21, 6 July 2018 (UTC)[reply]

dati beniculturali[edit]

non funzionano, Sandro Botticelli (Q55141722)--Oursana (talk) 10:22, 7 July 2018 (UTC)[reply]

Ehi tu, ciao. :) Riusciamo a sentirci al mio ritorno in Italia (cioè dal 24 in poi) su questa cosa al volo? Vorrei capire un attimo come possiamo coordinare il nostro lavoro, perché ho un pacco di identificatori ICCU da poter utilizzare in materia. Tra l'altro, stiamo discutendo in varie persone qui a Cape Town su un progetto sul patrimonio culturale italiano da inserire nella strategia di WMI. Fammi sapere! --Sannita - not just another it.wiki sysop 11:11, 21 July 2018 (UTC)[reply]

Q55167519: chiesa non identificata[edit]

Ciao. Non riesco a identificare Q55167519 nel comune di Luino. Non mi risulta una località di nome Bosco in quel comune. Lì vicino c'è però Bosco Valtravaglia, frazione di Montegrino Valtravaglia. --Yiyi .... (talk!) 20:16, 6 August 2018 (UTC)[reply]

Ciao @Yiyi:, ne so quanto te... Ho fatto l'import ma non conosco tutti i luoghi d'Italia :D --AlessioMela (talk) 12:46, 29 August 2018 (UTC)[reply]

Import data from MiBACT[edit]

Ciao, sto verificando un po' di informazioni su Wikidata e sto rilevando molti item duplicati dall'Import di dati da MiBACT (es.: Q45813094): si può fare qualcosa per evitarli e rimediare? Pietro (talk) 06:42, 29 August 2018 (UTC)[reply]

@Pietro: durante l'import era difficile identificare tutti gli item già esistenti come identici a una scheda Mibact. Per cui, per evitare troppe unioni sbagliate, il bot "ha preferito" creare qualche item quando era incerto. Se trovi delle entità che si rifanno ad item che esistono già puoi semplicemente unirle. Grazie! --AlessioMela (talk) 12:45, 29 August 2018 (UTC)[reply]
E' quello che sto facendo, ma il problema è che non si tratta di qualche unità ma praticamente di tutti i siti importati: non c'è modo si automatizzare questa ricerca? Pietro (talk) 12:50, 29 August 2018 (UTC)[reply]
@Pietro: sono tanti, ma non sono tutti, non disperare ;-) se si potesse fare in automatico lo avrei fatto durante l'import. Purtroppo quelli sono da passare al vaglio di una persona perché dalle info automatiche non si poteva affermare con certezza... --AlessioMela (talk) 12:57, 29 August 2018 (UTC)[reply]
Sinceramente non sono d'accordo: di chiese di San Francesco in un paese piccolo come Popoli ce n'è una ed il fatto di trovare 4 item WD mi fa pensare che che eventuali tentativi per evitare duplicati non siano stati fatti con la necessaria attenzione. Questo è solo un esempio, ma puoi dare uno sguardo ai miei contributi di questa mattina per trovarne a volontà: possiamo coinvolgere qualcuno per avere qualche altra idea? Pietro (talk) 13:05, 29 August 2018 (UTC)[reply]
@Pietro: quando dici "di chiese di San Francesco in un paese piccolo come Popoli ce n'è una" è vero ed è qui la differenza tra bot ed essere umano. Il bot non sa che a Roma ce ne possono essere dieci e in paesi come Popoli una, massimo due (sì ci sono paesi piccolissimi con due chiese col nome molto simile). Il bot doveva affrontare tutti i casi possibili. Trovi la documentazione su https://github.com/synapta/wikidata-mibact-luoghi-cultura/blob/master/docs/wikidata/documentazione.md. Puoi coinvolgere chi vuoi alla discussione, ma non presumere che non abbia messo la necessaria attenzione nel lavoro. --AlessioMela (talk) 13:15, 29 August 2018 (UTC)[reply]
Se non si è in grado di controllare il risultato dell'esecuzione di un bot, si evita di usarlo e di inquinare WD di item che non si sa come bonificare. Pietro (talk) 13:19, 29 August 2018 (UTC)[reply]
@Pietro: tutti i dataset esterni (come questo) importati su Wikidata hanno una componente automatica e una manuale. Perfino alle origini di Wikidata, quando si sono importate le pagine di Wikipedia dalle varie lingue si è dovuto procedere così. Purtroppo lo stato dell'arte dell'entity recognition presuppone ancora un intervento manuale. Ripeto, coinvolgi altri pareri se non ti fidi del mio, ma abbassa i toni. --AlessioMela (talk) 13:32, 29 August 2018 (UTC)[reply]
Item_Wikidata_duplicati_da_AlessioBot Pietro (talk) 18:48, 29 August 2018 (UTC)[reply]
Per il futuro quando si sa già che si corre il rischio di creare duplicati, magari prima di iniziare conviene chiedere un parere ad altri, chissà che non salti fuori qualche idea. Ora mi sa che questi duplicati rimarranno per sempre. --ValterVB (talk) 19:13, 29 August 2018 (UTC)[reply]
Mi sembra improbabile che rimangano per sempre, perché sono in uso attivo da parte di centinaia di persone al di fuori di Wikidata: given enough eyeballs, all bugs are shallow. La velocità di correzione dei dati è già molto alta. --Nemo 19:05, 1 September 2018 (UTC)[reply]

Afferenza P131 e P582[edit]

Nelle interrogazioni SPARQL delle liste, qual è il modo piú efficiente perché traversando le P131 si ignorino le affermazioni con data di fine nel passato? Al momento in w:it:Progetto:Wiki Loves Monuments 2018/Monumenti/Sardegna abbiamo Cuglieri (Q385643) che si presenta nelle liste di due province. Non è un gran danno, eh: i dati in Wikidata sono corretti e gli utenti della provincia di Nuoro magari non si sono ancora abituati al cambiamento. --Nemo 05:21, 4 September 2018 (UTC)[reply]

@Nemo_bis: sì si può fare via SPARQL tramite i qualificatori però si complica molto e in alcuni casi vanno in timeout. Se guardi la mia modifica di Cuglieri è il modo ideale per risolvere (anche se non è centralizzata come una singola modifica di una query), ovvero definire quale dei vari oggetti è il "preferito". In questo modo la query SPARQL attuale non duplica più. --AlessioMela (talk) 15:58, 4 September 2018 (UTC)[reply]
Sí, anch'io ho risolto in modo analogo per certi casi di afferenza a provincia o città metropolitana in cui le interrogazioni andavano storte. Va bene, continuiamo cosí. Grazie, Nemo 05:51, 5 September 2018 (UTC)[reply]

Structured Data on Commons Newsletter - Fall 2018 edition[edit]

Welcome to the newsletter for Structured Data on Wikimedia Commons! You can update your subscription to the newsletter. Do inform others who you think will want to be involved in the project!

Community updates
Things to do / input and feedback requests

Current:

Since the last newsletter:

Presentations / Press / Events
Partners and allies
  • The info portal on Structured Commons now includes a section on GLAM (Galleries, Libraries, Archives and Museums).
  • We are currently planning the first GLAM pilot projects that will use structured data on Wikimedia Commons. One project has already started: the Swedish Heritage Board researches and develops a prototype tool to provide improved metadata (translations, data additions...) from Wikimedia Commons back to the source institution. Read the project brief.
  • The documentation for batch uploads of files to Wikimedia Commons will be improved in 2019, as part of preparing for Structured Data on Wikimedia Commons. To prepare, the GLAM team at the Wikimedia Foundation wants to understand better which types of documentation you already use, and how you like to learn new GLAM-Wiki skills and knowledge. Fill in a short survey to provide input!
Stay up to date!

-- Keegan (WMF) (talk)

Message sent by MediaWiki message delivery - 17:58, 7 December 2018 (UTC)[reply]

Captions in January[edit]

The previous message from today says captions will be released in November in the text. January is the correct month. My apologies for the potential confusion. -- Keegan (WMF) (talk) 20:43, 7 January 2019 (UTC)[reply]

Structured Data - file captions coming this week (January 2019)[edit]

My apologies if this is a duplicate message for you, it is being sent to multiple lists which you may be signed up for.

Hi all, following up on last month's announcement...

Multilingual file captions will be released this week, on either Wednesday, 9 January or Thursday, 10 January 2019. Captions are a feature to add short, translatable descriptions to files. Here's some links you might want to look follow before the release, if you haven't already:

  1. Read over the help page for using captions - I wrote the page on mediawiki.org because captions are available for any MediaWiki user, feel free to host/modify a copy of the page here on Commons.
  2. Test out using captions on Beta Commons.
  3. Leave feedback about the test on the captions test talk page, if you have anything you'd like to say prior to release.

Additionally, there will be an IRC office hour on Thursday, 10 January with the Structured Data team to talk about file captions, as well as anything else the community may be interested in. Date/time conversion, as well as a link to join, are on Meta.

Thanks for your time, I look forward to seeing those who can make it to the IRC office hour on Thursday. -- Keegan (WMF) (talk) 21:09, 7 January 2019 (UTC)[reply]

Category[edit]

Hello.

Can you translate and upload en:Category:Azerbaijani wine and en:Category:Viticulture in Azerbaijan for the article it:Vino azero in Italian Wikipedia?

Yours sincerely, Matricatria (talk) 18:32, 8 June 2019 (UTC)[reply]

Community Insights Survey[edit]

Share your experience in this survey

Hi AlessioMela,

The Wikimedia Foundation is asking for your feedback in a survey about your experience with Wikidata and Wikimedia. The purpose of this survey is to learn how well the Foundation is supporting your work on wiki and how we can change or improve things in the future. The opinions you share will directly affect the current and future work of the Wikimedia Foundation.

Please take 15 to 25 minutes to give your feedback through this survey. It is available in various languages.

This survey is hosted by a third-party and governed by this privacy statement (in English).

Find more information about this project. Email us if you have any questions, or if you don't want to receive future messages about taking this survey.

Sincerely,

RMaung (WMF) 16:25, 9 September 2019 (UTC)[reply]

Reminder: Community Insights Survey[edit]

Share your experience in this survey

Hi AlessioMela,

A couple of weeks ago, we invited you to take the Community Insights Survey. It is the Wikimedia Foundation’s annual survey of our global communities. We want to learn how well we support your work on wiki. We are 10% towards our goal for participation. If you have not already taken the survey, you can help us reach our goal! Your voice matters to us.

Please take 15 to 25 minutes to give your feedback through this survey. It is available in various languages.

This survey is hosted by a third-party and governed by this privacy statement (in English).

Find more information about this project. Email us if you have any questions, or if you don't want to receive future messages about taking this survey.

Sincerely,

RMaung (WMF) 19:51, 20 September 2019 (UTC)[reply]

Structured Data - blogs posted in Wikimedia Space[edit]

There are two separate blog entries for Structured Data on Commons posted to Wikimedia Space that are of interest:

  • Working with Structured Data on Commons: A Status Report, by Lucas Werkmeister, discusses some ways that editors can work with structured data. Topics include tools that have been written or modified for structured data, in addition to future plans for tools and querying services.
  • Structured Data on Commons - A Blog Series, written by me, is a five-part posting that covers the basics of the software and features that were built to make structured data happen. The series is meant to be friendly to those who may have some knowledge of Commons, but may not know much about the structured data project.
I hope these are informative and useful, comments and questions are welcome. All the blogs offer a comment feature, and you can log in with your Wikimedia account using oAuth. I look forward to seeing some posts over there. -- Keegan (WMF) (talk) 21:33, 23 September 2019 (UTC)[reply]

Label of Q65032527[edit]

Hi AlessioMela,

Interesting additions from the sound archives. Thanks for adding them.

Just a minor point concerning the above item. The items label is currently "Gailloud Frédéric" instead of "Frédéric Gailloud". Also, it seems to lack a instance of (P31). I fixed a few similar ones I came across, but there seem to be more of them. You might want to have a look at the constraint report.

If the datasource allows to correct this easily, that would be most appreciated. If you have some raw data that could help, I can try to sort it out. --- Jura 18:12, 7 December 2019 (UTC)[reply]

@Jura1: thanks for the link to the report. When I add those data from the sound archive I saw that some label are inverted (surname name) but I don't recognize all. Fortunately for the major part of them there were additional informations like: this item is a person and this is the name and this the surname. The ones you see in the constraint report hadn't those information and I chose not to add myself because I was not sure (many bands, trios and names that I didn't know). --AlessioMela (talk) 10:33, 12 December 2019 (UTC)[reply]

Inversione cognome-nome (surname - given name inversion)[edit]

Ciao! Vedendo questo batch di QS, ho notato che moltissimi elementi da te creati sulla base di Swiss National Sound Archives ID (P6770) presentano un'inversione cognome-nome nell'etichetta (es. Keller Eduard anziché Eduard Keller). Ti sarebbe possibile correggerli tutti via bot? Grazie mille, --Epìdosis 17:56, 22 March 2020 (UTC)[reply]

Ciao @Epìdosis:, temo non sia possibile fare l'inversione proprio perché molti (la maggior parte) hanno invece l'ordinamento giusto. Per cui si rischia di invertire la situazione :(. --AlessioMela (talk) 12:51, 14 May 2020 (UTC)[reply]

Swiss National Sound Archives ID[edit]

On 14 May 2019 you've successfully proposed Swiss National Sound Archives ID Property (Property:P6770) to be created. (By the way thank you for your appreciated work /initiatives.) Well, I've found a problem that is connected to that: The VIAF nowadays has an ID named 'SZ' that doesn't point to Phonotek CH but to Swiss National Bibliothek. Please don't just tell me that maybe some professionals at VIAF or NatBib have caused it but let's try to find a suitable solution. 'SZ' property might be possibly renamed, here or there? It might be necessary to speak to the resonsible persons there? So sorry but I have to admit that I'm not a Swiss citizen and not locally near to the institutions staff. For having a starting point you could tell me how you seperate Swiss Phonotek and Swiss National Bibliothek as for ID properties (I'd suppose that this Phonotek is just a sub institution of NatBib). Wouldn't it be useful to rename our Wikidata 'SZ' to 'SZphon'? Please tell me nevertheless what you think about possible solutions. (In English or German or eventually French language.) -- Justus Nussbaum (talk) 07:56, 5 April 2020 (UTC)[reply]

I've just found this documentation on an identifier in the Swiss National Library's archive database. Does that really say there is still no Swiss National Library ID property? I wouldn't have thought that to be possible. -- Justus Nussbaum (talk) 08:22, 5 April 2020 (UTC)[reply]
@Justus Nussbaum: Phonotek is now a sub institution but when I talked to them some years ago they where in a transition phase. So this may reflect also in the data. I'm not a Swiss citizen either (I'm Italian). --AlessioMela (talk) 12:49, 14 May 2020 (UTC)[reply]

Q55137214[edit]

Ciao Alessio, non riesco a identificare questo museo, qualche idea? Buona serata--Patafisik (talk) 16:20, 13 May 2020 (UTC)[reply]

Ciao @Patafisik: sembra che l'abbiano tolto anche dal sito del Mibact, ne ho richiesto la cancellazione. Grazie! --AlessioMela (talk) 12:45, 14 May 2020 (UTC)[reply]

Same church[edit]

Ciao,

Coud you take a look at San Biagio (Q55166087) and San Biagio (Q19984435). I'm not 100% sure but it seems to be the same church (at least, it's the same name and same city).

Cheer, VIGNERON (talk) 10:34, 4 February 2023 (UTC)[reply]

Thanks for your suggestion @VIGNERON:! Same church: merged! --AlessioMela (talk) 11:31, 4 February 2023 (UTC)[reply]
Thanks ! Cheers, VIGNERON (talk) 11:32, 4 February 2023 (UTC)[reply]

Duplicate churches[edit]

Hi Alessio,

there are many more duplicate churches, I've just merged a few of them like Santissima Trinità dei Pellegrini (Q1852769) & Santissima Trinità dei Pellegrini (Q54860590). Do you have any idea how to deduplicate them mechanically?

Cheers, -- Jackie Bensberg (talk) 21:46, 20 April 2023 (UTC)[reply]

Hi Jackie, it was an import from the best official Italian dataset at the moment. I made, with the help of other users involved in the project (it was a Wikimedia Italia project) as much manual dedup as we found out after the mechanical deduplication. However the original source has non obvious items and unfortunately native duplicates inside. Some of them may be still duplicated both on the sources both on Wikidata. Moreover the information inside Wikidata at that time weren't sufficient to perform a secure deduplication, also manually speaking. Nowadays instead it's clearer when an item is duplicated thanks to the new attributes added time by time. This is the power of Wikidata :)
Thanks for your merge and I will always keep an eye open to find other duplicates! AlessioMela (talk) 14:17, 22 April 2023 (UTC)[reply]
Retrieved from "https://www.wikidata.org/w/index.php?title=User_talk:AlessioMela&oldid=1880560785"