Faculty Input – Angel and Mobile

10 10 2011

We’ve gotten a request from IR (via IRAC) for faculty member participation in two upcoming technology work groups, both to be led by Connie Wisdo in ITDA.  She’s looking for:

  • A few faculty members for a group on mobile apps. The University’s mobile app and mobile website have been up for a while, but are aimed at prospective students and alumni. The next phase of mobile development will focus on current students, faculty, and staff.
  • Six faculty members for a group on learning management systems (LMS). Our contract with Angel expires in 2013, so this group will be  identifying and prioritizing student and faculty needs, reviewing product options, and selecting the best comprehensive solution.

Faculty participants do not need to be TAG members, but we will ask that they share updates and information about the groups’ work to TAG so that we can disseminate it to the rest of the faculty (as described in our guidelines).

If you are interested in representing the faculty on either of these groups (or if you’d like to recommend a faculty colleague for participation), send me an email at yarmeyk2@scranton.edu by October 24.

Please feel free to pass this invitation along to colleagues. Thanks!

(Thanks to Dave Dzurec for being our IRAC connection.)





Guidelines for Faculty Input on Technology Decisions

9 12 2010

Once upon a time, there was a policy that became a Memorandum of Understanding that then became a set of guidelines.  Hopefully, the name of this document won’t change any more, since we think it’s finally done.  Well, for now.

After everyone we talked to universally agreed that an informal approach would be best, we decided to rename TAG’s first drafted policy as the “Guidelines for Faculty Input on Technology Decisions.” They’re posted here on the TAG website, and their purpose is to codify the shared expectations between the faculty and any administrative bodies that are responsible for technology resources on campus.  They’ve been reviewed by representatives from the Faculty Senate, Information Resources, Academic Affairs, and the Faculty Affairs Council.

Since the Guidelines aren’t an official policy, they can’t exactly be enforced – but we hope that they will serve as a useful model both for faculty members interested in providing feedback on technology decisions as well as administrative bodies interested in getting faculty feedback.

Here’s hoping that this language will help improve communication about technology decisions across campus.  Thanks to everyone who gave us feedback, and as usual, let us know if you have any questions.