Current work is available at http://clusive.cast.org
Demo uses both UIO and CAST's Figuration framework, along with Readium (https://www.edrlab.org/readium/readium-2/)
|CISL Overall Architecture and Development||Alan|
Overall architecture will be implemented in Django.
Development work proceeding here: https://github.com/cast-org/clusive/tree/development
|ILDH entry on adaptive and personalized learning||Alan||Synthesize work and thinking from Clusive, MyL3, work I did for DIAGRAM Center in 2019: http://diagramcenter.org/diagram-reports/diagram-report-2019/personalized-learning.html|
|Learner Preference Management and Storage using GPII tools||Alan||Starting to have conversations and explore possibilities|
Postgres table definitionGH-4: Add Postgres support for documented data models
Document RESTful API
| Preferences Service|
Security for the
|5: Define the API for the preferences server/service|
database, including OAuth2
3: OAuth2 support for authorized database access
|Joseph||FIrst pass brainstorm, based on GPII Preferences Service.|
- Using GPII OAuth2 documentation and code as the starting point.
- Moved documentation over and modifying (make more general).
- Moved code over and removing GPII-specific aspects.
Security for the database, including OAuth2GH-3: OAuth2 support for authorized database access
CISL: Create tech plan for Google & Clever single-sign-on integration
- Just assigned; will start this week.
Document RESTful API for the Preferences Service
GH-5: Define the API for the preferences server/service
|Joseph||Moving code over and removing GPII-specific aspects.||Using GPII OAuth2 documentation and code as the starting point.Moving documentation over and modifying (make more general).|
|Postgres database for Preferences Service - testing framework||Joseph|
- Using Tony's fluid-couchdb-test-harness,as a basis
- Using cockroachdb
- End result is a postgres server environment to be used in testing scenarios