Jump to content

Grants:Programs/Wikimedia Community Fund/Rapid Fund/ReCite Proof-of-Concept:Source Inspector (ID: 24029753)

From Meta, a Wikimedia project coordination wiki
statusFunded
ReCite Proof-of-Concept: Source Inspector
request or grant IDG-RF-2609-23706
proposed start date2026-11-15
proposed end date2027-10-15
requested budget (local currency)5000 USD
requested budget (USD)5000 USD
amount funded (USD)5000
amount funded (local currency)5000 USD
grant typeIndividual
funding regionUSCA
decision fiscal year2026-27
applicantconnieatwork
organization (if applicable)N/A
Review Final Report

Applicant details

[edit]
Main Wikimedia username. (required)

connieatwork

Organization

N/A

If you are a group or organization leader, board member, president, executive director, or staff member at any Wikimedia group, affiliate, or Wikimedia Foundation, you are required to self-identify and present all roles. (required)

N/A

Describe all relevant roles with the name of the group or organization and description of the role. (required)

Main proposal

[edit]
1. State the title of your proposal. This will also be the Meta-Wiki page title.

ReCite Proof-of-Concept: Source Inspector

2. and 3. Proposed start and end dates for the proposal.

2026-11-15 - 2027-10-15

4. What is your tech project about, and how do you plan to build the product?

Include the following points in your answer:

  • Project goal and problem you solve
  • Product strategy or project roadmap
  • Technical approach (infrastructure, tech stack, key tools and services)
  • Integrations or dependencies (if any)

Project goal and problem to solve

This larger goal of this project is ultimately to advance a front-end possibility related to the ReCite project, which proposes a curated reference database for reusable, reliable citations ([1]). As part of this ReCite effort, originally funded by WikiCred.org, I've developed a front-end Javascript tool called "ReCite Source Inspector." 

The ReCite Source inspector looks at a Wikipedia article's source in order to 1) display relevant wikitext around references, 2) show a suggested wikitext replacement that includes corrections based upon its presence in a Zotero library as well as some kind of ID linkage to the library and, 3) show potentially related reliability information about the source (e.g. judgments about the source's outlet made on enRSP). More information can be found at [2].

The tool is currently not ready for public use, and so for this grant, I would like to bring it to that level as well as to release the code around it.

As a secondary goal, I would also like to use this opportunity to reflect upon practices in using AI coding supports for the development of Wikipedia tools; these reflections would be with the final grant report as well as on-Wiki (at least within the ReCite Source Inspector tool description if not perhaps within the [3] work)

Product strategy or project roadmap

I'd like to develop this tool further to an adequate proof-of-concept state to support the three phases of development described in the ReCite proposal ([4]) along with currently three possibilities for front-end solutions ([5]). By the end of this grant, we can determine whether or not the Inspector needs to be developed further, as a tool that provides long lasting benefits to Wikimedian communities or if its purpose has been served and other front-end solutions are better suited to the task.

Technical approach (infrastructure, tech stack, key tools and services)

In addition to the documentation provided about the Source Inspector ([6]), I also plan to experiment around practices around using different AI coding supports. Currently the tool was built with Claude Code, and starting this week, my plan is also to introduce Gemini and hopefully also Liftwing for comparisons in different roles on different branches (e.g. QA).  

Integrations or dependencies (if any)

To work fully, ReCite Source Inspector requires a proxy via Toolforge in order not to violate CSP policies. The proxy isn't required for the tool to operate but so that it can gain additional information at an external Zotero.org library. This proxy/access was created in late August: https://github.com/connieimdialog/ReCite-Temp.  

The Inspector is also making use of Cite Unseen's classifications of sources at [7].

5. What is the expected impact of your project, and how will you measure success?

Include the following points in your answer:

  • Milestones and progress tracking
  • Project impact and success metrics

Project impact and success metrics

The impact this tool ultimately seeks is to advance discussion and possibilities regarding the usage of more reliable citations across Wikimedia. Thus, many of the project's impacts are potential, as the goal is not strictly about the usage of the Inspector tool itself, but trying to advance a path regarding reusable citations. In other words, while usage statistics of the tool itself are interesting, they are not an end goal in themselves. Successes for this project could be several, ranging from positive feedback and usage of the tool to constructive criticism about formats around citations in Wikipedia broadly (and a call to abandon the tool).

Additional potential impacts could include contributions to standardization around practices and considerations related to the use of AI in tool building.

At a minimum, this project will achieve a steady, public state for the Source Inspector tool and aim for its adoption/usage among 50 users in order to gain the feedback necessary to move forward.

Milestones and progress tracking

  • Source Inspector Tool - public ready state.  Includes shifting the tool from active development to stable, public usability as well as the publication of private Github repo.
  • Source Inspector Tool and ReCite sustainability. Includes decisions on whether and how to try and sustain the tool itself, continued progress on the larger ReCite proposal.
6. Who is your target audience, and how have you confirmed there is demand for this project? How did you engage with the Wikimedia community?

Include the following points in your answer:

  • Project demand and target audience description
  • Links to interaction(s) with Wikimedia community
  • Evidence from community consultation such as the [Community Wishlist]

The target audiences related to this project are people associated with the WikiCite ([8]) and WikiCred ([9]) communities. Secondary interest may also exist within WikiProject AI Tools ([10]). Interest in this project concept, which was born during WikiCredCon 2026 in April, led to the grant that allowed me to develop the ReCite concept.

My interactions with this community on this project have mostly been via a Google doc, email, and WikiCred WhatsApp groups, but I have been moving the work to open spaces. For example, I have started to have some public feedback via the Meta pages I created like this one: meta.wikimedia.org/wiki/Talk:WikiCite/ReCite/Data_Modeling.

7. How will your team predict and manage potential user security and privacy risks, and what risks do you currently see?

Include the following points in your answer:

  • The level of in-house or consulted security and privacy expertise you will have available to you during delivery of this project
  • How your development, testing, and deployment processes mitigate the introduction of unnecessary security or privacy risks

As a privacy professional (International Association of Privacy Professionals, CIPP/US and AIGP), I am very conscious that privacy and security concerns need to be 'baked in' from a project's inception.  Examples of this thinking: the ReCite Source Inspector tool has no need of collecting personal information, Zotero access is either via a public API or a guarded key, and the tool does not edit any pages directly.

As part of my secondary goal (reflection on the use of AI tools in software development), I will be testing the introduction of a QA plan specifically to address privacy and security issues as well. This should help mitigate risks as the tool continues to develop.

8. Who is on your team, and what is your experience?

Include the following points in your answer:

  • Your experience as a developer, relevant past projects
  • Wikimedia SUL (developer), Gerrit, Github, Gitlab or other relevant public account handles
  • Other team members, their roles and expertise

My experience

Wikimedia and relevant handles

9. How will the project be maintained long-term?

Include the long-term maintenance plan with maintainer(s) in your answer. If you expect the long-term maintenance to incur expenses, please list those and the plan for long-term expense coverage.

As mentioned in the project strategy section, the goal of this proposal would be to determine whether or not long-term maintenance is required.  

As for now, the script and documentation remain in Wikispace and the code would progress to public spaces that don't cost anything whether on Github or Toolforge.  

10. Under what license will your code be released, and how will you ensure the product is well documented?

Include the following points in your answer:

  • Code license and compatibility with Wikimedia projects
  • Documentation plan

Code for this project is currently released or planned to be released under Apache 2.0.

Documentation is published on Meta-Wiki and English Wikipedia under CC licenses.

11. Will your project depend on or contribute to third-party tools or services?

This project relies on Zotero.org as well as the other tools mentioned above.  

12. Is there anything else you’d like to share about your project? (optional)

The ability to develop this project, as well as the larger proposal, will take more funding than a rapid grant can provide; I will also be pursuing other funding sources to supplement.  However, I think that this concept is only worth pursuing if it provides something useful related to citations for different Wikimedia communities, which is why I have already contributed volunteer hours to its development and welcome this great opportunity to get feedback.  

Thanks for any thoughts and considering!

Budget

[edit]
13. Upload your budget for this proposal or indicate the link to it. (required)
14. and 15. What is the amount you are requesting for this proposal? Please provide the amount in your local currency. (required)

5000 USD

16. Convert the amount requested into USD using the Oanda converter. This is done only to help you assess the USD equivalent of the requested amount. Your request should be between 500 - 5,000 USD.

5000 USD

By submitting your proposal/funding request you confirm that you have read and agree to the Application Privacy Statement, WMF Friendly Space Policy, and the Universal Code of Conduct.

Yes

Endorsements and Feedback

[edit]

Please add endorsements and feedback to the grant discussion page only. Endorsements added here will be removed automatically.

Community members are invited to share meaningful feedback on the proposal and include reasons why they endorse the proposal. Consider the following:

  • Stating why the proposal is important for the communities involved and why they think the strategies chosen will achieve the results that are expected.
  • Highlighting any aspects they think are particularly well developed: for instance, the strategies and activities proposed, the levels of community engagement, outreach to underrepresented groups, addressing knowledge gaps, partnerships, the overall budget and learning and evaluation section of the proposal, etc.
  • Highlighting if the proposal focuses on any interesting research, learning or innovation, etc. Also if it builds on learning from past proposals developed by the individual or organization, or other Wikimedia communities.
  • Analyzing if the proposal is going to contribute in any way to important developments around specific Wikimedia projects or Movement Strategy.
  • Analysing if the proposal is coherent in terms of the objectives, strategies, budget, and expected results (metrics).

Endorse


This is an automatically generated Meta-Wiki page. The page was copied from Fluxx, the web service of Wikimedia Foundation Funds, where the user has submitted their application. Please do not make any changes to this page because all changes will be removed after the next update. Use the discussion page for your feedback. The page was created by CR-FluxxBot.