Jump to content

Grants:Programs/Wikimedia Community Fund/Rapid Fund/Supporting the Puno Quechua Language and its Communities (ID: 22828248)/Final Report

From Meta, a Wikimedia project coordination wiki
Elwinlhq
Supporting the Puno Quechua Language and its Communities
02 December 2024 - 31 March 2025
Report ID: 11556
Report status: Under review
Report due date: 30 April 2025
Grant ID: G-RF-2409-17167
Amount funded: 4475.24 EUR, 4998.66 USD
Amount spent: 4347.4 EUR
Rapid Fund Final Report

Application type: Standard application

Part 1: Project and impact

1. Describe the implemented activities and results achieved. Additionally, share which approaches were most effective in supporting you to achieve the results. (required)

Project Implementation Regards the general project implementation, we started by requesting rights for a bot user (link), so we can ingest hundreds and thousands of lexemes. In the process, we could not make the QichwaBot work. So we decided to use my personal account to ingest periodically a certain amount of lexemes (based on the curation of the lexemes from Qichwabase), it worked, and it is working like this since then. The migration of Puno Quechua lexemes into Wikidata Lexemes has been done considering that lexemes have at least one sense. Furthermore, we created and collected around 2000 sentences in Puno Quechua language to be uploaded on Wikisource, currently they are stored in a spreadsheet (link) for easy manipulation, while we advance the inclusion of the Puno Quechua Wikisource (Wikiqillqa).

Project Implementation: Online workshops During the implementation of the project, we have run several workshops, both on-site and online. On-site in the Puno region of Peru, see (Rimayninchisrayku), and online in partnership with the ELP organisation on transcribing language recordings (Transcribing with ELAN); these transcriptions and recordings can later be uploaded to Wikimedia Commons and Wikisource and linked as usage examples for lexemes.

Project Implementation: Localisation of tools In our efforts to localise tools, we contacted tool developers and asked for their assistance in localising tools for the Puno Quechua language. For example, to localise the Luthor tool, we first translated it on translatewiki.net (Luthor). Then we wanted to link the tools to Puno Quechua or (in the default case) Quechua (Runa Simi), but this was not possible due to the non-existence of a Wikisource project for the Quechua language. As a result, we started the process of creating a Wikisource project for the Puno Quechua language (Wikiqillqa), which is a work in progress. Then we translated the tool (Wikidata Lexeme Forms) to be used in the Quechua language. Finally, the manual for the Record Wizard of the LinguaLibre tool is available in Quechua.

Dissemination We submitted a paper to the SIMBig 2024 conference and it was accepted. The paper describes our approach to integrating Puno Quechua into Wikidata lexemes, and it will be published in the proceedings of the conference during 2025. In terms of the Wikimedia community, we planned to disseminate our results at Wikimania, but we did not get a scholarship. Therefore, we plan to write a diff diff article about our results.

2. Documentation of your impact. Please use space below to share links that help tell your story, impact, and evaluation. (required)

Share links to:

  • Project page on Meta-Wiki or any other Wikimedia project
  • Dashboards and tools that you used to track contributions
  • Some photos or videos from your event. Remember to share access.

You can also share links to:

  • Important social media posts
  • Surveys and their results
  • Infographics and sound files
  • Examples of content edited on Wikimedia projects

https://wikisource.org/wiki/Main_Page/Punu_Simi https://wikisource.org/wiki/Category:Qillqaq https://translatewiki.net/wiki/Translating:Wikidata_Lexeme_Forms https://translatewiki.net/w/i.php?title=Special:Translate&group=wikidata-lexeme-forms&language=qu&filter=&action=translate https://translatewiki.net/w/i.php?title=Special:Translate&action=proofread&group=wikimedia-tools-luthor&language=qu&filter= https://www.instagram.com/p/DFqI7VTM1Vp/?utm_source=ig_web_copy_link&igsh=MzRlODBiNWFlZA== https://docs.google.com/spreadsheets/d/1DFLP-GHAgeFE1PnNq75PYNNQKNOINoKRiJxNhjy7lxw/edit?usp=sharing https://commons.wikimedia.org/wiki/File:LL-Q7260479_(qxp)-Elwinlhq-uyachiy.wav https://commons.wikimedia.org/wiki/File:LL-Q7260479_(qxp)-Elwinlhq-usuchiy.wav https://www.wikidata.org/wiki/Lexeme:L1322212 https://www.wikifunctions.org/wiki/Wikifunctions:Catalogue/Natural_language_operations/Quechua https://www.wikifunctions.org/wiki/Wikifunctions:Catalogue/Natural_language_operations https://lexeme-forms.toolforge.org/template/quechua-verb/ https://www.wikidata.org/wiki/Wikidata_talk:Wikidata_Lexeme_Forms/Quechua

Additionally, share the materials and resources that you used in the implementation of your project. (required)

For example:

  • Training materials and guides
  • Presentations and slides
  • Work processes and plans
  • Any other materials your team has created or adapted and can be shared with others

https://codelookup.toolforge.org/qxp https://translatewiki.net/ https://lexeme-forms.toolforge.org/ https://lingualibre.org/wiki/Help:Main/en https://meta.wikimedia.org/wiki/Lingua_Libre/es https://lingualibre.org/wiki/Help:RecordWizard_manual/qu Qichwabase Import: https://github.com/kristbaum/QichwabaseImport The RecordWizard of LinguaLibre in Quechua: https://lingualibre.org/wiki/Help:RecordWizard_manual Report and dissemination material: https://commons.wikimedia.org/wiki/Category:LinguaLibre_in_Puno Produced Quechua sentences: https://docs.google.com/spreadsheets/d/1DFLP-GHAgeFE1PnNq75PYNNQKNOINoKRiJxNhjy7lxw/edit?usp=sharing

3. To what extent do you agree with the following statements regarding the work carried out with this Rapid Fund? You can choose “not applicable” if your work does not relate to these goals. Required. Select one option per question. (required)

Our efforts during the Fund period have helped to...
A. Bring in participants from underrepresented groups Strongly agree
B. Create a more inclusive and connected culture in our community Strongly agree
C. Develop content about underrepresented topics/groups Strongly agree
D. Develop content from underrepresented perspectives Strongly agree
E. Encourage the retention of editors Strongly agree
F. Encourage the retention of organizers Strongly agree
G. Increased participants' feelings of belonging and connection to the movement Strongly agree
F. Other (optional)

Part 2: Learning

4. In your application, you outlined some learning questions. What did you learn from these learning questions when you implemented your project? How do you hope to use this learnings in the future? You can recall these learning questions below. (required)

You can recall these learning questions below: The main goal of this proposal is to open up opportunities for Quechua communities to contribute to the Wikimedia ecosystem. To do this, we focus mainly on the technical aspect, such as modelling lexemes, preparing resources, and setting up tools. Then, we prepare online workshops and training sessions for capacity building of the quechua communities to facilitate their contributions. Some learning points are:

  • To what extent are the Wikimedia tools easy lo localize for under-resourced languages
  • What improvements can be proposed for the Wikimedia tools
  • Are there other Quechua communities willing to join our approach

Opening up opportunities for new contributors is sometimes very difficult, even if you want to contribute. For example, during the workshops, a Quechua user wanted to contribute to Wikidata, but she faced a huge barrier because the Wikidata interface was not easy for her to understand and not user-friendly.

It would be the case that most projects and tools (mostly) support established languages and are only available in specific languages.

What we proposed with our approach was to localise tools for an under-represented language, so that speakers of that language can contribute to the Wikimedia ecosystem without having to deal with complex interfaces or tools. By focusing on the technical parts; ingesting content in/about the Puno Quechua language and localising the tools to facilitate contribution in these languages, we support easy contribution. For example, by using the Wikidata lexeme forms which, given a Quechua verb, generate its conjugations, a user only needs to validate the conjugations generated by the tool.

Wikimedia tools are not easy to localise, they are very complex in terms of code, translations and project integration. For example, you can translate the Luthor tool into Quechua, but it will not work for the Quechua language because there needs to be a Quechua Wikisource project, which does not yet exist. The improvement we could suggest is to take small communities into account when developing tools and approaches.

During the course of our project, there were two Quechua communities from Huanuco (Peru) and Cuzco (Peru) that are very interested in following our approach, and we would like to support the integration of their languages into the Wikimedia ecosystem.

5. Did anything unexpected or surprising happen when implementing your activities? This can include both positive and negative situations. What did you learn from those experiences? (required)

Example sentences help users to understand and comprehend the meaning of a lexeme on Wikidata Lexemes. In this context, we saw that the Luthor tool works well for well-represented languages, and we decided to try it with Quechua languages. After trying to read the tool's documentation, we translated it and then contacted its developer. We were told that the tool only works with languages that have a Wikisource project, which is not the case for the Quechua languages. It was a moment of realisation and analysis: to what extent do the tools mainly support well-represented languages? This is a question that will be answered in the future, although we can see that the distribution of total number of lexemes on Wikidata Lexemes shows that 91% of the languages have less than 100 lexemes.

On the other hand, we were able to implement some Wikifunctions for the Quechua language, it was not planned in the project, but it supports the semi-automatic task of generating verb conjugations on Wikidata Lexeme forms. In this case, we were told to apply for Functioneer status on Wikifunctions (discussion) so that we can manage the integration of more features that can facilitate contributions from users in the Quechua communities.

6. What is your plan to share your project learnings and results with other community members? If you have already done it, describe how. (required)

Our plan is to connect with Wikimedia's Latin American affiliates and share our approach to integrating other indigenous languages into Wikidata Lexemes. For example, Wikimedistas de Bolivia, Wikimedistas de Peru, Wikimedia Chile and others. We also plan to meet informally at the Wikimedia Hackathon 2025.

Part 3: Metrics

7. Wikimedia Metrics results. (required)

In your application, you set some Wikimedia targets in numbers (Wikimedia metrics). In this section, you will describe the achieved results and provide links to the tools used.

Target Results Comments and tools used
Number of participants 45 40
Number of editors 10 5
Number of organizers 1 1
Wikimedia project Target Result - Number of created pages Result - Number of improved pages
Wikipedia
Wikimedia Commons 1000 741 741
Wikidata 4000 458 458
Wiktionary
Wikisource 1 5 10
Wikimedia Incubator
Translatewiki 141 141
MediaWiki
Wikiquote
Wikivoyage
Wikibooks
Wikiversity
Wikinews
Wikispecies
Wikifunctions or Abstract Wikipedia 41 41

8. Other Metrics results.

In your proposal, you could also set Other Metrics targets. Please describe the achieved results and provide links to the tools used if you set Other Metrics in your application.

Other Metrics name Metrics Description Target Result Tools and comments
2000 As our aim was to ingest around 4000 pages between diverse Wiki projects, we did not anticipate that the Luthor tool was not working for the Quechua language. The task was to import around 2000 sentences into Wikisource and add them to Wikidata Lexemes as usage examples. The sentences are collected, curated, and can be seen here. They will be imported in the near future as usage examples for lexemes.

9. Did you have any difficulties collecting data to measure your results? (required)

No

9.1. Please state what difficulties you had. How do you hope to overcome these challenges in the future? Do you have any recommendations for the Foundation to support you in addressing these challenges? (required)

Part 4: Financial reporting

[edit]

10. Please state the total amount spent in your local currency. (required)

4347.4

11. Please state the total amount spent in US dollars. (required)

4998.66

12. Report the funds spent in the currency of your fund. (required)

Provide the link to the financial report Budget Report


12.2. If you have not already done so in your financial spending report, please provide information on changes in the budget in relation to your original proposal. (optional)


13. Do you have any unspent funds from the Fund?

No

13.1. Please list the amount and currency you did not use and explain why.

N/A

13.2. What are you planning to do with the underspent funds?

N/A

13.3. Please provide details of hope to spend these funds.

N/A

14.1. Are you in compliance with the terms outlined in the fund agreement?

Yes

14.2. Are you in compliance with all applicable laws and regulations as outlined in the grant agreement?

Yes

14.3. Are you in compliance with provisions of the United States Internal Revenue Code (“Code”), and with relevant tax laws and regulations restricting the use of the Funds as outlined in the grant agreement? In summary, this is to confirm that the funds were used in alignment with the WMF mission and for charitable/nonprofit/educational purposes.

Yes

15. If you have additional recommendations or reflections that don’t fit into the above sections, please write them here. (optional)


Review notes

[edit]

Review notes from Program Officer:

N/A

Applicant's response to the review feedback.

N/A