Faculty Websites – Know Your Options

24 10 2011

TAG has heard some renewed concern and confusion about faculty websites lately, so we thought it might be a good time to revisit the available options and outline how faculty members can take advantage of them.

When building a personal website (not a departmental website), faculty have several options with varying levels of control and support:

1. Use the Content Management System (CMS) and build off of your department’s page.

  • You can choose to build a personal faculty website as an offshoot of your department’s page.
  • Faculty pages using this option must use the standard CMS templates (that is, the page will look like all of the other University pages).
  • An example is TAG member Dave Dzurec’s page off of the History Department website.
  • This option offers the least amount of design control, but it can be done pretty quickly.
  • To request a page like this, talk with your department’s webmaster.

2. Use the Content Management System (CMS) and build your own site.

  • You can choose to build an independent (that is, not an offshoot of your department’s page) personal faculty website within the CMS .
  • With this option, you’d store your page content within the CMS, but you are not required to use a standard University template – so your site doesn’t have to look like the rest of the University pages.
  • The CTLE offers two templates (basic and advanced) that you can use as a starting point, but both are completely editable either by the faculty member him/herself or with the help of a CTLE TechCon. So you can change colors, add features, etc. Note that neither template is branded with  University of Scranton colors or logos.  As an example, I made a demo page by tweaking the advanced template.
  • You can also choose to design your own site from scratch by copy/pasting HTML from a web design tool (like Dreamweaver) into the CMS. This choice gives you more control over the page design.
  • To request space on the CMS, simply contact Aileen McHale at the CTLE. The CTLE TechCons will set up your web space, and if you like, they can also help you build and edit the pages – just let Aileen know how much help you think you will need.

3. Use third party services to design and/or host your site.

In all cases, faculty members have complete control over their site’s content. PR and CTLE don’t have any control over the text, images, documents, and links you post.  All that is expected is that you follow the University’s Code of Responsible Computing.  Also in all cases, it’s the faculty member’s responsibility to keep their page up-to-date.

If you have questions or concerns about faculty websites, or if you want to share recommendations for third party web design/hosting tools, please let us know!

Many thanks to PR and the CTLE for helping us work out a user-friendly workflow for faculty websites in the CMS.





Follow-up on Faculty Webserver (Tiger) move

21 06 2011

If you have an account on the old webserver, Tiger, you should have just gotten this message from Connie Wisdo:

There is an attached file (here) with instructions for faculty to get their own website on the CMS. We highly encourage faculty who wish to maintain campus-based webpage to look at these instructions and consider building their own web page in the CMS this summer. The transitional webserver will NOT be a permanent space. Late this summer, TAG will be posting some more detailed instructions, as well as demo webpages, showing what is possible for faculty within the CMS. More details to follow.

Dear Faculty Members,

In case you missed the notices in Royal News, my.scranton, and Bboard, I wanted to share the following information, because you have a non-empty Web directory on the Tiger (academic.scranton.edu) server.
The Web server which is known as both “Tiger” and academic.scranton.edu will be officially retired on July 28, 2011, due to its operating system’s end-of-life. (Nearly all of the official web pages/sites of our academic departments and programs that were previously housed on the academic server (Tiger) have been migrated to the Web Content Management System (CMS).)
A transitional Web server is being set up for departments, clubs, and faculty/staff that have not yet migrated their Web sites to the CMS. Individuals (Faculty/Staff) who wish their web directories moved to the transitional server must send an email request to me (Connie Wisdo (wisdoc1@scranton.edu)) by July 1, 2011. In your email request, please specify the URL of the home/index page of the site(s) you need moved.
You also have the option of moving your Web site(s) to the CMS. Attached is a document containing more details. If you would like to move your site to the CMS, please contact the CTLE, as directed in the attachment, and they can provide assistance to you.
If you have your site moved to the transitional server, you will have SFTP access to your site on the new server, on July 29th, using your my.scranton username and password. Instructions will be sent to faculty in a few weeks, and will also be posted to the TAG Web site. Your Web site address (URL) will not change when it is moved to the new server. URLs will still begin with “http://academic.scranton.edu/”

Note: both the old academic server and the new transitional server will be unavailable for any updates to any Web sites from July 27th to July 29th. Web sites will be accessible on a read-only basis during this time.

If you have any questions, please contact me. For those of you who already sent me an email requesting your site be moved, and have received a reply, there is no need to contact me again.





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?





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?





New PIR website

3 06 2010

The Division of Planning and Information Resources home page is being converted over to the University’s new Hannon Hill content management software – and the new page is worth taking a look.  Some content that might interest faculty:

There’s also other content still in the works – like information on New Initiatives (including handheld devices), and a Division Organizational Chart.