Jump to content

User talk:Wolfgang8741

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Welcome

[edit]
Hello, Wolfgang8741, and Welcome to Wikipedia!

Welcome to Wikipedia! I hope you enjoy the encyclopedia and want to stay. As a first step, you may wish to read the Introduction.

If you have any questions, feel free to ask me at my talk page – I'm happy to help. Or, you can ask your question at the New contributors' help page.

Here are some more resources to help you as you explore and contribute to the world's largest encyclopedia...

Finding your way around:

Need help?

How you can help:

Additional tips...

Wolfgang8741, good luck, and have fun. – Aboutmovies (talk) 03:25, 22 July 2016 (UTC)[reply]

Wikipedia:WikiProject United States/The 50,000 Challenge

[edit]
You are invited to participate in the 50,000 Challenge, aiming for 50,000 article improvements and creations for articles relating to the United States. This effort began on November 1, 2016 and to reach our goal, we will need editors like you to participate, expand, and create. See more here!

--MediaWiki message delivery (talk) 02:41, 8 November 2016 (UTC)[reply]

ArbCom Elections 2016: Voting now open!

[edit]

Hello, Wolfgang8741. Voting in the 2016 Arbitration Committee elections is open from Monday, 00:00, 21 November through Sunday, 23:59, 4 December to all unblocked users who have registered an account before Wednesday, 00:00, 28 October 2016 and have made at least 150 mainspace edits before Sunday, 00:00, 1 November 2016.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2016 election, please review the candidates' statements and submit your choices on the voting page. MediaWiki message delivery (talk) 22:08, 21 November 2016 (UTC)[reply]

Lake Pickering

[edit]

Hi. Regarding Lake Pickering where you have requested an Infobox; did you have any in mind? Landform Infobox, perhaps? I am unsure of which Infobox you were thinking of. Regards. The joy of all things (talk) 14:41, 24 March 2017 (UTC)[reply]

Hey thanks for the follow up, actually reading the page closer the "body of water" infobox I was thinking might apply does not given the data may not exist for the historical lake that is no longer present to my understanding. — Preceding unsigned comment added by Wolfgang8741 (talk • contribs) 22:15, 24 March 2017 (UTC)[reply]

Women in Red World Contest

[edit]

Hi. We're into the last five days of the Women in Red World Contest. There's a new bonus prize of $200 worth of books of your choice to win for creating the most new women biographies between 0:00 on the 26th and 23:59 on 30th November. If you've been contributing to the contest, thank you for your support, we've produced over 2000 articles. If you haven't contributed yet, we would appreciate you taking the time to add entries to our articles achievements list by the end of the month. Thank you, and if participating, good luck with the finale!

ArbCom 2017 election voter message

[edit]

Hello, Wolfgang8741. Voting in the 2017 Arbitration Committee elections is now open until 23.59 on Sunday, 10 December. All users who registered an account before Saturday, 28 October 2017, made at least 150 mainspace edits before Wednesday, 1 November 2017 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2017 election, please review the candidates and submit your choices on the voting page. MediaWiki message delivery (talk) 18:42, 3 December 2017 (UTC)[reply]

WV cities

[edit]

Hey Wolfgang8741, I have noted a few rather remote places in WV being deemed as part of a cities scope. I have been to a few of these places...WHY is that happening? Just curiousCoal town guy (talk) 19:43, 9 January 2018 (UTC)[reply]

If you read the WikiProject Cities scope, unincorporated communities are included in the effort to provide consistent information presentation of articles. The places that I added are mentioned as such. My rational is to provide visibility for the articles the project to raise the likelihood that person with interest in that area can locate and add details. While I agree some communities are remote (and I've been to some of them too) they would still have the metadata to be included in their articles though it may be harder to locate. If not you, then who? (talk) 19:52, 9 January 2018 (UTC)[reply]

I love the spirit, but there is NO accuracy. So we publish incorrect categories and flood projects with bad/false data to get more visibility? Thats a BAD move because the data is patently false.
HOW does false data help? It does not, its inaccurate. I have ready the projects too, we could get a few in the LGBT community as well, but is that accurate?Coal town guy (talk) 19:55, 9 January 2018 (UTC)[reply]
I like your enthusiasm to advocate for not miscatigorizing and adding extra tags, but I need more specific supporting details to go on to make sure I'm not "flooding projects" as you put it. Please point out specific articles that have been improperly categorized and supporting data that they are not unincorporated communities or otherwise in scope. To state there has been incorrect categories applies without providing the articles does not help correct the issue nor educate on where the view of scope diverge. If not you, then who? (talk) 20:07, 9 January 2018 (UTC)[reply]
OK, I will be sincere and assume good faith. I am not sure, but I have created about 2,700+ articles on unincorporated communities in KY and WV. Most are coal towns. MOST of the nearby cities and nearby is subjective, detest, hate, dont like or view as an eye sore the mere existence of said places. SO, again in good faith I did indeed re read the cities project tag. The fault is called scope creep. If the Beatles visited a small town on a tour bus, does that mean the Beatles lived in that place? IF a coal town is near a city, do you honestly believe that city wants to have anything to do with a coal town? NO they dont. If a tour bus of strippers broke down in my burned out husk of what I call home, do you honestly believe I would have a stripper or adult wiki category project tag on that town page, NO.IF you place these category or project tags on these places, you are right, people will see those results, and they will say, this is all crap, or wrong WHY is this categorized this way? AND YOU SAY..to make them more visible.......regardless of the fact, that there is no relation at all..SO that means that your data integrity, as well as veracity is now in the shitter. AND SOME FOLKS, myself included, spend alot of time sourcing the articles and getting refs....WHY screw that up because you want people to have false positive result in a query? Now I could perform the same locution and have ANY tag on ANY page in wikipedia, but that does not make it, correct....I hope thats OK and yes, I am a volunteer tooCoal town guy (talk) 00:43, 10 January 2018 (UTC)you[reply]
Congratulations on the 2,700+ articles created, everyone appreciates your hard work including myself. I typically work on other basic geographic features, lakes and rivers to this point and just started expanding to the cities project. Please correct me if I'm misunderstanding what you are attempting to communicate. First I recognise the concern of scope creep, but that would be best addressed in the cities project. Since you are very active in creating unincorporated communities you might consider joining that project to better define the scope and how to manage unincorporated communities. The tag of WikiProject Cities isn't meant to say these are cities, but are where people live. I'm hoping that "cities" isn't leading to some misunderstanding of what the project is attempting to shape. Wikipedia:WikiProject_Cities/U.S._municipality_notes#Census-designated place (CDP) It also appears unincorporated communities are not the top priority at this time, but I'm sure I won't be the only person tagging these pages as it is in the scope of being a place where people live and with the work. I will not revert the tag reversions, but I suggest taking up the scope issue with the WikiProject Cities members who are interested in creating and building the information about where people live and named. It seems a perfect group of likeminded article creators. Second I believe that my visibility statement was not clearly communicated. In tagging to the cities project enables those who specialize in pages where people live to locate and improve articles. This would mean all levels of incorporated and unincorporated locations. Addressing a few other points. What I'm discussing here is a level distinction of all places where people live and the dynamics of coal town vs cities as you put it shouldn't be a dynamic when talking about creating ways that the information about the places people live. While yes there are dynamics in the communities about perceptions what we are addressing here are USGS GNIS identified locations which means they are notable named places regardless of who visited or what events happened or didn't. I hope we can both agree that we would like to see these unincorporated communities remain in existence and continue to be improved. My one and only intention is to improve the quality and quantity and linking of articles on Wikipedia, WikiData, and OpenStreetMaps. My main motivation is to enable more citizens to location points nearby where they and others building upon the data from these systems to have more refined data for participants in citizen science and other local activities.If not you, then who? (talk) 03:49, 11 January 2018 (UTC)[reply]
I think your idea is a very good one. No joke. It is a very good one. Perhaps another route would also be to the Appalachian project and yes mining project pages?? Just thoughts. I have tried the WV Culture anf Histiry folks and their maintenance of the WV History project, off wikipedia, but again local involvement is of the utmost importance to anyone. I did ALOT of that for Raleigh ansd McDowell Counties in WV. It has generated a local interest, BUT again, I found the roadblocks we all do. Some local people in cities have NEVER heard of these places and they live there Coal town guy (talk) 13:56, 11 January 2018 (UTC)[reply]

Welcome to The Wikipedia Adventure!

[edit]
Hi Wolfgang8741! We're so happy you wanted to play to learn, as a friendly and fun way to get into our community and mission. I think these links might be helpful to you as you get started.

-- 20:07, Tuesday, June 26, 2018 (UTC)

Mission 1 Mission 2 Mission 3 Mission 4 Mission 5 Mission 6 Mission 7
Say Hello to the World An Invitation to Earth Small Changes, Big Impact The Neutral Point of View The Veil of Verifiability The Civility Code Looking Good Together

ArbCom 2018 election voter message

[edit]

Hello, Wolfgang8741. Voting in the 2018 Arbitration Committee elections is now open until 23.59 on Sunday, 3 December. All users who registered an account before Sunday, 28 October 2018, made at least 150 mainspace edits before Thursday, 1 November 2018 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2018 election, please review the candidates and submit your choices on the voting page. MediaWiki message delivery (talk) 18:42, 19 November 2018 (UTC)[reply]

Haphead moved to draftspace

[edit]

An article you recently created, Haphead, does not have enough sources and citations as written to remain published. It needs more citations from reliable, independent sources. (?) Information that can't be referenced should be removed (verifiability is of central importance on Wikipedia). I've moved your draft to draftspace (with a prefix of "Draft:" before the article title) where you can incubate the article with minimal disruption. When you feel the article meets Wikipedia's general notability guideline and thus is ready for mainspace, please click on the "Submit your draft for review!" button at the top of the page. Jovanmilic97 (talk) 10:01, 30 November 2018 (UTC)[reply]

Lake Menghough

[edit]

I saw you tagged Talk:Lake Menghough as a stub. The lake does not seem to exist any more, and sources are hard to find, but what information needs to be added? Aymatth2 (talk) 15:06, 6 April 2019 (UTC)[reply]

I was going through articles quite fast, I reviewed this as C as it does seem quite extensive while I'm no expert to say if the intermittent lake no longer exists. Agreed that satellite photos currently show no water at the time they were taken. I personally am not putting articles above C until I better understand the way the project judges articles more complete or better state. Thank you for contacting me, loving that others are paying attention to the lakes and assessment! Cheers. Wolfgang8741 says: If not you, then who? (talk) 18:49, 6 April 2019 (UTC)[reply]
McArthur Lake (Idaho). Is this really a stub? See WP:Assessing articles. "A stub has very little meaningful content, and may be incomprehensible". Arbitrarily rating articles as "stub" without reading them can be very demoralizing to newbies. We are desperately short of newbies. I suggest you go back through the articles you have tagged and review your assessments, or just blank them. Thanks, Aymatth2 (talk) 19:14, 7 April 2019 (UTC)[reply]
Thanks for that catch, given the volume I'm reviewing I'll make a mistake from time to time, but am planning to run a report for these outlying mistakes.Wolfgang8741 says: If not you, then who? (talk) 19:19, 7 April 2019 (UTC)[reply]
You have tagged two of the articles on my watchlist, and assessed both as stubs. If you do not have time to read them, do not assess them. Aymatth2 (talk) 19:44, 7 April 2019 (UTC)[reply]

Requesting IPBE flag - for editing while logged in to Wikipedia via VPN over insecure networks.

[edit]
This user's unblock request has been reviewed by an administrator, who accepted the request.

Wolfgang8741 (block log • active blocks • global blocks • contribs • deleted contribs • filter log • creation log • change block settings • unblock • checkuser (log))

Request reason:

Caught by a colocation web host block. The IP address is 70.32.0.106. This should fall under http://us-washingtondc.privateinternetaccess.com though they appear to have different expirations. I use a VPN when not on a trusted (encrypted) networks and would like to be able to edit while at coffee shops through my VPN with the IPBE flag. I only plan to edit while logged in and understand the responsibility of being granted this permission. Wolfgang8741 says: If not you, then who? (talk) 19:16, 18 April 2019 (UTC)[reply]

Accept reason:

WP:IPBE granted for 1 year. You should be able to edit now. You can ping me if you have problems. NinjaRobotPirate (talk) 03:12, 19 April 2019 (UTC)[reply]

IP block exempt

[edit]

I have granted your account an exemption from IP blocking. This will allow you to edit through full blocks affecting your IP address when you are logged in.

Please read the page Wikipedia:IP block exemption carefully, especially the section on IP block exemption conditions.

Appropriate usage and compliance with the policy may be checked (through the use of CheckUser) periodically, due to the nature of block exemption, and block exemption will be removed when no longer needed (for example, when the block it is related to expires).

I hope this will enhance your editing, and allow you to edit successfully and without disruption. NinjaRobotPirate (talk) 03:13, 19 April 2019 (UTC)[reply]

Thank you for the permission, I understand why the blocks are in place. I read through the documents before requesting the exemption, but I will make sure to review them for compliance. Wolfgang8741 says: If not you, then who? (talk) 03:36, 19 April 2019 (UTC)[reply]

Mirond Lake

[edit]

If you can't be bothered to even glance at the article, do not rate it. I am ready to escalate this. Aymatth2 (talk) 22:49, 28 April 2019 (UTC)[reply]

I am look at each article, thank you for bringing this misclassification to my attention. What about this warrants escalation? I am not intentionally misclassifying these articles. I'm not claiming ownership of the articles or domains, for these errors others are more than welcome to join the work I'm doing on Wikipedia:WikiProject_Lakes and reclassify the few that were incorrectly classified. If a rating is thought to be in error I'm happy to review, and do look at these articles again. Wolfgang8741 says: If not you, then who? (talk) 23:12, 28 April 2019 (UTC)[reply]
As far as I can tell, you are rating all lake articles "stub" without even looking at them. I have seen 3 out of 3 like that. You have been told repeatedly it is better not to rate than to discourage newbies by giving incorrect ratings, but you persist in ignoring that advice. This is disruptive. Please stop. Aymatth2 (talk) 11:42, 29 April 2019 (UTC)[reply]
Thank you for the feedback. Telling me to stop without suggestions for how I can improve is discouraging to me to rate pages at all in the exact same way you're saying I'm discouraging newbies my misrating their articles, but what I am not seeing is how you want to work with me to improve my classifications. Additionally while you identified 3 errors (thank you for that, it helps to highlight my contribution issues), what is my error rate within the 1000's of articles that I reviewed over the past weeks? A marginal error rate in the grander picture of contributions are unavoidable because we are humans and together we can move these articles forward. Would you be willing to review my other contributions to get a larger picture of my contribution and show me a pattern of what I'm misclassifying? I think this would show that I haven't had a broad disruptioin, but unfortunately you happened to find three examples. I already stated above I plan to use the assessment tool to review for outlying classifications, if you have any suggestion of how best to review my contribution history for misclassifications instead stopping all together then we both will benefit. Let's find how we can make my process better, instead of telling me not to contribute. Wolfgang8741 says: If not you, then who? (talk) 16:08, 29 April 2019 (UTC)[reply]
Keep assigning articles to Wikiproject Lakes, which is useful. But do not give articles quality or importance assessments without first reading them and comparing them to the criteria. If you cannot be bothered to review the articles, just leave the rating/assessment fields blank. Each time (this is the third) one of your assessments shows up on my watchlist I see that you could not possibly have even glanced at the article. A newbie could have put a lot of work into researching and writing an article, and then you slap them down with an unjustified "stub" rating. That is disruptive. Do not rate articles without reading them. Aymatth2 (talk) 21:06, 29 April 2019 (UTC)[reply]

The request for a Third Opinion about this has been removed (i.e. declined) because as currently constituted this is a conduct dispute over how an editor is acting and 3O only gives opinions about article content. To obtain an opinion or file a complaint about editor conduct, speak to an administrator or, after carefully reading and complying with the directions there, file a report at ANI. Regards, TransporterMan (TALK) 13:57, 30 April 2019 (UTC) (Not watching this page)[reply]

Well we obviously have conflicting opinions here as I do take a chance to read articles to review them. I can outline my review process if you would like. I will admit maybe my calibration of what constitutes a stub vs start could improve and mentorship on that would be appreciated, but to claim I am not reading the articles is not accurate. I would appreciate an administrator mediate this conflict of conduct as 3 articles misclassified doesn't seem like its a huge harm to have the community help correct, while if a large pattern could be shown in my classifications to be inaccurate I would be more than happy to self regulate and not proceed in ratings. I have only received this notice of misclassification on these three articles, the remainder have not generated any reclassification request to my knowledge. Wolfgang8741 says: If not you, then who? (talk) 15:42, 30 April 2019 (UTC)[reply]

I have started a discussion at Wikipedia:Administrators' noticeboard/Incidents#Wolfgang8741 mass-rating articles as stubs. Feel free to comment there. Aymatth2 (talk) 17:47, 30 April 2019 (UTC)[reply]

The discussion has been archived here without any action, which is typical of minor incidents. You can continue your work on the lakes, but make sure you do not rate any more articles as stubs unless you are sure they meet the criteria for a stub. You may want to go back over your former ratings. See WP:ASSESS and WP:Assessing articles, and the basic grading scheme table below. It strikes me that you may not know that you can assign a lake to WikiProject Lakes without assessing it. It is easy. Just add:
{{WikiProject Lakes |class= |importance= |mapneeded= |needs-infobox= }}
on the article talk page. Other editors will come by later and fill in the missing values. This is much less likely to turn away a new editor than to assess the article as a stub ("Provides very little meaningful content") when it is actually quite substantial. Keep up the good work! Aymatth2 (talk) 12:34, 4 May 2019 (UTC)[reply]
WikiProject content quality grading scheme
Class Criteria Reader's experience Editing suggestions Example
 FA The article has attained featured article status by passing an in-depth examination by impartial reviewers from WP:Featured article candidates.
More detailed criteria
The article meets the featured article criteria:

A featured article exemplifies Wikipedia's very best work and is distinguished by professional standards of writing, presentation, and sourcing. In addition to meeting the policies regarding content for all Wikipedia articles, it has the following attributes.

  1. It is:
    1. well-written: its prose is engaging and of a professional standard;
    2. comprehensive: it neglects no major facts or details and places the subject in context;
    3. well-researched: it is a thorough and representative survey of the relevant literature; claims are verifiable against high-quality reliable sources and are supported by inline citations where appropriate;
    4. neutral: it presents views fairly and without bias;
    5. stable: it is not subject to ongoing edit wars and its content does not change significantly from day to day, except in response to the featured article process; and
    6. compliant with Wikipedia's copyright policy and free of plagiarism or too-close paraphrasing.
  2. It follows the style guidelines, including the provision of:
    1. a lead: a concise lead section that summarizes the topic and prepares the reader for the detail in the subsequent sections;
    2. appropriate structure: a substantial but not overwhelming system of hierarchical section headings; and
    3. consistent citations: where required by criterion 1c, consistently formatted inline citations using footnotes—see citing sources for suggestions on formatting references. Citation templates are not required.
  3. Media. It has images and other media, where appropriate, with succinct captions and acceptable copyright status. Images follow the image use policy. Non-free images or media must satisfy the criteria for inclusion of non-free content and be labeled accordingly.
  4. Length. It stays focused on the main topic without going into unnecessary detail and uses summary style where appropriate.
 Professional, outstanding, and thorough; a definitive source for encyclopedic information. No further content additions should be necessary unless new information becomes available; further improvements to the prose quality are often possible. Cleopatra
(as of June 2018)
 FL The article has attained featured list status by passing an in-depth examination by impartial reviewers from WP:Featured list candidates.
More detailed criteria
The article meets the featured list criteria:
  1. Prose. It features professional standards of writing.
  2. Lead. It has an engaging lead that introduces the subject and defines the scope and inclusion criteria.
  3. Comprehensiveness.
  4. Structure. It is easy to navigate and includes, where helpful, section headings and table sort facilities.
  5. Style. It complies with the Manual of Style and its supplementary pages.
  6. Stability. It is not the subject of ongoing edit wars and its content does not change significantly from day to day, except in response to the featured list process.
 Professional standard; it comprehensively covers the defined scope, usually providing a complete set of items, and has annotations that provide useful and appropriate information about those items. No further content additions should be necessary unless new information becomes available; further improvements to the prose quality are often possible. List of dates predicted for apocalyptic events
(as of May 2018)
 A The article is well organized and essentially complete, having been examined by impartial reviewers from a WikiProject or elsewhere. Good article status is not a requirement for A-Class.
More detailed criteria
The article meets the A-Class criteria:
Provides a well-written, clear and complete description of the topic, as described in Wikipedia:Article development. It should be of a length suitable for the subject, appropriately structured, and be well referenced by a broad array of reliable sources. It should be well illustrated, with no copyright problems. Only minor style issues and other details need to be addressed before submission as a featured article candidate. See the A-Class assessment departments of some of the larger WikiProjects (e.g. WikiProject Military history).
 Very useful to readers. A fairly complete treatment of the subject. A non-expert in the subject would typically find nothing wanting. Expert knowledge may be needed to tweak the article, and style problems may need solving. WP:Peer review may help. Battle of Nam River
(as of June 2014)
 GA The article meets all of the good article criteria, and has been examined by one or more impartial reviewers from WP:Good article nominations.
More detailed criteria
A good article is:
  1. Well-written:
    1. the prose is clear, concise, and understandable to an appropriately broad audience; spelling and grammar are correct; and
    2. it complies with the Manual of Style guidelines for lead sections, layout, words to watch, fiction, and list incorporation.
  2. Verifiable with no original research:
    1. it contains a list of all references (sources of information), presented in accordance with the layout style guideline;
    2. reliable sources are cited inline. All content that could reasonably be challenged, except for plot summaries and that which summarizes cited content elsewhere in the article, must be cited no later than the end of the paragraph (or line if the content is not in prose);
    3. it contains no original research; and
    4. it contains no copyright violations or plagiarism.
  3. Broad in its coverage:
    1. it addresses the main aspects of the topic; and
    2. it stays focused on the topic without going into unnecessary detail (see summary style).
  4. Neutral: it represents viewpoints fairly and without editorial bias, giving due weight to each.
  5. Stable: it does not change significantly from day to day because of an ongoing edit war or content dispute.
  6. Illustrated, if possible, by media such as images, video, or audio:
    1. media are tagged with their copyright statuses, and valid non-free use rationales are provided for non-free content; and
    2. media are relevant to the topic, and have suitable captions.
 Useful to nearly all readers, with no obvious problems; approaching (though not necessarily equalling) the quality of a professional publication. Some editing by subject and style experts is helpful; comparison with an existing featured article on a similar topic may highlight areas where content is weak or missing. Discovery of the neutron
(as of April 2019)
B The article meets all of the B-Class criteria. It is mostly complete and does not have major problems, but requires some further work to reach good article standards.
More detailed criteria
  1. The article is suitably referenced, with inline citations. It has reliable sources, and any important or controversial material which is likely to be challenged is cited. Any format of inline citation is acceptable: the use of <ref> tags and citation templates such as {{cite web}} is optional.
  2. The article reasonably covers the topic, and does not contain obvious omissions or inaccuracies. It contains a large proportion of the material necessary for an A-Class article, although some sections may need expansion, and some less important topics may be missing.
  3. The article has a defined structure. Content should be organized into groups of related material, including a lead section and all the sections that can reasonably be included in an article of its kind.
  4. The article is reasonably well-written. The prose contains no major grammatical errors and flows sensibly, but does not need to be of the standard of featured articles. The Manual of Style does not need to be followed rigorously.
  5. The article contains supporting materials where appropriate. Illustrations are encouraged, though not required. Diagrams, an infobox etc. should be included where they are relevant and useful to the content.
  6. The article presents its content in an appropriately understandable way. It is written with as broad an audience in mind as possible. The article should not assume unnecessary technical background and technical terms should be explained or avoided where possible.
 Readers are not left wanting, although the content may not be complete enough to satisfy a serious student or researcher. A few aspects of content and style need to be addressed. Expert knowledge may be needed. The inclusion of supporting materials should be considered if practical, and the article checked for general compliance with the Manual of Style and related style guidelines. Psychology
(as of January 2024)
C The article is substantial but is still missing important content or contains irrelevant material. The article should have some references to reliable sources, but may still have significant problems or require substantial cleanup.
More detailed criteria
The article cites more than one reliable source and is better developed in style, structure, and quality than Start-Class, but it fails one or more of the criteria for B-Class. It may have some gaps or missing elements, or need editing for clarity, balance, or flow.
 Useful to a casual reader, but would not provide a complete picture for even a moderately detailed study. Considerable editing is needed to close gaps in content and solve cleanup problems. Wing
(as of June 2018)
Start An article that is developing but still quite incomplete. It may or may not cite adequate reliable sources.
More detailed criteria
The article has a meaningful amount of good content, but it is still weak in many areas. The article has one or more of the following:
  • A useful picture or graphic
  • Multiple links that help explain or illustrate the topic
  • A subheading that fully treats an element of the topic
  • Multiple subheadings that indicate material that could be added to complete the article
 Provides some meaningful content, but most readers will need more. Providing references to reliable sources should come first; the article also needs substantial improvement in content and organisation. Also improve the grammar, spelling, writing style and improve the jargon use. Ball
(as of September 2014)
Stub A very basic description of the topic. Meets none of the Start-Class criteria. Provides very little meaningful content; may be little more than a dictionary definition. Readers probably see insufficiently developed features of the topic and may not see how the features of the topic are significant. Any editing or additional material can be helpful. The provision of meaningful content should be a priority. The best solution for a Stub-class Article to step up to a Start-class Article is to add in referenced reasons of why the topic is significant. Lineage (anthropology)
(as of December 2014)
List Meets the criteria of a stand-alone list or set index article, which is an article that contains primarily a list, usually consisting of links to articles in a particular subject area. There is no set format for a list, but its organization should be logical and useful to the reader. Lists should be lists of live links to Wikipedia articles, appropriately named and organized. List of literary movements

Your draft article, Draft:Haphead

[edit]

Hello, Wolfgang8741. It has been over six months since you last edited the Articles for Creation submission or Draft page you started, "Haphead".

In accordance with our policy that Wikipedia is not for the indefinite hosting of material deemed unsuitable for the encyclopedia mainspace, the draft has been nominated for deletion. If you plan on working on it further, or editing it to address the issues raised if it was declined, simply edit the submission and remove the {{db-afc}}, {{db-draft}}, or {{db-g13}} code.

If your submission has already been deleted by the time you get there, and you wish to retrieve it, you can request its undeletion by following the instructions at this link. An administrator will, in most cases, restore the submission so you can continue to work on it.

Thanks for your submission to Wikipedia, and happy editing. CptViraj (📧) 09:48, 5 July 2019 (UTC)[reply]

Mole Day!

[edit]

Hello! Wishing you a Happy Mole Day on the behalf of WikiProject Science.

Sent by Path slopu on behalf of WikiProject Science and its related projects.

Sent by MediaWiki message delivery (talk) 23:00, 23 October 2019 (UTC)[reply]

ArbCom 2019 election voter message

[edit]
Hello! Voting in the 2019 Arbitration Committee elections is now open until 23:59 on Monday, 2 December 2019. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2019 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:12, 19 November 2019 (UTC)[reply]

[edit]

Hi. Thank you for your recent edits. An automated process has detected that when you recently edited List of lakes of Michigan, you added links pointing to the disambiguation pages Clear Lake and Silver Lake (check to confirm | fix with Dab solver). Such links are usually incorrect, since a disambiguation page is merely a list of unrelated topics with similar titles. (Read the FAQ • Join us at the DPL WikiProject.)

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 14:57, 14 April 2020 (UTC)[reply]

Your submission at Articles for creation: Round Lake (Michigan) has been accepted

[edit]
Round Lake (Michigan), which you submitted to Articles for creation, has been created.

Congratulations, and thank you for helping expand the scope of Wikipedia! We hope you will continue making quality contributions.

The article has been assessed as Start-Class, which is recorded on its talk page. Most new articles start out as Stub-Class or Start-Class and then attain higher grades as they develop over time. You may like to take a look at the grading scheme to see how you can improve the article.

Since you have made at least 10 edits over more than four days, you can now create articles yourself without posting a request. However, you may continue submitting work to Articles for creation if you prefer.

If you have any questions, you are welcome to ask at the help desk. Once you have made at least 10 edits and had an account for at least four days, you will have the option to create articles yourself without posting a request to Articles for creation.

If you would like to help us improve this process, please consider leaving us some feedback.

Thanks again, and happy editing!

Sulfurboy (talk) 07:26, 31 May 2020 (UTC)[reply]


[edit]

An automated process has detected that when you recently edited Kitch-iti-kipi, you added a link pointing to the disambiguation page Spring (check to confirm | fix with Dab solver).

(Opt-out instructions.) --DPL bot (talk) 06:20, 15 July 2020 (UTC)[reply]


Otsego Lake (New York)

[edit]

Do you think Otsego Lake is ready for B-Class? 420Traveler (talk) 18:02, 22 July 2020 (UTC)[reply]


New Wikipedia Library Collections Now Available (September 2020)

[edit]


Hello Wikimedians!

The TWL owl says sign up today!

The Wikipedia Library is announcing new free, full-access, accounts to reliable sources as part of our research access program. You can sign up for new accounts and research materials on the Library Card platform:

Many other partnerships are listed on our partners page, including Adam Matthew, EBSCO, Gale and JSTOR.

A significant portion of our collection now no longer requires individual applications to access! Read more in our recent blog post.

Do better research and help expand the use of high quality references across Wikipedia projects!
--The Wikipedia Library Team 09:49, 3 September 2020 (UTC)

This message was delivered via the Global Mass Message tool to The Wikipedia Library Global Delivery List.

Fish River (Maine)

[edit]

Thank you adding the pushpin maps to the Maine lakes articles. I do not know how to format these maps, but I think there may be an error in the locations of the pushpins for the three lakes in subject article. It appears as if all three pushpins are located at the mouth of the river, while the lakes are actually distributed along the length of the river. Can you check my observation? Thewellman (talk) 03:57, 19 September 2020 (UTC)[reply]

@Thewellman: Ah, I see what you mean, you're right. I didn't check if the body of water infoboxes had a coord parameter value for each lake's infobox, seems they defaulted to the coord template for the article. I remember thinking it was weird, but didn't double check as I assumed it was due to the zoom of the map. To correct the lake locations, add the coordinates parameter per lake in each infobox to the inbox body of water coordinates parameter {{coord|DD|MM|SS|N|DD|MM|SS|W|region:ZZ_type:waterbody|display =inline,title}} - Coord Template. Good thing you flagged this as it appears that the category Category: Articles using infobox body of water without pushpin map, but I'm not seeing any three of the lakes there so this means that category isn't correctly flagging these infoboxes to be missing the parameter. I've noted this on the infobox talk page so it can be addressed to not miss this in the future. Wolfgang8741 says: If not you, then who? (talk) 12:54, 20 September 2020 (UTC)[reply]


A barnstar for you!

[edit]
The Original Barnstar
Thank you for adding pushpin maps to so many lake articles. Magnolia677 (talk) 10:01, 25 September 2020 (UTC)[reply]

Confusing edit

[edit]

Why did you do this? ―Justin (koavf)❤T☮C☺M☯ 16:37, 30 October 2020 (UTC)[reply]

@Koavf: Thanks for pointing this out. I was using rater and forgot the category class doesn't need to be explicit, but it also doesn't hurt to leave the category class since it still is technically correct and handled. I stopped once I remembered it wasn't needed while working through the WikiProject Rivers tagging. Wolfgang8741 says: If not you, then who? (talk) 17:36, 30 October 2020 (UTC)[reply]
Wolfgang8741, Good deal. Thanks for writing. ―Justin (koavf)❤T☮C☺M☯ 17:40, 30 October 2020 (UTC)[reply]


Lake class

[edit]

Do you think Otsego Lake (New York) is ready to be upgraded to B-Class? 420Traveler (talk) 18:40, 4 November 2020 (UTC)[reply]

@420Traveler: Yes, it is at least a B-Class, I set that assessment. There are a few things that could be touched up for example: Three Mile Point is a public swimming beach the linked item is not a beach, but a cape so would it make more sense to say "Three Mile Point contains a public swimming beach". The Infobox doesn't apply alt text to the image nor map. With those addressed this might be worth trying a nomination for GA. I haven't been through that process before, but it seems to me like a good article candidate. Also sorry I missed the earlier request, was bad timing for me to respond. Wolfgang8741 says: If not you, then who? (talk) 20:28, 4 November 2020 (UTC)[reply]
@Wolfgang8741: I will fix those things. And I was thinking the same about being a good article. Im going to add a few more things then nominate it. 420Traveler (talk) 21:04, 4 November 2020 (UTC)[reply]


ArbCom 2020 Elections voter message

[edit]
Hello! Voting in the 2020 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 7 December 2020. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2020 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 02:24, 24 November 2020 (UTC)[reply]


Article tagging

[edit]

Hello, I think that you have incorrectly tagged articles such as this one for Lincolnshire rather than Norfolk. I have changed this one but there appears to be several others in the same situation. Could you have a look through your last tagging edits? Many thanks. Keith D (talk) 14:26, 4 December 2020 (UTC)[reply]

@Keith D: Ah, you are correct, thank you for alerting me to this error. I'll go back over the Norfolk articles and make the corrections. Wolfgang8741 says: If not you, then who? (talk) 15:08, 4 December 2020 (UTC)[reply]
I believe I've now corrected the remaining incorrectly tagged articles. I found four other incorrectly tagged Lincolnshire rather than East Anglia and changed the WikiProject accordingly. Wolfgang8741 says: If not you, then who? (talk) 15:17, 4 December 2020 (UTC)[reply]
Thanks for correcting. I will look at the project changes on update listing tomorrow. Keith D (talk) 22:30, 4 December 2020 (UTC)[reply]

Nomination for deletion of Template:Michigan waters

[edit]

Template:Michigan waters has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. --TheImaCow (talk) 16:38, 5 December 2020 (UTC)[reply]

Wikiproject Rivers template "Natural history"

[edit]

Hi thanks for inviting me to Wikiproject Rivers, I think the template subsection heading "Natural History" is too limiting, as this is a rather narrow focus pertaining to naming and educating on important plants and animals. I would prefer Ecology and Conservation, as Ecology is the animals/plants plus their surroundings or habitat that affects them, more than just the narrower Natural History focus on plants and animals. For example, mentioning the environs as they pertain to the plant/animal community for example, "broad adjacent floodplains" or "high spring flows from snowmelt" would be included under Ecology but not Natural History. Secondly, Conservation would include the actions being taken to improve the environment which might include pollutants and their clean-up or the environmental impact of dam removal, not just the animal/plants therein. LMK your thoughts.Schmiebel (talk) 00:11, 6 December 2020 (UTC)Schmiebel[reply]


New Wikipedia Library Collections Available Now (February 2021)

[edit]

Hello Wikimedians!

The TWL owl says sign up today!

The Wikipedia Library is announcing new free, full-access, accounts to reliable sources as part of our research access program. You can sign up to access research materials on the Library Card platform:

  • Taxmann – Taxation and law database
  • PNAS – Official journal of the National Academy of Sciences
  • EBSCO – New Arabic and Spanish language databases added

We have a wide array of other collections available, and a significant number now no longer require individual applications to access! Read more in our blog post.

Do better research and help expand the use of high quality references across Wikipedia projects!

This message was delivered via the Global Mass Message tool to The Wikipedia Library Global Delivery List.

--12:57, 1 February 2021 (UTC)


New Wikipedia Library collections and design update (August 2021)

[edit]

Hello Wikimedians!

The TWL OWL says log in today!

The Wikipedia Library is pleased to announce the addition of new collections, alongside a new interface design. New collections include:

Additionally, De Gruyter and Nomos have been centralised from their previous on-wiki signup location on the German Wikipedia. Many other collections are freely available by simply logging in to The Wikipedia Library with your Wikimedia login!

We are also excited to announce that the first version of a new design for My Library was deployed this week. We will be iterating on this design with more features over the coming weeks. Read more on the project page on Meta.

Lastly, an Echo notification will begin rolling out soon to notify eligible editors about the library (T132084). If you can translate the notification please do so at TranslateWiki!

--The Wikipedia Library Team 13:23, 11 August 2021 (UTC)

This message was delivered via the Global Mass Message tool to The Wikipedia Library Global Delivery List.

ArbCom 2021 Elections voter message

[edit]
Hello! Voting in the 2021 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 6 December 2021. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2021 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:21, 23 November 2021 (UTC)[reply]

[edit]

An automated process has detected that when you recently edited Jim Boyd (politician), you added a link pointing to the disambiguation page Florida House.

(Opt-out instructions.) --DPL bot (talk) 06:06, 18 January 2022 (UTC)[reply]

fixed Wolfgang8741 says: If not you, then who? (talk) 23:01, 18 January 2022 (UTC)[reply]

Proposed deletion of List of mayors of Alliance, Ohio

[edit]
Notice

The article List of mayors of Alliance, Ohio has been proposed for deletion because of the following concern:

Fails WP:NLIST, WP:INDISCRIMINATE

While all constructive contributions to Wikipedia are appreciated, pages may be deleted for any of several reasons.

You may prevent the proposed deletion by removing the {{proposed deletion/dated}} notice, but please explain why in your edit summary or on the article's talk page.

Please consider improving the page to address the issues raised. Removing {{proposed deletion/dated}} will stop the proposed deletion process, but other deletion processes exist. In particular, the speedy deletion process can result in deletion without discussion, and articles for deletion allows discussion to reach consensus for deletion. AusLondonder (talk) 14:31, 25 April 2022 (UTC)[reply]

New Wikipedia Library Collections Available Now - April 2022

[edit]

Hello Wikimedians!

The TWL owl says sign up today!

The Wikipedia Library has free access to new paywalled reliable sources. You can these and dozens more collections at https://wikipedialibrary.wmflabs.org/:

  • Wiley – journals, books, and research resources, covering life, health, social, and physical sciences
  • OECD – OECD iLibrary, Data, and Multimedia​​ published by the Organisation for Economic Cooperation and Development
  • SPIE Digital Library – journals and eBooks on optics and photonics applied research

Many other sources are freely available for experienced editors, including collections which recently became accessible to all eligible editors: Cambridge University Press, BMJ, AAAS, Érudit and more.

Do better research and help expand the use of high quality references across Wikipedia projects: log in today!
--The Wikipedia Library Team 13:16, 26 April 2022 (UTC)

This message was delivered via the Global Mass Message tool to The Wikipedia Library Global Delivery List.

Wikidata weekly summary #518

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • The new "mul" term language code is now available on Test Wikidata
    • Lexicographical data: We are finishing up the information box that should help new users understand quickly what lexicographical data is. We also added the help text to encourage people to check if the Lexeme already exists before creating one.
    • REST API: We started working on the REST routes to get all statements of an Item and retrieve a single statement from an Item.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #519

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Closed request for permissions/Bot:
      • PangolinBot. Task/s: Automatically replace one property value with another (Approved)
  • Development
    • REST API: We are continuing to implement the REST routes to get all statements of an Item and retrieve a single statement from an Item (phab:T305988, phab:T307087, phab:T307088)
    • Lexicographical data: We are finishing the version of the page for browsers without JavaScript support (phab:T298160). We started working on the feature to pre-fill the input fields by URL parameter (phab:T298154). And we started working on better suggestions for lexical categories so commonly-used ones can more easily be added to avoid mistakes (phab:T298150).
    • We fixed an issue with recently added new language codes not being usable for Lexemes and not being sorted correctly on Special:NewItem (phab:T277836).

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

This Month in GLAM: April 2022

[edit]


Headlines
  • Australia report: Growing the record of Australian Music
  • Belgium report: About African Pagnes and Belgian music
  • Brazil report: Brazil wins the first place in WLM 2021
  • France report: French GLAM meeting
  • Italy report: Work with GLAMs on Wikisourse and Wikimedia Commons
  • Mexico report: GLAM professionals add an image and become Wikipedians; Edificio Carolino Edit-a-thon
  • New Zealand report: People in Paleontology, Digikult, and copyright term extension for New Zealand
  • Nigeria report: Wikidata for Nigerian Novelist and Novel
  • Poland report: Wikiresidence in progress and workshop Evolution in GLAM in Poland
  • Serbia report: Important activities within the GLAM
  • Sweden report: Training at the National Archives of Sweden; Training at the Stockholm City Museum; Training at the Swedish National Museum of Science and Technology; Improved images from Swedish Performing Arts Agency
  • Switzerland report: Wikidata Coffee Breaks
  • UK report: Khalili Collections
  • Uruguay report: Wikimedistas de Uruguay report
  • USA report: WVU Libraries; Earth Day-2022-SWC; Wiki-Gap
  • AvoinGLAM report: Open Access vs NFT, GLAM School, Saami language, family trees
  • Content Partnerships Hub report: Enter our logo competition; IGO/INGO; Needs assessments research results; Wrapping up some ISA-things
  • WMF GLAM report: 1Lib1Ref, Image Description Week, Commons calls, and the Add an image events
  • Calendar: May's GLAM events
Read this edition in full • Single-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Wikidata weekly summary #520

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
  • Development

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #521

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming:
      • 6 and 8 June: Scholia hackathon with focus on software-related visualizations and curation workflows
      • 29 July 2022: The submission deadline for the Wikidata Workshop 2022 that will be co-located with the 21st International Conference on Semantic Web (ISWC 2022).
    • Ongoing:
  • Tool of the week
    • LOD4Culture is a web application for exploring world-wide cultural heritage.
  • Other Noteworthy Stuff
    • UNLOCK, a Wikimedia Deutschland program, is looking for your project ideas. These could be the development of tools building on top of Wikidata's data, of applications for social and public good or related to civic tech. Apply until May 29th, 2022!
    • Job opening: Community Communications Manager - Wikibase at Wikimedia Deutschland.
  • Development
    • Wikibase REST API: Initial implementation of a route providing all statements of an item (phab:T305988), an a route to retrieve a single statement (phab:T307087) completed.
    • First batch of WBstack.com accounts successfully migrated to Wikibase.cloud. You can keep track of our progress on this phabricator ticket phab:T303852.
    • Lexicographical data: We updated the input placeholders on the new version of the NewLexeme special page (T302877, T307443). We finished the feature to prefill the inputs from URL parameters if present (T298154) and to suggest common lexical category items (T298150). We are working on some accessibility improvements (T303806, T290733, T305359) and improving validation / error messages (T305854).

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #522

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • Want to know more about Abstract Wikipedia & Wikifunctions? You can now subscribe to the weekly newsletter and get a friendly reminder every time a new issue is published!
    • Radioactivity map: Mind map about radioactive radiation built by importing from Wikidata with InfoRapid KnowledgeBase Builder
  • Development
    • Wikibase REST API: Expanding statement reading routes (a single statement specified by ID (phab:T307087), all statements of an item (phab:T305988), a single statement for a specific item (phab:T307088))
    • Fetch revision metadata and entity data separately in all use cases (phab:T307915, decision)
    • Update installation instructions in WikibaseLexeme.git readme file (phab:T306008)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #523

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
  • Development
    • Lexicographical data: We finished work on input validation and displaying errors for faulty input (phab:T305854) and are continuing work on accessibility improvements such as screen reader support and keyboard navigation (phab:T290733, phab:T30535).
    • REST API: We finished implementation of conditional statement requests (phab:T307031, phab:T307032) and published the OpenAPI specification document (still subject to change as the API develops). We started working on the write part of the API with adding statements to an Item (phab:T306667).

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

This Month in GLAM: May 2022

[edit]


Headlines
  • Albania report: Summer of Wikivoyage 2022
  • Argentina report: Face-to-face and virtual events on May
  • Australia report: Over 1000 references added in Australia and Aotearoa New Zealand for #1Lib1Ref
  • Belgium report: New Wikidata Property
  • Brazil report: Wiki Loves Espírito Santo is a sucess
  • Estonia report: From university to library
  • Finland report: Photowalks in Southern Finland, spring 2022
  • France report: International Museum Day 2022
  • India report: Digitization of Tibetan Buddhist canons, The International Museum Day 2022 Wikidata Competition
  • Italy report: May in and for museums
  • Kosovo report: Cooperation with the National Gallery of Kosova and Summer of Wikivoyage 2022
  • Malaysia report: WikiGap Malaysia 2022 @ Kuala Lumpur Library
  • New Zealand report: Pacific Arts Aotearoa Wikiproject, Auckland Museum's Exploratory Study and Report back on #1Lib1Ref
  • Poland report: Wikipedian in residence in the National Museum in Cracow; Training at the Wawel Royal Castle National Art Collection; How can we make GLAM’s digital resources more reusable in education?; The International Museum Day 2022 Wikidata Competition
  • Serbia report: New GLAM brochure and Wikilive 2022
  • Sweden report: Rembrandt and others – drawings from the Nationalmuseum in Stockholm; Stockholm Museum of Women’s History; The map book of Heinrich Thome; Sörmland Museum; Wikidata competition – International Museum Day 2022
  • Switzerland report: Diversity in GLAM Program
  • UK report: Khalili Collections
  • Uruguay report: Wikimedistas de Uruguay report: 1bib1ref, Museum of Natural History, and more!
  • USA report: Hackathons and Edit-a-thons
  • Content Partnerships Hub report: International Energy Agency share their knowledge and graphics on Wikipedia
  • Structured Data on Wikimedia Commons report: Uploading files to Wikimedia Commons with OpenRefine: looking for test uploads!
  • WMF GLAM report: Results from 1Lib1Ref May 2022
  • Calendar: June's GLAM events
Read this edition in full • Single-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Wikidata weekly summary #524

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call June 14, 2022: Will Kent (Wikidata Program Manager at Wiki Education) and Rosie Stephenson-Goodknight (Wikimedia Foundation Trustee; Visiting Scholar at Northeastern University; co-founder of Wiki Women in Red) will present on Leveraging Wikidata for Wikipedia – running a multi-language wiki project and the role of Wikidata in improving Wikipedia's content gender gap. Agenda
      • Live editing session on Twitch, in French, by Vigneron, June 14 at 19:00 CEST (UTC+2)
    • Ongoing
    • Past
  • Tool of the week
    • ExtraInterwiki. Some language links will never show up in your favorite Wikipedia, those who don’t have a corresponding article in this Wikipedia. This new tool aims to give them more visibility by searching topics closed to the one on an article with no article on your wiki.
  • Development
    • Fixed a bug where Item IDs where shown instead of the label after selecting an Item in an Item selector (phab:T306214)
    • Lexicographical data: finished accessibility improvement for the new Special:New Lexeme page (phab:T290733), improving error messages for the new page (phab:T310134) and worked on a new search profile to make selecting languages easier (phab:T307869)
    • REST API: continued work on creating statements (phab:T306667)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #425

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Lexicographical data:
      • Enabled Lua access to Lexemes for all Wikimedia projects
      • Continued work on improving the language search for Lexeme languages on the new Special:NewLexeme page (phab:T307869)
      • Improving the accessibility of a design system component and the new Special:NewLexeme page (phab:T290733)
      • Making it easier to understand what to do when the spelling variant isn't available on the new Special:NewLexeme page (phab:T298146)
    • REST API: Continuing work on making it possible to add a statement to an Item

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #426

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • New requests for permissions/Bot:
      • William Avery Bot 7. Task/s: Merge multiple references on the same claim citing Accademia delle Scienze di Torino.
  • Tool of the week
    • IsisCB Explore - is a research tool for the history of science whose books and subjects use imagery from Wikidata.
  • Other Noteworthy Stuff
    • Template Item documentation now includes a query to the corresponding lexemes. This is an attempt to make navigation between lexemes and items easier. For the record, Item documentation is available in the header of the talk page for each item.
  • Development
    • Lexicographical data: We are wrapping up the coding on the new Special:NewLexeme page. Testing and rolll-out will follow soon. We are still working on making it easier to find languages in the language selector on the Special:NewLexeme page. (phab:T307869)
    • REST API: We are continuing to code on the ability to create statements on an Item (phab:T306667)
    • Investigating an issue with labels not being shown after merges (phab:T309445)
    • Preparation for upcoming work: We are planning the next work on the Mismatch Finder to address feedback we have received so far as well as EntitySchemas to make them more integrated with other areas of Wikidata.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #522

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • New requests for permissions/Bot:
      • ListedBuildingsUKBot. Task/s: Add wikidata site links to appropriate wiki commons category pages for listed buildings with matching ID numbers. I've identified about 1000 entities that can be updated. e.g. [2] should have a wiki commons link to [3] since they both refer to [4].
  • Development
    • Lexicographical data:
      • We have finished most of the development on the new Special:NewLexeme page. You can try it at https://wikidata.beta.wmflabs.org/wiki/Special:NewLexemeAlpha. We will make this available on Wikidata for testing with real-world data on July 14th.
      • We are continuing to work on the new search profile for languages to make setting the language of a new Lexeme easier (phab:T307869)
    • REST API: We are putting finishing touches on the first version of the API route to add statements to an Item. It is still lacking support for automated edit summaries.
    • We are working on word-level diffs to make it easier to see what changed in an edit (phab:T303317)
    • We are investigating the issue of labels not being shown after some merges (phab:T309445)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


This Month in GLAM: June 2022

[edit]


Headlines
  • Albania report: CEE Spring 2022 in Albania and Kosovo
  • Argentina report: In the middle of new projects
  • Australia report: A celebration, a commitment, an edit-a-thon: Know My Name returns for 2022
  • Belgium report: Heritage and Wikimedian in Residence
  • Brazil report: FIRST WikiCon Brazil & Three States of GLAM
  • Croatia report: Network(ing) effect(s)
  • France report: French open content report promotion
  • Italy report: Opening and closing projects in June
  • Kosovo report: Edit-a-thon with Kino Lumbardhi; DokuTech; CEE Spring 2022 in Albania and Kosovo
  • New Zealand report: West Coast Wikipedian at Large and Auckland Museum updates
  • Poland report: Wikipedian in residence in the National Museum in Cracow; The next online meeting within the cycle of monthly editing GLAM meetings; Steps to communicate GLAM partnerships better and involve the Wikimedian community
  • Sweden report: 100 000 memories from the Nordic Museum; Report from the Swedish National Archives
  • Switzerland report: Diversity in GLAM Program
  • UK report: Featured images and cultural diversity
  • USA report: Fifty Women Sculptors; Juneteenth Edit-a-thon; Juneteenth Photobooths 2022; Wiknic June 2022; New York Botanical Garden June 2022; LGBT Pride Month
  • Structured Data on Wikimedia Commons report: Structured data on Commons editing now possible with OpenRefine 3.6; file uploading with 3.7
  • Calendar: July's GLAM events
Read this edition in full • Single-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Wikidata weekly summary #528

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming:
      • The next Wikidata+Wikibase office hours will take place on Wednesday, July 27th 2022 at 17:00 UTC (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call July 12, 2022: Houcemeddine Turki will speak on "Enriching and Validating Wikidata from Large Bibliographic Databases." This call will be part of the 2022 LD4 Conference on Linked Data, “Linking Global Knowledge.” While you can attend the call directly via the links below without registering for the conference, we encourage everyone to check out the full conference program and all the excellent sessions on Sched at Agenda
      • 7/30 OpenStreetMap x Wikidata @ COSCUP 2022
      • 2022 LD4 Conference on Linked data. July 11th through July 15th, 2022
    • Ongoing
    • Past:
  • Development
    • Data Quality Days!
    • Making plans for improving EntitySchemas and integrate them more into editing and maintenance workflows
    • Implemented word-level diffs of labels, descriptions, aliases and sitelinks (phab:T303317)
    • Continuing the investigation about labels not being shown after some merges (phab:T309445)
    • Lexicographical data:
      • Continuing work on making it easier to pick the right language for a new Lexeme (phab:T298140)
      • Fixing a bug where `[object Object]` was shown in the gramatical feature field (phab:T239208)
      • Fixing a number of places where labels for redirected Items were not shown even though the redirect target had labels (phab:T305032)
    • REST API:
      • Finished the first version of the API route for creating statements on an Item (excluding autosummaries so far)
      • Started work on the API route for removing a statement from an Item

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #529

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming
      • The next Wikidata+Wikibase office hours will take place on Wednesday, July 27th 2022 at 17:00 UTC (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
      • Next Linked Data for Libraries Wikidata Working Hour July 18, 2022: Working with diverse children's book metadata. The second Wikidata Working Hour in the series will cover reconciliation in OpenRefine, so we can identify which authors from our spreadsheet of children's book metadata already exist and/or need to be created in Wikidata. You are, as always, welcome to bring your own data to work on. Event page
      • Assessing the Quality of Sources in Wikidata Across Languages - Wikimedia Research Showcase, Wednesday, July 20, at 9:30 AM PST/16:30 UTC
      • Mark your calendars for the Wikimania Hackathon! The free, online, public event will take place from 16- 22 UTC August 12 and 12-17 UTC August 13, and include a final showcase on August 14.
    • Ongoing
    • Past
  • Development
    • Lexicographical data:
    • REST API: Continued working on the API route to replace or remove a statement of an Item
    • We are making Wikibase resolve redirects when showing Item labels and descriptions in a lot more places; notably, this includes the wbsearchentities API. (phab:T312223)
    • Mismatch Finder: We are discussing options for how to improve its handling of dates, specifically calendar model and precision.
    • EntitySchemas: We are trying to figure out how to best technically go about implementing some of the most-needed features for version 2.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #530

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming:
      • The next Wikidata+Wikibase office hours will take place on Wednesday, July 27th 2022 at 17:00 UTC (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
      • [Small wiki toolkits] [Upcoming bots & scripts workshop. "How to maintain bots" is coming up on Friday, July 29th, 16:00 UTC
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call July 26, 2022: Clair Kronk, Crystal Clements, and Alex Jung will be providing an update to Wikidata/gender discussions from the February 8 call with a focus on pronouns. Clair will introduce us to LGBTdb, a Wikibase instance created for and by LGBTQIA+ people from which we draw insight in Wikidata-related discussions. We also hope to discuss current pain points and share action items for future collaboration. Input from community members who are familiar with lexicographical data would be greatly appreciated. Agenda
      • Wikimedia Indonesia Wikidata meetup. 1300 WIB, July 30, 2022.
    • Ongoing:
      • Weekly Lexemes Challenge #51, Plants
  • Tool of the week
    • User:Magnus Manske/referee.js - is a userscript that automatically checks external IDs and URLs of a Wikidata item as potential references, and adds them with a single click.
  • Development
    • Lexicographical data: We went over all the feedback we received for teh testing of the new Special:NewLexeme page and started addressing it and fixing the uncovered issues. One issue already fixed is a bug that prevented it from working on mobile view. (phab:T313116)
    • Mismatch Finder: investigated how we can make it work for mismatches in qualifiers instead of the main statement (phab:T313467)
    • REST API: Continued working on making it possible to replace and remove a statement of an Item
    • We enabled the profile parameter to the wbsearchentities API on Test Wikidata (phab:T307869)
    • We continued making Wikibase resolve redirects when showing Item labels and descriptions in more places (phab:T312223)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #531

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #532

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming
      • Wikimania 2022, August 11 to 14, online event. The Hackathon will take place August 12-14. On this page you can find a summary of sessions and community gatherings related to Wikidata and Wikibase.
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call August 9, 2022: Pieter Vander Vennet on MapComplete, a thematic OpenStreetMap viewer and editor which uses species, language, and image data from Wikidata. Agenda.
      • The Wikimania Hackathon starts next Friday, August 16-22! There are still lots of spots in the schedule to add your Wikidata related sessions or project ideas (anyone can present a session)
    • Ongoing
      • Wikimedia Indonesia's Wikidata edit-a-thon (datathon) for the 77th anniversary of the Indnesian Independence Day started on 5th August and will be held until 12th August. Participants are instructed to edit items containing the statement country of origin (P495): Indonesia (Q252).
      • Toolhub is a catalog of 1500+ tools used every day in a wide variety of workflows across many Wiki projects. We are currently improving the search functionality and need your input – whether you are already familiar with Toolhub or not. Please take 5-10 minutes to leave feedback.
    • Ongoing
      • Weekly Lexemes Challenge #53, Sheep
    • Past
      • First online meet-up fully organized by volunteers of the Indonesian Wikidata Community has been held on 30th July where we edited items on Indonesian ethnic groups.
  • Tool of the week
    • Wiki tools - adds dozens of Wikipedia and Wikidata functions to your Google sheets.
  • Development
    • Lexicographical data:
      • Continuing to address feedback from the testing (e.g. phab:T312292, phab:T313113, phab:T313466)
      • We have pushed back replacing Special:NewLexeme with the new Special:NewLexemeAlpha a bit to address more of the testing feedback.
    • Continuing to tackle allowing sitelinks to redirects under some circumstances (phab:T278962)
    • REST API:
      • Finishing up the endpoints for removing and replacing statements and adding authentication and authorization to them
      • Looking into feedback from first testing

You can see all open tickets related to Wikidata here. If you want to help out, you can also have a look at the tasks needing a volunteer.

This Month in GLAM: July 2022

[edit]


Headlines
Read this edition in full • Single-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Wikidata weekly summary #533

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship:
      • Estopedist1 (RfP scheduled to end after 21 August 2022 12:36 UTC)
  • Events
    • Upcoming:
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group Wikidata Working Hour August 15, 2022: Fourth session of our summer/fall project working with diverse children's book metadata. We'll be covering manually creating publisher items: showing how to create items, add statements to items, add references, and use gadgets. You are, as always, welcome to bring your own data to work on. All sessions in our project series will be recorded for those who cannot attend. Links will be added to the event page when available. Event page
    • Ongoing:
  • Tool of the week
    • KnolCase is a case-based knowledge management tool for gathering information about subjects of interest and organizing these into case files.
  • Development
    • Took part in Wikimania and the Wikimania hackathon
    • Continuing work on making it possible to add sitelinks to redirects under some special conditions (phab:T278962)
    • Lexicographical data: continuing to address the feedback from testing
    • REST API:

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #534

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • List of created Wikidata items - a tool which combines Xtools pages created API with Wikidata API to get the list of items created by a user with their label.
  • Development
    • Lexicographical data: continuing to address feedback from testing. We are almost done now.
    • REST API: continued investigating the use of PATCH and JSON Patch and worked on a proof-of-concept
    • Birthday planning and prepping is in full swing

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #535

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
  • Development
    • REST API: working on the ability to change existing statements on an Item (phab:T306934)
    • Lexicographical data: Finishing up the remaining pieces of the new Special:NewLexeme page based on the testing feedback (subtickets of phab:T307866)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #536

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • New requests for permissions/Bot:
      • MsynBot 9. Task/s: manage existing GND ID (P227) identifier claims
      • DL2204bot. Task/s: Add ExternalID values, edit/create items, add/edit lexemes, senses, forms
  • Events
    • Upcoming:
      • Wikidata's 10th birthday is coming up soon: you can contribute to the celebration video, prepare an event or a birthday present.
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call September 6, 2022: Dominic Byrd-McDevitt will talk about the Digital Public Library's Wikimedia program, an effort to provide national leadership around access and discoverability of digital collections by leveraging Wikipedia and its sister projects. 2 years ago, DPLA launched a digital asset pipeline to enable participating institutions in the DPLA network to share their collections with Wikimedia Commons. DPLA is continuing to innovate by taking advantage of Wikidata entities and Structured Data on Commons to continually synchronize data and improve discoverability. We'll discuss issues around large datasets, aggregation, reconciliation, and other challenges DPLA has faced. Agenda
      • Talk to the Search Platform / Query Service Team—September 7th, 2022 Date: Wednesday, September 7th, 2022. Time: 15:00-16:00 UTC / 08:00 PDT / 11:00 EDT / 17:00 CEST / 19:00 GST
    • Ongoing:
  • Development
    • REST API:
      • We are continuing to work on the PATCH endpoint to make it possible to edit existing statements (phab:T306934)
      • We started the security review process for one of the libraries we are using. Until that is finished this part of the REST API can unfortunately not be tested on beta Wikidata. (phab:T316523)
      • For anything but the PATCH endpoint, you can follow along development on beta Wikidata and see the latest docs. More details at Wikidata:REST API feedback round.
    • Lexicographical data: Continued addressing remaining issues found during testing (phab:T314064, phab:T312633, phab:T312652)
    • Continuing work on supporting sitelinks to redirects under some special conditions (phab:T278962)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

View it! September update

[edit]
View it! Tool
View it! Tool update Sept. 2022


Thank you for signing up for View it! updates!

As a reminder, you can view details about how to install the View it! user script or use the Toolforge tool on our meta page. Please use the talk page there to contact the team!

August happenings

  • We held two community conversations, one in person at Wikimania 2022/Pittsburgh and one virtual during a Wikimedians in Residence Exchange Network meeting.
    • During both meetings we discussed final design of View it!, and results refinement and querying. Check the August updates for notes from both meetings.
  • View it! is working across all Wikimedia projects, and we are currently working on multi-lingual functionality.

Coming in September

  • Currently plan to focus development on multilingialism, on-wiki/editor features for the user script, and extending the search functions on Toolforge.
  • We are continuing to respond to user feedback and finalizing design.

Action to take

  • Install Beta script and see how it can used to add new images to articles.
  • All editors are invited to share the tool with their local wiki communities, or incorporate it into relevant local templates, such as infoboxes. If you do so, please let us know about it, so we can ensure backwards compatibility for that use case as we continue development!
  • Feel free to leave comments on our Discussion page

-- JamieF (talk) 19:57, 11 September 2022 (UTC)[reply]

Wikidata weekly summary #537

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group Wikidata Working Hour September 12, 2022: Sixth session of our summer/fall project working with diverse children's book metadata. We'll be creating items for books (works and editions) in Wikidata. You are, as always, welcome to bring your own data to work on. All sessions in our project series will be recorded for those who cannot attend. Links will be added to the event page when available. Wikidata Working Hour Event page
      • Webinar: Querying Wikidata: All the Knowledge in the World. Sep 15, 2022 5:00 PM Central European Summer Time
    • Ongoing:
      • Weekly Lexemes Challenge #58, City
  • Tool of the week
    • View it! Tool - (based on Wikidata) allows viewing a multitude of images that depicts a given topic on Wikipedia.
  • Development
    • REST API: Continued work on the endpoint for changing a statement (phab:T306934)
    • Lexicographical data: Made sure that the new Lexeme creation page also is shown in older browsers (phab:T311157), which was one of the last remaining issues before we can switch out the existing page (phab:T307866)
    • Continued work on enabling sitelinks for redirects under certain conditions (phab:T278962)
    • Spend a few days with people from Wikimedia Indonesia to discuss our partnership

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


This Month in GLAM: August 2022

[edit]


Headlines
Read this edition in full • Single-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Wikidata weekly summary #538

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • New requests for permissions/Bot:
      • بوٹ دا عثمان
        • Task/s:
          • Dual script support for Punjabi Wikidata labels and descriptions in Gurmukhi (pa) and Shahmukhi (pnb), taking a conservative approach (only making "obvious" transliterations).
          • Addition of labels and descriptions entirely consistent of information which can be inferred from other language labels (again, only for "obvious" cases).
  • Tool of the week
    • WD-FIST is a userscript that checks Wikipedia pages for available images if the item doesn't have one (automatically or manually via sidebar link).
  • Development
    • REST API:
      • Finished the endpoint for editing statements (phab:T306934)
      • Working on automated edit summaries (phab:T312811)
      • Making small modifications to the response format for statements (phab:T317866)
    • Lexicographical data:
      • Special:NewLexemeAlpha now uses the new search profile for languages, which makes it easier to select a language Item for the language of the new Lexeme (phab:T312853)
      • Finished the work on making sure that the example Lexeme falls back to other locally defined examples for languages other than English instead of the pre-set example Lexeme (phab:T313599)
      • Working on making sure that only *-x-Q123, not *-x-q123, can be used as a Lexeme language code (phab:T317863)
    • Sitelinks to Redirects are now available for testing on test.wikidata.org
    • Improved the wrapping and selection behavior of aliases in the header of an Item (phab:T315991) Thanks Fomafix for the patch!
    • Improved the translations of the Lexeme and EntitySchema namespaces (phab:T316770) Thanks to Amire80 for the patch!
    • Started supporting Codex work for some Wikidata-specific work needed in the new design system (phab:T306932)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #539

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • 🧵 Discussions
    • New requests for permissions/Bot:
      • JhsBot 6
        • Task/s: Add sitelinks to newly created wikis after wikis have been created and exported from the Wikimedia Incubator.
  • 🎊 Events
    • Upcoming
      • Live editing session on Twitch, in French, by Vigneron, September 26 at 18:00 CEST (UTC+2)
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group Wikidata Working Hour September 30, 2022: the seventh Wikidata Working Hour in the series will be a review session of creating contributor and publisher items in Wikidata. The primary goal of this session is to generate as many contributor and publisher items as we can in advance of the two following sessions which have to do with batch editing -- we want enough to make a good batch! We will review how to add items, but then reserve the bulk of the session for open editing, kind of like a mini-editathon! Naturally, participants can ask questions and share thoughts at any point during the editing! You are, as always, welcome to bring your own data to work on. All sessions in the project series will be recorded. Links will be added when available. Event page
    • Ongoing
      • Weekly Lexemes Challenge #60, Cows
  • 🧰 Tool of the week
    • User:Bovlb/notability.js is a userscript that adds a small notability indicator to the top right of an item showing how well the item satisfies the three notability criteria. Left to right, the three columns indicate sitelinks, identifiers and references, and structural need.
  • 🧑🏿‍💻 Development
    • Continuing work on making the mul language code work.
    • Continuing work on making Special:UnconnectedPages scale (phab:T300770)
    • Ensuring that Lexeme language codes using mis use uppercase Q consistently in the Item IDs (phab:T317863)
    • REST API: Working on automated edit summaries (phab:T312811)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Call for presentations for WCNA 2022 and Mapping USA

[edit]
Call for presentations for WikiConference North America 2022 and OpenStreetMap US's Mapping USA

This is a call for presentations by EOD, Sunday, October 15, for WikiConference North America (Nov 11-13), held jointly with OpenStreetMap US's Mapping USA. We encourage you to please submit your Wikipedia and Wikimedia proposals at Wikiconference:2022/Submissions or OpenStreetMap US proposals at Call for Proposals: WikiConference North America + Mapping USA. We are sending this mass message to you because we deduced that you may be in North America and interested in maps in Wikimedia or Wikipedia, OpenStreetMap, or OpenHistoricalMaps. We are looking for lightning talks in particular on Friday, Nov 11. Some suggestions:

  • Cultural similarities and differences, for instance OpenStreetMap and Wikivoyage (map and describe what you know) versus Wikipedia (verify with citations)
  • Type of licensing for each project and how they differ: OpenStreetMap, Commons, Wikidata, and Wikipedia
  • The flow of information from one project into another, and how maps are generated
  • How OpenHistoricalMap works and possible interactions with Wikimedia projects
  • Your ideas!

MediaWiki message delivery (talk) 23:31, 1 October 2022 (UTC)[reply]

MaggieMaps CC-By-SA
MaggieMaps CC-By-SA

Wikidata weekly summary #540

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • 🎊 Events
    • Upcoming
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call
        • October 4, 2022: Lana Soglasnova and Roman Tashlitskyy will talk about their preliminary work in creating and editing items for Slavic people and some of the complications involved in this work, especially around transliterating names in various languages. Agenda
        • Wikibase Working Hour! 25 October 2022, 2pm Eastern (Time zone converter) Amy Ruskin of Northeastern University Library, will speak on the topic of Wikidata vs. custom Wikibases: Community history case studies, Boston’s Chinatown. The Boston Research Center (BRC) is a digital community history and archives lab based in the Northeastern University Library. One of our current projects involves taking an inventory of historical materials related to Boston’s Chinatown, and we have been using Wikibase to store multilingual data about the linked collections, organizations, and people. In this presentation, we will discuss our experience of getting started with a custom Wikibase and give an overview of our progress so far on the Chinatown Collections project. Amy Ruskin is the Data Engineer in the Digital Scholarship Group in the Northeastern University Library. She has a Master's degree in Information Studies from McGill University and a background in computer science and statistics. Registration link
      • Live editing session on Twitch, in French, by Vigneron, October 4 at 18:00 CEST (UTC+2)
      • [Small wiki toolkits] Upcoming "How to interact with Wikidata via Pywikibot" workshop on Friday, October 7th, 16:00 UTC
      • The State of Wikidata and Cultural Heritage: 10 Years In. Oct 4, 2022 08:00 AM in Pacific Time (US and Canada)
      • Talk to the Search Platform / Query Service Team—October 5th, 2022
      • Wikidata Office Hour GLAM-Hack − online meet-up about the "library world" with Wikidata. October 5th, 12.00 UTC (online via Zoom)
    • Ongoing
      • Wikimedia Österreich, in cooperation with Wikimedia Deutschland, started the DACH Culture Contest as a Börthday present for Wikidata 10th anniversary! It features two categories: "libraries in Austria, Germany and Switzerland" and "Culture in Austria, Germany and Switzerland". So if you would like to improve data about libraries, books, music, art, video games, cinema etc as a börthday treat, join us and get the chance to win some nice prizes! The contest will last until October 16, 2022.
      • Weekly Lexemes Challenge #61, Time
  • 🧑🏿‍💻 Development


You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

This Month in GLAM: September 2022

[edit]


Headlines
Read this edition in full • Single-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Wikidata weekly summary #541

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • ✨ Other Noteworthy Stuff
    • The fourth edition of the Coolest Tool Award is looking for nominations. Please submit your favorite tools by October 12, 2022. The awarded projects will be announced and showcased in a virtual ceremony in December.
    • The September 2022 summary for the Wikidata Query Service backend update is out.
  • 🧑🏿‍💻 Development
    • MUL language code: fixed the order of languages shown in the termbox on desktop, especially when mul is used (phab:T311617)
    • Lexicographical data:
      • Made Special:NewLexemeAlpha use the same font as the rest of the wiki (phab:T313166) – this should be the last blocker for replacing the old special page
      • Disallowed *-x-qid with lowercase Q as Lexeme language codes in favor of *-x-Qid (phab:T317863)
    • REST API: worked on handling conditional HTTP request headers
    • Changed the unexpectedUnconnectedPage page prop so that Special:UnconnectedPages can show the latest pages first, which should finally resolve this old security task in production (phab:T300770)
    • Cleaned up the Wikibase and WikibaseLexeme ontology files (phab:T314360)
    • Added a few more globes for geocoordinates (phab:T314611) - Thanks, Mike!

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #542

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • 🧑🏿‍💻 Development
    • REST API:
      • Finished work on handling conditional HTTP request headers (If-Match, If-None-Match, etc)
      • Working on providing more clear error reports to PATCH route errors
    • Mismatch Finder: Implementing a new random mismatch feature (phab:T302289)
    • The text in the namespace tabs for Lexeme: and EntitySchema: pages can now be easily translated (phab:T316770) - thanks Amir!
    • Made the Wikibase error message "Malformed input" more meaningful (phab:T304943)
    • Continued working on the deployment of a patch to improve the Query Service lag integration in MediaWiki API's maxlag (phab:T315423)
    • Fixed a bug where the Kartographer map preview is erroneously closed, when clicking on zoom actions (+/-) (phab:T303103)
    • Still working on fixing a mobile termbox issue related to the "mul" language code (phab:T318137)
    • Added ircs as an allowed protocol for the URL datatype (phab:T320643) - thanks Lectrician1!

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #543

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
Wikidata passed another milestone on October 19.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Registration is open for WCNA 2022 and Mapping USA

[edit]
 WikiConference North America 2022 will be virtual, November 11-13. We will hold it jointly with OpenStreetMap US's Mapping USA. Our theme this year is open knowledge allies.

Registration is now open here! Please register by the 10th so that we can set everyone up online on our platform. Like last year, we are planning on using Hopin.

Our schedule is will be finalized and available in the next few days. We have an exciting line-up of sessions related to Wikimedia, OpenStreetMap, and the intersection of the two. Stay tuned!

Local meet-ups will occur in Indianapolis and New York City - if you are available and interested in attending either of these, you can find more details here.

If you want to connect with other participants or have questions, please join our Telegram channel here.

MaggieMaps CC-By-SA
MaggieMaps CC-By-SA

Wikidata weekly summary #544

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • 🧰 Tool of the week
    • sparklis (source) : query builder in natural language that allows people to explore and query SPARQL endpoints with all the power of SPARQL and without any knowledge of SPARQL, nor of the endpoint vocabulary.
  • ✨ Other Noteworthy Stuff
    • Word Finder is a tool based on Wikidata Lexemes that solves anagrams and find missing letters in crosswords.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

View it! update

[edit]
View it! Tool
View it! Tool update Oct. 2022


Thank you for signing up for View it! updates!

As a reminder, you can view details about how to install the View it! user script or use the Toolforge tool on our meta page. Please use the talk page there to contact the team!

October Update

[edit]

September/October Happenings

  • View it! is now multilingual! We are currently working on tool localization. Please consider helping us!
  • View it! now has advanced search option on Toolforge, simply toggle on to enable searching with a different property constraint, free text, specific resolution, and quality assessment.
  • Advanced search allows for searching by Commons Categories which have an associated P373.
    • Commons Category search will also show sub-categories for more specific results.

Coming Soon

  • We are releasing a new version of View it! that will implement some of the Toolforge functionality into the on-Wiki experience.
  • We are thinking about ways for View it! results to show up on page as an image grid, gallery or other form, without leaving the page. Please let us know what your idea/preference is.
  • Integrating editor features such as the ability to add an image from View it! or remove a faulty statement.

Action to take

  • Share your thoughts with us about the interface! What would you like the final product to look like? Should it be on-wiki? Preference on location of the button/link? We are open to ideas - please share them with us.
  • Install Beta script and see how it can used to add new images to articles.
  • All editors are invited to share the tool with their local wiki communities, or incorporate it into relevant local templates, such as infoboxes. If you do so, please let us know about it, so we can ensure backwards compatibility for that use case as we continue development!

JamieF (talk) 19:00, 2 November 2022 (UTC)[reply]

Wikidata weekly summary #545

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • 🎊 Events
    • Upcoming
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group Wikidata Working Hour November 7, 2022: tenth and final Wikidata Working Hour in the series will be using SPARQL to query and visualize the data we’ve added to Wikidata during our series. You are, as always, welcome to bring your own data to work on. All sessions in our project series will be recorded for those who cannot attend. Links will be added to the event page when available. Event page
      • Live querying session on Twitch, in French, by Vigneron, November 8 at 18:00 CET (UTC+1)
      • Wikidata and Wikibase office hour, taking place online on November 9th at 17:00 UTC (more details here)
      • Raising an Artist Profile with Wikidata: Thursday November 10, 2022 at 20:00 UTC (Session A) and 23:00 UTC (Session B). This free, step-by-step Wikidata workshop will focus mainly on Indigenous artists. Participants may choose to attend either Session A or Session B: both will cover the exact same material.
      • Wikidata editathon in Swedish with focus on climate politics and COP27, online and in Stockholm, 11 November 13.00-18.00 UTC
      • A Hands-On Introduction to Wikidata: Thursday December 1, 2022 at 17:00 UTC. By the end of this session, you will be able to edit Wikidata records about the cultural venues that matter most to you.
  • 🧰 Tool of the week
    • WikibaseEcho.js: Userscript that shows the labels of entities in your notifications. Currently only works on Firefox.
  • 🧑🏿‍💻 Development
    • Lexicographical data: Replaced the old Special:NewLexeme page with the new one (phab:T307866) - a few remaining issues will still be fixed
    • Vue 3: Almost finished the Vue 3 migration in Wikibase and WikibaseLexeme (phab:T321595 and (phab:T304534) - this is needed for finalizing the migration in MediaWiki overall
    • Mismatch Finder: Worked on improving the handling of dates (phab:T288511)
    • Search: Working with the WMF on making the new Vue-based Vector search understand Wikidata (phab:T316093)), especially regarding “load more” behavior
    • REST API:
      • Continued improving error reporting for PATCH routes (phab:T320358)
      • Ensuring that the API correctly marks bot edits as bot edits and treats them as such in various other places

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

This Month in GLAM: October 2022

[edit]


Headlines
Read this edition in full • Single-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Start Westward Memorial

[edit]

I used some of your pictures on Start Westward Memorial, which I just wrote. As you're nearby, I wonder if you might kindly be able to take pictures of the four pylons associated with the memorial, and the esplanade/ landing stage, including from across (or on) the river? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:19, 13 November 2022 (UTC)[reply]

Nice article, I'd be happy to take the photos requested. I've started discussing with the local historical society and plan to talk more with the local museums about considering Wikimedia integration, trying to start with just metadata level to records. I've been working on OSM, curating WikiCommons, and Wikidata prep to create some examples. I'll need to figure out how best to get the esplanade and landing since I don't have a boat and there is brush on the far bank making hard for a clear photo. I don't think the pylons should be an issue, but getting a fair weather day may take a while as we turn toward winter. Wolfgang8741 says: If not you, then who? (talk) 19:36, 13 November 2022 (UTC)[reply]
That sounds great, thank you. Points about access and weather noted. No rush. I've been a Wikimedian in Residence at numerous institutions, so do let me know if I can help or advise. Of course there are also local WiRs to you, at least in neighbouring states. Happy to introduce you, if you don't know who they are. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:39, 14 November 2022 (UTC)[reply]

Archiving

[edit]

Your talk page is very slow to load, becuase it is 1,808,107 bytes long. Please archive most of it. The simplest way is to add the wiki code: 

{{User:MiszaBot/config
|archiveheader       = {{talkarchivenav}}
|maxarchivesize      = 75K
|counter             = 1
|minthreadsleft      = 4
|minthreadstoarchive = 1
|algo                = old(28d)
|archive             = {{SAFESUBST:FULLPAGENAME}}/Archive %(counter)d
}}
{{archives|search=yes}}

at the top of the page; then a bot will do the rest for you. If that's not clear, let me know and I will do it for you. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:28, 13 November 2022 (UTC)[reply]

Thank you for the reference, I've always wondered what people are using, but haven't looked into it since it is not built into the Wiki as a setting for talk pages and has not been a priority. Does the archiving bot preserve the anchor link and provide a 301 redirect to the archived conversation location? If not, the archiving process is fundamentally flawed as it breaks links. I haven't notice any performance issues loading, are you experiencing issues loading the page? I largely rely on the find feature and content table, a large page is preferable to navigating to an archive and spending time to locate past discussions. Automatic pagination would be a simple solution for talk pages and could create a permalink structure without need for a bot ie /wiki/User_talk:Wolfgang8741/42 and when x number of talk items (ie h2 headers) have been added to a page the next section be added to an increment and the user talk link would route to the highest page number thus auto archiving could be implemented and permalink available, just requires some modification of Mediawiki. If the links are preserved, I'll use the bot, but if not, I'll be looking for a solution which keeps permalinks and redirects to accomplish an archiving function. Wolfgang8741 says: If not you, then who? (talk) 19:28, 13 November 2022 (UTC)[reply]
The page loads OK, but starting and saving a new topic were both very slow. The archiver doesn't update links, sadly, but there is a gadget - "find-archived-section" - you can use to find archived topics. Also, the code above adds a search box - you can see that in use on my talk page. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:54, 14 November 2022 (UTC)[reply]

Wikidata weekly summary #546

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • 🎊 Events
    • Upcoming:
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call November 15, 2022: We will be discussing the first Wikidata Affinity Group Working Hour series, which ran from July to early November of this year. We will offer visualizations based on our data, listen to some of our volunteers talk about their experience helping to build the series, and discuss the results of our participant survey. We want to hear your questions and suggestions for future series! Agenda
      • Enrichissement des données sur la danse: Wednesday 16 November at 6:30 pm UTC (Session A) and Thursday 17 November at 6:30 pm UTC (Session B). Join the Regroupement québécois de la danse (RQD) and the Linked Digital Future Initiative (LDFI) for two dynamic sessions focusing on dance data. Session A will focus on artists, while Session B will focus on organizations and dance companies. Note: These sessions are offered in French only.
    • Ongoing:
    • Past:
      • Wikidata/Wikibase Telegram office hours log (2022-11-09)
  • 🧰 Tool of the week
    • QLever - Alternative instance for SPARQL queries.
    • Discuss.js - Adds a link to a diff when clicked will open a new topic on the talk page that mentions the revision and the user.
  • 🧑🏿‍💻 Development
    • REST API:
      • Finished work on improved error reporting of the PATCH routes (phab:T320358)
      • Finished work on properly handling bot user right and marking bot edits as such
      • Adjusting statement data structure in Wikibase REST API responses and requests (phab:T321459)
    • Mismatch Finder: continuing work om improving the handling of dates in the Mismatch Finder (phab:T288511)
    • New Vector skin: continuing work with the WMF on making the new Vue-based Vector search understand Wikidata (phab:T316093, phab:T317682)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

William Mark Young

[edit]

Another Marietta-related article you might enjoy: William Mark Young.

I would love to know whether his murals are still in the Ohio Statehouse? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:26, 19 November 2022 (UTC)[reply]

Wikidata weekly summary #547

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming:
      • Online Wikidata meetup in Swedish #130, November 27 at 13.00 UTC
      • Wiki <3 Data - How to use Wikidata for data visualization. Join us on Monday 28 Nov. from 13:15 - 17:00 at Aalto University in Espoo, Finland or online! - Hosted by Visual Communication Design programme at Aalto Arts, workshop by Yamen Bousrih.
      • Next Wikidata Bug Triage Hour about Entity Schemas and other topics, on December 6th at 17:00 on Jitsi
    • Ongoing:
  • Development
    • REST API: continuing work on adjusting JSON request and response format (phab:T321459)
    • Lexicographical data:
      • Added separation between identifiers and other statements on Lexemes (phab:T318310)
      • Fixed the case where language fallback indicators where shown on Special:NewLexeme when they should not be (phab:T322687)
      • Adjusted the help link for the spelling variant input field (phab:T315161)
    • Mismatch Finder:
      • Finished work on better handling of dates (phab:T288511)
      • Finished work on allowing mismatches with empty Wikidata values to make it possible to use the Mismatch Finder also for suggesting missing data (phab:T313468)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #548

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming:
      • Save the date! The next WikidataCon will take place on October 28-29, 2023, and will be organized by Wikimedia Taiwan and Wikimedia Germany. The hybrid event will be streamed from Taipei and accessible for everyone online. More information and updates on d:Wikidata:WikidataCon_2023
      • Next LD4 Wikidata Affinity Group call November 29, 2022: We will be discussing openly managed data gathering and management with Holly Little (Smithsonian), Sabine von Mering (Museum für Naturkunde), Erica Krimmel (Florida State University), and Debra Paul (University of Illinois)! Agenda
      • A Hands-On Introduction to Wikidata: Thursday December 1, 2022 at 17:00 UTC. By the end of this session, you will be able to edit Wikidata records about the cultural venues that matter most to you.
      • Online Wikidata meetup in Swedish #131, December 4 at 13.00 UTC
    • Past:
      • Wikibase live session (November 2022) log
  • Development
    • REST API:
      • Finished the adjusted statement data structure (phab:T321459)
      • Simplifying the structure of sitelinks in Item data (phab:T321483)
      • Simplifying the value format for entity ID, time and globecoordinate value types (phab:T322734)
      • Investigating the way forward for rate limiting (phab:T322746)
    • Ontology issues: Preparing a survey for re-users of Wikidata's data about the different types of ontology issues and which ones are causing the most issues for application builders
    • Mismatch Finder:
      • Finishing the work on making it possible to provide mismatches with an empty Wikidata value so the tool can also be used to suggest new data (phab:T313468)
      • Finishing the work on better handling of calendar models and precision for dates (phab:T288511)
    • Lexicographical data: Fixing bugs:

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

ArbCom 2022 Elections voter message

[edit]

Hello! Voting in the 2022 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 12 December 2022. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2022 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:39, 29 November 2022 (UTC)[reply]

Wikidata weekly summary #549

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group Working Hour on December 5. We will be working on Structured Data on Commons with a WINTER FUN theme, adding depicts statements to images and playing with some tools. You are, as always, welcome to bring your own data to work on. This will be our last scheduled Working Hour for 2022. Please join us for a relaxing and enjoyable session to wrap up a year of excellent work together. Event page
      • Bug Triage Hour on December 6 at 17:00 UTC, on the topic of Entity Schemas (other topics also welcome). Come with your favorite Phabricator ticket so we can improve its description together!
      • Save the date! The next WikidataCon will take place on October 28-29, 2023, and will be organized by Wikimedia Taiwan and Wikimedia Germany. The hybrid event will be streamed from Taipei and accessible for everyone online. More information and updates on the WikidataCon 2023 page.
    • Ongoing
      • Weekly Lexemes Challenge #69, Cycles
  • Tool of the week
    • How many edits does Wikidata get per second? listen.hatnote.com/#wikidata is a tool that allows you to listen to the sound of Wikidata's recent changes feed.
  • Development
    • Improved the error message for sitelinks to redirects (phab:T320490)
    • Made the Property namespace a content namespace (phab:T321282)
    • Lexicographical data: Added a better link for a help message (phab:T315161)
    • Mismatch Finder:
      • Linked the header to make it easier to get back to the main page (phab:T323680)
      • Made the layout more compact (phab:T323678)
      • Fixed an issue where the whole header of a mismatch results table was a link instead of just the Item ID (phab:T323823)
      • Improved the text on a button (phab:T323682)
      • Finished better support for dates with calendar model and precision (phab:T288511)
      • Ordered the columns in the results page better so they make more sense (phab:T323819)
    • Fixed a bug where a large horizontal scrollbar appeared on RTL interface languages (phab:T321441)
    • Fixed a bug in the search in the new Vector skin (phab:T324148)
    • Query Service:
    • mul language code: continuing investigation for language fallbacks on mobile that is currently blocking it (phab:T323098)
    • REST API:

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


This Month in GLAM: November 2022

[edit]


Headlines
  • Africa report: Wiki Loves Africa 2022 Winners & 2022 ISA Drive
  • Albania report: An event at the National History Museum in Tirana
  • Brazil report: WLM tool, Wiki Takes, New WMB's Strategy, and 2 new GLAMs
  • India report: Two Open Culture films on India's Odia language, made with volunteer labour
  • Indonesia report: Open GLAM Conference; Sundanese Wikisource Workshop; Minangkabau books digitization
  • Italy report: Video and photo to share the beauty of Italy's heritage
  • Netherlands report: Linking heritage data at HackaLOD
  • New Zealand report: Integrating with the BHL, loading natural science specimens and data
  • Poland report: How Wiki helps to explore and enjoy art & culture; Wiki workshop for the National Museum in Krakow; GLAM online meeting on ideas for 2023; Wiki Loves Monuments 2022
  • Serbia report: Wikipedian in residence at Faculty of Dramatic Arts in Belgrade and National Museum of Zrenjanin
  • Sweden report: Wikipedian in Residence at Musikverket; Women and architecture; Gymnasiearbete; New uploads from the Swedish National Archives; WLM winners; Images of Äpplet
  • Switzerland report: Swiss GLAM Program
  • UK report: Khalili Foundation
  • Uruguay report: Let's GLAM Together in Uruguay: Help us organize the GLAM Wiki Conference 2023
  • USA report: WikiConference North America 2022; Punk Wikipedia Edit-a-thon; Kensho Technologies Impact-a-thon
  • Special story: We need your opinion: GLAM Wiki Conference 2023 & Your Favorite Tools
  • Content Partnerships Hub report: Survey: your favorite tools
  • Calendar: December's GLAM events
Read this edition in full • Single-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Wikidata weekly summary #550

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
  • Development
    • REST API:
    • Vektor 2022: Finished work on making Vector’s new Search work with Wikidata. The changes roll out for testing on test.wikidata.org next week (phab:T275251)
    • Query Service:
      • Getting a link to the query is now possible in the same place as getting a link to the result of the query (phab:T324218)
      • Removed the gif that showed on hover over the button that advertises the Query Builder to make it less annoying (phab:T296135)
      • Added wikibase:identifiers to the autocomplete feature (phab:T302057)
      • Adjusted the layout of the Query Builder header to be more in line with other application (phab:T288939)
    • Constraint violations: When a language name is mentioned in the constraint it will now show the name of the language in the interface language instead of the language itself to make it easier to understand (phab:T316936)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #551

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming:
      • You can now register for the Wikimedia Hackathon 2023, taking place on May 19-21 in Athens, Greece. You can also apply for a scholarship until January 14th. More information: Wikimedia Hackathon 2023/Participate
      • digital@IANLS: online Wikidata workshop for Neo-Latinists in February 2023
      • Call for Papers on Linked Open Data on Journal BiD: Deadline: Sun, 04/09/2023. Some of the ideas and issues to be included in this issue: Creation and exploitation of knowledge graphs, Information services based on linked open data and knowledge graphs, Artificial intelligence and linked open data, Textual corpora and linked open data, Textual corpora and knowledge graphs, Application of bots in linked open data, Application of bots in knowledge graphs, Linked open data and diversity of genres, Graphs of knowledge and diversity of genres, FAIR and linked open data, FAIR and knowledge graphs, Ontologies and linked open data, Ontologies and knowledge graphs, Application of ontologies in information services.
    • Ongoing:
  • Tool of the week
    • Wikidata Atlas is a system allows the user to search for different types of entities (with geo-coordinates) on Wikidata and visualize them on a world map. (Feedback is very welcome to help evaluate and improve the tool.)
    • Check out a similar tool: wiki-atlas
  • Development
    • REST API: We are getting ready for a release in January and would really love more people to test the current state on beta. You can find details for testing at Wikidata:REST API feedback round.
    • Vector 2022 search: We have worked on making the new search in the Vector 2022 skin work for Wikidata. You can now test it on test.wikidata.org and soon on Wikidata.
    • Query Service:
      • Removed the SVG download options for result views where SVG downloads are not supported, such as Map (phab:T311594)
      • Fixed the indentation of autocompletion suggestions (phab:T291695)
      • Fixed downloading query results in the Query Builder (phab:T323451)
    • Lexicographical data:
      • Working on showing the Lexeme lemmas when you look at a Lexeme’s history (phab:T312660)
      • Fixing a keyboard navigation issue in the lookups on Special:NewLexeme (phab:T324743)
    • mul language code:
      • Continuing to investigate how to implement language fallbacks on mobile termbox (phab:T323098)
      • Investigating how to disallow `mul` descriptions (phab:T313027)
    • Improving and harmonizing the footers in the Query Builder (phab:T324356) and Mismatch Finder (phab:T324366)
    • Preparing for showing constraint violations to visitors who aren’t logged in (phab:T272132)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #552

[edit]

Many thanks to everyone who has contributed to and read the newsletter this year. If you have a moment, please let us know what you would like to see changed in the newsletter in 2023. Thank you again for your support and have a happy new year!

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming
      • The next Wikidata+Wikibase office hours will take place on Wednesday, November 9th 2022 at 17:00 UTC (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
    • Ongoing
  • Development
    • Due to the winter holidays, the development team is taking a break and no deployment is happening for Wikidata at the moment.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #553

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming
      • The next Wikidata+Wikibase office hours will take place on Wednesday, 17:00 UTC on Wednesday, 18th January 2023 (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
    • Ongoing
      • Weekly Lexemes Challenge #74, Urology
  • Tool of the week
    • OWL Map - a tool to help in linking Wikidata items with the matching object on OpenStreetMap.
  • Development
    • The development team took a break during the winter holidays and as a result, no development occurred.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Happy New Year, Wolfgang8741!

[edit]
Happy New Year!

Wolfgang8741,
Have a prosperous, productive and enjoyable New Year, and thanks for your contributions to Wikipedia. See this for background context.
— Moops ⋠T⋡ 22:23, 3 January 2023 (UTC)[reply]

   Send New Year cheer by adding {{subst:Happy New Year fireworks}} to user talk pages.

— Moops ⋠T⋡ 22:23, 3 January 2023 (UTC)[reply]

View it! has been expanded and will have an official launch demo session Jan. 12th

[edit]
Goat View it! results
View it! Tool update Jan. 2023

Big news, View it! users! Over the last two months, View it! has been expanded to two versions. Our new full version shows images within the wiki content page, and the "View" tab displays a gallery of images without leaving the site you are on, as you can see at right. We have rebranded the original version, which utilizes the "View" tab to link to our Toolforge search results, to "Lite". We invite you to switch to full version and try it out! Major changes:

  • The full version includes an image carousel on each content page (at the top, under the article navigation buttons) which can be expanded for pagination.
  • You may notice the "View" button has moved to between the "Read" and "Edit" buttons - the View button is in the same place for both versions and we felt this was a better placement for editors.
  • In full version, clicking the "View" tab will take you to a full-screen gallery.

Action to take

Thank you for being a part of the View it! journey and please join us for the launch on January 12th!

As a reminder, you can view details about how to install the View it! user script or use the Toolforge tool on our meta page. Please use the talk page to contact us with comments or issues.

JamieF (talk) 04:00, 9 January 2023 (UTC)[reply]

Wikidata weekly summary #554

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • New requests for permissions/Bot:
      • Bean49Bot 2. Task/s: Adding statements to plwikisource items with no statements.
      • RPI2026F1Bot 4. Task/s: Reconstruct npm dependencies.
    • Closed request for permissions/Bot:
  • Events
    • Upcoming
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call January 10, 2023: Egon Willighagen will be introducing us to SARS-CoV-2 queries, a well-documented series of Wikidata queries around the SARS-CoV-2 virus and the pandemic. This work contributes to Wikiproject COVID-19 and documentation is currently available in Japanese, Dutch, Spanish, and Portuguese. Agenda
      • Talk to the Search Platform / Query Service Team—January 11, 2023. Time: 16:00-17:00 UTC / 08:00 PDT / 11:00 EDT / 17:00 CET
      • The full version of View it! Tool is out! The new user script uses structured data to display related media in any Wikimedia content pages—including Wikidata items—in an on-wiki image panel or gallery view. Please join the public launch and demo of the full version of this new tool on Thursday, January 12th, 5:00 UTC via Zoom (Meeting ID: 160 454 5329) to learn more and discuss forthcoming editing features.
      • The next Wikidata+Wikibase office hours will take place on Wednesday, 17:00 UTC on Wednesday, 18th January 2023 (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
      • About 2 months left to register for the first digital@IANLS workshop: Learn the basics of Wikidata and how to use it in your Neo-Latin research. Event is online, free, and open to all. More info on event and registration.
    • Ongoing
      • Weekly Lexemes Challenge #75, Tools
  • Tool of the week
    • Web Hub allows users to navigate between origin and destination on the web using information from Wikidata, primarily on Wikimedia sites.
  • Development
    • REST API: Preparing the first release to test.wikidata.org on January 17th and to Wikidata on January 24th
    • Entity Schemas: Continuing to investigate and prototype technical approaches for version 2
    • Mismatch Finder: Working on giving mismatch providers access to the reviews of the mismatches they uploaded (phab:T304794)
    • Investigated how to best do language switching for the Query Builder and Mismatch Finder. So far they only support it by specifying the language via a URL parameter and not yet via the UI (phab:T324653)
    • Query Service:
      • Lexeme IDs now have tooltips so you can see the Lemma in the SPARQL code, similar as for Items and Properties (phab:T255245)
      • Fixed a bug where the y-axis label on a graph were misaligned and hard to read (phab:T325808)
    • Lexicographical data:
      • Statements linking to a Sense now also show the language of the Lexeme to make it easier to see for example which language a translation statement refers to (phab:T207392)
      • Fixed a bug in the language dropdown on Special:NewLexeme (phab:T324743)
      • The Lemma of a Lexeme is now shown in the title of the revision history of the Lexeme as well (phab:T312660)
    • Vector 2022 theme: worked on making the search on Wikidata work in this new theme. You can test it on test.wikidata.org now and next week on Wikidata. (phab:T316093)
    • mul language code:
      • Continued investigation around how to handle language fallbacks on mobile, which is a blocker for adding this language code (phab:T323098)
      • Preventing the addition of descriptions for mul (phab:T313027)
    • Constraint violations: Working on also showing them to non-logged in users (phab:T272132)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

This Month in GLAM: December 2022

[edit]


Headlines
Read this edition in full • Single-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Wikidata weekly summary #555

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Vector 2020 skin: the search that works properly with Wikidata has been deployed
    • Entity Schemas: Making progress on the proof of concept that will help us figure out the technical way forward
    • REST API: getting ready to deploy the first version to test.wikidata.org on February 17th
    • Lexicographical data: When linking to a Sense in a statement the language of the Lexeme for that Sense is now also shown. This makes it easier to understand translation statements for example (phab:T207392)
    • Constraints: Constraint violations are now also shown to logged out users (phab:T272132)
    • Fixing a regression where Wikipedia and co are no longer notified about a disconnected sitelink when the Item that contains the sitelink is deleted (phab:T326082)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #556

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Past
    • Upcoming
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call January 24, 2023: We will be discussing plans for 2023, and requesting feedback and ideas for future programming. Based on a previous recommendation to host a discussion on advocacy for Wikidata within libraries, we will introduce and provide time to complete a short survey to foster conversation in a future Group Call. Please come ready to share your thoughts Agenda
      • Introductions to Wikidata, online meetings organized by Wikimedia Australia on January 25, 26 and 31
  • Development
    • Wikibase REST API: The new API is now available for testing on Test.Wikidata
    • Ontology issues: We finalized and published the survey to better understand which types of ontology issues are most problematic for reusers of our data.
    • Wikipedia and co: Fixing a regression where there is no entry in recent changes and watchlist when an Item is deleted that was connected to an article on that wiki (phab:T326082)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #557

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • A citation hunt program was organized for secondary school students at IIS School in Dubai as part of the 74th Republic Day celebration of India. 16 students participated, with different mother tongues and from different states of India living as expatriates in Dubai. The goal was to increase references for Wikidata statements based on research. The students were introduced to the importance of protecting India's history on the internet, and were taught how to edit Wikipedia and Wikidata. They were given a special event page on Wikidata with instructions and a list of Wikidata items to add citations to, and they searched for references in their textbooks and search engines to add to the Wikidata items.More details are given here.
    • Next Linked Data for Libraries LD4 Wikidata Affinity Group Working Hour January 30, 2023: The #1Lib1Ref campaign is afoot, so we will be working on adding references to Wikidata statements. We'll have some data for you to work with, but you're welcome to bring your own. We'll be mainly working with adding webpages as sources, but if you want to get experience using books or articles as sources, we recommend bringing some to the session to use as references for Wikidata items you have identified. You are, as always, welcome to bring your own project to work on Event page
  • Tool of the week
    • theyrule.net is a website that helps to explore the boardroom connections of the largest US companies.
  • Development
    • Wikibase REST API: The first version of the new API is released on Wikidata now \o/ We'd love to hear your feedback on what to improve next in the API.
    • Property Suggester: We updated the data for the Property Suggester so suggestions for new statements to add to an Item should be more in line with current Property usage on other similar Items again.
    • Fixed an issue with Item deletions not showing up on Wikipedia and co if they affect an article on that wiki (phab:T326082)
    • Vector 2022: Made it possible to add a new sitelink on Wikipedia and co in the new Vector 2022 language selector (phab:T310259)
    • Lua: Working on two new Lua functions, getDescriptionByLang (phab:T230839) and getBadges (phab:T305378)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #558

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Let's Quiz is a game that generates random quizzes to test your knowledge & learn something new every day.
    • User:Nikki/AddTermboxLanguage.js - makes it easier to add/edit labels to an item in a language other than the ones shown by default.
  • Development
    • REST API: adding a new GET /entities/items/{item_id}/descriptions endpoint (phab:T327881)
    • Lua: added two Lua functions, getDescriptionByLang (phab:T230839) and getBadges (phab:T305378) that make it easier to get this data on Wikipedia and co
    • Lexicographical data: added documentation for the WikibaseLexeme JSON structure (phab:T201489)
    • Action API: fixed a bug that prevented the wblistentityusage API module from being used as a generator (phab:T254334)
    • Dates: working together with Matěj Suchánek to fix date parsing issues in Czech (phab:T221097)
    • Constraints: working on showing constraint clarification messages to make it easier to understand why a constraint violation is happening and how to fix it (phab:T219037)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

This Month in GLAM: January 2023

[edit]


Headlines
Read this edition in full • Single-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Wikidata weekly summary #559

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • New requests for permissions/Bot:
      • CJMbot (CJMbot lets users upload a CSV file in a certain format. The data inside this file is then validated and processed. New items wil be created based on the data in the CSV file and existing items wil updated by adding statements and references).
      • RPI2026F1Bot 5 Task/s: Import dependency and version data from PyPi
  • Events
    • Upcoming
      • Next Linked Data for Libraries LD4 Wikibase Working Hour February 13, 2023. The February Working Hour will feature a presentation by Steve Baskauf on using VanderBot with Wikibase: The Wikibase API provides a mechanism for programmatic control of uploads, and its behavior is consistent across instances (Wikidata, Structured Data in Commons, and those that are established privately). In this session, Steve will discuss basic interactions with the API and demonstrate using the VanderBot Python application to rapidly upload tabular data to a wikibase.cloud instance. After performing a mass deletion, Steve will conclude by describing how he's used the Wikibase API to facilitate addition of structured data to Commons. Registration link
      • Strategically Using Production Photos to Increase Your Online Discoverability, February 22 and 24, 2023. This two-part workshop presented by CAPACOA will explain how to upload performing arts production photos to Wikimedia Commons and how to document credits in Wikidata.
    • Ongoing
      • Weekly Lexemes Challenge #80, Work
  • Other Noteworthy Stuff
    • Wikidata Graph Builder released a major update, introducing new layouts and visualization ideas. You can read the full changelog here.
    • The new Service Level Objective for the Wikidata Query Service has been implemented: the current aim is to maintain a 95% uptime based on a 90 day rolling window. You can read the full announcement here.
    • Observablehq.com recently introduced a system of tags. Anyone authoring a notebook using data from Wikidata can add the #Wikidata tag: https://observablehq.com/tag/wikidata?filter=recent.
    • a.gup.pe provides group features for Mastodon. @wikidata@a.gup.pe is a group about Wikidata in general. @querywikidata@a.gup.pe is a group about Wikidata queries. Anyone can join those groups simply by following them in Mastodon. Anyone can share a message with all members of those groups by mentioning them in a publication in Mastodon or any other application of the Fediverse.
    • The hashtag #Wikidata can be used to tag all publications related to Wikidata in Mastodon. Anyone can find recent publications using this tag using the search feature: https://wikis.world/tags/Wikidata.
    • @wikidata@wikis.world is the official Mastodon account of the Wikidata project.
    • You can now vote for your favorite proposals on the Community Wishlist Survey 2023/Wikidata. The voting phase is open until February 24th.
  • Development
    • [Significant change] Heads-up: Upcoming fixes for date parsing - Thank you Matej for moving this forward!
    • REST API:
      • Went over the feedback on the first release and deciding on the next routes to add
      • Added a new endpoint for getting descriptions (phab:T327881)
      • Worked on throwing exceptions when something goes wrong (validation failed, Item not found, etc.) instead of returning an error response object (phab:T327527)
    • Entity Schemas: Finished the technical exploration that will unblock the next steps for actual development
    • Query Service: Changed URLs with URL-encoded characters to be shown un-encoded for better line-breaks and readability (phab:T327514)
      • Query Builder:
      • Adding support for a few additional datatypes (phab:T328528)
      • Adding a basic language selector to make it easier to switch the language of the page (phab:T328764)
    • Constraint checks: Working on showing constraint clarification messages to make it easier to understand how to fix a violation on a statement (phab:T219037)
    • Search: Exploring design options for how to make it easier to search for entities other than Items (phab:T327507)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #560

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • New requests for permissions/Bot:
      • Cmtqwikibot 2 (Task/s: Add credits (cast and crew) for audiovisual work produced in Quebec based on the Cinémathèque québécoise's catalogue data. Adds reference. Deletes redundant, more general existing statements in certain circumstances.)
      • Gabrabot (Bulk upload Maltese lexeme data to wikidata from Gabra.)
      • MsynBot 12 (import missing GND ID (P227) identifier based on linked VIAF cluster)
  • Events
    • Upcoming
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call February 21, 2023: Jim Hahn and John Mark Ockerbloom will be presenting on Penn Libraries' Linked Data Vision. They will discuss their framework for activities and goals around linked data, which includes both existing standards and new functionality. Additionally, they will share successes and areas where progress has not yet been made. The presentation will cover projects with Wikidata tie-ins, such as the Digital Scriptorium Wikibase project and the Deep Backfile copyright information project. The presenters also plan to have ample time for conversation with those interested in using linked data to bring new functionality to their libraries. Agenda
      • Wikidata and Wikibase - SEMIC workshop 2 physical hands-on workshop in Brussels on the 23rd of February (Register here)
      • If you are interested in organizing or joining the Wikimedia Hackathon 2023 satellite events, you can apply for funds by March 20 via the Rapid Grants maintained by the Wikimedia Foundation.
      • Call for papers for the 10th Wiki Workshop in 2023 is out. Submit your 2-page abstracts by March 23.
    • Ongoing
      • Weekly Lexemes Challenge #81, Eye
  • Development
    • REST API:
      • Finished work on endpoints for getting labels and descriptions (phab:T325647, phab:T327881)
      • Started work on makign it possible to get statements from an Item based on the Property ID instead of just the statement ID (phab:T309021)
    • Entity Schemas: finalized technical investigation and making plan for the next steps
    • Working on more validation for valid URIs for units, globes and calendar models (phab:T102840)
    • Query Builder:
      • Adding support for additional data types (phab:T328528)
      • Adding a language selector to make it possible to switch the UI language (phab:T329487)
    • Constraint: Putting finishing touches on showing the constraint clarification messages in the constraint violation popup (phab:T219037)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #561

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • New requests for permissions/Bot:
    • Closed requests for permissions/Bot:
      • Cmtqwikibot 2 (Task/s: Add credits (cast and crew) for audiovisual work produced in Quebec based on the Cinémathèque québécoise's catalogue data. Adds reference. Deletes redundant, more general existing statements in certain circumstances.)
      • MsynBot 12 (Task/s: import missing GND ID (P227) identifier based on linked VIAF cluster)
  • Press, articles, blog posts, videos
    • Videos
      • LIVE Wikidata editing #106 - YouTube
      • CALA Speaker Series "Describing Chinese Rare Books and Cultural Heritage Collections" Session 1 - YouTube
      • TWed Talk (21 Feb 2023): Sola Shirai on "Working with Wikidata" - YouTube
  • Tool of the week
    • AutosuggestSitelink is a gadget that suggests Wikidata items for possible linking with a Wikimedia site page, using interwiki linking.
  • Development
    • REST API:
      • We added a way to get all statements on an Item for a given Property ID via a filter (phab:T309021)
      • We made it possible to configure the server for the "Try it out" button on the OpenAPI spec (phab:T329606)
    • Query Builder:
    • Constraints: We added support for showing constraint clarifications in constraint violation pop-up (phab:T219037)
    • We finished restricting unit/calendar/globe URIs to sensible values (phab:T102840)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #562

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • wikidata-todo is a tool that helps you find Commons categories with files, where none of the files are used on Wikidata.
  • Other Noteworthy Stuff
  • Development
    • Wikibase REST API:
      • The statements endpoint now supports filtering by Property ID like ?property=P123 (phab:T309021)
      • We started working on GET /entities/items/{item_id}/aliases (phab:T327882)
      • We started working on including sitelink URLs in GET /entities/items/{item_id} (phab:T330252)
    • Community Wishlist Survey: We reviewed the results and what we can do to address some of the wishes.
    • Query Builder:
      • We continued work on the language selector to make it possible to switch the UI language (phab:T328764)
      • We have added support for the datatypes for Form (phab:T329205) and Property (phab:T329207)
    • Search: We are looking deeper into how we can make it possible to search for Properties, Lexemes and EntitySchemas in the search box, not just Items (phab:T321543)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


This Month in GLAM: February 2023

[edit]


Headlines
  • Albania report: I Edit Wikipedia Online Campaign 2023
  • Belgium report: Public Domain Day Belgium 2023
  • Brazil report: GLAM-Wiki initiatives in Brazil spark academic investigation
  • Croatia report: Activities during first two months of 2023
  • Indonesia report: Launching of Wikisource Loves Manuscripts; Bincang GLAM continues
  • Italy report: New project and collaboration in February
  • Kosovo report: I Edit Wikipedia Online Campaign 2023
  • New Zealand report: Wikidata and the Biodiversity Heritage Library, Wellington WikiCon 2023 and Auckland Museum local suburb project funding
  • Poland report: The European GLAM Coordinators online meet-up; GLAM-Wiki workshop at the Wawel Royal Castle State Art Collection; Wikimedians-in-residence online meet up
  • Sweden report: 100 000 Bildminnen; Report from The Association of Swedish Museums; Wikipedia for all of Sweden; ArkDes edit-a-thons
  • UK report: In Memoriam Jo Pugh / Cultural Diversity
  • USA report: Black History Month and More
  • Wiki Loves Living Heritage report: Wiki Loves Living Heritage launches 17 March 1pm UTC
  • WMF GLAM report: Gender, language, and living heritage events in collaboration with affiliates
  • Calendar: March's GLAM events
Read this edition in full • Single-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Wikidata weekly summary #563

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Open Etymology Map - is an interactive map that shows the etymology of names of streets and points of interest. (blogpost in Polish)
  • Development
    • Query Builder: We continued the work on making it possible to switch the language of the UI (phab:T328764)
    • EntitySchemas: We started the development of version 2 with some underlying cleanup and technical improvements.
    • REST API:
      • We worked on getting full URLs for sitelink data in the responses (phab:T330252)
      • We worked on a dedicated way to get the aliases of an Item (phab:T327882)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #564

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • EntitySchemas: We are preparing for adding a new datatype and other changes by improving tests, documentation, etc.
    • Date input: We did a bug triage hour around issues with date parsing and improved it for Japanese dates (phab:T214002)
    • Ontology issues: We started evaluating the survey responses for the survey about different types of ontology issues reusers are facing. More work is needed before we have results.
    • REST API: We finished work on including the URL of an article in sitelink data (phab:T330252) as well as providing all aliases of an Item (phab:T327882)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #565

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming:
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group Working Hour March 27, 2023: We will be creating items related to notable book podcasts. You are, as always, welcome to bring your own project to work on.Event page
      • WikiCite Monthly Meeting, online on 28 March 2023 at 16:00 UTC. Information and notes
      • Wikidata Query Service backend update office hours will be held on Jitsi on 27 March 2023 at 17:00 UTC (link to the Etherpad) and 28 March 2023 at 10:00 UTC (link to the Etherpad)
      • Weekly Lexemes Challenge #86, Clothes
  • Development
    • EntitySchemas: We started working on the new datatype to link to EntitySchemas in statements (phab:T214884)
    • Query Builder: We finished the work on the language selector so you can swithc the interface language of the tool (phab:T328148) It will be available on the site in the next days.
    • Wikibase REST API: We implemented the functionality to provide an Item's label, description or aliases in a specific language (phab:T323173)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #566

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • EntitySchemas: We are continuing the development of a new datatype to link to EntitySchemas in statements (phab:T214884)
    • Search: We are doing user testing with prototypes for search that makes it easier to find Properties, Lexemes and EntitySchemas (phab:T321543)
    • REST API: We are workng on making it possible to create, or replace, a label or a description in a given language (phab:T323813)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

This Month in GLAM: March 2023

[edit]


Headlines
Read this edition in full • Single-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Wikidata weekly summary #568

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming
      • The next Wikidata+Wikibase office hours will take place on Wednesday, 16:00 UTC on Wednesday, 19th April 2023 (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group Call, Tuesday, April 14, 2023 - Indigenous Artists and Wikidata: Report launch and discussion. Agenda.
    • Ongoing
  • Tool of the week
    • Query Chest is a tool that allows you to store Wikidata queries if they are too long for w.wiki to shorten it.
  • Development
    • EntitySchemas: We are continuing the work on creating the new datatype that allows linking to EntitySchemas in statements. It will be available on test systems next. (phab:T332139)
    • QueryBuilder: We are putting finishing touches on the language selector so you can switch the UI language of the Query Builder. (phab:T328764)
    • Wikibase REST API: We continued working on making it possible to create or replace labels and descriptions in a iven language. (phab:T323813)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

CS1 error on Connie Walker (astronomer)

[edit]

Hello, I'm Qwerfjkl (bot). I have automatically detected that this edit performed by you, on the page Connie Walker (astronomer), may have introduced referencing errors. They are as follows:

  • A "missing periodical" error. References show this error when the name of the magazine or journal is not given. Please edit the article to add the name of the magazine/journal to the reference, or use a different citation template. (Fix | Ask for help)

Please check this page and fix the errors highlighted. If you think this is a false positive, you can report it to my operator. Thanks, Qwerfjkl (bot) (talk) 16:26, 20 May 2023 (UTC)[reply]

Page full

[edit]

Your talk page has grown so large that it has reached the maximum size of a Wikipedia page and new messages cannot be posted. You really should archive it. * Pppery * it has begun... 00:27, 25 June 2023 (UTC)[reply]

Seems to still be working. — xaosflux Talk 15:14, 10 January 2024 (UTC)[reply]

Speedy deletion nomination of Category:SIA-Class Lakes articles

[edit]

A tag has been placed on Category:SIA-Class Lakes articles indicating that it is currently empty, and is not a disambiguation category, a category redirect, a featured topics category, under discussion at Categories for discussion, or a project category that by its nature may become empty on occasion. If it remains empty for seven days or more, it may be deleted under section C1 of the criteria for speedy deletion.

If you think this page should not be deleted for this reason you may contest the nomination by visiting the page and removing the speedy deletion tag. ✗plicit 12:37, 17 October 2023 (UTC)[reply]

Your talk page size

[edit]

Hi Wolfgang8741, some editors have reported that it may be hard or impossible to communicate with you due to the size of this page. If you do not object, some of the content may be cut and paste to a subpage so that you may still easily view it without impacting others. If you do object, please let me know. Thank you for your attention to this matter and for your positive contributions to Wikipedia. Best regards, — xaosflux Talk 15:18, 10 January 2024 (UTC)[reply]

Hi there! To follow up on the response from my own user talk; I've done a one-time archive of 2 of the larger newsletter types that were older to a subpage for you, User_talk:Wolfgang8741/Newletter Archive. This is linked at the top of this page for ease of use. This was not an exhaustive exercise, but has restored standard capabilities to your talk page again. If you hate it, revert from history, but I hope it is at least a good start for you. Best regards, — xaosflux Talk 20:58, 12 January 2024 (UTC)[reply]

Speedy deletion nomination of Template:Todo, lakes

[edit]

If this is the first article that you have created, you may want to read the guide to writing your first article.

You may want to consider using the Article Wizard to help you create articles.

Hello, and welcome to Wikipedia. This is a notice that the page you created, Template:Todo, lakes, was tagged as a test page under section G2 of the criteria for speedy deletion and has been or soon may be deleted. Please use the sandbox for any other test edits you may want to do. Take a look at the welcome page if you would like to learn more about contributing to our encyclopedia.

If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be deleted without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. If the page is deleted, and you wish to retrieve the deleted material for future reference or improvement, then please contact the deleting administrator, or if you have already done so, you can place a request here. WikiCleanerMan (talk) 13:40, 3 April 2024 (UTC)[reply]

Speedy deletion nomination of Category:Lakes articles with to-do lists

[edit]

A tag has been placed on Category:Lakes articles with to-do lists indicating that it is currently empty, and is not a disambiguation category, a category redirect, a featured topics category, under discussion at Categories for discussion, or a project category that by its nature may become empty on occasion. If it remains empty for seven days or more, it may be deleted under section C1 of the criteria for speedy deletion.

If you think this page should not be deleted for this reason you may contest the nomination by visiting the page and removing the speedy deletion tag. ✗plicit 14:54, 3 April 2024 (UTC)[reply]

Reminder to vote now to select members of the first U4C

[edit]
You can find this message translated into additional languages on Meta-wiki. Please help translate to other languages.

Dear Wikimedian,

You are receiving this message because you previously participated in the UCoC process.

This is a reminder that the voting period for the Universal Code of Conduct Coordinating Committee (U4C) ends on May 9, 2024. Read the information on the voting page on Meta-wiki to learn more about voting and voter eligibility.

The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. Community members were invited to submit their applications for the U4C. For more information and the responsibilities of the U4C, please review the U4C Charter.

Please share this message with members of your community so they can participate as well.

On behalf of the UCoC project team,

RamzyM (WMF) 23:10, 2 May 2024 (UTC)[reply]

Invitation to participate in a research

[edit]

Hello,

The Wikimedia Foundation is conducting a survey of Wikipedians to better understand what draws administrators to contribute to Wikipedia, and what affects administrator retention. We will use this research to improve experiences for Wikipedians, and address common problems and needs. We have identified you as a good candidate for this research, and would greatly appreciate your participation in this anonymous survey.

You do not have to be an Administrator to participate.

The survey should take around 10-15 minutes to complete. You may read more about the study on its Meta page and view its privacy statement .

Please find our contact on the project Meta page if you have any questions or concerns.

Kind Regards,

WMF Research Team

BGerdemann (WMF) (talk) 19:28, 23 October 2024 (UTC) [reply]

Retrieved from "https://en.wikipedia.org/w/index.php?title=User_talk:Wolfgang8741&oldid=1254405082"