Skip to end of metadata
Go to start of metadata
- UW map identitied as one of five great university campus maps
- UW Campus Map Updates
- Kilian Frey and Dane Odekirk presenting
- Doing a lot of things behind the scenes to improve campus maps
- Updated to Google Maps API version 3, which will allow mobile presentation
- Changes to Maps
- Added parking lot, photo, and landmark layers (includes panorama of landmark)
- Added Feedback button
- Search by keyword, by name, building code, organizations inside buildings
- Added Directions
- Using Google direction services, which does not have a concept of our buildings
- Does not have a concept of obstacles for disabled, yet, but does show bike routes and there is a link below to Disability Services building and route information.
- Added little circles to show you are on a building
- Had problems making it work in IE, but figured it out
- Added links to popular directions, such as from airport
- Also still have links to other map resources
- Entire map is now managed through Wordpress
- Each building is a point (a metabox that can contain information), using the Google Map API
- Objects can have multiple points, such as shuttle routes or campus tours
- Creating a new building or new parking lot is like adding a post
- Uses Picasa plugin to manage images, which automatically sizes images on retrieval
- Google is considering doing photomapping of bike routes on our campus
- Maintaining your building information
- If you need to change information about your building, send email to uweb@uw.edu
- You can manage the information for your own building, send email to uweb@uw.edu for how
- Can have multiple editors for a building, but do not mess up each others information
- SiteImprove's SiteCheck service contract signed
- Gina Hills presenting
- http://siteimprove.com/Solutions/SiteCheck/SiteCheck2.aspx
- UW has a one year subscription to the SiteCheck service
- SiteCheck scans for spelling, broken links, accessibility issues
- Can search for names, such as people who have left
- Contract allows scanning up to 50,000 pages
- Once we know which sites will be focusing on, will have tutorial at a Web Council sessions
- Access to a site can be given to unlimited users
- Do not have unlimited contact with SiteCheck services; send questions to uweb@uw.edu, which will respond to you or will work with SiteCheck, if necessary, and get back to you
- Contract goes for one year
- Who is being included
- Top level pages
- Large schools
- If want to be counted, send email to Gina (ghills@uw.edu)
- Want people who will take advantage of the services, actually work with SiteCheck routinely
- Will total all the likely pages up to see if total comes to less than 50,000 pages, might not be able to include everyone who is interested
- Drupal Tutorial
- Lucien DiPeso and Mark Squires, School of Nursing, presenting
- Drupal training is now online http://nursing.uw.edu/tier/drupal
- Put together online classes in Moodle to making training more efficient
- Three lessons are available: 101 (basic intro), 102 (what elese you need to know), 103 (site editor)
- 101 and 102 are up, 103 will be up by end of month
- Lucien is joining the Peace Corps to work in Togo
- Web resources on the Marketing site
- Go to the Marketing site and click on "Web" in the left column; a list of resources will appear
- Resources
- Header & Footer Wizard
- Online Giving Form - easy to add to your page
- Request for Custom Search form
- UW Alert Banner
- Web Color Palette
- Web Guidelines
- WordPress Theme
- Working on updates, offers option of pulling in the full header with dropdowns from the home page sites
- If you use that feature, please install the Cache plugin in WordPress first
- Going to roll out the new privacy links in footer shortly
- UW Design in Drupal toolkit, assembled into a ZIP file
- 150th Toolkit is being built
- New policies on privacy and terms of use - REQUIREMENT
- Daniel Schwalbe, Ann Nagel, Suzanne Blais presenting
- New policy statements are now available
- Locations
- University of Washington Online Privacy Statement
- University of Washington Web Site Terms and Conditions of Use
- Placement
- Look at the footer on the UW home page (http://uw.edu/) for an example
- Links should be in the footer of every page. Standard footers in the Marketing provided templates, including WordPress and Drupal, now include the links
- Do not reproduce the language in your pages, just link to the privacy and terms pages, as they will be updated through time
- Basically says by using the site you are agreeing to collectng the personally identifiable information
- Providing the information may be a condition to using the site, such as an employment application
- How do you implement link to policy from Facebook or Twitter?
- Whenever someone leaves your site to go to social media, important to have terms and privacy info available on the page they launch from
- Policy statement on personally identifiable information" is something different
- It is being updated as well and should be out shortly
- Much work went into these statements and into thinking about how they should be used
- Linking to these pages is REQUIRED
- Linking to the pages helps protect you
- What about sites that collaborate with the UW?
- Trickier when they are external sites, but if referring to the UW as a brand, good idea to have the links on their pages
- Anything within uw.edu or washington.edu domain should have the policy linked to from every page
- If hosted within the UW domain yet has a different URL, it should still have policy links
- If associated with the UW, the UW privacy policy should prevail because the organization is receiving the benefit of the association with UW
- Better to have the links. The policies will protect you, even if in a specific case they does not fully apply
- When negotiating for external services (example: UW Google Apps) take care to include the topic of whose privacy policy applies in your negotiation agenda
- Next Meeting, Thursday June 9
- Terrill Thompson will talk about how to make accessible PDF files
{"serverDuration": 190, "requestCorrelationId": "2d46f0dd492921de"}