Child pages
  • Web Council - October 18, 2012
Skip to end of metadata
Go to start of metadata
  • Announcements - Chris Heiland
  • Evans School Website - Ellen Whitlock Baker, Justin Williams - Evans School of Public Affairs
    • Brand new website; http://evans.uw.edu/
    • Old site developed in 2008; very purple
      • Home page was a giant news feed
      • Three different navigation bars
      • Many internal documents were only accessible through footer menu
      • Done with Drupal; one of the first UW Drupal sites
      • Hard to give permissions to others to maintain their content
    • Changes that prompted that move
      • Budgets are slimmer
      • Lots of employee turnover
      • Subject matter experts left
    • New site
      • Goals
        • Easier to maintain
        • Malleable for centers within Evans
      • Features
        • Calendar on home page
        • What We Do section
          • Prospective students are major population visiting the site
        • Evans School News box
        • Event box for upcoming events
        • Navigation
          • One set of major tabs in menu bar
          • On each page within a tab, nav on left
          • Footer repeats the whole structure
        • Centers and Projects pages have a sub-banner
      • Planning content organization was a huge job
        • A lot of pages in the old site where in odd locations, did not have a home
      • Planning the move
        • Decided to stay with Drupal
        • Drupal is an open source product; big community using it on campus
        • Looked at hiring outside people to help but it would have been really expensive
          • Looked around for how to do it on the cheap
        • School of Nursing had already done everything in their Drupal site that Evans School wanted to do, and they offered a complete build free
          • Right off the top, saved hundreds of man hours
          • Already functional management system
          • Already hooked into UW identity management system
      • Making the move
        • Had to make some customizations
          • Nursing build did not have mechanism for sub-branding; Evans needed to have a method for "sub-masthead"
          • Had to build out blocks, add them to proper locations on pages
        • Had to tear down and reorganize old content for the new site
      • What we would do differently next time
        • Would have hired an expert to help with the Drupal config; project could have been more quickly
        • Had a 20 hour a week research assistant to help move the content; more manpower would have been good
        • Hardest part was getting people to take control of their own content
          • Were able to use the UW Groups infrastructure
          • Workflow for moderation is fairly well thought out
          • WISIWYG editor was limited; people would occasionally cut and paste from Word into editor, which required cleanup
          • Each of the 15 units within Evans School is responsible for its own content
        • Manpower allocation is the single biggest thing they could have done better; had two websites running for a year; frustrating
      • Discussion
        • Build came with the Drupal Workflow module, which is relatively simple; adequate for Evans
        • Accessibility is good; carried forward Nursing's methods for menus
  • SpaceScout - Jason Civjan and Janice Fournier, UW-IT Academic & Collaborative Applications
    • Mobile application for students to find places to study on the UW central campus
    • Available in multiple forms
      • Web version comes out tomorrow 10/19 - http://spacescout.uw.edu/
      • Spacescout iOS version - on Apple Store
      • Spacescout Android version coming
    • Grew out of feedback received from students over several years
      • When computer labs closed in Mary Gates Hall, studies were conducted on what students needed
      • Learned that students really did not know about the spaces available to them; many places around the campus were underutilized
      • Students were frustrated in looking for places that met their specific needs
      • ACA wrote a proposal to Student Tech Fee committee to develop an application
    • Method
    • Performance
      • Faster on native app
      • Working on improving performance of Web app
    • Work
      • Two developers, built it in six weeks
      • Janice was product owner and data wrangler
      • Over 200 spaces in database. Visited every space to verify information, took photos
      • Will be creating versions for Bothell and Tacoma as well
      • Developed a vocabulary
        • Study area; larger area for a group, not enclosed
        • Study room; smaller group, enclosed space
    • Discussion
      • In focus group, students talked a lot about wanting natural light; less interested in controllable light
      • Students were allso interested in noise level
      • Built in basic features; will be waiting for feedback to guide further development
      • Keeping data fresh
        • Need a way to give owners ability to update hours; working on interface
        • Hope eventually to make it a crowd-sourced resource; students suggesting spaces, rating spaces
      • Other possible uses for the app
        • The app available as open source on GitHub
        • Could develop an app for finding meeting spaces
        • One faculty wanted to develop an app for students to find places for film shoots
      • Reserving spaces
        • SpaceScout provides link and instructions, but you cannot reserve through the app
          • Owners of spaces that are reservable have no one common system for making reservations
        • Some buildings have access restrictions, which are noted in the "Notes" section
      • Future
        • Give users the ability to login, and then see spaces they have access to (such as a lab only for engineering students)
  • CISO Social Media Guidelines - Suzanne Blais and Daniel Schwalbe - Office of the Chief Information Security Officer
    • Has new page on Social Media Guidelines
    • Guidelines are more general than policies
      • Apply to the institutional use of social media on behalf of UW
      • Does not apply to use of social media for teaching or research
    • Training video on The use of Social Media at the UW
    • Using Facebook
      • Gray area - To maintain work related Facebook page you have to login as an individual, but individual use of Facebook is against state regulations
        • Facebook does not permit you to have multiple accounts; not supposed to created accounts not linked to an individual, such as a departmental account
        • State law prohibits using personal accounts during work
        • Not likely to be challenged
  • Youtube Copyright Policies - Harry Hayward
    • Youtube audioID and VideoID
      • YouTube watches for copyright violations, can block content if it seems to be violating copyright
      • YouTube built a database of information from people who own content; everytime you upload content it checks it against the database. If it decides the content is owned by someone other than the person who posted it, it will do one of three things:
        • Block - may remove from all or certain countries
        • Track - Video runs but is tracked by the copyright owner
        • Monetize - Video runs and YouTube runs ads while it is playing
    • Examples
      • Ending Polio; student project assembled photos and used sound track from South African artist but did not get permission from the artist
        • Was blocked in 151 countries, available in 96 countries
        • Student eventually took down the video since it was not playing in the places he wanted it to
      • Washington Way video contains very short clip owned by someone else; content use is being tracked
    • Many videos and pictures are licensed Creative Commons licenses (http://creativecommons.org/)
      • Lot of Creative Commons stuff do not allow commercial use; if you sell tickets to go there, think of it as commercial; otherwise educational use is pretty much non-commercial
  • No labels