...
property | type | required | format checking | state of implementation | remarks |
---|---|---|---|---|---|
id | integer, autoincrement | yes | isInteger | implemented | |
title | string | yes | implemented | ||
timestamp | date | yes | auto generated | implemented | |
content | string | yes | ?? only allowed tags | implemented | |
markdown | string | no | ?? only allowed tags | not implemented yet | |
user | integer, autoincrement | yes | isInteger | implemented | |
parent | object { id: objectId, revision: objectId } | no | not implemented | keeps link to a previsous revision | |
speakerNotes | string | no | implemented | ||
popularity | integer | no | isInteger | not implemented | |
comment | string | no | implemented | comment of revision | |
tags | array of Tags | no | implemented | ||
media | array | no | not implemented | ||
dataSources | array of DataSources | no | implemented | ||
language | string | yes | implemented | ||
usage | array of objects { id: object_id, revision: object_id} | no | not implemented | ||
ltiURL | string | no | being implemented | ||
ltiKey | string | no | being implemented | ||
ltiWidth | string | no | being implemented | ||
ltiHeight | string | no | being implemented | ||
ltiZIndex | string | no | being implemented |
Changes in SlideRevision schema:
As part of making Slidewiki as an LTI consumer, the LTI content needs to be shown live in the saved slides. For that purpose, I propose adding these attributes to SlideRevision schema: ltiURL, ltiKey, ltiWidth, ltiHeight, ltiZIndex.