<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="/topics-files/atom2xhtml.xsl" type="text/xsl"?>
<!-- This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers. -->
<feed xmlns="http://www.w3.org/2005/Atom"
><title
>Blog@Case Topics: case blog</title
><link rel="self" href="http://blog.case.edu/topics/case%20blog"
 /><id
>http://blog.case.edu/topics/case%20blog</id
><category term="case blog" label="case blog"
 /><link rel="related" href="http://blog.case.edu/topics/mainblog" title="mainblog"
 /><link rel="related" href="http://blog.case.edu/topics/blog@case" title="blog@case"
 /><link rel="related" href="http://blog.case.edu/topics/blog" title="blog"
 /><link rel="related" href="http://blog.case.edu/topics/linkblog" title="linkblog"
 /><link rel="related" href="http://blog.case.edu/topics/blog@case%20developments" title="blog@case developments"
 /><link rel="related" href="http://blog.case.edu/topics/weblog%20tech" title="weblog tech"
 /><link rel="related" href="http://blog.case.edu/topics/syndicated%20feeds" title="syndicated feeds"
 /><link rel="related" href="http://blog.case.edu/topics/blogs%20in%20academia" title="blogs in academia"
 /><link rel="related" href="http://blog.case.edu/topics/xml" title="xml"
 /><link rel="related" href="http://blog.case.edu/topics/failures%20of%20technology" title="failures of technology"
 /><link rel="related" href="http://blog.case.edu/topics/case" title="case"
 /><contributor
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></contributor
><updated
>2006-07-27T18:42:19Z</updated
><entry
><title
>I'll Be Giving a Presentation Tomorrow on Blogging</title
><link href="http://blog.case.edu/jeremy.smith/2006/07/26/ucite_blogging_presentation"
 /><id
>http://blog.case.edu/jeremy.smith/2006/07/26/ucite_blogging_presentation</id
><published
>2006-07-26T19:37:00Z</published
><updated
>2006-07-27T18:42:19Z</updated
><category term="blog" label="blog"
 /><category term="blog@case" label="blog@case"
 /><category term="blogs in academia" label="blogs in academia"
 /><category term="case blog" label="case blog"
 /><category term="mainblog" label="mainblog"
 /><category term="presentation" label="presentation"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>Tomorrow at noon in the 
<a href="http://wiki.case.edu/Herrick_Room">Herrick Room</a> at 
<a href="http://wiki.case.edu/Allen_Memorial_Medical_Library">Allen Library Building</a>, I'll be giving a presentation for 
<a title="Case Western Reserve University" href="http://www.case.edu/provost/UCITE">UCITE</a>. From the 
<a title="UCITE: Event Description" href="http://www.case.edu/cgi-bin/AuroraCGI/ucite/desc.cgi?curyear=2006&amp;curmonth=7&amp;curday=27">description</a>:
<blockquote>This is the age of the internet and those who are most adept at using it are the ones who get noticed. Personal and professional websites and blogs and other internet formats can make more people aware of your work and raise your profile, provided those are done well enough and take advantage of the kinds of things that search engines use when people look for information.</blockquote>Stop on by if you want to see it. I'll be posting the slides and my notes here afterwards. 
<strong>Update:</strong> The slides are online at 
<a title="Blogging at Case" href="http://blog.case.edu/jms18/presentations/2006/07/blogging/">Blogging at Case</a>. Notes for the slides are available in the print out version. Audio of the presentation should be coming soon (
<a title="Finagle's law - Wikipedia, the free encyclopedia" href="http://en.wikipedia.org/wiki/Finagle%27s_law">Murphy willing</a>).</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>I'm Doing It!</title
><link href="http://blog.case.edu/jeremy.smith/2006/07/21/im_doing_it"
 /><id
>http://blog.case.edu/jeremy.smith/2006/07/21/im_doing_it</id
><published
>2006-07-21T19:23:59Z</published
><updated
>2006-07-21T19:56:44Z</updated
><category term="And Now for Something Different" label="And Now for Something Different"
 /><category term="blog@case" label="blog@case"
 /><category term="case blog" label="case blog"
 /><category term="mainblog" label="mainblog"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>Just helping to 
<a title="We Can Do It! - brian's blog" href="http://blog.case.edu/bmb12/2006/07/we_can_do_it">take back</a> 
<a href="http://planet.case.edu">Planet Case</a>. You may have seen the announcement about 
<a title="Blog@Case: Trackback is Back" href="http://blog.case.edu/news/2006/07#trackback_is_back">spammers and trackback</a>. Our increasingly complex anti-spam setup really deserves a blog entry to describe it. It's getting surreal. I, also, 
<a title="Apple Campus Rep: Kyle Niemeyer: First Apple-related post: Putting videos on Video iPods" href="http://blog.case.edu/apple/2006/07/18/first_applerelated_post_putting_videos_on_video_ipods#23440">promised to do an entry on my switch from Windows to Apple</a>. Maybe I'll do that entry today. Have you seen that 
<a title="Apple Campus Rep: Kyle Niemeyer" href="http://blog.case.edu/apple/">Apple blog</a>? He really did a great job on the templates. Also, did you see 
<a title="Gregory Szorc's blog - Rambling on: and now&#226;&#8364;&#8482;s the time; the time is now" href="http://blog.case.edu/gps10/">Greg's</a> post on 
<a title="Gregory Szorc's blog - 5 Things You Probably Didn't Know About PHP" href="http://blog.case.edu/gps10/2006/07/15/5_things_you_probably_didnt_know_about_php">5 Things You Probably Didn't Know About PHP</a>? Everybody and their brother 
<a title="Technorati Search: blog.case.edu/gps10/2006/07/15/5_things_you_probably_didnt_know_about_php" href="http://technorati.com/search/blog.case.edu%2Fgps10%2F2006%2F07%2F15%2F5_things_you_probably_didnt_know_about_php">linked</a> to that thing.</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>Planet Planet! Powered Planet Case</title
><link href="http://blog.case.edu/jeremy.smith/2006/06/09/planet_case"
 /><id
>http://blog.case.edu/jeremy.smith/2006/06/09/planet_case</id
><published
>2006-06-09T22:13:00Z</published
><updated
>2006-06-09T22:14:29Z</updated
><category term="Blog@Case Developments" label="Blog@Case Developments"
 /><category term="blog@case" label="blog@case"
 /><category term="case blog" label="case blog"
 /><category term="mainblog" label="mainblog"
 /><category term="rss" label="rss"
 /><category term="syndicated feeds" label="syndicated feeds"
 /><category term="xml" label="xml"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>I spent a little bit of time hacking on 
<a title="Planet Planet!" href="http://www.planetplanet.org/">Planet Planet!</a> to see if I could get it to power 
<a title="Planet Case" href="http://planet.case.edu/">Planet Case</a>. I was able to whip out a slightly "weeded" OPML file located at 
<a href="http://planet.case.edu/opml">http://planet.case.edu/opml</a> and generated this site using Planet Planet! &#8212; 
<a title="Planet Case" href="http://planet.case.edu/beta/">Planet Case Beta</a>. Not sure what to do now, though. That's the defacto skin, and I don't particularly care for its organization. I'd like to change that. Also, comment/trackback counts don't propagate through, and getting that to work will take some serious hackery. I don't plan on getting rid of the original 
<a title="Planet Case" href="http://planet.case.edu/">Planet Case</a>, but I may regulate that over to http://planet.case.edu/old or something and replace it with Planet Planet! Planet Planet! will provide a bit more flexibility. I'll be able to weed out some blogs from appearing; I'll be able to include external blogs to participate; better control over the sorting of entries and such. It's just going to take me a little more time than I had hoped because of the comments/trackback counts. If you have any comments, feel free to chime in. If you have any design skills, HTML/CSS prototypes are welcome for the design of the new Planet Case. All right, I've gotta get back to the stuff I put to the side while I spent a couple of hours and indulged myself in this.</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>Case Conversations</title
><link href="http://blog.case.edu/jeremy.smith/2006/04/26/case_conversations"
 /><id
>http://blog.case.edu/jeremy.smith/2006/04/26/case_conversations</id
><published
>2006-04-26T19:43:37Z</published
><updated
>2006-04-26T19:44:16Z</updated
><category term="blog@case" label="blog@case"
 /><category term="case" label="case"
 /><category term="case blog" label="case blog"
 /><category term="case western" label="case western"
 /><category term="case western reserve university" label="case western reserve university"
 /><category term="mainblog" label="mainblog"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>There has been a lot of great comments and discussions happening at 
<a title="Alumni Talkback: Alumni Relations: Case Western Reserve University" href="http://blog.case.edu/alumni/">http://blog.case.edu/alumni/</a> and 
<a title="CASEPOINT: News and Information: Marketing and Communications: Case Western Reserve University" href="http://blog.case.edu/casepoint/">http://blog.case.edu/casepoint/</a>. And I keep meaning to point at them. So here it is. A recent comment on 
<a title="Alumni Talkback: Alumni Relations: Case Western Reserve University" href="http://blog.case.edu/alumni/2006/03/16/resignation_of_president_edward_m_hundert_md">Resignation of President Edward M. Hundert, M.D.</a> goes as follows:
<blockquote>As a CWRU (Law) graduate who does not live in Ohio, I have been anxious to learn more about what was going on at CWRU ever since Dr. Hundert's resignation tipped me off to the fact that all was not well with the institution. I'm grateful for this BLOG because it has helped me get a sense of what led to Hundert's resignation and what the pressing issues are now at CWRU (as opposed to the carefully-worded letters from him and the Board Chair, etc., which told us outlanders very little about the actual situation). As a contributor, I'm interested in knowing that my donations are being spent wisely. It sounds as if some accounting is called for now - it also sounds as if the current Board of Trustees is too large, unwieldy and therefore incapable of real oversight. It needs to be comprised of individuals from all parts of the country -- who will be less parochial and more interested in making CWRU a nationally recognized institution. And indeed more board members should be alumni - the people who are the greatest stakeholders with respect to CWRU's reputation and future prospects.</blockquote>I like see all of the fostering of discussions and the community empowerment. It's good stuff. The conversations happen 
<a title="Technorati Search for: blog.case.edu/casepoint" href="http://technorati.com/search/blog.case.edu%2Fcasepoint">all over the place</a>.</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>Aaron Shaffer's Presentation</title
><link href="http://blog.case.edu/jeremy.smith/2006/03/02/aaron_shaffers_presentation"
 /><id
>http://blog.case.edu/jeremy.smith/2006/03/02/aaron_shaffers_presentation</id
><published
>2006-03-02T18:53:03Z</published
><updated
>2006-03-02T18:50:04Z</updated
><category term="case blog" label="case blog"
 /><category term="case wiki" label="case wiki"
 /><category term="mainblog" label="mainblog"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>Last night, I watched 
<a title="Here I develop ideas, thoughts, and dreams. Chip in, help out, or go away." href="http://blog.case.edu/aaron.shaffer/">Aaron Shaffer's</a> presentation on 
<a title="Freedman Center Archives" href="http://blog.case.edu/FreedmanCenter/2006/03/01/blogs_wikis_podcasts_for_beginners">Blogs, Wikis, &amp; Podcasts for Beginners</a>. It was a good presentation and provided a great overview of blogs, podcasting, and wikis covering the implementations we have at Case. I would like to give out a hearty thanks to 
<a title="Here I develop ideas, thoughts, and dreams. Chip in, help out, or go away." href="http://blog.case.edu/aaron.shaffer/">Aaron</a> for putting so much time and effort into creating the presentation and for helping to raise the level of awareness of these technologies, how they are offered at Case, and how they can be used. I have little to add to his presentation because he pretty much covered everything. There was a question near the end as to why the 
<a title="Blog@Case" href="http://blog.case.edu/">Blog</a> and 
<a title="Main Page - Edit this page - CaseWiki" href="http://wiki.case.edu/Main_Page">Wiki</a> systems are still in "Beta." It's true that the database they run off of is backed up nightly. The filesystem that serves the blog content sits on the 
<acronym title="Network Attacked Storage">NAS</acronym>, so it gets 
<em>automagically</em> backed up. So there are no problems there. The reason they were put into Beta initially was: a) we didn't know how well our architecture would scale, b) the only user support was the engineers and developers who designed the system, and c) we had no failovers i.e. there was not another server sitting around such that if the current server caught fire (or had whatever other irreparable damage) we could just repoint the hostnames (blog and wiki) to this other server and be back up and running. So that's why we're still in Beta. We're working on getting failover spots for the service, and once that is done, the Beta tag will come flying off.</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>Blog Miner</title
><link href="http://blog.case.edu/jeremy.smith/2006/02/23/blog_miner"
 /><id
>http://blog.case.edu/jeremy.smith/2006/02/23/blog_miner</id
><published
>2006-02-23T17:23:31Z</published
><updated
>2006-02-23T17:22:43Z</updated
><category term="Weblog Tech" label="Weblog Tech"
 /><category term="blog" label="blog"
 /><category term="blog@case" label="blog@case"
 /><category term="case blog" label="case blog"
 /><category term="linkblog" label="linkblog"
 /><category term="syndicated feeds" label="syndicated feeds"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<a title="Blog Miner - Edit this page - CaseWiki" href="http://wiki.case.edu/Blog_Miner">Blog Miner</a> Sounds interesting. Once the project gets going, will there be a 
<a href="http://wiki.case.edu/Syndicated_feed">feed</a> located at 
<a title="EECS 439 Project" href="http://vorlon.case.edu/~mxh147/eecs439.htm">http://vorlon.case.edu/~mxh147/eecs439.htm</a> that I can subscribe to and follow the project along?</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>Case Admissions Blog on Salon</title
><link href="http://blog.case.edu/jeremy.smith/2006/02/15/case_admissions_blog_on_salon"
 /><id
>http://blog.case.edu/jeremy.smith/2006/02/15/case_admissions_blog_on_salon</id
><published
>2006-02-15T18:43:43Z</published
><updated
>2006-02-15T18:43:23Z</updated
><category term="case blog" label="case blog"
 /><category term="linkblog" label="linkblog"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<a title="Salon.com Life | The campus crusade for guys" href="http://www.salon.com/mwt/feature/2006/02/15/affirmative_action/index1.html">Case Admissions Blog gets a mention in Salon.com</a>
<blockquote>Since teenage boys are often crazy about technology, a number of universities, including Case Western Reserve, Seton Hill and MIT (which, admittedly, at 57-43, doesn't seem to have a problem attracting men), have launched 
<a title="Undergraduate Admission" href="http://blog.case.edu/admission/">admission-oriented blogs</a> designed to offer an intimate, uncensored look at college life.</blockquote>
</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>Wednesday's GB Bandwidth Boost</title
><link href="http://blog.case.edu/jeremy.smith/2006/01/26/wednesdays_gb_bandwidth_boost"
 /><id
>http://blog.case.edu/jeremy.smith/2006/01/26/wednesdays_gb_bandwidth_boost</id
><published
>2006-01-26T17:37:07Z</published
><updated
>2007-01-22T17:20:35Z</updated
><category term="blog@case" label="blog@case"
 /><category term="case blog" label="case blog"
 /><category term="linkblog" label="linkblog"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>Something weird is happening on 
<a title="Statistics for blog.case.edu (2006-01)" href="http://blog.case.edu/stats/awstats.pl?framename=mainright#daysofweek">Wednesdays</a> with persons/things accessing the blog system. I wonder what user/robot is out there that decides that Wednesdays are a good day to read lots of data from the system?</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>Upcoming Anniversary</title
><link href="http://blog.case.edu/jeremy.smith/2005/12/09/upcoming_anniversary"
 /><id
>http://blog.case.edu/jeremy.smith/2005/12/09/upcoming_anniversary</id
><published
>2005-12-09T23:03:04Z</published
><updated
>2005-12-09T23:04:50Z</updated
><category term="blog@case" label="blog@case"
 /><category term="case blog" label="case blog"
 /><category term="linkblog" label="linkblog"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<a title="Blog@Case News: Blog@Case is Open for Beta Testing" href="http://blog.case.edu/news/2005/01#blogcase_is_open_for_beta_testing">January 10th</a> will be the one year anniversary of when the 
<a title="Blog@Case" href="http://blog.case.edu/">Blog system</a> was opened up. I keep meaning to start 
<strong>now</strong> on a big presentation of lessons learned, statistics, what works v. what doesn't, what makes a successful blog, graphs, graphs, graphs. Knowing me, I'll be putting it together Jan. 9th.</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>Planet Case Mac Widget</title
><link href="http://blog.case.edu/jeremy.smith/2005/12/05/planet_case_mac_widget"
 /><id
>http://blog.case.edu/jeremy.smith/2005/12/05/planet_case_mac_widget</id
><published
>2005-12-06T04:47:47Z</published
><updated
>2005-12-06T04:53:51Z</updated
><category term="apple" label="apple"
 /><category term="blog@case" label="blog@case"
 /><category term="case blog" label="case blog"
 /><category term="linkblog" label="linkblog"
 /><category term="osx" label="osx"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<a title="Arcanum" href="http://blog.case.edu/clk13/">Casey Kearns</a> creates a 
<a title="Arcanum: First Entry - Planet Case Widget" href="http://blog.case.edu/clk13/2005/12/05/first_entry_planet_case_widget">Mac widget</a> for 
<a title="Planet Case" href="http://planet.case.edu/">Planet Case</a>. 
<em>Nice!</em></div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>Mass Communication</title
><link href="http://blog.case.edu/jeremy.smith/2005/11/16/mass_communication"
 /><id
>http://blog.case.edu/jeremy.smith/2005/11/16/mass_communication</id
><published
>2005-11-16T22:07:59Z</published
><updated
>2005-11-16T22:13:48Z</updated
><category term="Email Services" label="Email Services"
 /><category term="Failures of Technology" label="Failures of Technology"
 /><category term="case blog" label="case blog"
 /><category term="mainblog" label="mainblog"
 /><category term="sympa" label="sympa"
 /><category term="syndicated feeds" label="syndicated feeds"
 /><category term="xml" label="xml"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>So 
<a title="Gregory Szorc's blog" href="http://blog.case.edu/gps10/">Greg</a> started the thread with 
<a title="Gregory Szorc's blog: Too Many Newsletters" href="http://blog.case.edu/gps10/2005/11/16/too_many_newsletters">Too Many Newsletters</a>. I responded in 
<a title="Jeremy Smith's blog: Too Many Newsletters Probably Means Alternate Communication Paths Need to be Employed" href="http://blog.case.edu/jms18/2005/11/16/newsletters">Too Many Newsletters Probably Means Alternate Communication Paths Need to be Employed</a>. 
<a title="Aaron Shaffer" href="http://blog.case.edu/axs221/">Aaron Shaffer</a> chimed in with 
<a title="Aaron Shaffer: Mass Communication at Case" href="http://blog.case.edu/axs221/2005/11/16/mass_communication_at_case">Mass Communication at Case</a>. (Just in case you need to catch up on the thread.) I've done some further thinking about this and have brought it up in a meeting. There was much discussion. I am going to mention that discussion here and respond to a couple of things Aaron said. From 
<a title="Aaron Shaffer: Mass Communication at Case" href="http://blog.case.edu/axs221/2005/11/16/mass_communication_at_case">Aaron</a>:
<blockquote>I think all mass communication should be handled by the department of communications here at Case.</blockquote>It is. All mass emails end up going through 
<a title="Marketing &amp; Communications: Case Western Reserve University" href="http://www.case.edu/univrel/marcomm/">Marketing &amp; Communications</a>. I think the problem is, the people sending out the mass emails may not know or may not know how to use the other avenues of communication. (This is what we talked about in the meeting -- ways in which we could promote these other avenues.) Right now, we may have a case of "functional fixedness"; it may be perceived that all there is is email. We need a way to change that. It's going to get easier and easier to send out mass emails. That's one of the goals of one of the projects I am working on. Designated people will be able to sit at an email client of their choosings, send out a mass email, that email will go to a moderation queue, a certain select group of "Mass Communication Custodians" will get notified something is waiting for their approval, and they can approve it for dissemination. It's only going to get easier, which means there will be more of it. What we need is to raise the level of awareness of the other avenues of communication. And, we need to raise the awareness of the tools we have on campus that facilitate them. Leverage the 
<a href="http://blog.case.edu">Blog system</a> for your department or organization's web page so you can have 
<a href="http://wiki.case.edu/XML_feeds">XML feeds</a> and email susbscriptions to your updates like the 
<a title="Information Technology Services at Case" href="http://www.case.edu/its">ITS homepage</a>. Use 
<a title="Case Mailing List Manager" href="https://lists.case.edu/">lists.case.edu</a> to hand create your groups. People will be able to opt-in and opt-out (though, that can be disabled for a given list), but you can prepopulate a list with whomever you want. An email to 
<a href="mailto:listmaster@case.edu">listmaster@case.edu</a> (depending on your requirements) can even have your list automatically prepopulated with our Directory data. I think that in between these:
<ul>
<li>XML feeds for web sites built leveraging the blog system</li>
<li>Email subscriptions to web sites built from the blog system</li>
<li>Hand-edited, opt-out-able Sympa lists</li>
<li>Hand-edited, non-opt-out-able Sympa lists</li>
<li>Pre-populated, opt-out-able Sympa lists</li>
<li>And, Pre-populated, non-opt-out-able Sympa lists</li>
</ul>We have an excellent set of tools at the disposal of those wanting to effectively communicate with groups on campus in ways that won't barrage and irritate them. What is needed is guidance and documentation... lots of documentation. And, whaddya know, we have a 
<a href="http://wiki.case.edu">wiki</a> for documentation. Pages full of screen shots and step-by-step tutorials and informative descriptions on the different technologies should exist. Something like 
<a href="http://wiki.case.edu/Howto:Communicate_with_the_students">http://wiki.case.edu/Howto:Communicate_with_the_students</a> or 
<a href="http://wiki.case.edu/Howto:Reach_the_students">http://wiki.case.edu/Howto:Reach_the_students</a> explaining all of this and detailing the options, when the options are applicable, and why the options are better (in some circumstances) than mass emails. It will probably need broken down into sections like 
<a href="http://wiki.case.edu/Howto:Create_XML_feeds_at_Case">http://wiki.case.edu/Howto:Create_XML_feeds_at_Case</a>, 
<a href="http://wiki.case.edu/Howto:Setup_email_subscriptions_to_my_Case_website">http://wiki.case.edu/Howto:Setup_email_subscriptions_to_my_Case_website</a>, 
<a href="http://wiki.case.edu/Howto:Create_a_mailing_list_for_my_newsletters">http://wiki.case.edu/Howto:Create_a_mailing_list_for_my_newsletters</a>, etc. I may take a stab at it, but I don't know how much time I'll be able to devote to it. I have a 
<a title="Blog@Case: Intermittent Failures" href="http://blog.case.edu/news/2005/11#intermittent_failures">blog/wiki/planet/topics/mysql/subversion server on the fritz</a> with a rapidly depleting supply of any hardware to move it to, the whole project about fixing the mass email system, an authentication web service for 
<a href="http://wiki.case.edu/CAS">CAS</a>, and day-to-day ops to worry about (not to mention all these blog entries 
<b>*whew*</b>). But, I'll see if I can get something jumpstarted.</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>Fostering Community</title
><link href="http://blog.case.edu/jeremy.smith/2005/11/09/fostering_community"
 /><id
>http://blog.case.edu/jeremy.smith/2005/11/09/fostering_community</id
><published
>2005-11-09T18:29:31Z</published
><updated
>2005-11-09T18:30:01Z</updated
><category term="case blog" label="case blog"
 /><category term="mainblog" label="mainblog"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>From 
<a title="Cymfony's Marketing Insight" href="http://blog.cymfony.com/">Cymfony's Marketing Insight</a> in the article 
<a title="Cymfony's Marketing Insight: Blogging on the College Campus" href="http://blog.cymfony.com/2005/08/college_bloggin.html">Blogging on the College Campus</a>:
<blockquote>I visited my alma mater (
<a href="http://www.case.edu">Case Western Reserve University</a>) last week to show my wife my old stomping grounds. There were a lot of physical changes to the campus, which were cool to see. But I also found out they recently started up a 
<a href="https://blog.case.edu/">campus wide blogging system</a> that hosts blogs for any student, faculty, staff and alumni. I think this is a great way for colleges to foster a sense of community and encourage discussion and interaction between students. I'm excited that the university *I* attended is at the forefront of promoting the use of blogs.</blockquote></div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>New Experimental Feature: Tracking Commenters</title
><link href="http://blog.case.edu/jeremy.smith/2005/10/10/follow_case_blog_comments"
 /><id
>http://blog.case.edu/jeremy.smith/2005/10/10/follow_case_blog_comments</id
><published
>2005-10-10T22:53:03Z</published
><updated
>2005-10-10T22:52:23Z</updated
><category term="Blog@Case Developments" label="Blog@Case Developments"
 /><category term="Programming" label="Programming"
 /><category term="Web Services" label="Web Services"
 /><category term="Weblog Tech" label="Weblog Tech"
 /><category term="aggregator" label="aggregator"
 /><category term="atom" label="atom"
 /><category term="blog" label="blog"
 /><category term="blog@case" label="blog@case"
 /><category term="case blog" label="case blog"
 /><category term="mainblog" label="mainblog"
 /><category term="syndicated feeds" label="syndicated feeds"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>Yet-Another-New-Experimental-Not-Officially-Supported feature &#8212; 
<a title="Blog@Case Comments: Most Recent 20 Comments" href="http://blog.case.edu/comments">http://blog.case.edu/comments</a>. Track the newest comments made on the 
<a href="http://blog.case.edu">Case blogging system</a>. You can break it down by commenter according to his or her email address: 
<a title="Blog@Case Comments: jeremy.smith@case.edu" href="http://blog.case.edu/comments/jeremy.smith@case.edu">http://blog.case.edu/comments/jeremy.smith@case.edu</a> Keying in via email address comes with two problems. 1) Users have multiple addresses. 2) There is no guarantee that the user posting under jeremy.smith@case.edu is actually me. But, it may be of slight use to some; so go ahead and play with it if you would like. Send 
<a href="mailto:blog-admin@case.edu">email</a> if you have any feedback. And, of course, you can subscribe to those URLs in your favorite 
<a href="http://wiki.case.edu/news_aggregator">news aggregator</a> in case you want to track all of the comments someone makes on the system.</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>First Case Blog Podcast!</title
><link href="http://blog.case.edu/jeremy.smith/2005/10/07/first_case_blog_podcast"
 /><id
>http://blog.case.edu/jeremy.smith/2005/10/07/first_case_blog_podcast</id
><published
>2005-10-07T21:31:19Z</published
><updated
>2005-10-07T21:31:34Z</updated
><category term="Blog@Case Developments" label="Blog@Case Developments"
 /><category term="Weblog Tech" label="Weblog Tech"
 /><category term="blog" label="blog"
 /><category term="blog@case" label="blog@case"
 /><category term="case blog" label="case blog"
 /><category term="mainblog" label="mainblog"
 /><category term="podcast" label="podcast"
 /><category term="podcasting" label="podcasting"
 /><category term="rss" label="rss"
 /><category term="syndicated feeds" label="syndicated feeds"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<p>
<strong>Awesome!</strong> 
<a href="http://blog.case.edu">Blog@Case's</a> first 
<a href="http://wiki.case.edu/podcast">podcast</a>! &#8212; 
<a title="The Freedman Center in Kelvin Smith Library: Podcast" href="http://blog.case.edu/FreedmanCenter/2005/10/07/podcast">The Freedman Center in Kelvin Smith Library: Podcast</a>. And, it worked!</p>
<p>Check out the 
<a href="http://http://blog.case.edu/FreedmanCenter/rss20.xml">RSS feed for the Freedman Center blog</a>. It includes the following little snippet where the magic happens:</p>
<pre>
<code>&lt;item&gt;
    &lt;title&gt;Podcast&lt;/title&gt;
    &lt;link&gt;http://blog.case.edu/FreedmanCenter/2005/10/07/podcast&lt;/link&gt;
    &lt;description&gt;Testing a podcast &amp; learning how MoveableType enclosures work on our blog system......&lt;/description&gt;
    &lt;guid&gt;http://blog.case.edu/FreedmanCenter/2005/10/07/podcast&lt;/guid&gt;
    &lt;pubDate&gt;Fri, 07 Oct 2005 14:51:19 EST&lt;/pubDate&gt;
    
<strong>&lt;enclosure url="http://blog.case.edu/FreedmanCenter/podcasts/10-07-05.mp3" length="4412159" type="audio/mpeg" /&gt;</strong>
&lt;/item&gt;</code>
</pre>
<p>Go head. Check it out in iTunes. Just point your podcast subscriptions to 
<a href="http://http://blog.case.edu/FreedmanCenter/rss20.xml">http://http://blog.case.edu/FreedmanCenter/rss20.xml</a> and watch the magic happen.</p>
</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>Hurricanes</title
><link href="http://blog.case.edu/jeremy.smith/2005/10/07/hurricanes"
 /><id
>http://blog.case.edu/jeremy.smith/2005/10/07/hurricanes</id
><published
>2005-10-07T16:53:01Z</published
><updated
>2005-10-07T16:50:54Z</updated
><category term="And Now for Something Different" label="And Now for Something Different"
 /><category term="blog" label="blog"
 /><category term="blog@case" label="blog@case"
 /><category term="case blog" label="case blog"
 /><category term="mainblog" label="mainblog"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>If you haven't seen it yet, Ronald Vojacek is volunteering for The Salvation Army to aid those areas and people hit by hurricanes Katrina and Rita; and he's blogging it in 
<a title="Ronald Vojacek's Hurricane Journal" href="http://blog.case.edu/ronald.vojacek/">Ronald Vojacek's Hurricane Journal</a>.</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>About This Weblogs Being Deleted Thing</title
><link href="http://blog.case.edu/jeremy.smith/2005/10/03/about_this_weblogs_being_deleted_thing"
 /><id
>http://blog.case.edu/jeremy.smith/2005/10/03/about_this_weblogs_being_deleted_thing</id
><published
>2005-10-04T04:43:31Z</published
><updated
>2005-10-04T04:44:10Z</updated
><category term="Blog@Case Developments" label="Blog@Case Developments"
 /><category term="Failures of Technology" label="Failures of Technology"
 /><category term="Programming" label="Programming"
 /><category term="case blog" label="case blog"
 /><category term="mainblog" label="mainblog"
 /><category term="mysql" label="mysql"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>For the record, about this 
<a title="Blog@Case: Weblogs Being Deleted" href="http://blog.case.edu/news/2005/10#weblogs_being_deleted">weblogs being deleted</a> thing. As of right now, I have no idea how it is happening. Nothing is appearing in the Movable Type logs. Nothing is in the web server logs indicating a "delete this weblog" URL was hit. I'm going to increase the logging level of the database and see if I can't track it down via that. (Of course, to be able to track this down, it would need to strike at another unsuspecting user, which is unfortunate.) In the meantime, I have removed the self-service delete-my-weblog option from the administrative panel. And, I have removed all of the code in the Movable Type base that performs a weblog delete operation. Though, I don't know how effective those measures will be to curb the problem. Like the 
<a title="Blog@Case News" href="http://blog.case.edu/news/">Blog@Case news</a> items said, email the 
<a href="mailto:blog-admin@case.edu">Case Blog Administrators</a> if this happens to you. It takes a bit of time to restore a single weblog, though, because the backups we take of the database are full backups &#8211; meant to be used in the event of a database/hardware disaster to do a full restore of the system. To do these selective restores, one needs to perform a pseudo-restore of the whole system into a temporary location, meticulously pick through the resultant files for the necessary components of the blog you want to restore, perform a test restore of the blog in a test database, and, finally, actually restore it. It's a time consuming operation.</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>Another Case Law School Blog</title
><link href="http://blog.case.edu/jeremy.smith/2005/09/24/law_school_blog"
 /><id
>http://blog.case.edu/jeremy.smith/2005/09/24/law_school_blog</id
><published
>2005-09-24T18:23:31Z</published
><updated
>2005-09-24T18:22:49Z</updated
><category term="blog" label="blog"
 /><category term="blogs in academia" label="blogs in academia"
 /><category term="case" label="case"
 /><category term="case blog" label="case blog"
 /><category term="case western" label="case western"
 /><category term="case western reserve university" label="case western reserve university"
 /><category term="mainblog" label="mainblog"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<a title="Jeremy Smith's blog: Case Western Global Security Blog" href="http://blog.case.edu/jms18/2005/09/14/case_western_global_security_blog">Another</a> 
<a title="Case Western Reserve University" href="http://law.case.edu/">Case Law School</a> blog &#8212; 
<a title="Grotian Moment Blog" href="http://www.law.case.edu/saddamtrial/">Grotian Moment Blog</a>. But... ummm... there is no 
<a href="http://wiki.case.edu/XML_feed">XML feed</a>. How am I supposed to follow it? How can you have a blog without a 
<a href="http://wiki.case.edu/syndicated_feed">syndicated feed</a>? Does anyone know who is setting these blogs up over at the 
<a href="http://wiki.case.edu/Law_School">Law School</a>? Maybe I could assist them in the areas such as 
<a href="http://wiki.case.edu/RSS">RSS</a> feeds.</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>More Blog@Case Topics Features</title
><link href="http://blog.case.edu/jeremy.smith/2005/09/16/more_blogcase_topics_features"
 /><id
>http://blog.case.edu/jeremy.smith/2005/09/16/more_blogcase_topics_features</id
><published
>2005-09-16T23:17:17Z</published
><updated
>2005-09-16T23:17:09Z</updated
><category term="Blog@Case Developments" label="Blog@Case Developments"
 /><category term="Programming" label="Programming"
 /><category term="Web Services" label="Web Services"
 /><category term="Weblog Tech" label="Weblog Tech"
 /><category term="blog" label="blog"
 /><category term="blog@case" label="blog@case"
 /><category term="case blog" label="case blog"
 /><category term="linkblog" label="linkblog"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<a title="Blog@Case: Topics" href="http://blog.case.edu/topics">Blog@Case: Topics</a> Now, with some more features.</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>Case Western Global Security Blog</title
><link href="http://blog.case.edu/jeremy.smith/2005/09/14/case_western_global_security_blog"
 /><id
>http://blog.case.edu/jeremy.smith/2005/09/14/case_western_global_security_blog</id
><published
>2005-09-14T17:07:01Z</published
><updated
>2005-09-14T19:27:41Z</updated
><category term="Weblog Tech" label="Weblog Tech"
 /><category term="atom" label="atom"
 /><category term="blog" label="blog"
 /><category term="blogs in academia" label="blogs in academia"
 /><category term="case" label="case"
 /><category term="case blog" label="case blog"
 /><category term="mainblog" label="mainblog"
 /><category term="rss" label="rss"
 /><category term="semantic web" label="semantic web"
 /><category term="syndicated feeds" label="syndicated feeds"
 /><category term="xml" label="xml"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>This is the first 
<strong>I</strong> have heard of this (others may have heard about it before), but 
<a href="http://www.case.edu">Case Western's</a> 
<a href="http://law.case.edu">Law School</a> has a 
<a title="Institute for Global Security Law and Policy" href="http://law.case.edu/terrorism/">Global Security Law &amp; Policy Blog</a>. I found it via the new 
<a title="Google Blog Search" href="http://blogsearch.google.com/">Google Blog Search</a> for the terms 
<a title="Google Blog Search: Case Western" href="http://blogsearch.google.com/blogsearch?q=Case%20Western">Case Western</a>. Yet another good reason your web site should be publishing 
<a href="http://wiki.case.edu/Syndicated_Feeds">Syndicated Feeds</a> of its content.</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
><entry
><title
>Blog@Case Topics Broken in IE</title
><link href="http://blog.case.edu/jeremy.smith/2005/08/31/blogcase_topics_broken_in_ie"
 /><id
>http://blog.case.edu/jeremy.smith/2005/08/31/blogcase_topics_broken_in_ie</id
><published
>2005-08-31T06:01:01Z</published
><updated
>2005-08-31T06:01:22Z</updated
><category term="Blog@Case Developments" label="Blog@Case Developments"
 /><category term="blog" label="blog"
 /><category term="blog@case" label="blog@case"
 /><category term="case blog" label="case blog"
 /><category term="linkblog" label="linkblog"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<strong>*sigh*</strong> I just realized that my work done this evening has horribly broken 
<a title="Blog@Case: Topics" href="http://blog.case.edu/topics/">Blog@Case Topics</a> in every which way possible on Internet Explorer. That sucks. IE is 
<em>such</em> a momentum killer. Tomorrow. I'll resume work on it tomorrow. I do not have the gumption right now to wrestle with Internet Explorer.</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
></feed
>
