Product Manager for The-Wikipedia-Library at the Wikimedia Foundation
Also User:Samwalton9 (WMF).
We can measure the impact of our logged-in experience redesign in other ways, such as:
Due to the necessity of adding invasive tracking to distinguish individual users, we have opted against tracking this data. We'll use our proxy measures of how many users initiate searches, access EZProxy content, and cite sources to evaluate the library's impact.
Full Text Finder is now correctly proxying outbound links.
Not sure when this happened but it no longer seems applicable.
@Amire80 do you plan to work on the remaining pieces of this?
Waiting on T282768.
@jsn.sherman I think we're ready to move forward with requesting that performance review. I'm reopening this and moving it back to ready to remind us to update the ticket.
Since the original bug seems to be solved, I'm marking this ticket as resolved.
Hooray! Yes, to start with editors will only ever receive this notification once. We've talked about other ways to remind folks they have access to the library but repeat notifications probably aren't the best method for that.
@XanonymusX We believe we've fixed this issue, would you be able to make a few edits on Beta wiki to check that you don't get this spam anymore?
Looks good to me :)
https://wikipedialibrary.idm.oclc.org/login?auth=production&url=https://doi.org still gives me a permission error.
I think the message could benefit both from rewording and from not being a red message box. There are other red boxes used in this tool to let you know that you're, for example, missing a subject or delivery list. Getting this red message makes it seem like it's also a blocker to sending the message. The text could be reworded to something like "Please check you don't have any unclosed HTML tags" instead of the vague "may have" language.
This is now working after a change on Orlando's end.
I was just doing a search and got sent through Full Text Finder. The links from FTF weren't going through EZProxy so I've put in a support request to change that because the setting for it isn't obvious to me.
I think there's a good chance this launch happens next quarter. Best case end of June.
Rather than create a new task I just reframed this one for the rest of the work on this :)
We think we've addressed the issues raised in this Spike - any additional work is going to be based on new observation.
Looking good to me!