BCStudentSoftwareDevTeam / BCStudentSoftwareDevTeam/bcsr
Integration of the Box API to improve direct access to stored syllabi, particularly archival data
- Dominant language
- CSS
- Stars
- 0
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
**[Original report](https://bitbucket.org/laborstudents/bcsr-flask/issue/53) by Scott Heggen (Bitbucket: [sheggen](https://bitbucket.org/sheggen), GitHub: [sheggen](https://github.com/sheggen)).**
----------------------------------------
# Context
Berea has syllabi dating back to 1949. Currently, new syllabi are stored in our system, old are in fileshare, and they would like them all in a single location. Currently, the UI would become way too cluttered to have all syllabi in our system. However, integration with box would allow them all to be in the same location (i.e., Box), and accessible, without having them in the UI as well as filling up our server. We would need to think about a process for removing entries from the database after X years (likely 5), without deleting the files.
# Expected Behavior
Using Box's API, integrate access to an account (likely registrar@berea.edu) that syncs two folders; 1) where we store all syllabi in BCSR, and 2) all of the archived syllabi since 1949. This would allow the Registrar's office direct access to all old syllabi and our syllabi, from a central location. Since they have unlimited storage, we have no issue with that.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.