Tag Archives: tagging

The Commons and Orientation

Stakeholder: Katy Abbott
Website: http://www.middlebury.edu/campuslife/commons and http://www.middlebury.edu/campuslife/events/orientation
Redo Contact: Ryan Kellett

General: Orientation in both February and September is run, in part, by CCAL (JJ Boggs). There are five commons, each with unique personality and work processes. This report represents all five commons.

Orientation Requirements:

  • Constant Update: the orientation website is unique in that information changes almost daily, especially in the several weeks prior to Orientation which takes place in September and February. That said, the authors of these updates are far and wide since Orientation brings in many areas of the College. It is essential to both have a “working space” for information updates and then a one-click solution to immediately reflect those changes on outward-facing website which is presented to all incoming first-years. Currently, it is far too cumbersome to update the site that often and results in misinformation among first-years who then choose to call in or email.
  • Workflow: The collection of people in charge of Orientation do not have the time or background to necessarily update the website. They have other roles at the College and therefore updating falls to the wayside.
  • AskHiba: It would be nice to have an AskHiba-type (http://askhiba.wordpress.com/) place for first-years to ask questions and receive answers from peers (both upperclassmen and other first-years). This would relieve some of the pressure of calls and emails while still being quite personal. Students should be able (and are likely willing) to run this site. If it’s possible, it would be nice to dynamically feed a FAQ from these questions and answers.
  • Facebook: Start “official” Facebook groups for the admitted students (which then turn into first-years). It should be official in that the school or a Middlebury student moderates it, but it should not be moderated by the Orientation committee. Link our pages into this group.
  • Text Online: find a better way to display lots of info in CMS rather than lists and PDFs.
  • Visually Stimulating: better visual appeal and presentation of orientation information. Rollover graphics would be nice.
  • Similar CCAL (Doug Adams) functionality: online forms, payment, ticketing, embedded interactive media, etc. We do need to be able to take reservations and payment on line.  Class photos, Bread Loaf accommodations, and more mean that having that capacity would be ideal.

Commons Requirements:

  • FYS and Sophomore Experience: Find ways to support the first-year seminars and sophomore experience as part of the 4/2 Commons System. This could take the form of displaying some of the work from the FYS, as fed up through class blogs or websites. This should not require students to do any more work than they already do — should be automated in feeding up content to populate some sort of display of the Commons experience
  • Dynamic Bulletin Boards: Commons are often places to post information (for example in weekly “newsletter” type publications that are posted in bathrooms). An online space (message board, wiki, or wall?) for such activity might be nice but must be sure not to compete with other online spaces. If underused, it becomes useless. Some sort of moderation/vetting needs to be in place.
  • Neighborhood: there should be a way of identifying students online (within the Middlebury universe) as from a certain commons.
  • Deans and Faculty Heads: There should be a better way to connect with deans and faculty heads which are the “family” within the Commons. A lot of emails go out from Commons Coordinators that say: “faculty heads have tickets available for these performances” or “the dean reminds you to bundle up because of extra cold weather this week!” These types of announcements are common but finding a way for deans/faculty heads to connect (but also get information from) is important.

Sponsored Research Office

Jim Ralph, Dean of Faculty Development and Research

Franci Farnsworth, Coordinator of Sponsored Research

Alison Darrow, Science Grants and Writing Facilitator

Our website serves several constituents:

  • the Controller’s office: we host their grant-related policies and information
  • faculty seeking grants: we supply tips, data, institutional policies & guidelines, forms, etc. to help guide proposal writing and application
  • Advancement’s office of Corporate and Foundation Relations: we share some policies and procedures, which are hosted at our site
  • the Dean of Faculty Development and Research: our site announces faculty grants and annual reports of grants awarded, a key way to celebrate faculty successes

We are a two-person office that reports to the DFDR; both of us maintain and update the site. Out offices are spread throughout campus (the Library, Bi Hall, Old Chapel), so sharing information electronically is crucial. The current site is an artifact of dumping old paper-based documents online in order to have at least some web resource and then not having the time to update or redesign. As a result, the site doesn’t invite active engagement and participation and is static and text-heavy. Faculty currently underuse our site, probably because it’s easier to just call us than it is to find and use information at our site. Revision and redesign is now ongoing, but a lot of what we do is still email-driven.

What we hope for from a new site:

  • an easier and more intuitive way to add linked pages, to help break up long blocks of text a way to add pop-ups, drop-down menus, etc., to keep users from having to navigate to other pages for short bits of supporting or related information
  • an easier way to “hide” and control access to sensitive and confidential content
  • ability to assign levels of access for stuff the office shares: currently we use Google docs for our department “whiteboard”
  • access for many users (including faculty and student workers) to edit the site and notify us easily so we can approve content before publishing it
  • dynamic linking to other departments’ information, through Banner and other means, so that redundant updates aren’t necessary
  • a platform-neutral system
  • ability to edit the site remotely

Features that would improve efficiency and help our workflow:

  • customized user profiles
  • a shared calendar
  • an anual grants-deadline calendar with a way to let faculty subscribe to alerts and reminders (currently we have to spam them)
  • a way to let faculty notify us that they plan to apply for specific grants
  • ability to dynamically link to and from faculty CVs and other content required for proposal writing (Institutional Research data especially; links with the library’s thesis archive; central database for faculty publications/achievements; faculty pages; career-path info for science alums, etc.)

Types of interactivity that would help our office communicate more effectively:

  • drop-down menus and pop-up windows so we don’t need to link to new pages – would flatten and simplify navigation considerably
  • an index of terms & acronyms (offices, agencies, etc)
  • dynamic timelines, checklists, and other forms that could be filled out online
  • calculators, worksheets, spreadsheets with College and funding rates and percentages built in
  • dynamic comments (e.g., user-contribute FAQ)
  • feeds of sponsored & relevant events, such as guideline updates, workshops
    & seminars
  • integrated links to Banner information
  • dynamic link updating, so that if material shared with another department is moved, the link on our page still works (or we’re notified to fix it)

Examples of functionality, design, and features from other colleges or industries that we like and admire:

  • Google docs: clean, simple, fast, super-easy to use and share
  • Google calendar: ditto
  • Boston University: clean, uncluttered design, yet there’s a lot going on; really like the tabbed navigation on the Home page and the way each tab slides aside to launch a video, interactive map, etc. (and that user has the option to interact or not).
  • The Daily Beast: the Cheat Sheet is a great feature

Current functionality of the Middlebury site and CMS:

    Editing is OK but clunky and subject to unexpected results; especially formatting carrying over when you cut & paste. It would be helpful to be able to see formatting tags (toggle on and off) so we could find and fix weirdness. Currently sometimes have to delete and redo because we can’t figure out how to fix the formatting.
    When Save refreshes the screen, it puts you at the top of the page: very annoying to have to scroll back down! Would be easier if it refreshed to where you left off.
    Hyperlink Mgr is great, very easy to use. Same with uploading documents.
    Really hate the way the right sidebar either doesn’t reflect the page titles or creates redundancy – not certain what creates this problem – editing page titles after they’re created? If so, the sidebar should reflect any changes to the page titles dynamically. Right now, we’re not even sure the sidebar can be changed, once created.
    More flexibility with fonts and text size would be nice.

Middlebury College Museum of Art

Stakeholder: Doug Perkins
Current: http://museum.middlebury.edu/
WebRedo Contact: Mike Roy

General: The Middlebury College Museum of Art is an AAM-accredited museum serving the students, faculty, and staff of Middlebury College as well as local and regional residents of and visitors to Addison County and the Champlain Valley. The museum preserves and displays the college’s permanent collection and offers 5-7 traveling loan exhibits each year to as many as 18,000-20,000 visitors. We serve as a visual resource for a broad spectrum of courses across the college’s curriculum, most notably the departments of History of Art and Architecture and Studio Art, though in any given year we are likely to work with courses in religion, languages, music, philosophy, anthropology, American studies, classical studies, English and American literature, environmental studies, theater, and teacher education. In addition, we welcome nearly 1,000 local K-12 school students to the museum each year through the Museum Assistants Program, a volunteer docent program that offers Middlebury College students a chance to learn about the museum and to lead tours. The museum also oversees and maintains a collection of 20 works of public art displayed around the Middlebury campus, and the museum director chairs the Committee on Art in Public Places.

Requirements:

Needs
* flexibility with respect to aesthetics and typography
* have a portion of the museum home page that shows the next several upcoming museum events
* ability to create email lists to allow patrons to subscribe to relevant lists
* offer RSS feeds for museum press release pages
* maintain the majority of the current site’s look
* participate in brand mapping exercises and discussions related to the college’s brand and sub brands
* online credit card membership form
* e-commerce capability for museum bookstore directly through museum site
* flash banners
* rotating home page image with a click through
* ability to allow people to control font size easily (for accessibility/readability) with one click
* alt text balloons that follow the cursor so that image captions are noticeable (e.g.
http://www.louvre.fr/llv/commun/home.jsp?bmLocale=fr_FR

* online forms for teacher workshop and school group registration

* video-taped lectures for podcasts and vodcasts linked to exhibits (e.g. Art in Public Places iPod tour)

* ability to link to press published electronically on the campus newspaper site as well as other news sites (Addison Independent, BFP, Seven Days, e.g.) and maybe have those stories pulled into a sidebar

* ability to zoom in on images as well as 360 degree image rotation

* online searchable database of the museum collection that is linked to the library’s online catalogue search function so that when students search for books or other media related to objects in the museum collection they will be alerted that the museum holds works that are relevant to their subject

Wants
* be involved in focus groups and usability as design process begins
* create a ‘museum module’ that users could choose to put on their customizable middlebury.edu home page that would allow pushing of info about exhibits, events, and other museum news to users’ customizable home page
* liquid layout, or at least a wider fixed width (950 pixels)
* enable comments on exhibit pages to allow visitors to leave their thoughts about exhibits and related events
* offer virtual audio and video tours either streaming through the site or for download
* allow museum Friends to RSVP on-line for members-only events
* distribute 8.5×11 .pdfs of posters (for printing and distributing at schools, etc.)
* high-quality videos of classroom discussions about art
* tagging
* facebook site (fans of the museum) to reach people through facebook
* ability to create online versions of exhibits with unique appearance (i.e. NOT within existing templates)
* updated design treatment for the Committee on Art in Public Places (CAPP) website that creates a visual link between CAPP and the museum

Nice-to-Haves

* allow students to create their own online exhibits from items in the museum collection (e.g. like what the pachyderm project might allow)

ES/EA/Sustainability Integration (SI)

Stakeholder: Jack Byrne

Redo Contact: MS Costanza-Robinson

Currently, ES/EA/SI has a relatively low-tech site that includes text and photos on their page and has a variety of file types for download (powerpoint files of presentations, pdfs of reports and newsletters). This functionality needs to remain, but be expanded and improved upon. The current status of the site is due largely to limited personnel time dedicated to the website. A recent (1-year only) hire will have some role in introducing content and improvements. Requests and or plans for future functionality/technology include:

  • Embedded video and/or audio (e.g., of the weekly ES Colloquium or other seminars)
  • Better access (possible including standard reports) to better web-use statistics
  • Ability to easily form Listservs or groups that specifically include non-Midd addresses (not just built within Outlook) and the ability to generate an email newsletter to the listserv participants; people should be able to subscribe and unsubscribe.
  • Training / portal functions
  • Tagging/aggregating/approving sustainability information from across the website (athletics, EA, SI, IS) and feed it to the ES/EA/SI site
  • Add ability to accept online submission of grant proposals (see URO stakeholder report for more on this requirement)
  • Add searchable archive of ES/EA/SI funding (proposals/reports from previous grant awards) or perhaps of Environmental Council minutes of meetings (see Faculty Council requirement document)
  • Integration of databases across campus and web-output of data: for example Facilities has a lot of information (facility energy consumption, building occupants) that Jack needs. The current process includes too many file-type conversions and people involved in getting the right information. The data exist, but the searches/databases (Sightlines?) are not web-based. Obviously, permissions issues would be important here.
  • The possibility for people to web-submit photos/ideas/text for the website for possible inclusion on the page.

Specific problems with the current site/CMS that were mentioned

  • Tiny blue font
  • CMS awkwardness – simplify direct editing of pages (uploading too many clicks, particularly when you upload the wrong file by accident, to remove that and upload the correct one takes far too many clicks; what you see (even in preview mode) isn’t always what you get)
  • CMS editor permissions issues: student workers have historically done some of the content management for ES/EA/SI. Jack Byrne, as the person in charge of these areas, would like privileges to set-up/approve student permissions. Currently, the administrative hurdles here are time-consuming.
  • Channel pages creating/editing: is it possible to reduce administrative bottlenecks
  • Improve ability to edit CMS on Macs

Specific non-technological requests/thoughts for new site

  • Increase EA/SI prominence on webpage (homepage?)
  • Branding is important, but the flexibility of many templates would be helpful
  • More training – existing training is good, but more could be useful on more topics

Academic Departments

Heard from Susan Campbell, Department Chairs, Academic Coordinators
Drafted by Renée Brown and Jason Mittell

In surveying department chairs and coordinators, as well as casual discussions with many faculty, frustrations with our current web design and system run deep. Key problems mentioned include lack of design flexibility, difficulty in updating, poor navigation and organization, inability to easily embed images and media, and the static nature of information and site design. There was widespread enthusiasm for the makeover and willingness to participate in the process. Given that every academic department has different needs and specific uses, it is difficult to assess the relative importance of various features, but this document attempts to synthesize key needs and requirements as expressed across the curriculum.

Needs for Departmental Sites

We have identified a number of types of information that departments feel are important to their sites, broken into four major areas:

  • Department Overview: brief mission statement, central contact info, feed of news/events, and visual vibrancy for splash page
  • People: lists of faculty & staff with links to detailed profile pages, office hours & contact info, updates of publications/grants/achievements, alumni & student profiles
  • Curriculum: major requirements (including potential concentrations & sample sequences for more complex programs like ENVS and AMST), independent project guidelines, downloadable forms (both departmental and from the registrar), courses/schedule, links to class websites
  • Resources: departmental library guide, career info, study abroad recommendations, departmental newsletter, facilities & equipment overviews/policies, external links (research sites, grad programs, opportunities for community outreach, etc.), guide to “what can be done with a XXX major?”, feeds from external blogs, video/images of specialized facilities

Many departments indicate that they currently underuse their websites, with minimal information that is rarely updated. There was consensus that this makeover process could help show people some new ways to use the web effectively. During sessions where other websites were demoed, there were frequent “a-has” upon seeing capabilities that other schools are using, so we feel there will be enthusiasm for innovation. Some specific innovations that seemed particularly popular include dynamically generating course listings (a “modular catalog”), faculty pages feeding & linking to schedules and courses, feeds of sponsored & relevant events, and integrated links to Banner information.

We discussed the option of choosing among a group of templates, customized for both visual variety and optimized for different needs (such as more graphics/media, more text-based, etc.) – most coordinators and faculty seem to embrace this option. Coordinators wanted more flexibility with fonts and sizing of text. There was a clear desire for more graphic and media capabilities, especially within the Arts.

Some faculty embraced the idea of student and/or alumni work being profiled and displayed on the site, especially in the Arts. Potential links with the library’s thesis archive is an option worth considering.

Some departments currently publish newsletters, and many would consider publishing them to the web instead of, or in addition to, paper and mailing. Ongoing updated departmental blogs were of interest to a few departments as well.

Needs for Individual Faculty

Faculty pages were noted for being rarely updated, dry, and lacking variability or personality. Faculty were interested in being able to edit their own profile, recognizing that some faculty would be less likely to do so (although no less likely than emailing the updates to coordinators, which could still be an option). Arts faculty specifically want the ability to host images and media of their creative work.

An idea discussed with coordinators was to have a central database for faculty publications/achievements – either faculty or coordinators would enter the information about a new publication (including link to online version or Midd subscription through JSTOR, etc.), which would then feed to the faculty’s homepage, their department(s) page, a college-wide faculty achievement page (which would be useful for library acquisitions as well as PR), and into the annual report for faculty given to the Provost. Coordinators thought this would be a better option than updating individual faculty pages, and expected between 1/3 and 1/2 faculty would enter their own info, growing over time with increased technological fluency.

The idea of automatically feeding a faculty’s scheduled teaching with links to courses to their profile page (as on Amherst) was quite popular. It’s uncertain how many faculty would maintain separate pages through Segue or the community.middlebury.edu server if the core website were more flexible – one option would be to embed separately designed pages into the core departmental site.

Workflow

The current CMS restricts editing to coordinators, although some faculty have edited on the platform. A number of chairs expressed interest in editing their pages, having other faculty edit, or having student workers edit. Coordinators generally want to be involved in the editing process, both to oversee consistency and maintain their web skills, but recognize that the current workflow leads to infrequent updates and little input from faculty.

An easy-to-use editing and authoring system, especially for incorporating media and images, was seen as essential, with the ability to increase participation of faculty in the editing process. One issue expressed by some faculty was that the new system not be tied to a specific browser or platform (e.g. must be usable on Mac/PC and Firefox/IE).

Coordinators were concerned that expanded content on the department site would lead to increased workload. Sharing editing responsibilities would help. Additionally, the ability of sites to be dynamically assembled, rather than static updates, would be useful – for instance, feeding events, faculty publications, career links, library research tools, and alumni news from other offices and systems would make the site update regularly without requiring manual changes.

In imagining the workflow model that would work best for academic departments, coordinators endorsed a system where many users could be given editing ability for the department page (including faculty and student workers), but that all edits must be approved by the coordinator before publishing (via a notification system). This should increase updates from faculty on the content they know best, and allow delegation and distribution of work more effectively, without sacrificing consistency and appropriate form & use of media. Some thought it would be helpful to be able to turn the approval requirement on and off, allowing the possibility of all authorized editors to publish directly.

The idea of a student/alumni section of the site that could be updated (with approval) by students and alumni themselves was mentioned as a way to encourage participation. Another option is a simple webform for alums to send in info to feed into the site, perhaps at the college-wide level with tags to majors and field of employment.

Other Desired Features

  • Many coordinators were enthusiastic about being able to easily customize their own user profiles to make their web use more efficient – after a clear explanation, all coordinators present at the meeting said they’d definitely use this feature.
  • One consistent theme with coordinators and faculty was that as much Banner information as possible should be accessible from the website directly without using BannerWeb. Course rosters (linked from course pages, as on Amherst), student schedules, faculty schedules, lists of majors, and the like should be accessed via links rather than BannerWeb login.
  • More sophisticated use of feeds and targeted info via the web was endorsed, especially as an alternative to email-driven communication.
  • One idea would be to have lists of new library acquisitions in a certain discipline feed into the departmental site.
  • Better management of events and calendar info was mentioned, both in terms of flexible feeds by tag, department, location, medium (lecture, performance, film), and the ability to click “Add to my Calendar” to export to Outlook or other systems.
  • Some language departments mentioned the need for varying language character sets (such as Cyrillic and Greek).
  • Some arts departments want the ability for students to create their own portfolios of their work, as Teacher Ed currently does. This would ideally be embedded directly into the core department site, not externally hosted on Segue.
  • A few faculty expressed interest in having the ability for social networking, and a couple said they have used Facebook pages to coordinate with current majors and alums.
  • A few mentioned the use of wikis, but only for specific purposes (for instance, a wiki for documentation of FMMC equipment).
  • Some suggested a “majors-only” area, although there was not a clear sense of what information and material should have restricted access.
  • One coordinator suggested that departments could have a list of current majors on the site, potentially with links to student pages/profiles.
  • One coordinator suggested the possibility of online sign-up for scheduling of meetings and appointments. Another suggested the use of an online order form for equipment requests (currently used on CHEM site), which might also be expanded to request access to facilities (like MUSIC practice rooms), reserve specialized equipment (like FMMC cameras).
  • A few faculty expressed interest in having the departmental website offer the possibility for discussion and community involvement, not just a one-way flow of information. Options include blog-like updates with comments, an open “wall” to make announcements/promotions, and a department wiki open to Midd users as a workspace for engaging with the department.