Note: Since we are evaluating blogging software, we're keeping our running notes on a blog at http://wesblogevaluations.blogspot.com/ . This page will contain a summary/synthesis of what we write in that space.
From Flickr: Note: Wordpress users, your API Endpoint is http://your.blog.address/xmlrpc.php
UC Davis - https://confluence.ucdavis.edu
Here are some examples of universities using blogs and their policies.
1. College Web Editor http://collegewebeditor.com/blog/
2. Harvard Law School - blog policy http://blogs.law.harvard.edu/home/terms-of-use
3. UThink- UMN blogs http://blog.lib.umn.edu/ – policy http://blog.lib.umn.edu/service.html
4. NC State http://www.ncsu.edu/policies/academic_affairs/library/RUL02.61.01.php
5. Willamette Univ policy http://blog.willamette.edu/blog-policy.html
6. Western Kentucky Libraries Blog policy http://blog.wku.edu/library/?page_id=136
7. Liberty Univ policy http://www.liberty.edu/media/1616/blog_policy.pdf
8. Amherst https://cms.amherst.edu/about/terms_conditions
9. Oberlin (draft) http://dokuwiki.wesleyan.edu/doku.php?id=its:blogs:oberlin-draft
10. Colby http://www.colby.edu/info.tech/policies
It is our sense that we will need to provide both the Journal LX tool for use within blackboard, and another tool for general purpose blogging. We will however look hard at Journal LX to see if it could serve as both.
For some uses, we may want to recommend that our clients choose to use an externally hosted solution. Both blogger and typepad are viable candidates for that function. (We need to define when we would want to make that recommendation.)
In addition to the general requirements for all of the web 2.0 applications that we've developed, we have developed the following list of requirements that are specific to blogging:
1.use content management system to create ad hoc groups Ideally, we will be able to use either the content management system or Active Directory to allow the creation and maintenance of ad hoc groups, rather than relying on the group functions within the application.
2. ability to create blogs for invididuals by request with caveats Individual faculty, staff, and students should be able to create blogs by request, in an automated way. We would need to develop policy about what to do with blogs that have become inactive and/or obsolete.
3. subscribe to comments via email and RSS It should be possible to subscribe to comments via email to allow people to track on-going conversations taking place on the blog and/or on individual posts witin a blog.
4. exportability The data within the blog should be exportable so that it can be imported into a new system should we decide to change systems.
5. no anonymous comments As a policy, we think it makes sense to not allow anonymous comments.
6. moderated comments The owner of a blog should be able to allow/disallow comments, and if allowed, choose whether or not comments need to be moderated before appearing.
<iframe width='1000' height='400' frameborder='0'src='http://spreadsheets.google.com/pub?key=pLglBzHAsINLvaaX--L-2DQ&output=html&gid=0&single=true&range=A1:B7'></iframe>
We're storing our examples at http://wesblogevaluations.blogspot.com/2007/01/academic-examples.html for the time being.
You might also want to check out the links at delicious under http://del.icio.us/tag/BloggingAcademicExamples
where else?
Entry in NITLE blog pointing to a specific blog assignment.
Some resources: