Tentative Agenda:
- Implementation update (see Implementation)
- Jim is posing questions there for further consideration. Please review.
- Changes that need to be made to the Date widget
- Schedule
- Particularly for QA
- Reordering of resources
- Post-post 2.2.0
Useful links
Date Widget samples: http://kimsooil.is-a-geek.net/calendar_demo2/test_en-US.html http://kimsooil.is-a-geek.net/calendar_demo2/test_en-GB.html http://kimsooil.is-a-geek.net/calendar_demo2/test_en-ZA.html
Reordering Resources UI Document
Minutes:
Implementation update
Questions:
- Should the timed release functionality be in Dropbox, My Workspace, and for the root folder of a site?
- Consensus: dropbox yes, My Workspace no, root folder no
- Should the visual cue for unavailable be greying-out?
- Consensus: yes, and Jim will talk to Gonzalo about the CSS for handling this
- Should we tell users when items due for retraction are going to disappear?
- Consensus: we'll leave that to the instructor to handle for now, and not have any notification in the interface.
Mike: If the start date is set past the end date, we should set a new standard by handling that in a reasonable way. The end date should at least catch up to the start date.
Consensus: Since retraction will likely most often happen at the end of a term, we'll try to get the end of the term from sakai.properties, and make that the default setting.
Kathy: what about adding extra update and cancel buttons at the top of the page as well?
Jim: It could be a good idea, but it's outside the current scope. And I'd feel better if we got some further advice from others who designed this before, to make sure there isn't some reason we might be overlooking.
Kathy: I can take the question to the DG-UI group, to at least try to get some informal agreement as to what would be a good thing to do.
Consensus: Kathy will take the issue to the design group, and it may be considered for future work.
Date Widget: There's a brief delay on completing the date widget. It needs to be refactored to allow for multiple widgets to function within the same page, but that work can't get started until the end of next week. In the interim some preliminary testing can be done using a legacy widget.
Schedule
Permissions testing (i.e. testing access permissions without the new date widget) can begin early next week. It would be good to have a test matrix for this.
Clay: I don't have anyone who can put together such a matrix over the next couple days, but I'll send a note to Francette and see what we can do. I can do QA next week, however.
Mike: Should I help out with QA or pursue some work on the reordering of resources?
Jim: I think it's important to continue on with the reordering work, if we don't need extra help with the QA.
Clay: If we're going to need extra help with the QA, it will likely be when the Date widget is included. For this first round I think it would be just as well if you continued with the reordering.
Reordering resources
Did we come to a final decision last week?
Consensus from last week: http://www-personal.umich.edu/~jimeng/Sort3.html
Should we stack the arrows right on top of each other?
- We'd have to make them smaller, and that could make them harder to click on
- We can at least tighten up the columns for now.
Reordering of resources may not get done for a Sept. 1 release. (No one is surprised by this)
Post-post 2.2
Jim: There are lots of resources issues floating around in Jira, and I could use some help going through and prioritizing them, once we're done with the current work.
Mike: I'm willing to help, but I can only represent a limited opinion on what should be a priority for the whole project.
Jim: That's fine, that's all any of us can do.
Clay: We have a long-term interest in fleshing out the resources tool, so I can help out, too.