>I thought having some stats by api-user-agent from backend could help me
to understand these points and improve in the future my project in the best
way. What do you >think ? Is there a procedure that can I follow to have
these stats?
The stats would be the same, viviana, raw counts of call from your client
to the API, we do not have the ability to provide those upon requests but
it will be easy for you to gather the data from your client, there are open
source solutions like https://matomo.org/ that you can use to keep track of
stats on your end.

Thanks,

Nuria

On Fri, Mar 8, 2019 at 5:21 AM viviana paga <viviana.p...@hotmail.it> wrote:

> Hi Dan,
> thanks for your reply !
> I agree with you and in fact I do that in my front-end, but I think that
> it would be interesting have same general stats from Wikimedia too; in
> particular to understand which impact could my project have on general
> Wikimedia stats and which will be the behaviour of the users arriving to
> Wikimedia from my site (if the attended one or not).
> I thought having some stats by api-user-agent from backend could help me
> to understand these points and improve in the future my project in the best
> way. What do you think ? Is there a procedure that can I follow to have
> these stats?
> Many thanks,
> Viviana
>
> ------------------------------
> *Da:* Analytics <analytics-boun...@lists.wikimedia.org> per conto di
> analytics-requ...@lists.wikimedia.org <
> analytics-requ...@lists.wikimedia.org>
> *Inviato:* venerdì 8 marzo 2019 13:00
> *A:* analytics@lists.wikimedia.org
> *Oggetto:* Analytics Digest, Vol 85, Issue 2
>
> Send Analytics mailing list submissions to
>         analytics@lists.wikimedia.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.wikimedia.org/mailman/listinfo/analytics
> or, via email, send a message with subject or body 'help' to
>         analytics-requ...@lists.wikimedia.org
>
> You can reach the person managing the list at
>         analytics-ow...@lists.wikimedia.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Analytics digest..."
>
>
> Today's Topics:
>
>    1. Stats of mediawiki API / Access to non-public data (viviana paga)
>    2. Re: Stats of mediawiki API / Access to non-public data
>       (Dan Andreescu)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 7 Mar 2019 14:15:27 +0000
> From: viviana paga <viviana.p...@hotmail.it>
> To: "analytics@lists.wikimedia.org" <analytics@lists.wikimedia.org>
> Subject: [Analytics] Stats of mediawiki API / Access to non-public
>         data
> Message-ID:
>         <
> pr1pr06mb4698b179051d012c970a8928e4...@pr1pr06mb4698.eurprd06.prod.outlook.com
> >
>
> Content-Type: text/plain; charset="utf-8"
>
> Hi all,
>
> I’m working on a project about the sharing of the cultural heritage and,
> more in general, about the sharing of the open knowledges.
> In particular, I'm developing a webservice that use the Mediawiki API and
> I'd like to have some stats about the traffic of my api calls to the
> commons.wikipedia.org domain.
>
> More specifically,  I'd like to have:
> - the number of GET Requests by Api-User-Agent
> - the number of views/edit by Api-User-Agent
> - the stats of the Wikipedia traffic from inbound links by a specif domain
> or url
>
> Is this possible somehow to access to these limited non-public data?
> Is there a procedure that I can follow?
>
> The project is still in development, but next April we will release a beta
> version for a limited range of users-testers.
> The project is completely non-profit and it would provide maximum freedom,
> independence and privacy for its users.
> That’s why, I’d like to have from backend some stats by api-user-agent:
> that would guarantees the total privacy of the user, and, at the same time,
> the project could have some general stats about the traffic, the
> utilisation and its impact on the general Wikimedia stats.
>
> If someone among you is interested in these issues (open-shared-cultural
> heritage, open linked data), I’d like to keep in touch and, even, to
> propose to partecipate as tester in April.
>
> Thank you in advance,
> Kind regards,
> Viviana Paga
> https://www.linkedin.com/in/viviana-paga-42bb8b44/
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lists.wikimedia.org/pipermail/analytics/attachments/20190307/7f195cb4/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Thu, 7 Mar 2019 11:14:32 -0500
> From: Dan Andreescu <dandree...@wikimedia.org>
> To: "A mailing list for the Analytics Team at WMF and everybody who
>         has an interest in Wikipedia and analytics."
>         <analytics@lists.wikimedia.org>
> Subject: Re: [Analytics] Stats of mediawiki API / Access to non-public
>         data
> Message-ID:
>         <CA+aepCTUpeuH+KuygjKp4Sjs-BKgxh512=
> qby1k8+n47zmh...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Viviana,
>
> Great project!  The first thought I had looking at your question is that
> you can collect all the data you're asking about.  If your service is
> making API calls and people are clicking on Wikipedia links from your
> interface, you can just collect that information and process it yourself.
> Is there a reason you're not doing so?  It just sounds like the easiest way
> to get what you need.
>
> Dan
>
> On Thu, Mar 7, 2019 at 9:15 AM viviana paga <viviana.p...@hotmail.it>
> wrote:
>
> > Hi all,
> >
> > I’m working on a project about the sharing of the cultural heritage and,
> > more in general, about the sharing of the open knowledges.
> > In particular, I'm developing a webservice that use the Mediawiki API and
> > I'd like to have some stats about the traffic of my api calls to the
> > commons.wikipedia.org domain.
> >
> > More specifically,  I'd like to have:
> > - the number of GET Requests by Api-User-Agent
> > - the number of views/edit by Api-User-Agent
> > - the stats of the Wikipedia traffic from inbound links by a specif
> domain
> > or url
> >
> > Is this possible somehow to access to these limited non-public data?
> > Is there a procedure that I can follow?
> >
> > The project is still in development, but next April we will release a
> beta
> > version for a limited range of users-testers.
> > The project is completely non-profit and it would provide maximum
> freedom,
> > independence and privacy for its users.
> > That’s why, I’d like to have from backend some stats by api-user-agent:
> > that would guarantees the total privacy of the user, and, at the same
> time,
> > the project could have some general stats about the traffic, the
> > utilisation and its impact on the general Wikimedia stats.
> >
> > If someone among you is interested in these issues (open-shared-cultural
> > heritage, open linked data), I’d like to keep in touch and, even, to
> > propose to partecipate as tester in April.
> >
> > Thank you in advance,
> > Kind regards,
> > Viviana Paga
> > https://www.linkedin.com/in/viviana-paga-42bb8b44/
> >
> > _______________________________________________
> > Analytics mailing list
> > Analytics@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/analytics
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lists.wikimedia.org/pipermail/analytics/attachments/20190307/84a9d0e2/attachment-0001.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Analytics mailing list
> Analytics@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/analytics
>
>
> ------------------------------
>
> End of Analytics Digest, Vol 85, Issue 2
> ****************************************
> _______________________________________________
> Analytics mailing list
> Analytics@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/analytics
>
_______________________________________________
Analytics mailing list
Analytics@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/analytics

Reply via email to