Evergreen DokuWiki

Notes from November 2015 Developers Hack-A-Way

Since Syrup has already set up a viable database structure we can move many of these tables, with some minor adjustments, directly in to Evergreen. We suggest adding a new course_reserves schema into Evergreen.

All of these tables will have OU owner column added:

• syrup_course
• 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_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_term

• auth_user - actor.usr
• syrup_item - incorporates bib, volume, and copy data in one table.
  • Will now map copy_id to a course reserves site.
  • This table also contained stored volume/copy parameters that were used for easy reverting. Will address this through distinct development project outside of course_reserves scheme (more details below).