{"id":4724,"date":"2019-06-27T09:02:31","date_gmt":"2019-06-27T16:02:31","guid":{"rendered":"http:\/\/blog.quickschools.com\/?p=4724"},"modified":"2023-09-27T00:07:14","modified_gmt":"2023-09-27T07:07:14","slug":"odysseyware-integration-app","status":"publish","type":"post","link":"https:\/\/blog.quickschools.com\/2019\/06\/27\/odysseyware-integration-app\/","title":{"rendered":"Odysseyware Integration App"},"content":{"rendered":"
<\/div>\n

After several months of work, we now have a working integration app with Odysseyware<\/a> using their available API. You can check it out in our App Store<\/a>:<\/p>\n\n\n\n

\"Odysseyware<\/figure>\n\n\n\n

This particular integration app works differently from our other LMS<\/a> integration implementations (like Schoology<\/a> and Canvas<\/a>). For Schoology and Canvas, QuickSchools<\/a> is treated as the source for all Roster elements, like students, teachers, sections and even section enrollments. Only grades are pulled from the LMS into the QuickSchools Gradebook<\/a>. However, since Odysseyware is also a Curriculum Management System, we treat Odysseyware as the source for courses and section enrollments too. So after mapping students, teachers and sections from QuickSchools, we will pull both section enrollments as well as grades from Odysseyware into QuickSchools. So what does that all mean?<\/p>\n\n\n\n

In summary, once the app is installed and linked, the flow of data is as follows:<\/p>\n\n\n\n\n\n\n\n