?️ Dev-plan for this week（9/18 – 9/24）

  • Refactor the code of the project as a whole to improve code readability and extensibility
  • Fix issue #45, add user input restrictions and backend judgment to profile
  • Add a ‘Best Documentation Practices’ section in the README. The goal is to showcase the most effective documentation (available for user testing) and the most recommended documentation layout

? Inspiration

For learners, one of the best habits should be regular self-testing – Make It Stick: The Science of Successful Learning

When I’m learning a new technology, I have the habit of taking notes and jotting down important information. It’s a good habit, but I also have a bad habit of not enjoying reading the notes I’ve written (I’m not sure if this is the case for most people ?). This results in my notes becoming mere mementos without substantial use. That’s why I choose to create an application that continuously prompts you with questions to review your note contents.

? Start

Clone this repo

git clone https://github.com/codeacme17/examor.git
cd examor

Run docker compose

docker-compose up

Please make sure Docker is installed on your local machine, and ports 51717, 51818, and 52020 are available on your local host

Open http://localhost:51818 in your browser to access Examor. (Due to optimization scheme for modules, it may be slow when loading the program or entering a certain page for the first time)

✨ Features

Generate Issues from Documentation

When users create notes, they can upload associated documents. The application generates a set of questions from these documents, based on their content. These questions will be presented to the users in the future.When creating notes, users can choose the types of questions they want to generate, providing them with a richer learning experience.

Answer Detection

After users receive daily questions, they can provide answers. GPT will score, validate, and provide the correct answers. The score is determined by evaluating the correctness of the answers and the linked document (0 ~ 10 points). This score influences the subsequent Ebbinghaus review process.

Ebbinghaus Memory

I’ve implemented a simplified version of Ebbinghaus memory, currently consisting of only 8 lines of code. I plan to optimize this function further in the future (v0.1).

Regarding the actual function, once GPT generates a test, the score is recorded and affects the future review date. Higher scores result in longer intervals until the next review.

Role Selection

Important Recommend to use the GPT-4 model for a stable experience.

Roles can provide more possibilities for question generation and assessment. You can set roles in the configuration page. For more information about various roles, it’s recommended to refer to the Role Manual.

Question Type Selection

Choose the question type when creating notes.

When practicing questions, you can answer using different methods. The image below shows an example of a single-choice question.

? Modules

Notes Management

Notes Management is a module to oversee all uploaded documents. Within this module, you can delete or add new files to your uploaded notes. Note that deleting all documents under a note will clear the associated questions.

Random Question

Random Question is a module that randomly selects a question from the existing question bank. Implementation of this module enables this feature.

Note

Note is a virtual module generated in your app for each note you create. In this module, you can answer questions. Question pushing is implemented according to the Ebbinghaus memory curve. You will receive three types of question data:

  • Questions for Today’s Review: As the name suggests, this data pertains to questions that need review on the current day for questions answered in the past.

  • Expired Questions: These are questions not completed within the required review timeframe on the same day, resulting in this data being collected.

  • New Questions: When the user-defined daily question count is not met from the above two data sets, this supplementary data set is pushed to the user.

Examine

Examine is a central module where users answer questions, allowing GPT to score and validate answers. The module comprises three components:

  • Answer: Users enter their answers, and test content can be displayed after submission.

  • Last Record: Records the user’s previous answer to the question and the detection outcome.

  • Document Content: This component displays the actual uploaded document content, serving as the basis and final answer for the question.

♻️ Update the Project

When starting the project, the application checks for updates. If an update is required, the user will be notified. You can follow these steps to update:

  1. Export your notes, questions, or configuration items as a backup through the Export Configuration and Notes button on the personal settings page. This will export a file named examor-data.xlsx. You can view the file contents, but it’s not recommended to modify the file content

  2. Pull the latest remote code updates to refresh your local project.

  3. Delete the existing Docker container and rebuild the project with the docker-compose run command to incorporate the latest changes.

  4. Once the build is successful, navigate to the personal settings page, click the Import File button, and re-import the backed-up data into the project.

The current updating process is based on my personal usage. It might not be the best way to update. If you have better update methods, please feel free to provide assistance in the issues section ❤️

Contributing

Since the project is in a very early stage, there are still many problems and bugs in the project. If you find a bug or have an idea for a new feature, please submit an issue or pull request. See more in CONTRIBUTING.

License

AGPL-3.0 license © 2023-Present leyoonafr

GitHub

View Github