User talk:Ocaasi

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Click here to leave me a message...

Leave me a message, ask me a question, share your thoughts, or concerns, leave me some WikiLove...

I am a new administrator. If you think I messed something up, please let me know where and how!

It is 2:57 PM where this user lives in the United States


Jake, I sent you one, in case you didn't see it. Johnbod (talk) 16:56, 11 April 2014 (UTC)

The Signpost: 09 April 2014

guided tours question

Hey Jake! I have a GuidedTours technical question for you. Do you know of anything you can use in place of gt.isPostEdit to check whether someone just pressed the Save button whether or not they actually made any changes to create a new revision?--Sage Ross (WMF) (talk) 19:23, 17 April 2014 (UTC)

Pinging Superm401 (talk · contribs), as Sage, I am not sure :). Sage Ross (WMF) (talk · contribs), Matt Flaschen, was the real brains behind TWA's code so if anyone knows it will be him. Ocaasi t | c 20:33, 17 April 2014 (UTC)
Unfortunately, I'm the one that suggested Sage talk to you. I couldn't think of a way; I just thought it might have come up in TWA. Superm401 - Talk 20:44, 17 April 2014 (UTC)

Ah, I see :/

Sage, what we did to avoid the no-edit Save was to insert the forced go-back message and reload the page's editing function.

// Fail gracefully post-save but not postedit
var postEditButtons = [];
if ( mw.config.get( 'wgAction' ) === 'view' && !gt.isPostEdit() ) {
        postEditButtons.push( {
                name: 'Click here to go back and make an edit',
                onclick: function() {
                        window.location.href = new mw.Uri().extend( { action: 'edit' } ).toString();
        } );

Not sure if that's useful to you, or if you have situations where you want them to save null edits. Cheers, Ocaasi t | c 21:03, 17 April 2014 (UTC)

Thanks. I already stole that feature, but was hoping for a little more flexibility. For the BeBold tour, the users edit and interact with a single page over the course of multiple edits, then follow links they created. If they follow the directions precisely, they will get through it, but if they improvise (such as, say, creating the correct link as well as another link), then they may end up needing to be redirected back to an edit page to try again but not actually needing to make an edit in order to follow the directions. Probably its an edge case, but I was hoping to find a way to account for it via tour logic (instead of more tedious instructional text).--Sage Ross (WMF) (talk) 17:25, 19 April 2014 (UTC)

WVS Montana

The WVS Montana link is a private Google Doc (FYI) czar  04:00, 19 April 2014 (UTC)

fixed the doc link Yes check.svg Done
(and the Rutgers link doesn't have contact info or a timeframe, and the Riverside app was due on the 10th, though it was just posted—might be worth clarifying on the page) czar  04:02, 19 April 2014 (UTC)
great catch! working on it Czar (talk · contribs) Ocaasi t | c 17:38, 19 April 2014 (UTC)

Books & Bytes - Issue 5

Wikipedia Library owl.svg The Wikipedia Library


Books & Bytes
Issue 5, March 2014
by The Interior (talk · contribs), Ocaasi (talk · contribs)

  • New Visiting Scholar positions
  • TWL Branch on Arabic Wikipedia, microgrants program
  • Australian articles get a link to librarians
  • Spotlight: "7 Reasons Librarians Should Edit Wikipedia"

Read the full newsletter

MediaWiki message delivery (talk) 17:54, 19 April 2014 (UTC)

Wikipedia Visiting Scholars and the University of Alabama

I am a professor at the University of Alabama who often works with its libraries' administration and who has contributed to Wikipedia since 2005. I'd like to help UA could get involved in the Wikipedia Visiting Scholars program, but I'm not sure where to start. The link to OCLC on the Visiting Scholars article ( does not work. Can you please advise me? Thanks. Jeremy Butler 11:34, 22 April 2014 (UTC)

Hello :)

Hi Jake, hope everything is fine! I sent you an email last week, and I really count on your answer. Thanks! --Elitre (WPS) (talk) 14:29, 22 April 2014 (UTC)

Sorry about the vandalism to LJN

Title says it, and it won't happen again! Vandalism normally doesn't happen from this account. Thebestofall007 (talk) 16:55, 22 April 2014 (UTC)

Education Program technical update, April 2014

Since the last update, development of the editor campaigns project has been continuing, and it's almost at the point that it will be useful to users running edit-a-thons and other non-course outreach events. (If you are planning such an event soon and would like to beta test it for tracking the contributions of newcomers, get it touch.) In the meantime, we've made a few small improvements and bug fixes to the Education Program extension:

Default course end date

The default end date for courses is now approximately six months in the future, instead of immediately. This will prevent the common problem where a user creates a new course page but does change the default dates, resulting in a course that is immediately considered "ended" and thus cannot be enrolled in.

Notifications when you get added to a course

Whenever a user gets added to a course by someone else, they will now receive a Notification.

Disabling individual student profiles

The student profile special page (Special:Student/Username, not to be confused with Special:Students) is a page that lists the courses a student editor is enrolled in, and is also supposed to list the articles that user is working on. However, the list of articles can include incorrect data in cases where an instructor or volunteer assigned the articles to the student editor. These profiles are being removed from the extension altogether. This change should go into effect Thursday, May 1. (Logs are still available to find out which courses a user is enrolled in.)

Article edit notifications for students coming soon

A nearly complete patch from Facebook Open Academy student Jeff Lloyd will add a new type of Notification: students will be alerted to edits made by others to the article(s) they are assigned (as well as the corresponding talk pages). Expect to see this feature within the next several weeks.

Duplicate courses and API deletion

Bugs in the course page creation process (now fixed) led in some cases to duplicate listings for the same course at Special:Courses. This happens when the same course page had two (or more) different course ID numbers. It is possible to clean up such duplicate entries using by making calls to the API. I've documented this process and written a Python script for it.

If you have feedback about these changes, or other questions or ideas related to course pages, please let Anna Koval or me know!--Sage Ross (WMF) (talk) 19:23, 22 April 2014 (UTC)

Subscribe or unsubscribe from future Wikipedia Education Program technical updates.

The Signpost: 23 April 2014

Creative Commons License