Do you have an idea for the Case Wiki? Post it below! (You can sign and date your post by ending the post with:

--~~~~    (minus minus tilde tilde tilde tilde)

---

I was thinking that it would be almost trivial to start an interactive course evaluation system using the discussion sections. If you go to Category:Courses and navigate to MIDS485 you can see what I've set up as a model. --Grayden.maclennan 16:18, Jun 16, 2005 (EDT)

---

It would be nice to see an interwiki link to the EECS Wiki or perhaps even trying to convince them to merge into CaseWiki--They have no interest in merging so interwiki definitely --Alexander.converse 15:49, Jun 25, 2005 (EDT)

---

The VLINK color is very similar to plain text, maybe someone should tweak the VLINK color --Alexander.converse 23:07, Jul 1, 2005 (EDT)

---

What do people think of requiring licensing information with all media uploads. I really think we should keep track of license and copyright holder or if it's public domain how it came to be that way. If we do this we probably should make templates like wikipedia has for this. --Alexander.converse 20:06, Jul 18, 2005 (EDT)

---

Can the titles of subpages (like http://wiki.case.edu/I_need_to/Find_information) appear as "Find Information" instead of "I need to/Find Information"?--Jeremy.Smith 17:48, November 22, 2005 (EST)

---

I think pages begining with ADS in their titles (like ADS OpalforNonAdministrators) should be renamed to Active_Directory_* to avoid conflicts with the default adblock plus ruleset --129.22.169.201 12:08, December 2, 2005 (EST)

---

Warning: Selector expected. Ruleset ignored due to bad selector. Source File: http://wiki.case.edu/index.php?title=MediaWiki:Case.css&action=raw&ctype=text/css&smaxage=18000 Line: 1 main.css bugs: line 88 needs a semi-colon.... "Warning: Expected end of value for property but found 'margin'. Error in parsing value for property 'color'. Declaration dropped. Source File: http://wiki.case.edu/skins/case/main.css Line: 89" Line 127 needs a colon "Warning: Expected ':' but found '0p'. Declaration dropped. Source File: http://wiki.case.edu/skins/case/main.css Line: 127" Line 396 extra space "Warning: Expected end of value for property but found 'em'. Error in parsing value for property 'margin'. Declaration dropped. Source File: http://wiki.case.edu/skins/case/main.css Line: 396" Line 454 display spelled wrong "Warning: Unknown property 'dispaly'. Declaration dropped. Source File: http://wiki.case.edu/skins/case/main.css Line: 454"

Fixed.--Gregory.Szorc 11:47, April 4, 2006 (EDT)

---

How about a feed for recent changes of any article except articles in a specified category? ---Andrew.Witte 17:17, October 5, 2006 (EDT)

That should definitely be doable. I'll look into it next time I sit down and play with WikiFeeds. --Gregory.Szorc 01:04, October 6, 2006 (EDT)

Contents 1 Regarding User Names 2 Skin Design 3 Category graphs 4 Naming 5 Nuke Tasks Extension?

[edit] Regarding User Names

It has been proposed that the usernames are the same case as our actual names.

1. MediaWiki treats all keywords as case-sensitive after the first character. John.Smith would be different from John.smith. Things get confusing when you have a capital letter in the middle of a name. It might be harder to find people when that is done.
2. Firstname.lastname is uniform. The first character will always be capitalized. All those following will not.

If enough people clamor for this change, it can be made. If not, we will settle for the current implementation.

--Gregory.szorc 10:29, Jul 1, 2005 (EDT)

New usernames now have the first letter of every name and initial capitalized. Old usernames will be manually converted to the new format.

Firstname.Lastname is now the format. If you have a middle initial, M, then the format will be Firstname.M.Lastname. --Gregory.szorc July 28, 2005 11:45 (EDT)

Some comments have been made about not using abc123 as your user name. The reason we don't do this is because the university is moving away from using your network id as a public identifier. This directive comes straight from the desk of the Chief Security Officer. When you log into the wiki, we take your network id and do an LDAP look-up of your primary e-mail address, which is in the format firstname.lastname@case.edu. These e-mail addresses are globally unique. There is a one-to-one mapping of network id's to e-mail addresses of this format. This e-mail address will always be valid, even as an alumni. We tell the wiki that the e-mail address is your username and it does what it does. During the account creation phase, we also populate the name and e-mail fields for that username with the values listed in the LDAP. The only problem left is that of capitalization. MediaWiki does lots of voodoo when it comes to capitalization. Initially, when integration with the single sign-on service was done, I tried to follow correct capitalization with the usernames. Unfortunately, MediaWiki makes lots of redundant calls to the capitalization functions and was overriding my changes. If correct capitalization was followed, we would also have issues with people finding pages for users like John.McCormick because John.McCormick is different from John.Mccormick. It is much easier to say the only letter capitalized is the first and everything after is lower case. --Gregory.szorc 15:59, Jul 10, 2005 (EDT)

[edit] Skin Design

My opinion on the skin design and color scheme keeps going back and forth. Anyone out there care to chime in? --Gregory.Szorc 02:21, April 5, 2006 (EDT)

[edit] Category graphs

Can they be antialiased?

They used to be. I'm not sure why it stopped working. --Gregory.Szorc 12:08, April 21, 2006 (EDT)

Fixed it! The graphs look beautiful now! --Gregory.Szorc 14:04, April 24, 2006 (EDT)

[edit] Naming

Is there any thing we can do to help persuade people to name pages descriptively? Many classes appear to be putting up pages, but there is nothing on the page that would even suggest it is related to Case. I would think their content may be in jeopardy, since no one knows what context the information is being used. --Brian.C.Gray 12:42, August 21, 2006 (EDT)

Put the markup {{cleanup title}} at the top of the page.

--Jeremy.Smith 13:20, August 21, 2006 (EDT)

This is really where a wiki farm would come in handy. The Case Wiki is great for a shared resource for courseware (notes, etc), but for individual class groups, we really need something that can be isolated from other parts of the site. A compromise until the wiki farm is deployed is the creation of a courses namespace. All per-course specific material should belong there. All information for general courses can still go in the main namespace. In both cases, we definitely need a more formal naming structure, such as Dept Code/Course Number/Semester/Title. Still, that can get confusing. Until then, we have our cleanup templates which can be placed on poorly-formed articles. --Gregory.Szorc 21:03, August 21, 2006 (EDT)

[edit] Nuke Tasks Extension?

The Tasks extension (click the Tasks tab on an article) hasn't seen much use. It also doesn't filter content through the spam filters before saving, which explains why spammers are getting through. I'm seriously thinking about removing it. Does anyone have any objections? --Gregory.Szorc 00:52, September 14, 2006 (EDT)

I nuked it a few days ago. Nobody has yet complained. --Gregory.Szorc 01:40, September 20, 2006 (EDT)