User talk:Harmonia Amanda
About this board
Previous discussion was archived at User talk:Harmonia Amanda/Archive 1 on 2015-08-10.
Wolfram Language entities for surnames
Matching one id to multiple items with OpenRefine
I have stumbled upon https://twitter.com/Harmonia_Amanda/status/1037207702060113920
In short, yes you can do that with OpenRefine. I haven't seen your dataset but intuitively this should be doable simply by doing the reconciliation in two columns, so that each id can be matched to one or two items. Just let me know if you need a hand!
Good to know! I'll try to configure it this evening. Do you have an example at hand? It would help me.
If you have not used OpenRefine yet you might want to start with generic tutorials for simple cases (I wrote some at Wikidata:Tools/OpenRefine/Editing).
For your own case, again I would need to see what your data looks like - otherwise I cannot give any precise indications. Is your dataset available anywhere, ideally in the form of a table or spreadsheet?
I have a spreadsheet that I can send to you. Otherwise, here is an example of one entry for two people. There are entries for only one person in the database (for example) but you can know if it should be matched to one or two items based on the sport discipline (top right).
Hello @Harmonia Amanda - hope you had nice summer vacations :)
just tell me to get out if I'm wrong, but would those case not be a typical "Bonnie and Clyde" ?
If it were Wikipedia articles and we were obligated to create an entry for each ISU identifier, then yes. But we are not under obligations to follow the ISU way, and these IDs are widely used is the figure skating world for individuals. They are the key to find who participated to which competitions (and with whom). The ISU create a new entry each time something significant change for a skater. So people changing their sport country, passing from junior to senior, marrying and changing their names, etc., all of this warrant a new ISU IDs. So I'm not really that keen on following their modeling ^^
I see :D
good luck with your matching...^^
Great! Yes I think this should work. Happy to have a look at the spreadsheet.
Please discuss first
Before undoing other users contributions, please open a discussion on the relevant project.
I let you a message just before yours.
My user page is n0t the relevant project .. please undo your changes and speedy deletions.
You didn't create a discussion before creating an item outside of the project scope (since we don't accept items in lieu of queries when queries would be the relevant way to deal with things), so no, I didn't think it necessitated a discussion there. You are welcome to start one and I'll participate.
Ok. I will undo it your place then.
please justify before your need for this item. If there is a use I missed, wich was not obvious, I'll gladly undo it myself (and use this item on all relevant names, and not just half ot it). Right now, it seems very obviously out of scope. I may be wrong about that but i would like an explanation please.
There is no requirement to discuss items before creating them.
Please restore Q56228301. If you think an item should be deleted, please use the relevant page.
I will open a discussion on WikiProject Names later this week.
i created a discussion for the restoration of this element: Wikidata:Requests_for_deletions#Q56228301. Please explain your need there. Thank you
If you want it to be discussed there, you need to restore it.
No, I agree, we don't usually discuss creation of new items. And when they are out of scope, they are speedy deleted. And sometimes that is contested and then it's discussed.
I honestly thought you created this item because you didn't know how to write the relevant query, so in my mind, writing the query solved yours needs and suppressed any need for the item.
It seems like you have a specific need you have not yet stated clearly which necessitate an item instead of a query. I can't imagine what but I'll be glad to learn.
It seemed a very clear cut case of a test item created because someone didn't know SPARQL. I didn't think it was controversial. I have no problem discussing it now that you are saying it is.
So when are you going to undelete it?
Your request got archived as you didn't restore the item: Wikidata:Requests for deletions/Archive/2018/08/31
I undeleted as soon as I had back Internet access and re-opened the request.
There is an open question for you in the discussion.
Propositions en attente
Bonjour. Aurais-tu l'occasion de créer des propriétés qui attendent de l'être depuis quelques jours ? Je suis l'auteur de la proposition et je ne peux donc pas le faire moi-même. Il y a par exemple Wikidata:Property proposal/Academia URL, Wikidata:Property proposal/Index of Historic Collectors and Dealers of Cubism ID, Wikidata:Property proposal/National Medal of Arts ID, Wikidata:Property proposal/PAM ID, Wikidata:Property proposal/So Foot ID et Wikidata:Property proposal/TPA ID. Je n'entends pas que tu te tapes l'ensemble du remplissage à faire. J'ai juste besoin que tu appuies sur le bouton de création, à charge pour moi de compléter tout le reste dans les minutes qui suivent. Peux-tu voir ?
Je regarde ça.
Merci beaucoup. C'est excellent. (Je prends les deux autres quand tu auras le temps.)
Salut. Je reviens vers toi parce que Category:Properties ready for creation s'est à nouveau remplie. Je vais m'occuper de certaines propositions parmi celles que je n'ai pas avancées, mais il y a en revanche Wikidata:Property proposal/Angelicum ID, Wikidata:Property proposal/PUSC ID, Wikidata:Property proposal/Historic Hotels of America ID et Wikidata:Property proposal/Voetbalstats ID pour lesquelles je vais devoir compter sur des tiers pour une création, donc peut-être toi ! La dernière est à la demande d'un contributeur de Wikipédia. Peux-tu voir, éventuellement ?
Et j'ajoute Wikidata:Property proposal/Historic Hotels Worldwide ID. Désolé !
Give your feedback about changes to Special:Block
You are receiving this message because you are a top user of Special:Block on this wiki. Thank you for the important work that you do. There is a discussion happening about plans to improve Special:Block with the ability to set new types of blocks. To get the best design and new functions added, it is essential that people who use the tool join the discussion and share their opinions about these changes.
Instead of a full site wide block, you would be able to set a Partial Block. A user could be blocked from a single page, multiple pages, one or more namespaces, from uploading files, etc. There are several different ways to add this feature to Special:Block. Right now Important decisions are being made about the design and function.
Please review the page on Meta and share your feedback on the discussion page. Or you can reach me by email Also, share this message with anyone else who might be interested in participating in the discussion.
I appreciate any time that you can give to assist with making improvements to this feature. Cheers, SPoore (WMF) (talk) , Trust and Safety Specialist, Community health initiative (talk) 01:59, 10 August 2018 (UTC)
- Apologizes for posting in English.
Structured Data Newsletter - Research link fix
The newsletter omitted two interwiki prefixes, breaking the links on non-meta wikis as you might see above. Here are the correct links:
- 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.).
- 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.
Structured Data on Commons Newsletter - Summer 2018
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.
- A workshop on what Wikidata properties Commons will need. This workshop will be open for the entire month of July 2018 at minimum.
- Join the community focus group!
- Do you want to help out translating messages about Structured Data on Commons from English to your own language? Sign up on the translators page.
- Contribute to the next newsletter.
- Discussions held
- In late February there was a discussion around how Commons generally sees data being modeled.
- The first discussion on copyright and licensing with Commons was held in March. This was a "high level" discussion, there will be a consultation later this summer about the deeper mapping of copyright and licensing in a structured way.
- In April there was an exercise for GLAM partners in metadata and ontology mapping.
- A discussion about the design for Multilingual Captions on the file page took place in May. You can still review the designs and leave feedback.
- There was an IRC office hour in June to discuss progress so far and future plans.
- Wikimania 2018
- Three sessions about Structured Commons are officially scheduled for Wikimania 2018 - Cape Town, South Africa - July 2018.
- Wikimedia Commons and GLAM needs around the world (Friday 20 July, 10:30 local time)
- Structured Data on Wikimedia Commons and knowledge equity (Friday 20 July, 14:00 local time)
- Design challenge workshop: How can multilingual structured metadata bring knowledge equity to Commons? (Friday 20 July, 14:30 local time)
- Structured Data on Commons is also a focus area during the Wikimania 2018 Hackathon. We will, among other things, do 'live' modelling of Wikidata properties for Commons - an offline spin-off of the community consultation taking place on wiki.
- 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!
- Structured Data on Commons was presented to GLAM audiences during EuropeanaTech 2018 in Rotterdam (15 May 2018) and at the Deutsche Digitale Bibliothek Forum in Berlin (4 June 2018).
Two research projects about Wikimedia Commons are currently ongoing, or in the process of being finished:
- 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.).
- 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.
- Prototypes will be available for Depicts soon.
- Stay up to date!
- Follow the Structured Data on Commons project on Phabricator: https://phabricator.wikimedia.org/project/profile/34/
- Subscribe to this newsletter to receive it on a talk page of your own choice.
- Join the next IRC office hour and ask questions to the team! The date for next quarter will be announced soon.
Message sent by MediaWiki message delivery - 21:07, 6 July 2018 (UTC)
José - differentiating between Spanish and Portuguese
Hi there! You told me I could ask questions, so here goes ;-) In the description of José Q2190619 it says: (male given name (use Q29043257 for Spanish and Q29043256 for Portuguese). This gets a bit messed up when compound names like Francisco José Q47484032 has both Portuguese and Spanish set as languages, but uses the Portuguese José (Q29043256 ). What is the thinking here? And doesn't mixing them cause problems with properties like Soundex and Caverphone? What about the etymology?
For a clearer example, there is the last name Falla Q20519159. This is a family name in both Spain and Norway, but they are only *spelled* the same way - they don't share pronunciation, etymology or much anything else. Wouldn't names like these be better kept as separate entities?
I don't understand at all the thinking there. The majority of the Names project agree that all three "José" should be merged together, in line with all the other names but a contributor is really intent in keeping them separated, even though it doesn't really make sense. I only use the generic "José" and know of no one using the specialized ones.
Soundex and Caverphone are based on writing, deducing a pronunciation as it would be said in English. It doesn't indicate the real pronunciation.
The idea of the project is that in most cases we can't know if someone use the name "Falla" as the Norwegian or Spanish name (and for many names you'll also have Spanish immigrants to Norway, or the reverse, or cases like these muddling the waters). Everything depend on context and context is something we can't really have for all entries in our database. We can know how it's written and we use that. Everything more specific go to the person/family item.
Hello! Please, when you remove the statement "instance of (P31) Wikimedia disambiguation page (Q4167410)", could you fix better the item?
For example, here it remained to fix the descriptions and move one of the sitelinks to the relative DAB item.
I've been observing your behaviour for a long time and I noticed that you often leave a lot of backlog behind you.
I usually verify these things, but this time there was a wrong merge a few days before. I didn't spot the wrong merge because I was working on wrong disambiguation pages and it looked like all the others I fixed that day while it was a totally different case. (And the merge should have been undone instead of the wrong P31 deleted, which would have also fixed the descriptions).
Since I quite literally spend more than half my time here fixing wrong descriptions, I really don't think I leave "a lot of backlog". I can decide not to fix some items manually when I know that a few days later I'll use a script, which I do regularly for names, but more than half my work is actually in fixing these issues.
Hi! Please don't add any more labels to 'sr-el' like  since it needs to be transliterated in Serbian, not just copied.
I changed it not, but I think there is a lot more that needs to be fixed. I'll make a bot for this soon, but just to notify so no one brake any changes more. Cheers!