%%html
<!--Script block to left align Markdown Tables-->
<style>
  table {margin-left: 0 !important;}
</style>

Agenda for 23 Sep 2020 Curriculum Comittee Meeting

• Curriculog Updates

1. Build the data table and decide course numbers for new courses to fully catalog, stick with our block numbering system if possible
   1. Raw tables for CE,ENVE,CONE built. Example for CE in today's workbook file http://54.243.252.9/cece-dev-databases/CurrilogFiles/CurrilogWorkbook.html
   2. Prepare any supporting documents (usually just syllabi) - placeholders for syllabus links in data table, will store NEW syllabi as needed (existing easy enough to get from Digital measures)

• Common first year update

1. Review courses identified for downstream insertion of CT,BID,ST theme problems
   1. Will show existing .xlsx file
   2. Will build Raw tables built, to get away from .xlsx/.xml (vendor lock-in) format
2. Demonstrate some in-progress CT examples

• Digital Infrastructure / Data Management

1. Use TOSM supported infrastructure for data with personally identifiable information (A state and federal requirement)(i.e. Banner, Blackboard, etc. No-change)
2. For this comittee, build an OwnCloud server on AWS (like Dropbox, but truly free - limited by physical hardware, not subscription tier) Our needs are pretty small, and AWS scales way cheaper than Dropbox; Also it has elements of Git built-in, so there is distributed back-up, literally need to lose all physical machines at once for data loss. I think I can mount a filesystem and make automated backups as native files (OwnCloud uses a maria database to store files).
   1. Need some guidance on what to store for ABET
   2. Also how to structure, my first thought is strictly by course, then semester.