<?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: podcasting</title
><link rel="self" href="http://blog.case.edu/topics/podcasting"
 /><id
>http://blog.case.edu/topics/podcasting</id
><category term="podcasting" label="podcasting"
 /><link rel="related" href="http://blog.case.edu/topics/mainblog" title="mainblog"
 /><link rel="related" href="http://blog.case.edu/topics/podcast" title="podcast"
 /><link rel="related" href="http://blog.case.edu/topics/heidi's%20entries" title="heidi's entries"
 /><link rel="related" href="http://blog.case.edu/topics/case%20blog" title="case blog"
 /><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/copyright" title="copyright"
 /><link rel="related" href="http://blog.case.edu/topics/linkblog" title="linkblog"
 /><link rel="related" href="http://blog.case.edu/topics/blog@case" title="blog@case"
 /><link rel="related" href="http://blog.case.edu/topics/weblog%20tech" title="weblog tech"
 /><link rel="related" href="http://blog.case.edu/topics/blog" title="blog"
 /><link rel="related" href="http://blog.case.edu/topics/ruby" title="ruby"
 /><contributor
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></contributor
><contributor
><name
>George Klippel</name
><email
>george.klippel@case.edu</email
><uri
>http://blog.case.edu/ghk4</uri
></contributor
><contributor
><name
>Heidi Cool</name
><email
>heidi.cool@case.edu</email
><uri
>http://blog.case.edu/webdev</uri
></contributor
><updated
>2006-10-04T01:09:41Z</updated
><entry
><title
>Case Wordnerds to discuss blogging</title
><link href="http://blog.case.edu/webdev/2007/03/13/blogging.html"
 /><id
>http://blog.case.edu/webdev/2007/03/13/blogging.html</id
><published
>2007-03-13T22:08:50Z</published
><updated
>2007-03-13T22:51:05Z</updated
><category term="Announcements" label="Announcements"
 /><category term="Blogging" label="Blogging"
 /><category term="Heidi's Entries" label="Heidi's Entries"
 /><category term="Podcast Recommendations" label="Podcast Recommendations"
 /><category term="Podcasting" label="Podcasting"
 /><summary type="text/plain"
>The Case Writers' and Editors' Forum, &lt;a href="mailto:wordnerds@case.edu"&gt;&lt;strong&gt;WordNerds&lt;/strong&gt;&lt;/a&gt;, will discuss blogging next Wednesday, March 21st, in room 2280 (2nd floor) at the School of Nursing. I'll be leading this discussion in which we'll cover a brief overview of blogging, then discuss ways to use blogging in our marketing, recruitment and other communication efforts. I've asked &lt;a href="http://wiki.case.edu/User:Jeremy.Smith"&gt;Jeremy Smith&lt;/a&gt;, Case's blog administrator, to join us to share his opinions and expertise. </summary
><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<p class="photoright">
<img alt="nur.jpg" src="http://blog.case.edu/webdev/2007/03/13/nur.jpg" width="180" height="128" />
<br />School of Nursing</p>
<p>The Case Writers' and Editors' Forum, 
<a href="mailto:wordnerds@case.edu">
<strong>WordNerds</strong>
</a>, will discuss blogging next Wednesday, March 21st, in room 2280 (2nd floor) at the School of Nursing. I'll be leading this discussion in which we'll cover a brief overview of blogging, then discuss ways to use blogging in our marketing, recruitment and other communication efforts. I've asked 
<a href="http://wiki.case.edu/User:Jeremy.Smith">Jeremy Smith</a>, Case's blog administrator, to join us to share his opinions and expertise.</p>
<h5>About Wordnerds</h5>
<p>For those looking for brainstorming partners, story ideas, or the chance to benefit from the best practices other Case communicators have developed, Case's WordNerds meets every third Wednesday of each month for lunch, networking, professional discussions, and general moral support. All university staff members involved in writing, editing, communications, public relations, marketing, and recruiting are welcome. Send e-mail to 
<a href="mailto:wordnerds@case.edu">wordnerds@case.edu</a> for more information, or to join the mailing list.</p>
<h5>Blogging? What's to know?</h5>
<p>Regular readers of the Web Development Blog are already quite familiar with blogging. For members of Wordnerds, who may not be as familiar with the topic, I've posted a very general introduction to blogs and podcasts below. I wrote this last summer as part of another project, but the principles still apply. Read this now to get a jumpstart on next week's discussion.</p>
<h5>Blogs: Web sites with benefits</h5>
<p>According to the 
<a href="http://wiki.case.edu/CaseBlog/FAQ">Case Blog FAQ</a>, "Weblogs, or blogs, are a way of publishing to the web one idea at a time. By simplifying the process of publishing, letting authors create posts easily, and making it simple to link to related ideas on the Web, blogs make it easy to update a Web site while still making sure your words retain a clear, personal voice."</p>
<p>While often thought of as online diaries or journals, blogs can be written by one or more authors and used in any number of ways. Here at Case, the 
<a href="http://blog.case.edu/admission/">Undergraduate Admission blog</a> allows admission staff to share ideas with one another and give prospective students a glimpse into the way the admission process works. Because the blog system allows readers to make comments, prospective students can ask questions related to specific blog postings and receive answers not only from admissions staff, but also from other Case faculty, staff and students who read the blog.</p>
<p>According to admission's former writer&#8212;now director of media relations, Lisa Chiu "We launched our blog last summer as another way to connect with prospective students. Ours is a group blog, so we have several people who post&#8212;admission counselors, financial aid counselors, and marketing and communications staff. We post on a variety of topics, some serious, some silly. We love when high school students leave comments on our entries&#8212;it's always great being able to spark a stimulating conversation. It's exciting to see that high school students from all over the world are reading our blog and learning more about Case."</p>
<p>One of the greatest features of a blog is its ability to syndicate content. As wire services such as Reuters distribute news to media outlets around the globe, you as a blogger can distribute your content via 
<a href="http://en.wikipedia.org/wiki/RSS_(file_format)">RSS</a> or 
<a href="http://en.wikipedia.org/wiki/Atom_%28standard%29">Atom</a> feeds. These feeds allow users to subscribe to a variety of blogs via aggregators such as 
<a href="http://www.bloglines.com">http://www.bloglines.com</a>.</p>
<p>What this means to you as a reader is that instead of visiting the 10 different Web sites where your favorite blogs are published, you can instead go to an aggregator such as Bloglines, subscribe to your favorites, then read them all in one place. Another example of an aggregator is 
<a href="http://planet.case.edu">Planet Case</a>. Planet Case aggregates all the most recent postings from the Case blogs. I usually skim Planet Case at least once a day because it allows me to catch up with my favorite Case blogs as well as learn of new ones.</p>
<p>Highlights of the blogs on Planet Case today (last summer) include the latest updates&#8212;with photos&#8212;from 
<a href="http://blog.case.edu/kellio/">Kelly</a>, who is studying and doing community outreach in Uganda; a post from Weatherhead's 
<a href="http://blog.case.edu/kep2/">Professor Piderit</a>, in which she explores the nature of an "organization" and opens up the topic for group discussion; and part 4 of a series of insightful philosophical entries entitled "Why we must learn to see ourselves as others see us" written by Case's most prolific blogger, 
<a href="http://blog.case.edu/mxs24/">Mano Singham</a>, director of the University Center for Innovation in Teaching and Education.</p>
<p>While content found on the blogs is easily viewed through aggregators, it can also be found elsewhere on the Case Web site. Our office uses the blog system to 
<a href="http://blog.case.edu/case-news/">publish news stories about Case</a>. The headlines from these stories are automatically pulled into pages such as the 
<a href="http://www.case.edu/">home page</a> and the MyCase portal and can be repurposed in their entirety or by topic on pages throughout the Case site.</p>
<p>The blog system's ability to syndicate information is also what enables us to podcast audio or video content.</p>
<h5>Podcast, both noun and verb</h5>
<p>A 
<a href="http://en.wikipedia.org/wiki/Podcasting">podcast</a> (the noun) is basically just an audio or video file that has been uploaded to the Web in such as way that it can be downloaded automatically through software&#8212;such as 
<a href="http://www.apple.com/itunes/">iTunes</a>&#8212;that can read syndicated feeds. While users may also be able to download such files from regular Web sites, the ability to subscribe to a feed&#8212;as one subscribes to a magazine&#8212;lets users have their audio and video content delivered automatically to their computers. 
<a href="http://wiki.case.edu/Freedman_Center:Podcasting">To podcast</a> (the verb) is simply a matter of publishing your content to a system, such as a blog, that can disseminate the file via syndication.</p>
<p>This is much less complicated that it sounds. As I type this on my computer, iTunes is checking my subscriptions and downloading new files. The podcasts I listen to include radio shows from the 
<a href="http://www.bbc.co.uk/radio4/history/inourtime/">BBC</a> and 
<a href="http://www.npr.org/programs/waitwait/">NPR</a>, lectures from the 
<a href="http://www.cityclub.org/content/podcasts/index/Podcasts.aspx">City Club of Cleveland</a>, 
<a href="http://uc.princeton.edu/main/">academic lectures</a> as well as some very 
<a href="http://www.mygermanclass.com/">amusing videos on learning German</a>. To subscribe to these I simply copied the addresses of their feeds from their Web sites and pasted them into iTunes. Now I can watch or listen to the files&#8212;at my convenience&#8212;by copying them to my iPod, burning them to CD or just using my computer.</p>
<p>Here on campus, it is also fairly simple to produce a podcast. For example, earlier last year 
<a href="http://blog.case.edu/aaron.shaffer/">Aaron Shaffer</a>, formerly of the university's Freedman Center, gave a talk about blogs, wikis, and podcasting. Using a digital recorder, he recorded the talk, then&#8212;using software provided by the center&#8212;he added the slides from his demonstrations and saved the augmented audio file in the appropriate format. To podcast the file, he simply uploaded it to the Freedman Center Blog&#8212;which supports RSS and Atom feeds. Those who couldn't attend the lecture can 
<a href="http://blog.case.edu/FreedmanCenter/2006/03/01/blogs_wikis_podcasts_for_beginners">listen online or subscribe to the podcast</a>.</p>
<p>Podcasting has become so easy in fact that Silicon Republic.com announced in March 2006 that podcasts now outnumber radio stations.</p>
<h5>On a different topic&#8230;</h5>
<p>I will be out of the office tomorrow through Tuesday. Please direct any Web development questions to 
<a href="mailto:kevin.adams@case.edu">Kevin</a> in my absence.</p>
</div
></content
><author
><name
>Heidi Cool</name
><email
>heidi.cool@case.edu</email
><uri
>http://blog.case.edu/webdev</uri
></author
></entry
><entry
><title
>Sharing</title
><link href="http://blog.case.edu/jeremy.smith/2006/10/03/sharing"
 /><id
>http://blog.case.edu/jeremy.smith/2006/10/03/sharing</id
><published
>2006-10-04T01:07:23Z</published
><updated
>2006-10-04T01:09:41Z</updated
><category term="copyright" label="copyright"
 /><category term="mainblog" label="mainblog"
 /><category term="podcast" label="podcast"
 /><category term="podcasting" label="podcasting"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>I read 
<a title="dive into mark" href="http://diveintomark.org/">Mark Pilgrim's</a> 
<a title="Waiting for the revolution [dive into mark]" href="http://diveintomark.org/archives/2006/09/15/cc-by-nc">Waiting for the revolution</a> back when he wrote it and thought to myself, "that makes sense." But didn't think too much on it. Just not that into the subject matter of copyrights and licensing and such. Then I read 
<a title="ongoing" href="http://www.tbray.org/ongoing/">Tim Bray's</a> 
<a title="ongoing &#239;&#191;&#189; Licensing Modes" href="http://www.tbray.org/ongoing/When/200x/2006/09/19/Licensing-Modes">response</a>, and I thought that it made sense, too:
<blockquote>I discover that my attitudes towards code and non-code are different. The notion of restricting anyone from 
<em>using</em> code I contribute to feels entirely foreign... But I have 
<em>strong</em> negative feelings about other people making money from my words or pictures without involving me.</blockquote>At that point, I found myself being entirely too agreeable with everyone. So I started 
<a title="Copyright - Wikipedia, the free encyclopedia" href="http://en.wikipedia.org/wiki/Copyright">reading</a>. I checked out all the 
<a title="Technorati Search: diveintomark.org/archives/2006/09/15/cc-by-nc" href="http://technorati.com/search/diveintomark.org%2Farchives%2F2006%2F09%2F15%2Fcc-by-nc">people linking back to the entry</a> specifically looking for dissenters because those people are more interesting than the yea-me-too's. I started going through the 
<a title="Waiting for the revolution [dive into mark]" href="http://diveintomark.org/archives/2006/09/15/cc-by-nc">comments</a>. I spent a lot of time reading all of the different opinions and such and began thinking in terms more like Tim Bray's notions as did many others.
<img alt="copyright1.png" src="http://blog.case.edu/jms18/2006/10/03/copyright1.png" width="418" height="216" /> Of course, in all of the talking; there seemed to be a lot of people suggesting/speculating/claiming that the area between is much murkier and that 
<em>some</em> pictures and 
<em>some</em> words and (even) some code can fall on the side opposite than originally classified depending on a lot of things such as context, intent, expression, etc. 
<img alt="copyright2.png" src="http://blog.case.edu/jms18/2006/10/03/copyright2.png" width="384" height="224" /> And that got me thinking that maybe the delineating factor isn't code and non-code/"art"; rather, there was another criteria that separates what is one and what is the other. Intent? A desire for others 
<em>to</em> create more with it? Maybe something else? Then it struck me. I'm getting to be an 
<a title="Old fogey - Wikipedia, the free encyclopedia" href="http://en.wikipedia.org/wiki/Old_fogey">old fogey</a>. When I "grew up" as a programmer, the open source methodology was in full swing. It never seemed odd to me to release code. It 
<em>has</em> never seemed odd to me to release code because (from my vantage point) it's just 
<strong>always</strong> been done. It's more weird the other way around where no one would release code. And in this day of 
<a title="Pages tagged with " mashups="" on="" href="http://del.icio.us/tag/mashups%20music">music mashups</a>, sampling, "Web 2.0" mixins, 
<a title="Main Page - Wikipedia, the free encyclopedia" href="http://en.wikipedia.org/wiki/Main_Page">Wikipedia</a>, etc.; sharing for re-
<strong>purposing</strong> and re-
<strong>creating</strong> will become the norm and will rely on copyrights, licensing, and having the rights to do such things. Mark left this 
<a title="Waiting for the revolution [dive into mark]" href="http://diveintomark.org/archives/2006/09/15/cc-by-nc#comment-7398">comment</a> on the entry:
<blockquote>Where would Ubuntu Linux be if every single one of their 
<a href="http://packages.ubuntu.com/dapper/allpackages.en.txt.gz">14437 packages</a> required contacting the author for permission to 
<a href="http://linuxcdrs.com/">sell a CD for $1</a>? What the hell kind of "commons" is that?</blockquote>So I took it more seriously after doing my reading and am now including a 
<a title="Welcome | Creative Commons" href="http://creativecommons.org/">Creative Commons</a> cc-sa license on the main page and each individual entry's page along with some appropriate metadata in my syndicated feed.
<blockquote>
<a href="http://creativecommons.org/licenses/by/2.5/">
<img alt="cc-sa.png" src="http://blog.case.edu/jms18/cc-sa.png" width="88" height="31" />
</a>
<p>This work is licensed under the Creative Commons Attribution 2.5 License. To view a copy of this license, visit 
<a href="http://creativecommons.org/licenses/by/2.5/">http://creativecommons.org/licenses/by/2.5/</a> or send a letter to Creative Commons, 543 Howard Street, 5th Floor, San Francisco, California, 94105, USA.</p>
</blockquote>Hopefully the revolution does eventually happen so 
<a title="Case Forum :: General&#239;&#191;&#189;Discussion :: Podcasts for MediaVision" href="http://forum.case.edu/read/7/10860">course material can be "podcasted"</a>, but I fear we're going to have to wait for another generation or two of 
<a title="Old fogey - Wikipedia, the free encyclopedia" href="http://en.wikipedia.org/wiki/Old_fogey">old fogies</a> like me to die off and make way for the "commons."</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
>Listening to academic podcasts: Who would and why? Part I</title
><link href="http://blog.case.edu/webdev/2006/04/03/listening_to_academic_podcasts_who_would_and_why_part_i.html"
 /><id
>http://blog.case.edu/webdev/2006/04/03/listening_to_academic_podcasts_who_would_and_why_part_i.html</id
><published
>2006-04-03T17:46:34Z</published
><updated
>2006-04-03T19:58:35Z</updated
><category term="Heidi's Entries" label="Heidi's Entries"
 /><category term="Podcasting" label="Podcasting"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<p class="photoright">
<img alt="ipod.jpg" src="http://blog.case.edu/webdev/2006/04/03/ipod.jpg" width="138" height="218" />
</p>
<p>Friday on 
<a href="http://blog.case.edu/kep2/2006/03/31/lectures_via_itunes">Management Professor Notes II</a>, Professor Piderit wrote, "Jeremy Smith writes that 
<a href="http://blog.case.edu/jms18/2006/03/20/case_itunes">Case has been accepted into Apple's iTunes University program</a>, which sounds exciting... as long as it doesn't mean that students stop coming to my class." Instead of worrying about this, she (and her commenters) then focused on ways to make classroom attendance worthwhile, while I started thinking about ways in which students and others might use podcasts.</p>
<p>As our iTunes workgroup waits to learn more about the technical requirements for the iTunes project, now seems like a good time to consider how classroom (and other) lectures podcast via iTunes might be used by various listening audiences. I've thought about this primarily in regard to podcasts that are available to everyone. There may be circumstances in which a podcaster would restrict a podcast to a limited group, such as students in a particular class, but I think in most cases there are benefits to be found in reaching out to a wider audience.</p>
<p>What follows are some suggested reasons various groups might listen to a lecture/discussion via podcast. I've organized them by audience. Today I've focused on members of the Case community. Next time I'll write about listeners from outside the university.</p>
<h5>Case students enrolled in the course might listen to that course's podcasts to:</h5>
<ul>
<li>Review material for exams.</li>
<li>Listen again to segments of discussion that were missed while taking notes.</li>
<li>Watch or listen to a lecture that demonstrated how to operate a certain piece of lab equipment, or that documented certain safety procedures.</li>
<li>Review material that was confusing during the first lecture. This could be particularly helpful in foreign language classes or in classes that introduce something new or challenging for the first time.</li>
<li>Listen to a lecture that was missed due to absence. While most students understand that class attendance provides benefits&#8212;such as participation in real-time discussion&#8212;unavailable in a podcast, there will be times when absences are unavoidable. At least this way&#8212;when students do have to miss a class&#8212;they will benefit from hearing the whole discussion rather than trying to make sense of a classmate's illegible notes!</li>
</ul>
<h5>Case students not enrolled in this particular course might listen to academic podcasts to:</h5>
<ul>
<li>Review material covered in a previous course that provides foundational elements to their current course.</li>
<li>Learn more about a specific topic&#8212;that is also studied in a different or related field&#8212;in preparation for researching a paper. For example, a history student writing a paper on the Renaissance, may gain insight by listening to a related podcast from a class in art history or literature.</li>
<li>Identify a professor's teaching style. When trying to decide whether to take a course from Professor A or Professor B, a student could listen to the podcasts to determine which professor's teaching style fits most closely with that student's learning style.</li>
<li>Explore new subject areas in anticipation of choosing classes for the following semester.</li>
<li>Learn more about topics outside the student's primary areas of study. Students may be interested in a variety of classes that don't fit into their schedules. By sampling subjects through podcasts they can satisfy their curiosity as time allows.</li>
</ul>
<h5>Case faculty &amp; staff might listen to academic podcasts to:</h5>
<ul>
<li>Find out more about related research being done by faculty in other departments.</li>
<li>Listen to information&#8212;presented by colleagues&#8212;related to joint research projects.</li>
<li>Learn about a topic outside one's area of expertise&#8212;simply because it sounds interesting.</li>
<li>Gain insight into a subject related to a particular work project. For example, fundraisers looking to match donors to specific programs, writers looking to publicize a project, and others can augment their knowledge by listening ro relevant podcasts.</li>
</ul>
<p>So far I've covered only a fraction of possible reasons members of the Case community might listen to academic podcasts. I'm sure those of you reading this will have many additional ideas, so please share them by commenting below or via the iTunes working group. If you are interested in becoming more involved in the development of iTunes at Case, we also welcome you to join our 
<a href="http://itunes.case.edu/charter/">charter working group</a> by 
<a href="https://lists.case.edu/wws/info/itunes">subscribing to the iTunes@Case Mailing List</a>.</p>
</div
></content
><author
><name
>Heidi Cool</name
><email
>heidi.cool@case.edu</email
><uri
>http://blog.case.edu/webdev</uri
></author
></entry
><entry
><title
>Podcasting macht Spa&amp;szlig;! (Podcasting is fun!)</title
><link href="http://blog.case.edu/webdev/2006/03/06/podcasting_macht_spa_podcasting_is_fun.html"
 /><id
>http://blog.case.edu/webdev/2006/03/06/podcasting_macht_spa_podcasting_is_fun.html</id
><published
>2006-03-06T16:55:16Z</published
><updated
>2006-04-06T21:47:08Z</updated
><category term="Podcasting" label="Podcasting"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<p class="photoright">
<img alt="iPod mit &#220;bel Kn&#252;bel der erste" src="http://blog.case.edu/webdev/2006/03/06/german.jpg" width="300" height="453" />
</p>
<p>Saturday afternoon I sat chortling on my couch as &#220;bel Kn&#252;bel (a teenage boy played by an Evil Knieval figure), flirtatious Gummi-Bears, and a pair of rubber shoes tried to teach me German. This was not the latest in children's progamming on WVIZ, but rather a new podcast from 
<a href="http://www.mygermanclass.com/">http://www.mygermanclass.com/</a>. The primitive animation and kitsch story lines, were so amusing, and so distinctly German, that I was compelled to watch all 10 episodes at once. Having taken 2 years of German in college (much of which I have since forgotten) I was able to understand most of the plots, and while I am not yet sure if &#220;bel's pet is meant to be a dinosaur, horse or dragon, it was quite clear that he has a freundin named Heidi mit blaue augen&#8212;just like me! Those unfamiliar with the language will still be able to follow along, as the "acting" is meant to underscore the meaning of the dialogue.</p>
<p>As I watched Uwe the red Gummi-Bear struggle self-consciously with romance, and young &#220;bel suffer from the bad advice offered by his vater, &#220;bel der Erste (pictured right on my iPod&#8212;no wonder he's a bad parent!), it occured to me that, as silly as it was, this was a great example of using podcasting for education. With a clever script, simple props or volunteer actors, and equipment borrowed from the 
<a href="http://fc.case.edu/">Freedman Center</a>, anyone at Case could create a video podcast. Whether you are teaching a language, demonstrating the use of lab equipment, or reviewing the disastrous results of a particular military strategy, the tools are now available to produce audio-visual aids more easily than ever before. While it might take experience and skill to draw an animation in Flash, almost anyone can talk into a microphone while moving Gummi-Bears around a table. Such videos&#8212;produced to achieve specific goals&#8212;can offer added value to your website.</p>
<p>Produced by 
<a href="http://www.col.k12.co.us/">Colorado Online Learning</a> as part of a fee-based German class, the 
<a href="http://feeds.feedburner.com/mygermanclass">video podcasts</a> are distributed&#8212;for free&#8212;from 
<a href="http://www.mygermanclass.com/">http://www.mygermanclass.com/</a>. They are produced in German, with German substitles. Scripts, discussions, self-checks, oral exams, and teacher feedback are available to those who sign up for the course.</p>
<p>For those of you not already familiar with podcasting, I highly recommend 
<a href="http://blog.case.edu/FreedmanCenter/2006/03/01/blogs_wikis_podcasts_for_beginners">Blogs, Wikis, &amp; Podcasts for Beginners</a>, Aaron Schaefer's recent presentation on this subject. 
<a href="http://blog.case.edu/FreedmanCenter/podcasts/03-01-06.m4b">Listen to the podcast</a>.</p>
</div
></content
><author
><name
>Heidi Cool</name
><email
>heidi.cool@case.edu</email
><uri
>http://blog.case.edu/webdev</uri
></author
></entry
><entry
><title
>Podcast 411 Website</title
><link href="http://blog.case.edu/ghk4/2006/02/16/podcast_411_website"
 /><id
>http://blog.case.edu/ghk4/2006/02/16/podcast_411_website</id
><published
>2006-02-16T13:37:28Z</published
><updated
>2006-02-16T13:38:40Z</updated
><category term="Podcasting" label="Podcasting"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<a href="http://www.podcast411.com/">http://www.podcast411.com/</a>
</div
></content
><author
><name
>George Klippel</name
><email
>george.klippel@case.edu</email
><uri
>http://blog.case.edu/ghk4</uri
></author
></entry
><entry
><title
>Aaron Shaffer and Mano Singham</title
><link href="http://blog.case.edu/jeremy.smith/2005/12/16/aaron_shaffer_and_mano_singham"
 /><id
>http://blog.case.edu/jeremy.smith/2005/12/16/aaron_shaffer_and_mano_singham</id
><published
>2005-12-16T09:03:29Z</published
><updated
>2005-12-16T09:04:26Z</updated
><category term="linkblog" label="linkblog"
 /><category term="podcast" label="podcast"
 /><category term="podcasting" label="podcasting"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>By the way, if you haven't heard 
<a title="The Freedman Center in Kelvin Smith Library: All About Blogging from Case's Most Prolific Blogger" href="http://blog.case.edu/FreedmanCenter/2005/12/13/all_about_blogging_from_cases_most_prolific_blogger">Aaron Shaffer's and Mano Singham's podcast</a>, I highly recommend it.</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
>Freedman Center</title
><link href="http://blog.case.edu/jeremy.smith/2005/12/05/freedman_center"
 /><id
>http://blog.case.edu/jeremy.smith/2005/12/05/freedman_center</id
><published
>2005-12-05T23:29:29Z</published
><updated
>2005-12-05T23:38:03Z</updated
><category term="freedman center" label="freedman center"
 /><category term="mainblog" label="mainblog"
 /><category term="podcast" label="podcast"
 /><category term="podcasting" label="podcasting"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>Today, I finally made my way over to check out the new 
<a href="http://wiki.case.edu/Freedman_Center">Freedman Center</a> and 
<em>man</em> is it nice. The equipment there is top notch (and plentiful). And there was some real 
<strong>wow!</strong> factor in their inventory management systems. 
<a title="Aaron Shaffer" href="http://blog.case.edu/axs221/">Aaron Shaffer</a> and I sat around and recorded some dialogue that Aaron is planning on cleaning up and posting as a podcast. I'll point to it once it's up. Hopefully, my long, acronym-laden techno-geeky monologues I regularly launch into somehow seem tempered. 
<b>P.S.</b> I also added RSS enclosure support to 
<a title="Planet Case" href="http://planet.case.edu/">Planet Case</a>. So if one wants to just subscribe to any and all podcasts coming out of the 
<a title="Blog@Case" href="http://blog.case.edu/">Case Blogging system</a>, they are encoded into the 
<a title="Planet Case RSS Feed" href="http://planet.case.edu/rss20.xml">RSS feed</a>. 
<strong>Update:</strong> I mentioned it the same time it was posted &#8212; 
<a title="The Freedman Center in Kelvin Smith Library: RSS Feeds, Podcasting, &amp; the Case Wiki" href="http://blog.case.edu/FreedmanCenter/2005/12/05/rss_feeds_podcasting_the_case_wiki">The Freedman Center in Kelvin Smith Library: RSS Feeds, Podcasting, &amp; the Case Wiki</a>. I haven't heard it yet (downloading it as soon as I get home), so I haven't been able to count the number of times I say "uhh" or "ummmmm" yet.</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
>Podcasts + iTunes + del.icio.us == Beauty</title
><link href="http://blog.case.edu/jeremy.smith/2005/07/01/podcasts_itunes_delicious_beauty"
 /><id
>http://blog.case.edu/jeremy.smith/2005/07/01/podcasts_itunes_delicious_beauty</id
><published
>2005-07-01T21:31:11Z</published
><updated
>2005-07-01T21:31:50Z</updated
><category term="del.icio.us" label="del.icio.us"
 /><category term="mainblog" label="mainblog"
 /><category term="perl" label="perl"
 /><category term="podcasting" label="podcasting"
 /><category term="ruby" label="ruby"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
<code>
<a title="del.icio.us/tag/system:filetype:mp3+programming" href="http://del.icio.us/tag/system:filetype:mp3+programming">del.icio.us/tag/system:filetype:mp3+programming</a>
<a title="del.icio.us/tag/system:filetype:mp3+perl" href="http://del.icio.us/tag/system:filetype:mp3+perl">del.icio.us/tag/system:filetype:mp3+perl</a>
<a title="del.icio.us/tag/system:filetype:mp3+ruby" href="http://del.icio.us/tag/system:filetype:mp3+ruby">del.icio.us/tag/system:filetype:mp3+ruby</a></code>
</pre>This is the greatest thing since peanut butter.</div
></content
><author
><name
>Jeremy Smith</name
><email
>jeremy.smith@case.edu</email
><uri
>http://blog.case.edu/jeremy.smith</uri
></author
></entry
></feed
>
