Hi, this is a issue which collects the state of this feature and it documents what has been decided on how to implement this.
This is so that who ever wants to implement it has a clear picture on how to do it.
In general we have agreed that this kind of data store should work as follows:
Storing data
- In the vault in a customizable location (by default in "/Spaced Repetition"), as the obsidian sync service doesn't sync random files in the plugin folder by default and because it is hard to create/update files in the plugin folder on mobile
- The schedule data will be stored in a file named "schedule-data.sr.md" which is located in the "Spaced Repetition" folder
- The data is stored in json format, but still in a markdown file, so that the "obsidian sync service" syncs it by default
Linking data
- Each reviewable card gets a block id like this ("sr-id" is used to make them easy to find)-> ^sr-id-[generated short uuid goes here]
- Each reviewable note gets a sr-id in the frontmatter like it is already sort of done
- Those ids link then to the schedule data files
More resources
There has already been some progress on this which can be found in the data store folder in a zip file called "WIP_DataStores". So feel free to have a look at this to maybe reuse some of the code.
In there are files which already kind of implement that kind of data store, but it never really worked out.
Maybe you can use them as a starting point for your own data store. Also have a look at this PR for a more detailed infos on this: #1471
List of issues requesting it
Hi, this is a issue which collects the state of this feature and it documents what has been decided on how to implement this.
This is so that who ever wants to implement it has a clear picture on how to do it.
In general we have agreed that this kind of data store should work as follows:
Storing data
Linking data
More resources
There has already been some progress on this which can be found in the data store folder in a zip file called "WIP_DataStores". So feel free to have a look at this to maybe reuse some of the code.
In there are files which already kind of implement that kind of data store, but it never really worked out.
Maybe you can use them as a starting point for your own data store. Also have a look at this PR for a more detailed infos on this: #1471
List of issues requesting it