I am creating a Google form for people to submit any errors they find in my shared deck. Given that the deck is huge, I did something like this to my cards:
Notice the bottom-right corner. The icon there, when clicked should take people to a Google form with information about the card pre-filled. The users, then can simply tell me what’s wrong with the card and I’ll already know which card they are talking of
Issue I’m Facing
But I need a value that I can use to pinpoint the card. I have considered adding an extra field to the note types but,
I don’t know how to quickly fill in unique values to that field for all my notes
I think it’s less helpful when you have a lot of sibling cards.
Request
Could you add a special field replacement like {{CardID}} or {{NoteID}}, please?
If there is already a way to include unique IDs in links like this and anyone here is aware, please also tell me.
I can’t use the add-on on Android, but I still tried adding {{Card}} but seems it doesn’t add card type number. It’s obvious now looking at the docs but without the card type number, it’ll not work for cloze.
Most of my cards/content is cloze. Example:
Then I guess it’ll also not work for Image Occlusion notes (and just a few days ago, I converted all IOE cards to IO notes manually :sadge: ).
The current implementation incurs a (small) cost for every extra field we add, regardless of if it’s used, so I’m reluctant to add more until we can implement it better. That said, I appreciate the problem the OP is trying to solve, and think we can probably add an exception in this case. We’d need to decide on a name - ‘nid’ is unlikely to conflict with people’s existing fields, but is inconsistent with the other special fields. ‘NoteID’ would be more consistent, but I think there are some shared decks that use it already, so it would be a bit more disruptive.
I don’t think consistency is that important here so {{nid}} isn’t bad. And {{NoteID}} sounds good too. I assume most people would be using that field to store Note IDs so even if the behaviour changes, that shouldn’t be an issue for them, right?
If their setup depends on the IDs store in a note field, and those IDs differ from Anki’s note ID, then their setup could break until they rename the field.
Another solution is to add {{CardID}} instead of {{NoteID}}. If you get the card, then you also know the note. What do you think?
I assume the only reason a lot of people use {{NoteID}} is because they are using the fields of their note to store the data. And so, you can’t have different data for sibling cards.
Special fields allow card-specific data to be retrieved (like flags) so {{CardID}} would work right?
This feels like the ideal solution, we are neither sacrificing users with OCD nor we are breaking existing notes and decks.
In the OP’s case, the note id would probably be preferred, but you make a reasonable point, and if we’re only adding one, the card ID is more flexible & less likely to conflict.
Yes. Most of my decks — and all of my shared decks — have their own Note IDs to ensure uniqueness across the decks and the collection.
Using NoteID might not be a problem, as my decks use “Note ID” as the first column. This is a habit developed from initially using an odd-on that created a column of the same (or similar?) name.
However, if you decide to use that name/field, I can change all the decks that I have shared.
