Washington State University World Class. Face to Face. Campuses WSU Home WSU Search my WSU

Future Releases

From skylightwiki

Jump to: navigation, search

Contents

Scheduled Releases and their features

Index to Releases

  • Release 1.0 Clean up from beta test, get to production (Target March 1, 2008)
  • Release 1.1 Instructor Dashboard and Reporting when survey is completed (Target April 1, 2008)
  • Release 1.2 Business entities, begin plan for retirement of Silhouette (Target Sept 1?, 2008)
  • Release 1.2.5 Dashboard upgrade (Flex experiments)
  • Release 1.3 User Interface Upgrade (Google Docs interface replace folders) & Messaging System Management Overhaul
  • Release 1.4 Preconditions on Questions
  • Release 1.5 Instructor Questions and Matrix Upgrade
  • Release 1.6 Authoring Upgrade (Item Banks and Templates and UI improvements)
  • Release 1.7 Report Upgrade (custom reports)
  • Release 1.8 Alternative delivery modes
  • Future Releases

Future Releases

Key features planned (but not scheduled)

  • Search/ Collaboration/ Community features

Features and Improvements needed (but not scheduled)

Blake

  1. email means to notify to all users in the system (dependent on Matt's admin page) Work included in 1.0_Punch_List

#review status - add logic to Messaging so that you can only send email to appropriate types of pools

  1. store all elements of message that was sent with survey (thus if survey is re-used, next person does not need to re-invent the message)
  2. tone down the message when a Notice is sent to a pool with zero enrollment. Take away the red, add an explanatory header Work included in 1.1_Punch_List

*Sending Email/Notices

  • Give author more info on "compose" page about who recipients are
  • Let author preview message in new window. When there are multiple pools, I say preview, it says which one?
  • for Notice, grab Stop date for notice from Pools stop date. If none in pool, grab from survey. In no case make stop date for notice less than start date (which currently happens). Work listed in 1.1_Punch_List


  • Respondent pool filtering
  • Filter remain set until it is unset (allows filter once and then visit details of multiple pools)
  • Filter on "Has data"
  • Provide progress feedback for users downloading Excel Report (JSON?). probably not needed now that process is faster. Work included in 1.0_Punch_List
  • Re-implement Notice sending procedure using JSON to make user experience better (have feedback). Being addressed by making notice sending and email sending asynchronous. Work included in 1.0_Punch_List
  • Respondent pool upload using XML debugged Work included in 1.0_Punch_List
  • Respondent pool upload using Excel file, design & developed Work included in 1.0_Punch_List
  • Refresh the Respondent Pool Data from Section Picker w/ full diff (update enrollment count also?) Work included in 1.0_Punch_List
  • Tracking Respondent Pool and/or Respondent that was sent a Notice Work included in 1.0_Punch_List

Matthew

  1. Finish new main page user interface. Work included in 1.3_Punch_List
  2. Very seriously need to add a bit more logging around the creation and deletion of survey objects so their history can be traced.
  • While reordering, it would be sweet to click on the title of a question and see it pop-up to help remember what the title means. Work included in 1.6_Punch_List
  • Need to add a tag to the dynamic text generator to return the url for a survey.

Nils

  1. Excel Custom Report + Procedure

Unassigned (unprioritized)

  • Testing/Previewing surveys
  • when a pool is NOT Single URL, allow "Test" url to work as if it were single URL so faculty can see the dynamic content filling for their pool
  • </strike>Mechanism to email all faculty associated with a survey the test URL of their pool(s) so they can look at the survey -- EMAIL must have a reply address where the feedback can go aka Survey Author ID (not Nils!)</strike> This is the instructor dashboard Work included in 1.1_Punch_List
  • Need way to get re-assign who is the survey author; should there be multiple authors? AD group? Work included in 1.0_Punch_List
  • Need an event log for many user actions in the system, so that when SYSADMIN helps user, they can better track who, what, why, when and where of changes to the survey. Work included in 1.2_Punch_List
  • I have had two help requests where students deleted their WSU Notice before taking the survey. Interface to browse/pick survey URLs to take to make this help function more self-service. Work included in 1.1_Punch_List
  • Respondent way to check if they are on the extra credit list. Log in and we take NID and report sections they took. Put this on the standard thank you page. Work included in 1.1_Punch_List
  • Respondent clicks Finish when they didn't mean to, double check if they really mean finished or had their fingers crossed.
  • More resources for WSU survey administrator to help with debugging (in CTOWiki?)
  • links to
  • RONET for class lists
  • Schedule of classes for what is being offered (faster for this than RONET)
  • MyWSU Manage Notices (how do these people get authorized for viewing notices?)
  • SectionPicker to see what was in the cart originally
  • reports on # people and which people have responded in a Respondent Pool (and when??)
  • Training on
  • how to re-gather URLs for respondent pool (student deleted the Notices)
  • How to detect if instructor is listed in teaching effort DB
  • various procedures for debugging problems using the resources (in CTOwiki?)
  • Respondent Pool Import/Export
  • Custom Excel Report Template with narrowed SurveySummary scope
  • Read-only access to surveys (my worry is that during copy/paste of survey questions, I damage the source survey)
  • persist respondent metadata through to reporting
  • Set "complete" flag for respondent when they complete a survey using multiple URL delivery mode
  • refuse retake of survey for respondents that have already completed a survey for multiple URL delivery modes and single url authenticated modes.
  • mass actions on selected respondent pools. the one that I immediately want is setting start or stop dates on groups of pools. Work included in 1.0_Punch_List

====Admin Functions====

Look up

  • users who have recently logged in (define recently)
  • running surveys (and their owners)
  • look up all users from a specific group (eg a single campus)
Contact

Email to results of any of the look-ups above Email all survey owners in the system All this addressed in 1.2_Punch_List

Item Banks and Templates

Definitions: see Glossary

Item Banks
  • Once "locked" these are read-only. They open in the editor so that questions can be copied out.
  • Owner can "unlock" and then edit as needed.
  • Owner can set "Publish" flag, making the item visible to searches within the system.
  • Owner can set "Publish+Public" flags, making the item appear in an unauthenticated view such that it can be indexed by Google
Templates
  • Once "locked" these are read-only. They cannot be opened in the editor. All a user can do is copy the whole template and paste (at which point the result is a survey that can be edited).
  • Owner can "unlock" and then edit as needed.
  • Owner can set "Publish" flag, making the item visible to searches within the system.
  • Owner can set "Publish+Public" flags, making the item appear in an unauthenticated view such that it can be indexed by Google
Retrieved from "http://wiki.wsu.edu/skylightwiki/Future_Releases"
Personal tools