You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the optional mapping of contexts in this plugin, there is the risk that some notes may not have any context mapped to it. This can lead to notes being "lost" in the spaced repetition practice if users have any context toggled to active but have forgotten that some subset of notes will never show up because they lack a context frontmatter property. Need to build some functionality to help surface these and maybe also to fill in the gaps. Older raw thoughts below:
Perhaps when creating new contexts via settings UI, can make a clear highlight calling out that N number of notes are onboarded to the SE plugin but do not have any context set, thus will not show up unless all contexts are set to inactive (I think?).
Could maybe even include a handy button below to copy to clipboard links to the top N (~15 or so) notes that fall into this bucket to help facilitate updating the notes. Alternatively / in addition, include a dropdown + button to directly apply some selected context to all currently-unmapped notes. Both the these could maybe persist forever when they open up the settings page to highlight risks of any notes that could become orphaned.
Similarly, when deleting contexts out of the settings UI, need to run a check for any notes that currently contain that context. If any exist, should prompt whether to continue (maybe do an actual Prompt with the question and details and ask the user to type in "Yes"). Could also maybe have an option the user can select to have the code delete out that context value from all notes in the vault (while keeping other context values in tact).
Also could generate Dataview queries to help them surface such notes.
The text was updated successfully, but these errors were encountered:
With the optional mapping of contexts in this plugin, there is the risk that some notes may not have any context mapped to it. This can lead to notes being "lost" in the spaced repetition practice if users have any context toggled to active but have forgotten that some subset of notes will never show up because they lack a context frontmatter property. Need to build some functionality to help surface these and maybe also to fill in the gaps. Older raw thoughts below:
Perhaps when creating new contexts via settings UI, can make a clear highlight calling out that N number of notes are onboarded to the SE plugin but do not have any context set, thus will not show up unless all contexts are set to inactive (I think?).
Could maybe even include a handy button below to copy to clipboard links to the top N (~15 or so) notes that fall into this bucket to help facilitate updating the notes. Alternatively / in addition, include a dropdown + button to directly apply some selected context to all currently-unmapped notes. Both the these could maybe persist forever when they open up the settings page to highlight risks of any notes that could become orphaned.
Similarly, when deleting contexts out of the settings UI, need to run a check for any notes that currently contain that context. If any exist, should prompt whether to continue (maybe do an actual Prompt with the question and details and ask the user to type in "Yes"). Could also maybe have an option the user can select to have the code delete out that context value from all notes in the vault (while keeping other context values in tact).
Also could generate Dataview queries to help them surface such notes.
The text was updated successfully, but these errors were encountered: