scratchpad:course_reserves
This is an old revision of the document!
Table of Contents
Moving Syrup Course Reserves to Evergreen
Notes from November 2015 Developers Hack-A-Way
Notes on Database
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.
Syrup tables that can be added to course_reserves schema
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
Syrup tables no longer needed because the data already exists in Evergreen
- 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).
Syrup tables supporting features that won't make phase 1
- syrup_group
- syrup_membership
Syrup tables no longer needed
- auth_group
- auth_group_permissions
- auth_message
- auth_permission
- auth_user_groups
- auth_user_user_permissions
- django_admin_log
- django_content_type?
- django_session
- django_site
- syrup_userprofile
- syrup_config
- syrup_z3950target
scratchpad/course_reserves.1446749009.txt.gz · Last modified: 2022/02/10 13:33 (external edit)