TAG Meeting Notes 9/29/11

29 09 2011

We had our first TAG meeting of 2011-2012 this morning.  We had a lot to catch up on from the summer, so apologies for the long notes! As always, post a comment if there are any questions or concerns.

  • New members. Teresa Conte joined us from Nursing as a replacement for Cathy Lovecchio. Ben Bishop (Computing Sciences) joined us late last spring, as did Lori Nidoh (representing Public Relations). S.P. Chattopadhyay is currently on sabbatical, and Kevin Wilkerson has returned from his.
  • Novel Pedagogy Cohort. Jeremy and a few other CAS faculty members have formed a small group to explore and implement new pedagogy techniques in their classes – some of which involve technology while others don’t.  Tools to be explored include lecture capture and clicker systems. If any other faculty are interested in innovative pedagogy, let Jeremy know.
  • Lecture capture.  A team of stakeholders (including TAG members Jeremy, Kristen, Sandy, and Eugeniu) met several times in the spring and summer to review possible products for lecture capture.  The final recommendation was a hybrid solution of Media Site (as a back end) and Crestron HD appliances for the actual capture. Implementation will start in the Science Center and then spread to other departments. Right now, IR is working on setting up the back end servers while VistaComm is implementing the front end capture devices. The goal is to have LSC lecture capture ready to go by Spring 2011, and then expand to other departments next year as funding allows. Sandy and Teresa noted that Education and Nursing would be very interested in implementing lecture capture in their classrooms. Thanks to Jason Oakey over in Instructional Technology for taking the lead on this project!
  • Office 2010.  The upgrade to Office 2010 for faculty and staff is tied to the email conversion (see below) due to the incorporation of Outlook.
  • Windows 7. The upgrade to Windows 7 for faculty and staff machines currently running Windows XP is held up due to a security issue. XP users are currently admin users on their computers. While this gives us a lot of flexibility and control over our own machines, it also introduces security risks – users can accidentally install malicious code.  When we move to Windows 7, IR will change XP users’ roles from admin to standard user accounts. By default, standard users wouldn’t be able to install or delete applications, but ideally there will be a way for users to obtain temporary admin status when they need to install programs. IR is currently working out these privilege management issues, so Windows 7 deployment is pushed back to (tentatively) Spring 2011.   Wesley asked about 64 bit vs 32 bit machines – Jim said that by default new machines will be 32 bit, but faculty who need 64 bit should let him know.
  • Email conversion. The Microsoft Live @ Edu email transition has been delayed by issues with identity management (e.g., automatically assigning set permissions to new hires, and removing permissions from retirees, departing employees, etc). IR is working on a workaround plan that would let us go forward with the email conversion while temporarily skipping over identity management. IR is aware of “crunch times” in faculty schedules, so faculty email conversion will probably wait until intersession or beyond.
  • Personally identifiable information.  Ben asked about security concerns for faculty members who don’t use University email.  Jim recommends that any University business, and especially any University business that involves confidential information, be done using University services (like Angel and Royal Drive). The Identity Finder tool is available to help faculty and staff find any PII that might be on their machines. IR also has security training videos that faculty can watch to get an entry-level awareness of PII.
  • Information Resources Advisory Committee.  IRAC had been inactive for a year but is now reconstituted. IRAC members will be providing input on IR’s service portfolio. TAG members Dave, Paul, Eugeniu, and Lori will be on it as CAS faculty, PCPS faculty, CTLE, and PR representatives, respectively.
  • TechQual. IR ran this customer service survey over the summer. Preliminary results just came in, but IR is still processing them and will present them to IRAC next month.
  • Loyola Science Center. Most of the IT work in LSC is done, but there are still a few equipment issues popping up in classrooms. IR will continue working on this. Remaining projects include lecture capture, the auditorium, and RoomView, a tool that will allow Instructional Technology to monitor and maintain classroom equipment (e.g., whether or not a projector has been left on).
  • Wireless. The wireless upgrade project was approved.  Phase I (freshmen residences, the new Mulberry Street residences, and the LSC) is complete and adds 350 new WiFi points to the campus. Phase II is currently underway and will add 252 WiFi points in 21 buildings (residences, St. Thomas, and the Long Center). Phase III is scheduled for summer 2012 and will include the remaining academic and administrative buildings as well as outdoor coverage.  This is a big improvement – many thanks to the Network Infrastructure staff!
  • CTLE liaison. CTLE used to have two faculty liaisons who focused teaching and pedagogy. They have now added a third faculty liaison, TAG member Sandy Pesavento, to provide input on faculty interests and needs regarding pedagogical uses of technology.
  • Mobile access to Angel. CTLE and IR experimented with Blackboard’s iOS app for Angel, but found it to be a very limited tool, particularly for teachers (e.g., faculty can’t enter grades or interact with Angel dropboxes).  So mobile access to Angel still isn’t conveniently available at this time.
  • LMS review. Our contract with Angel expires in 2013, so a review committee will begin exploring other learning management system (LMS) options in January. Connie Wisdo in ITDA will lead the group. Eugeniu said that we might have an opportunity to use a “free” installation of Blackboard temporarily (on top of our existing Angel installation) so that faculty could try it out. Dave asked whether or not we would be able to migrate courses from Angel into a new LMS. Eugeniu said that from our current version of Angel (7.4), we could export/import single courses into Blackboard, with some imperfections. If we upgraded to v8 of Angel, we’d be able to batch migrate courses. Blackboard would also complement our Royal Card and emergency notification systems, since they’re Blackboard products (Transact and Connect), but it might not be easily tied into Banner.
  • Academic Technology Plan. The Provost’s office has no updates on the Academic Technology Plan.
  • Mobile website and app. Lori shared some analytics to give us an idea of how the mobile website and mobile app are being used. The app has been downloaded 7,604 times (mostly by iOS rather than Android devices). An in-app poll asked about the user’s identity, and 57% of the poll-takers were current students, 28% were alumni, 10% were prospective students, with faculty, staff, and other community members making up only 6%.  New app modules include Admissions and the Library (live but still being tweaked), with an Alumni module on the way. An iPad version is also on the timeline for this year, and hopefully mobile authentication is on the horizon.  The m.scranton mobile site is getting plenty of traffic. The most commonly viewed mobile pages are the home page and the admissions and academics home pages. [Note: Stats on the mobile app are here (in PDF). Stats on the mobile site are here (also in PDF).] PR is also setting up automatic redirects from the full site to the mobile site for recognized mobile devices – right now, the only active redirect is from the full site home page to the m.scranton home page.
  • Faculty websites. We’ve figured out a good workflow for faculty websites with CTLE. Any faculty member who wants to create a new website in the CMS should contact Aileen McHale in the CTLE. The CTLE TechCons will set up the faculty member’s web space, and then can help him or her as needed with templates or other support.  Sandy and Anne Marie would like to encourage faculty members (and any other page admins) to keep their websites current.
  • Continuing education. TAG members interested in learning more about academic uses of technology should keep an eye out for continuing education opportunities, since funding may be available. Jeremy and Sandy will each attend a day of the EDUCAUSE conference, courtesy of the Provost’s office.  Anne Marie and a few representatives from IR will also attend. TAG members who do participate in continuing education are asked to report back and share conference highlights.
  • Computerized testing. Teresa reported on concerns from the Nursing department. Nursing licensing exams are all online, so the department uses computerized testing to help their students prepare for the licensing environment.  Nursing faculty have run into trouble finding places to conduct their computer tests – there isn’t enough space to accommodate large classes, and classrooms that do accommodate that many students have been booked for other courses.  An ideal solution would be a large “shared resource” lab (possibly run by CTLE/Library) that faculty could schedule for tests, with computers set up to restrict access to the testing environment. Anne Marie suggested that we look at how other schools have solved this problem. Teresa will get more details on Nursing needs. Jim asked if other departments have this need, and for what class sizes. Once we have more information, we can agree on a good solution and then seek funding.
  • Our next meeting will be October 27. TAG members are asked to keep collecting (specific!) feedback from other faculty members on technology concerns or issues, and we’ll keep sharing information here as projects continue.

——

Note: Updated 10/24/11 with PDF docs of mobile app and website statistics shared during the meeting.





Connecting to the Academic Webserver

29 07 2011

IR has shared with us these instructions (PDF) for faculty and staff who need to update pages on the new academic server (not the CMS).

As always, if you have questions or run into any trouble, please let us know!

——————–

Update (8/1/11): Instructions were revised – the link now takes you to the corrected PDF. Thanks to Tim Cannon for catching the errors!





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?





Meeting Notes 1/24/2011

25 01 2011

Sorry for the outburst of posts today! But just wanted to share some news from our TAG meeting yesterday.

The meeting centered around our frighteningly long to-do list and how to tackle all of TAG’s various projects.  One of our main discussion points was how to get more faculty actively involved in TAG – so if anyone has any suggestions, please let us know! We’re hoping that our departmental meeting visits in early Spring 2011 will help us recruit more willing victims volunteers.  If not, we may have to cut back on our project list.

Here’s a snapshot of some of the projects we’re working on, somewhat in order of priority:

  1. Transition to Microsoft Live @ Edu email.  This transition will have two main impacts on faculty.  Firstly, faculty who currently use Thunderbird will need to adjust to a new interface (Outlook desktop client or web client).  Secondly, IR is still exploring ways to migrate faculty email both from the current RoyalMail server and especially from faculty local drives to Live @ Edu cloud storage.  TAG is figuring out the best ways for us to be involved in this transition – whether that means training faculty on the new interface, participating in discussions about migration strategies, etc.
  2. Classroom Mediation Survey. TAG is working with IR, Academic Affairs, and the CTLE to put together a survey that will determine what classroom technology is used in what classrooms, so that equipment budgets can be allocated more efficiently.
  3. User ID change. TAG’s role here will basically be to help get the word out to faculty so that no one will be surprised come March/April when they need to log in with their R number.
  4. Knowledge base. TAG hopes to provide here on our website lists of faculty who use certain classroom technologies (see, for example, our list of campus resources on Facebook and other social media) – so that if you’re interested in trying out a new technology tool in your classroom, you’ll know who on campus you can talk to about it.
  5. Faculty websites. TAG is working with PR to establish protocols for requesting and building faculty websites within the new CMS.  We’re on track to have two models to show other faculty, one built using a basic template and one built using an advanced template.
  6. Faculty scholarship database. Word has it that Academic Affairs is reviewing products for tracking and cataloging faculty publications. TAG hopes to provide faculty feedback on the products reviewed before a decision is made.
  7. Keeping the TAG website up to date. We hope that this website becomes (if it isn’t already) a useful resource for faculty.
  8. Evaluating and providing feedback on technology training for faculty.

If you or anyone you know would be interested in and willing to lend a hand on any of these projects, please let us know!

Last but not least, TAG’s next major step is to visit a department meeting in early Spring 2011 for each department on campus. We’re currently working on developing talking points for those visits. Keep an eye out for your TAG liaison at your next faculty meeting!

 





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.