Hey @Isaac, after talking today with Sage, he told me that we currently have 4 workers consuming tasks for programs and events dashboard, and 3 for wikieducational dashboard. So I guess that the max number of concurrent requests would be 7 (if all the workers are working at the same time). This shouldn't be too demanding for the API we think. Let us know if you have any other question/concern.

Also, as I was asking about this with our parsing folks, I found out that there's a newer endpoint that they're slowly migrating to that also solves the "need page title to get revision" problem! So you might want to use this form of URL to get the revision HTML: https://en.wikipedia.org/w/rest.php/v1/revision/1201413530/html (documentation)

hmm @Ragesoss could you help me to answer theses questions please? These are my thoughts, but please let me know if I'm not in the right path:

The process of importing ref counts is through (sidekiq) automatic tasks that calculate the "unscored" revisions for a course, and retrieve the ref counts for all of them. I think that depending on the size of the course and the kind of update (it could be a full or a daily update), the batch of requests would be considerably large. Does it answer your question?

Oh that's great. Thank you. I was doing something wrong when trying to retrieve the wiktionary article, that's why it didn't work for me.

I have another follow-up question.

Thank you for the explanation. It looks like I was looking at an incorrect version of the mwparserfromhtml/parse/article.py file and didn't notice that get_citations() was already implemented. That's great news. Will use that then!

I was playing around a bit with Parsoid and mwparserfromhtml, and I have a follow-up question.

Cool. That's great context. I'll work on this and let you know my thoughts/progress.

Hey all!
Yes, I'm currently working on improving how the "references added" metric is calculated in the Wiki Ed Dashboard. We already deployed it to staging and we're doing the last tests. Changes should be in production soon (likely by next week).

This is excellent news @Gabinaluz, your project will make many librarians and organizers happy! Wishing you all the best for this internship!

Hi @SEgt-WMF! Glad to hear you're excited about this project!
As you may noticed, this is part of my Outreachy internship, which ends at Mar 01, 2024.
I'm currently in the first half of the internship and, although I have had to make some adjustments to the schedule,
all indications are that we are on time, and that the project would be ready to go into production in early March.

Hey, I have a quick question again.
Currently, the sourcecode running in Toolforge is in my personal repo (https://github.com/gabina/wikimedia-references). I created that to test the app locally before deploying it to Toolforge.
I just noticed that Toolforge allows me to create a respository in https://gitlab.wikimedia.org/toolforge-repos.
This is the repo I created: https://gitlab.wikimedia.org/toolforge-repos/reference-counter
I would like to add files from the command line to that repo (instead of using my personal one), but I'm not able to make any git push because of the following error:

Thank you! That was great context. Really appreciate it.

Just FYI, there is a first version of the new references API deployed in Toolforge, you can make a request:

Thank you. Makes sense, I don't think this is high priority.

@Isaac thank you very much. I was checking the code!

Hey @Isaac, thank you! I was reading your suggestion, and it sounds good. Thank you for the detailed context! I'm still doing some research on the current behavior for the references added. Will back to you when I get a better idea of this.

Hi @Aklapper. My mentor specifically told me I was supposed to post my application materials as a Phabricator ticket. Should I remove it?