Grants:Project/Rapid/-jem-/Precisions management

statusfunded
Precisions management
Developing a new web tool to manage precisions in parenthesis used in titles, showing information about current cases and allowing to fix the incorrect or unnecesary precisions.
targetes.wikipedia initially; others in the future
start dateDecember 28
start year2019
end dateMarch 15
end year2020
budget (local currency)975 EUR
budget (USD)1074.52 USD
grant typeIndividual
grantee-jem-
contact(s)• joseemiliomori(_AT_)wikimedia.es
join
endorse


Project GoalEdit

Briefly explain what are you trying to accomplish with this project, or what do you expect will change as a result of this grant. Example goals include, "recruit new editors", "add high quality content", or "train existing editors on a specific skill".

In Wikimedia projects and in particular in Wikipedias, there is a need to add precisions in parentheses to disambiguate / differentiate titles that could refer to several things. But when it comes to choosing the content of the precisions, particularly in Wikipedia in Spanish, there is no clear regulation on which exact words to use depending on the type or subject of the article (for example, TV series can have the precision "(serie de televisión)" —TV series— or just "(serie)" —serie—), causing differences that reduce the perception of Wikipedia as a unique and self-consistent work among its readers, and that generate doubts for the new cases among its editors, even greater when more complex precisions are needed. Additionally, in some cases precisions are used when they would not be necessary because the title without the precision does not yet exist; generally this is due to an imitation of a title whose content has been translated from another language in which the precision is necessary.
In order to address these problems, it is first necessary to have data about the precisions that currently exist, which will identify which cases are the most used, which cases are avoidable and which cases are equivalent to each other and could be unified; this would help to define lists of recommended words or formats, mandatory or prohibited, as decided by the community of users. I will try to promote a community debate in es.wikipedia to move in that direction.
For this reason, I consider useful the development of a web tool that manages everything related to the precisions in parentheses, including the compilation, analysis, presentation and ordering by frequency of the existing cases, the assisted move of individual titles or sets that follow the same pattern at the request of the user, and other support tasks and statistics. The code will be prepared for projects other than es.wikipedia and for future use with other types of precisions or differentiating elements within the titles that allow a systematic analysis.
In short, the goal of the project is to improve the uniformity and coherence of the Wikimedia projects and to save time in researching and carrying out moves on the part of the users, who will be able to focus on other useful tasks.

Project PlanEdit

ActivitiesEdit

Tell us how you'll carry out your project. What will you and other organizers spend your time doing?

The web tool will include the following functions:
  • Extraction, identification, accounting and presentation of all the precisions in parentheses existing in the articles' titles, grouped by text patterns (for example, all the "film of (year)") and defining subgroups (for example, within the group “ranges of years”, distinguish the cases "2010-11" and "2010/11").
  • Flexible introduction of any existing community consensus/rules on precisions for each project, recognizing recommended, mandatory or prohibited words or patterns, in order to offer the appropriate options in each case.
  • Presentation of various links for the assisted move of articles, individually or jointly by patterns, including different alternatives, with or without parenthesis, and the elimination of the precision if it is detected that the title without a precision doesn't exist.
  • Automatic fixing of inbound links to titles moved by the tool, and automatic deletion of unnecessary redirections that may remain.
  • Marking and differentiated presentation of moves already carried out until the next data update, and prior verification of other possible moves carried out without the tool since the last data update.
  • Suggestion of priority tasks to be carried out, according to the configured community rules.
  • Collection and presentation of use statistics and other useful information, and benefit from it by indicating the number of precedents in each possible proposed move.

How will you let others in your community know about your project (please provide links to where relevant communities have been notified of your proposal, and to any other relevant community discussions)? Why are you targeting a specific audience?

The project, together with other ideas presented for discussion and evaluation for grant proposals, has been announced in several Wikimedia projects:
All announcements refer to this page in es.wikipedia for the discussion of all my ideas, or this page in meta for other Wikimedia projects to be included.
I have targeted specifically other projects in Spanish and the Wikipedias in the other languages spoken in Spain because they are nearby communities with which I can communicate easily and which probably already know me or my work. Anyway, the idea can be carried on to any other project with precisions in titles, specially Wikipedias, and I don't exclude anyone, but when getting down to the announcements, time and practical limitations made me choose only those ones.

What will you have done at the end of your project? How will you follow-up with people that are involved with your project?

After programming and testing, the web tool will be available and operational at https://tools.wmflabs.org/jembot/pm and users will have the possibility to check the current precision data and make the desired moves among the options allowed by the tool. In the projects, the pages will be moved, the links fixed and the redirections removed by the Jembot account, and the user will see the link to the diffs of those actions. The tool will also include some use statistics and other useful information, and all operations will be logged.
The project will stay open indefinitely to further feedback and improvements with my volunteer time, and anyone interested in getting involved will be welcome to do so.

ImpactEdit

How will you know if the project is successful and you've met your goals? Please include the following targets and feel free to add more specific to your project:

  1. Number of total participants: N/A
  2. Number of articles improved: 50 precisions fixed at least, for the tests and startup phase in es.wikipedia (potentially, more than 1000 articles or annexes precisions could be fixed with future uses, not counting other projects)
  3. Number of media uploaded to Wikimedia Commons: N/A
  4. Number of media used on Wikimedia projects: N/A

ResourcesEdit

What resources do you have? Include information on who is the organizing the project, what they will do, and if you will receive support from anywhere else (in-kind donations or additional funding).

The programming and testing will be carried on totally by myself, with feedback of any wikimedians interested, of course. The code will be published, so other contributions can come through direct code improvements in the future. There are no additional donations or funding.

What resources do you need? For your funding request, list bullet points for each expense:

  • Previous analysis and design work (5 h)
  • Code for reading, analysis and two-level presentation of precisions used in a project (10 h)
  • Code for user input and configuration of community rules (5 h)
  • Code for individual/multiple options generation based on community rules and previous statistics (5 h)
  • Code for project interaction (moving, link fixing, removing) and logging of those actions (5 h)
  • Code for form for page or project requests, bug reports or general feedback for all my tools (3 h)
  • Testing and fixing to ensure proper operation (4 h)
  • Documentation and integration in my framework for logging, source code publishing, etc. (2 h)
Total: 39 hours, at a rate of 25 euros/hour (as in my previous grant requests): 975 euros
That would be completed with my volunteer time in complementary tasks and future maintenance.

EndorsementsEdit