Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blog on Pro hitting 300,000 requests and noting design of service to prompt publication of previously private requests is working #1280

Open
FOIMonkey opened this issue Jul 13, 2022 · 10 comments
Assignees

Comments

@FOIMonkey
Copy link
Collaborator

FOIMonkey commented Jul 13, 2022

A suggested by @garethrees at 100k, relevant for 200,000.

We should mark this milestone when it comes by blogging to highlight good use of the service.

@FOIMonkey FOIMonkey changed the title Blog on Pro hitting 100,000 requests Blog on Pro hitting 200,000 requests Jul 13, 2022
@garethrees
Copy link
Member

garethrees commented Jul 13, 2022

Or for another angle I've just noticed we've recently crossed 100,000 requests previously private are now public:

irb(main):017:0> was_embargoed_and_now_public
=> 102121
irb(main):018:0> was_embargoed_and_still_embargoed
=> 26668

Couple of key points off the top of my head…

  • > 75% eventual publication is a very good thing
  • case studies of use – some impactful journalism; I think there was a pro user asking about plastic document wallets so interesting commercial/climate angle
  • We know there's a higher rate of non-classification, but I don't see that as a negative. Community helps the pro user (and other readers) through eventual classification.

@RichardTaylor
Copy link

75% eventual publication is a very good thing

Yes.

Many of the 25% of embargoed requests will still be within their initial, default, 3 month embargo period. That statistic would presumably be even more impressive/reassuring if requests made within the last 3 months were excluded.

I wonder if embargo extension is common or rare?

Community helps the pro user (and other readers) through eventual classification.

Theoretically "community", but in practice lots of the effort comes from a small number of people, many of whom are, or have been, WDTK volunteers. We know this kind of thing happens elsewhere eg. on Wikipedia but it's worth noting.

See also:

@FOIMonkey
Copy link
Collaborator Author

75% eventual publication is a very good thing

As Richard says, if the ones that are still embargoed are more recent, it could be that this would trend towards 100% if we were to turn new requests off for a bit.

In terms of commercial use, I've noticed this company use pro, (I'm guessing to gather the data for some of their products): https://neosypher.com/

@RichardTaylor RichardTaylor changed the title Blog on Pro hitting 200,000 requests Blog on Pro hitting 200,000 requests and design of service to prompt publication of previously private requests is working Jul 24, 2022
@RichardTaylor RichardTaylor changed the title Blog on Pro hitting 200,000 requests and design of service to prompt publication of previously private requests is working Blog on Pro hitting 200,000 requests and noting design of service to prompt publication of previously private requests is working Jul 24, 2022
@RichardTaylor
Copy link

We could mention things we're considering doing to encourage publication of even more Pro requests/responses:

@HelenWDTK
Copy link
Contributor

Flagging this for me to look at, as we should hit the 200k mark very soon (IIRC was just over 196k last time I checked).

@HelenWDTK HelenWDTK self-assigned this Jun 20, 2023
@HelenWDTK
Copy link
Contributor

We've made it! I'll get on this.

@HelenWDTK
Copy link
Contributor

The alternative is to hang fire until 250,000 - shouldn't take that long.

@HelenWDTK HelenWDTK changed the title Blog on Pro hitting 200,000 requests and noting design of service to prompt publication of previously private requests is working Blog on Pro hitting 250,000 requests and noting design of service to prompt publication of previously private requests is working Jul 3, 2023
@JenMysoc
Copy link
Member

Helen mentioned that we have hit this milestone for Pro now so it's worth investigating writing this post in the next cycle

@HelenWDTK
Copy link
Contributor

I think we hit 300,000 this week...

@HelenWDTK HelenWDTK changed the title Blog on Pro hitting 250,000 requests and noting design of service to prompt publication of previously private requests is working Blog on Pro hitting 300,000 requests and noting design of service to prompt publication of previously private requests is working Sep 27, 2024
@MyfanwyNixon
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants