Repository navigation
3. Study material and organization
The ability to create flashcards is the main purpose of the app. These flashcards will show a question and an answer written by the user on each side. Then, depending on the memory retention specified by the user and his/her performance when reviewing the cards, the application will assign a review date to each card.
Each flashcard has a front field, which should hold the question, and a back field, which should hold the answer. In addition, they all have a card_statistic. This model holds the user's performance on that card: the level of understanding, the times answered correctly and incorrectly, the total time it takes to answer it, and the next review date.
To better organize the flash cards a topic must be created. Topics resemble card decks and serve the purpose of grouping together cards that contain directly related information.
Each topic has a title field, which holds its title. They could belong to a subject, but its not mandatory. Also, each topic can have many topic_configs. The topic_config model keeps a record of user specific configurations for that topic. Because topics can be shared in collaboration, each collaborator holds an individual topic_config with its own settings. A particular topic can be archived, set for reviewing, or its recall_percentage can be changed from the default.
Subjects is yet another way to organize the flashcards by grouping multiple related topics. This classification is greatly useful for a student user that wants to organize its flashcards into the classes he/she is taking during a certain semester.
Each subject has a name and a code. Like topics, subjects also have multiple subject_configs objects related to them, one for each collaborating user. Subjects can be archived, and can have an identifying color set by the user.