Dr. Strangepage: Or How I Learned to Stop Worrying and Love the CMS

26 01 2011

Note: In light of some of TAG’s recent discussions about the CMS, we thought it might be useful to have a real live faculty member’s perspective on what it’s like to manage a departmental page.  Many, many thanks to Dave Dzurec for being willing to write up a post about his experiences working on the History Department’s page!

The migration of the History Department’s website to the CMS has not been without its bumps. There have been times when segments of the page have been a complete mess, there have been times when I’ve lost whole folders, there have been times when I’ve inadvertently changed the department chair’s picture to suggest that he is a member of the Italian Communist Party (not really, he did that himself). Migrating the content from the old site to the new was a great deal of work. Part of the challenge was learning the new system. Some of these challenges were ultimately beneficial as the process of migrating the site helped to familiarize me with some of the idiosyncrasies of the CMS (with a great deal of help from Sarah Johnson). Since we’ve manage to get the pages up and running, however, things have been relatively smooth. I try to review the page at least once every couple weeks to make sure everything is functioning and there’s nothing wrong with our links, I update student events (meetings of the Royals Historical Society, calls for applications to the Phi Alpha Theta, the History Honor Society) as they are announced, and once a semester I update the faculty news section, based on reports given to me by members of the department. There are of course still occasional bumps. This past semester, when we realized that our links to the department course offerings were out of date, I spent a good deal of time working with Ann Marie Stamford to correct the issue. On the whole, however, our current CMS software seems to be a reasonable option (at the very least, no better or worse than any of the alternatives available at the institutional level).

In addition to concerns about ease of use, there has been some concern about individual faculty pages. Within the History Department, faculty continue to be responsible for their own pages. I have simply linked to individual pages from our faculty/staff page. When one of our faculty members moved his personal page to a new site, I simply updated the link. As I understand it, the move to the CMS has had no direct impact on individual pages and we continue to have a great degree of autonomy in maintaining our individual sites. [Note: TAG is currently working with PR to set up a protocol for how faculty can request websites. Existing websites will be moved over to a new academic server. See our post on The Straight Dope on Faculty Websites for more details.]

From the consumer side, response to the final product has been generally positive. Over the course of the past couple of years and three job searchers, we have received a number of compliments from various job candidates about the overall appearance and ease of use of our department webpage. While I realize that it’s highly unlikely for a job candidate to insult a potential employer (especially given the realities of the job market in the humanities), the fact that they made special note of the quality of the pages is, I think, illustrative of the quality of our redesigned web presence.

One area of concern I do have is the issue of general responsibility for maintaining these pages. There doesn’t seem to be a great deal of consistency across the University about who is in charge of department sites. The CMS workshops I have attended have included everyone from department secretaries, to faculty, to members of the PR department. I think it would be beneficial to define roles and expectations more clearly. For department secretaries, is the addition of maintaining a department webpage to their already large workload a reasonable expectation? For faculty (and on a personal note) while I don’t find maintaining the department webpage to be terribly onerous and my department has certainly counted the work I have done as service in my annual evaluation, is working on a department site the best use of faculty time?





Meeting Notes 11/11/2010

11 11 2010

Another month, another TAG meeting.  We had a packed agenda today and did our best to at least touch on each issue.

New member:

  • Anne Marie Stamford, Assistant Provost for Operations, has joined the committee as a representative for the academic administration.  Anne Marie was invited to join after we realized she was dealing with some of the same questions as TAG (e.g., how to get feedback from faculty on technology issues). Welcome, Anne Marie!

Follow-up on survey results:

  • The results from our 2010 survey on faculty communication have been posted to the TAG site, both summarized and in full.
  • Jim, Jeremy, and Kristen drafted up responses to the “Top 9” major concerns from the survey comments.  TAG members have until Monday to make any edits/suggestions.
  • What’s the best way to distribute these “Top 9” responses to faculty?  On one hand, we want to get the information out quickly rather than holding it back – and some of the issues (i.e., requesting new computers) are time sensitive. On the other hand, we do want people to actually consider and respond to the “Top 9,” not just ignore them as tl;dr.  Our current plan is to post them (individually) to the TAG site, and then send out an all-faculty email with the first response on communication, and links to the next 8 responses.  If we don’t get a lot of feedback on the other 8 responses, we can also send out updates on the next 8 posts at regularly spaced intervals (e.g., 2x/week).  Jeremy and Kristen will coordinate this with Anne Marie.
  • Sending email to all faculty that includes non-scranton.edu links is somewhat of an issue. IR wants to make sure that people are very cautious about what links they click on, in light of the many recent phishing attacks.
  • Anne Marie suggested that some of the “Top 9” responses would be of interest to staff.  She will share them with the Data Technologies group.
  • More detailed statistical analysis of the survey results is on the way.

Catalog

  • There are several reasons why faculty feel strongly about having paper copies of the catalog (e.g., ease of advising, being able to bookmark/make notes, concerns about monitor sharing…).  This seems to be a major issue mostly in CAS, where most faculty are advisors (unlike in PCPS and KSOM, which have professional advisors).
  • We posted a PDF of the catalog to the TAG site.  Anne Marie has 10 printed copies of the catalog in the Provost’s Office if anyone wants one, and she will look into printing enough copies of the catalog for all advisors next year.

Feedback from English Department

  • Teresa brought feedback from the English department on three main issues: the need for a print copy of the phone book/directory, recommendations for a WYSIWYG editor for HTML code (for the CMS), and difficulty with TSC customer service.
  • In general, TAG will respond to faculty feedback like this by 1) posting a summary of the question, with a response from TAG, to the TAG site and 2) emailing the faculty member directly with the response.
  • Kristen will coordinate with Teresa to get responses to these concerns posted to the TAG site.

Soliciting faculty feedback

  • There are several issues on which faculty feedback is needed, including the CMS (per Anne Marie), classroom mediation (per Jim), and faculty areas of technology interest/expertise.  What’s the best way for TAG to gather this information? Our communication survey was useful, but didn’t hit all faculty.
  • TAG will work on assigning liaisons from TAG to each department.  Liaisons could visit February department meetings to solicit feedback from entire departments.  They’d also be able to let faculty know that TAG exists and talk about how we can be a resource.
  • To assign TAG members to departments, Cathy will work on dividing PCPS departments between herself and Kevin, and Jeremy and Teresa will work on assigning CAS departments between them, Tim, and Kristen.  Neither SP or Sufian were in attendance, so we will ask them to choose KSOM departments.  Jim and Anne Marie will send Kristen specific questions on which they need faculty feedback.

Email and Calendaring change

  • Campus email will be moving to Microsoft Live@Edu.  To smooth this transition, TAG has offered to help IR communicate with faculty about the transition.
  • Since this is a big issue, we’ll have a meeting sometime after January specifically dedicated to the email issue.  By then, we should have some test accounts so TAG members can identify potential faculty concerns.
  • We discussed describing the change as a benefit rather than an annoyance – while faculty will have to learn a new interface, they’ll get a much larger quota and along with other new features. We also need to communicate to Google fans that, while Gmail was considered, IR did have valid reasons for choosing Microsoft.

TAG Policy

  • A few TAG members drafted a policy for codifying how TAG interacts with IR and facilitates faculty feedback into technology decisions.  We’d like the rest of the TAG members’ feedback on the draft policy, with an eventual goal of passing it up to the Faculty Senate Academic Support committee.   We’ll post the policy on the TAG site next week after all members have gotten to review it.
  • Cathy pointed out that the policy does not address all of TAG’s original goals – so we need to be clear that the document is not a mission statement for TAG but instead a single policy that defines one aspect of TAG’s goals.

Other points of discussion

  • We discussed the idea of visiting Dean’s Conferences in order to spread the word about TAG, but we agreed that checking in with the Faculty Senate would be best before approaching the Deans directly.
  • Cathy and Kristen will meet after Thanksgiving to start working on aggregating classroom technology resources for faculty.




CNAC Reminder… and Brown Bag Postponement

9 11 2010

Just a reminder that we’ll all have to log in to Cisco NAC Agent tomorrow morning in order to be able to access the University network.

Also, the Provost’s office is trying to reschedule this week’s Brown Bag on the CMS.  It seemed like this Thursday wasn’t a good time for most people. We’ll keep you updated on any new dates and times.





CMS Complaints? Brown Bag It

9 11 2010

Just a reminder that the Provost’s office is holding a Brown Bag Lunch on “Web Content Management System: Issues, Concerns, Frustrations” this Thursday, November 11th at 11:45am in the Provost’s Conference Room (RSVP to Linda Walsh at walshl7@scranton.edu if you plan to attend). TAG’s own Jeremy Sepinsky will be co-hosting.

Before you go, you may also want to take a quick look at our post on “The Straight Dope on Faculty Websites” – which we’ll be updating as soon as we get more information from PR.





The Straight Dope on Faculty Websites

8 11 2010

Update: This explanation has been superseded by “Faculty Websites: Know Your Options,” posted on 10/24/11.

————————————————-

There’s been a lot of confusion and concern about faculty websites lately.  With a generous tip of the hat to TAG’s friends in Public Relations and the CTLE, here’s what faculty need to know about creating personal websites (note: this post does not apply to departmental websites).

Faculty are NOT required to use the CMS for their personal websites.  There are actually three different options for faculty members.

1. Use the CMS.

  • You can CHOOSE to use the CMS for your personal website.
  • Using the CMS, you’ll have two templates to work from.  There’s the “Basic” template, which is simple and (let’s be honest!) pretty ugly, and there’s the “Advanced” which is prettier and more customizable.  Note that neither template is branded with  University of Scranton colors or logos.
  • PR has promised to send along more information on how faculty can request space on the CMS server for a personal website.  I’ll update this post when I hear back from them.
  • Should you choose to use the CMS, YOU are in control of your content.  PR doesn’t have any control over what you post.  All that is expected is that you follow the University’s Code of Responsible Computing.

2. Use the academic server.

  • If  you want to put your personal website on the academic server, stop by the CTLE  (either make an appointment or walk in during lab hours) and check in with one of the TechCons.
  • A TechCon will set up space for you on the academic server.
  • Once you coordinate your log in with the TechCons, you have the freedom to upload any HTML files you like. So if you want, you can design your own website with a WSIWYG editor (like Dreamweaver or Expression, etc) and have it look however you like.
  • If you want help building your website, you can choose to have the TechCons help you.  They have several templates that they work off of (see a few examples here).  They’ll do a prototype to get you started, and you can maintain it from there.
  • If you want a LOT of help on your website, the TechCons can also help you update the content when you need to.
  • You may hear about changes happening on the academic server.  The academic server is in an environment that’s no longer supported, so it is going to be replaced sometime in Spring 2011.  This won’t have any noticeable effect on your website – your files will just be migrated to the new server.  At some point, IR and/or PR will probably encourage everyone with files on the academic server to review their content and delete any outdated files.  This is just a request and a chance to get rid of old web pages- anything you do not choose to delete will be migrated over.

3. Go “rogue.”

  • You can always feel free to use a third party service to create your own, externally hosted website.  Some popular, free, and relatively easy-to-use web hosting tools include Google Sites and WordPress.  I’m a fan of Sharon Meagher’s Philosophy and the City website, which she built and hosted with Network Solutions, a service that charges a small monthly fee.

Hopefully this will help resolve some questions about faculty websites.  If you have other concerns about either faculty websites or the CMS, be sure to attend the Provost’s Brown Bag on November 11th at 11:45am. The whole session will be dedicated to discussing CMS issues and will be co-hosted by TAG’s very own fearless leader, Jeremy Sepinsky.





CMS – Faculty Friend or Foe?

9 09 2010

A recent faculty discussion brought up several questions and concerns about the University’s new content management system (which was purchased from Hannon Hill):

  • Do faculty use personal websites for teaching, research, and service?
  • Does/will the CMS hinder faculty from accomplishing their teaching, research, and service?  Some faculty members described the CMS as too restrictive and too user-unfriendly for their needs.
  • Several faculty members were concerned about the increase in workload that would be required to maintain departmental websites.  Some expressed resentment that IR imposed a new system on them and now expects them to spend the time to learn how to use the CMS and maintain their own departmental websites.
  • There was also concern about being forced to conform to PR-restricted designs and formats (feeling “branded”).

Where can TAG take this issue from here? Should we hold an open forum to elicit more feedback?