Date Picker Meeting Notes

Attendees: Erin, Gonzalo, Allison

• Gonzalo thinks we've already captured the important contexts

• uniformity & user visibility of the date picker is important

• maintainability is important - some have hard-coded dates, some have date ranges

  • single, multiple, range

• internal & external restrictions

• certain things should be parameters passed by the context to the component (language, blackout dates, e.g. Friday and Saturday are not work days)

• internal parameters the date picker should know about because other date pickers should tell it (e.g. start and end dates for a range)

  • context should know about the restrictions

• a couple ways to figure out the important contexts:

  • frequency

    • resources - hide and show resources - mostly used by instructors, but students use it too when they create project sites)

      • very important as well

      • potential scenario: team in charge of promotion and tenure, and information is released in a certain order

    • schedule (especially for students)

  • importance

    • assignments (but may not be frequent)

• most of core tools were developed at Michigan 4 years ago, the widgets that the core tools use aren't as friendly, not user or server or maintenance friendly

  • this is the opportunity to fix the Michigan tools as they are ready to implement the date picker in them

  • any tool using hide/show (announcements, resources, & one more Gonzalo can't remember at the moment)

  • any tool that has a date setting as part of it's core definition (assignments & schedule), e.g. won't allow a submission after a certain date

• Gonzalo thinks it would be great to get this finished in time to go in Sakai 2.7

• Gonzalo would like us to speak with his instructional designer, perhaps after Allison returns from the JA-SIG unconference