{"id":304,"date":"2010-04-08T19:41:03","date_gmt":"2010-04-08T11:41:03","guid":{"rendered":"http:\/\/www.ssedro.com\/blog\/?p=304"},"modified":"2010-04-08T19:41:03","modified_gmt":"2010-04-08T11:41:03","slug":"username-dilemmas-with-web-2-0-apps","status":"publish","type":"post","link":"https:\/\/www.ssedro.com\/blog\/2010\/04\/08\/username-dilemmas-with-web-2-0-apps\/","title":{"rendered":"Username Dilemmas with Web 2.0 Apps"},"content":{"rendered":"

\"\"<\/a><\/p>\n

Our three-year edtech strategic plan was ratified by the board earlier this year. \u00a0Now that it is in place, we are moving ahead to make anytime, anywhere learning more feasible. \u00a0Part of our strategy to accomplish this is to move more of what we do into the cloud.<\/p>\n

When I arrived four years ago, we already had Blackboard and made Outlook Web Access available to staff. \u00a0Two years ago we added Sharepoint. \u00a0This year we began using our own Google Docs for Education account with some students and staff.<\/p>\n

In the past few months we have purchased corporate Wikispaces.net<\/a> and a campus subscription to Edublogs<\/a>. \u00a0I am trying to write up the SOP (Standard Operating Procedures) for both. \u00a0I keep getting stuck at the same point with both, so I hope you can help me think it through.<\/p>\n

While I’ve been at my school, student usernames have evolved over time. When I first arrived, we used the child’s first initial followed by their last name. \u00a0This sounds good, but in an Asian school with many duplicate names, this did not work well.<\/p>\n

Next we switched to using ID number as username. \u00a0This was somewhat successful. It is a challenge for younger students to remember the number, but it was workable. However, as we started to use Google Docs and other online tools we realized that it was inconvenient to not be able to tell who a student was from their username. \u00a0Seeing that you received an email or were asked to share a document with 936618 isn’t very useful. Their active directory account could have a different username than these other accounts, but it would be best if students have one username for all school accounts.<\/p>\n

The next year we switched to using last name followed by student ID. \u00a0This seemed like the perfect solution, especially for middle and high school where teachers have 150-200 students. \u00a0Those teachers were delighted.<\/p>\n

It was more challenging in the elementary school. \u00a0A surprising number of third graders cannot spell their last name. \u00a0Those with long names often made mistakes. \u00a0Memorizing their ID number was a challenge for many. \u00a0However, we soldiered on and it was working until we started using more Web 2.0 applications.<\/p>\n

The problem with web 2.0 apps was that we often ended up having both the child’s first and last name appear together online. \u00a0In the elementary school, our policy is that students’ work and photos may appear online with their first names as part of school projects. \u00a0With the student username containing their last name, and children often forgetting and using first names in their posts and comments, we were violating our own policy and Best Practice as stated on many Internet safety sites.<\/p>\n

We talked around and around on the idea of changing usernames to first name <\/em> followed by student I.D.<\/em> We love the idea for elementary students. \u00a0Students know how to spell their first names, and for a classroom teacher, even if they have a few students with the same first name, it would be easy to remember their ID numbers to tell them apart online.<\/p>\n

Middle and High school teachers were strongly opposed to the idea. \u00a0Given the large number of students they work with, they find it much more convenient to use last names for student identification. \u00a0Other problems arose around nickname versus official first name. \u00a0Many of our students, especially Korean students, use a nickname at school. \u00a0For example, in their passport a child’s first name may be Su Fang but at school she may have always gone by Clara. This leads to confusion and discomfort.<\/p>\n

We cannot use nickname instead of first name because many of our systems talk with each other by means of scripts. For example, Blackbaud and Powerschool exchange information and using nickname leads to duplicate accounts and other problems.<\/p>\n

To get around these problems, we came up with the idea of using first name<\/em> followed by student I.D.<\/em> in the elementary school, and then switching to last name<\/em> student ID <\/em>in middle and high school. \u00a0This could work. \u00a0Since some of our high school students already have a Google Docs for Education account, they won’t need to change over to a new account. \u00a0However, it means that any accounts children have in elementary school go away as they enter middle school. In Edublogs, deleting a child’s account deletes their blog as well. \u00a0Likewise, they’d lose their Wikispaces and other accounts.<\/p>\n

This also doesn’t help us with account deletion. \u00a0Ideally, when a student graduates, we want an easy way to find their account and delete it. \u00a0To do that, we would need to have their graduation year as part of their account. \u00a0For platforms such as Google Docs, that means it would need to be part of their username. \u00a0However, if we combine graduation year with student first or last name, we will end up with more than one child having the same username. If we try something such as graduation year followed by first<\/em> or last name<\/em> followed by ID number<\/em>, it will be so long students won’t be able to type it correctly.<\/p>\n

It seems we will need to make compromises, but we aren’t sure which will be the most workable. \u00a0How does your school deal with this dilemma?<\/p>\n

Photo by <\/em>Scott McLeod<\/em><\/a> used under a Creative Commons licensed.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

\n

Our three-year edtech strategic plan was ratified by the board earlier this year. Now that it is in place, we are moving ahead to make anytime, anywhere learning more feasible. Part of our strategy to accomplish this is to move more of what we do into the cloud.<\/p>\n

When I […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[72,23],"tags":[],"class_list":["post-304","post","type-post","status-publish","format-standard","hentry","category-systems","category-web2-0","odd"],"_links":{"self":[{"href":"https:\/\/www.ssedro.com\/blog\/wp-json\/wp\/v2\/posts\/304","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ssedro.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ssedro.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ssedro.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ssedro.com\/blog\/wp-json\/wp\/v2\/comments?post=304"}],"version-history":[{"count":8,"href":"https:\/\/www.ssedro.com\/blog\/wp-json\/wp\/v2\/posts\/304\/revisions"}],"predecessor-version":[{"id":332,"href":"https:\/\/www.ssedro.com\/blog\/wp-json\/wp\/v2\/posts\/304\/revisions\/332"}],"wp:attachment":[{"href":"https:\/\/www.ssedro.com\/blog\/wp-json\/wp\/v2\/media?parent=304"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ssedro.com\/blog\/wp-json\/wp\/v2\/categories?post=304"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ssedro.com\/blog\/wp-json\/wp\/v2\/tags?post=304"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}