Key/Value store

There are various use cases where a key/value store would be useful. This would immediately become useful in situations like storing arbitrary settings for a user (last selection of a table filter for instance), and would later become useful when we support plugins, and the plugins need a place to store their data.

A key/value store should be available in three places:

for each user
for each student/teacher in a course (i.e. a separate store per course per student/teacher)
for each course instance

The interface for this should be something like:

For a user:
/api/v1/my/values

For a course:
/api/v1/courses/{id}/values

For a person in course:

/api/v1/courses/{id}/{ssn}/values

Comments (0)