User Tools

Site Tools


scratchpad:course_reserves

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
scratchpad:course_reserves [2015/11/06 11:44] klussierscratchpad:course_reserves [2022/02/10 13:34] (current) – external edit 127.0.0.1
Line 7: Line 7:
  
 === Syrup tables that can be added to course_reserves schema === === Syrup tables that can be added to course_reserves schema ===
-All of these tables will have OU owner column added:+All of these tables will have OU owner and delete column added:
  
   * syrup_course   * syrup_course
   * syrup_department   * syrup_department
   * syrup_servicedesk? - Need feedback from users about whether separate servicedesk is needed or if its purpose can be served through use of copy locations.   * syrup_servicedesk? - Need feedback from users about whether separate servicedesk is needed or if its purpose can be served through use of copy locations.
-  * syrup_site (consider renaming site): owner_id field maps will need to map to the actor.usr id for the instructor that leads the course.+  * syrup_site (consider renaming site): owner_id field maps will need to map to the actor.usr id for the instructor that leads the course. Many-to-one relationship so that two instructors can be assigned to course sites.
   * syrup_term   * syrup_term
  
Line 55: Line 55:
    * When reverting parameters, the system should remove the table entry with the stored parameters.    * When reverting parameters, the system should remove the table entry with the stored parameters.
  
 +
 +==== Staff Interfaces ====
 +     * Staff interfaces will be largely the same as they are in current Syrup, but should follow the same guidelines as the ones used in the web client.
 +       * Web client UI style guide would be useful here.
 +     * May be no need to add service desks. Ask opinion of course reserves users.
 +     * Need to add a logical progression for the following tasks: Create Course --> Create Course Site --> Add materials to Course Site
 +       * Example: After creating course, add a link that provides the option to create a site (section) for that course or to create another course.
 +     * May not need granular permissions for viewing a course site. Maybe just make use options for public / private.
 +     * Add an option from course list to add all / selected copies to a copy bucket or to load copies from a copy bucket.
 +
 +==== Public Interfaces ====
 +    * A new tab for course reserves search. 
 +      * Search should be by course, department, professor. Toggle for searching active / all courses.
 +      * Also need a link to display all courses for that OU (how do we know what OU to display here if a parameter has not yet been set?)
 +    * Course site - search results page styled a bit differently (e.g. no facets).
 +      * We need to handle parted copies differently than we do on a typical search results page. A parted copy should show up as a distinct entity on the search results page. Example: A professor puts volume 2 and volume 3 of //The Book of Evergreen// on reserve. The course list should have a distinct entry for each volume and should only display copy details belonging to that part. Students don't need to worry about volume 1 because it is not on the reserves list. 
 +    * Record summary page essentially the same as current page, but with active course information added to the copy details. 
  
  
  
scratchpad/course_reserves.1446828244.txt.gz · Last modified: 2022/02/10 13:33 (external edit)

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.