Using ankihub ID for new notes

🙋 Support
,
2

I’ll help you understand how to work with “forked” notes and AnkiHub. Let me search for relevant information about AnkiHub IDs and note syncing.

Search

Found 5 results for 'tags:official ankihub id notes sync status:public'

Search

Found 5 results for 'tags:official custom notes ankihub sync status:public'

Search

Found 5 results for 'tags:official ankihub fork note duplicate status:public'

Read topic

Reading: Why are notes skipped after subscribing to a deck?

Thank you for your detailed explanation about your note-taking approach. I understand you’re creating “fork” versions of existing AnkiHub notes to test yourself on related but slightly different information, and you’d like to maintain AnkiHub synchronization for other fields like extra and sketchy (especially for the new images).

Current Behavior with AnkiHub IDs

Currently, each note in AnkiHub has a unique ID that links it to the deck’s master version. This system prevents duplicates by identifying notes with the same ID across different decks, as explained in Why are notes skipped after subscribing to a deck?:

Notes are identified by their Anki note id. If two notes from two different decks have the same Anki note id, they (probably) stem from the same source…In general you don’t want to have duplicate notes, so the note that is installed second is skipped.

Your Request: Using Original AnkiHub ID in Modified Notes

What you’re proposing is an interesting workflow that isn’t currently supported in AnkiHub’s design. When you create a forked note, it gets a new Anki note ID, severing the connection to the original AnkiHub source.

Why this doesn’t currently work:

  • AnkiHub uses the note ID as the unique identifier for syncing content
  • Having multiple notes with the same AnkiHub ID could create conflicts in the syncing system
  • The system is designed to prevent duplicates, not manage variations of the same note

Potential Workarounds

  1. Field Protection: You’re already using field protection for the text field, which is a good approach. You could continue creating your modified notes and manually update them when original notes are updated.

  2. Consider Tags: You could create a system to tag your forked notes with the original note’s ID in the tag field (not the AnkiHub ID field). This wouldn’t enable syncing but would make it easier to identify which original note your fork is based on.

  3. Suggest a Feature: Your suggestion about adding this capability would indeed be useful for users who create “derivative notes” while wanting to maintain synchronization with original content. Consider posting this as a feature request in the appropriate section of the forum.

Alternative For Now

For now, you might consider creating a streamlined workflow for checking and updating your forked notes:

  1. Tag all your forked notes with something like “forked_note”
  2. Include the original note ID in a tag or field
  3. Periodically review updates from AnkiHub and apply them to your forked versions

The feature you’re requesting would be valuable and aligns with how some users create personalized learning materials while still benefiting from community updates. However, it would require changes to how AnkiHub handles note identification and synchronization.