|
|
|
I'm adding this use case to the Jira ticket for
The Undergraduate Research Opportunities program has two components: 1. Students are matched with a faculty mentor, under whom they perform research work over the course of an academic year. 2. Students attend a biweekly seminar, for which they complete regular classroom assignments. This seminar is run by upper-class peer advisers. There are approximately 800 students, 600 faculty, and 30 peer advisers participating in the program. Each student is in 1 seminar and has 1 faculty mentor, but a given faculty mentor may have students in various seminars: Seminar 1 (Peer Adviser 1) ----------------------- |Student1 PA1 | Prof1 |Student2 | (Student1, Student4) ------------------------ Seminar 2 (Peer Adviser 2) ----------------------- Prof2 |Student3 PA2 | (Student2, Student3) |Student4 | ----------------------- For purposes of reflection and creating a presentation portfolio, we want all the students' UROP-related work in their portfolio matrix. Originally we designed a single matrix through which all work was to be submitted. However, the Peer Advisers, who are used to the Assignments Tool, found this approach to be very clumsy. The solution we hit on was to allow the Peer Advisers to manage their assignments through the Assignments Tool, but to auto-populate an appropriate matrix cell with the assignment information. An unresolved question is when the auto-population should occur: after the form is first added, after submission, or after completion. An important consideration in this is whether there will be reflection on the assignment, and if so, whether the reflection will be done in the Assignment Tool or in the Portfolio. Since we will not be using this Assignment Tool integration until next year, we have not worked out the details of when or how reflection would take place. Grades for the entire UROP course would be calculated using both the results of the Seminar assignments (given through the Assignments Tool) and the results of assignments given through the Portfolio matrix. If the reflection on the Seminar assignment were done in the Portfolio matrix, then the students would be graded on a Seminar assignment two places, based on different criteria (how they did on the assignment v. whether they reflected on it). r34539
Shorten and change the table name for osp_scaffolding_cell_attachments to osp_wiz_page_def_attachments. Oracle hates it when table names are longer than 30 chars! Basic functionality completed -- Gonzalo, can you take a look at the jsp presentation and close this when done?
Adding comments from portfolio@collab.sakaiproject.org list (24-Aug-2007)
) The feature will be disabled and hidden by default. It can be enabled in sakai.properties as follows: osp.experimental.assignments = true 2) Assignments can be selected by a matrix/wizard designer and added to a cell/page. Notes: For now the assignments will be restricted to the current site, but we should be able to extend this to a "Select from other sites" functionality. When this is done, assignments will be displayed in a users cell/page only if they are a member of the assignment site. There was much discussion on the implication of multi-site assignments, so this may warrent further discussion. 3) Assignment submissions will be displayed in a student's cell/page The same data will be displayed here as is available to the same user in the assignments tool. Currently only metadata is displayed: assignment title, submission date, status, grade (if available). I'd like to display a read-only page of the assignment submission itself, to be displayed only after assignment has been submitted. There were some comments suggesting that students/instructors could have write-access to an assignment through the matrix cell, but this is not currently implemented. I'd suggest this be left for future development, and written up as a separate JIRA. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Since assignments are another type of "evidence" (just as filled out forms, and attached files are) of a student's proficiency in this area, I would recommend including them with the other "items" on the screen, in the same table.
I see you have the date that the assignment was submitted listed...would that be the same as a "last modified" date? I think it may be close enough, right?
In the spirit of complicated autonaming of items attached to cells ;-) we could combine some other relevant information such as the class the assignment came from and the grade in the name of the item.
I just think its important that we try to simplify this page in a way that doesn't break up that visual cue (the "items" table) that says "this is student stuff".
(note see attached mockup)