Resource-Based UWorld Tags for the AnKing Deck

🙋 Support
1

I’m considering contributing a new tagging project to the AnKing deck and wanted to get feedback before I start.

I have a detailed mapping of UWorld QIDs, and I could use Python scripts to automatically tag the entire AnKing deck with resource- and topic-based tags for each UWorld question.

For example, instead of only having:

  • “UWorld::QID::12345”

cards could also receive tags such as:

  • “UWorld::Sketchy”
  • “UWorld::Boards_and_Beyond”
  • “UWorld::Pathoma”
  • “UWorld::Bootcamp”
  • “UWorld::Cardiology”
  • “UWorld::Renal”
    and further by videos by finding pattern in relevant cards.

This would let users study all AnKing cards relevant to a UWorld question by resource or topic, rather than only by QID.

Would this be something the community would find useful? Is this something that AnKing/AnkiHub would be interested in incorporating if the mappings were accurate and consistently generated?

2
Thinking

Search
Found 1 result for ‘tags:official UWorld tags AnKing deck resource-based Sketchy Boards and Beyond Pathoma Bootcamp order:latest_topic max_posts:20 status:open’

Yes—this sounds potentially very useful and very much in line with how many people use the AnKing deck with UWorld.

A few thoughts and questions that might help shape this into something AnkiHub/AnKing could realistically adopt:

1. Potential value

Big pros for users:

  • Being able to filter within a QID’s cards by:
    • Resource (UWorld::Sketchy, UWorld::BnB, etc.)
    • System/topic (UWorld::Cardiology, UWorld::Renal, etc.)
  • Quickly building filtered decks like:
    • “All AnKing cards for UWorld questions I missed that are covered by Sketchy”
    • “All renal cards linked to UWorld questions I flagged”

This lines up nicely with how people already organize around:

  • Only_Step_1&2 tags
  • UWorld QID tags
  • Resource-based tags (e.g., Sketchy, Pathoma, etc.)

2. Things AnkiHub / AnKing team will probably care about

To increase the chance this can be incorporated officially, it helps to clarify:

  1. Data source & accuracy

    • How are you mapping QIDs → topics/resources?
    • Is this pulled from UWorld’s own categorization or manually curated?
    • How accurate is it (e.g., % of QIDs tagged correctly in a spot check)?

  2. Tag structure / naming convention

    • Matching existing conventions is key so tags don’t become chaotic.
    • For example:
      • UWorld::System::Cardiology
      • UWorld::Resource::Sketchy
    • Or something close to how Only_Step and current UWorld tags are structured.

  3. Coverage & maintenance

    • Does your mapping cover:
      • All current UWorld Step 1 & 2 questions?
      • Only certain subjects or question blocks?
    • How easy would it be to:
      • Update tags when UWorld adds/archives questions?
      • Regenerate tags for new deck versions?

  4. Implementation via AnkiHub

    • AnkiHub pushes tag changes really well, so this could be delivered as:
      • An additional “UWorld resource/topic tag layer” on the main Step deck, or
      • A separate, opt‑in tag pack/sister deck that users can subscribe to.
    • The team will likely want:
      • A preview subset (e.g., one system) to test tag quality.
      • A clear, reproducible pipeline (script + mapping file) in case they need to re-run it for future deck versions.

3. Next concrete steps you could take

If you’re up for it, you could:

  1. Create a small pilot

    • Pick one system (e.g., Cardiology) and:
      • Apply your UWorld::System + UWorld::Resource tags to that subset.
    • Share:
      • Sample cards or screenshots
      • The exact tag patterns you propose

  2. Document your pipeline (non-code overview)

    • Very high-level description like:
      • “I start from a CSV of [QID, System, Topic, Resource…], then map to card tags based on existing QID tags in the AnKing deck, then generate tags in the format UWorld::System::X, UWorld::Resource::Y.”

  3. Ask specifically about integration preferences
    In this same topic, you could tag / invite input from the AnKing/AnkiHub team (e.g., “Would you prefer this as an official tag layer on the main Step deck vs. a separate opt-in project?”).

4. Short answer to your questions

  • Would the community find this useful?
    Very likely yes—many users want more granular ways to connect UWorld with AnKing beyond just QID tags.

  • Is this something AnKing/AnkiHub might incorporate?
    It’s plausible if:

    • The mappings are accurate and reproducible,
    • Tag naming fits existing conventions,
    • It doesn’t create excessive maintenance load.

Your idea is strong; sharing a small, concrete demo in this thread is probably the best way to move it toward something official.

3

how will i share my master tag to ankihub

4

To get your “master tag” setup onto AnkiHub, you essentially have two paths:

1. Contribute directly to an existing AnkiHub deck (most likely what you want)

If you want your new UWorld resource/topic tags to be part of the official AnKing Step deck on AnkiHub, the usual flow is:

  1. Subscribe to the AnkiHub deck

    • Make sure you’re using the latest AnKing Step deck version that’s linked to AnkiHub.
    • Sync with AnkiHub so your local deck is properly connected.

  2. Apply your tags locally

    • Run your script on your local copy of the AnKing deck.
    • Confirm tags are:
      • On the correct notes/cards
      • Following a clean convention (e.g. UWorld::System::Cardiology, UWorld::Resource::Sketchy).

  3. Submit tag changes as AnkiHub edits

    • In the AnkiHub add-on, you can propose edits (including tag changes) to notes.
    • Those changes get uploaded as suggestions that maintainers can review and merge.
    • Practically, for a large tagging project, the AnKing/AnkiHub team will probably want:
      • A description of what you changed (tag formats, scope, how generated).
      • Maybe to test it on a subset first (e.g. one system).

  4. Coordinate with the maintainers in this thread

    • Post here:
      • A short explanation of your tag scheme,
      • How many notes/cards will be affected,
      • Whether you’ve already applied a pilot (e.g. all Cardiology questions).
    • Ask explicitly:

      “If I apply these tags locally and push them via AnkiHub as note edits, would you be open to reviewing/merging them as part of the official deck?”

This route means no separate deck—just enriched tags on the official one, delivered through normal AnkiHub sync.

2. Create a separate “tag layer” deck (opt‑in project)

If the maintainers prefer something more modular:

  1. Create a new Anki deck that only carries your tag changes

    • This is usually done via a copy of the main deck + your tags, then:
      • Upload that as a separate project on AnkiHub.
    • Users subscribe to your project in addition to the main AnKing deck.

  2. Describe clearly what your project does

    • In the AnkiHub project description:
      • “This deck adds UWorld resource/system tags such as UWorld::System::Cardiology, UWorld::Resource::Sketchy to cards already tagged with UWorld QIDs in the AnKing deck.”

  3. Link it in this topic

    • Once created, you can share the project link here so others can subscribe and give feedback.

What you should do next (practical steps)

  1. Make a small pilot first

    • Choose one system (e.g. Cardiology).
    • Apply your new tags to that subset only.
    • Take 1–2 screenshots in the Browser showing:
      • Existing QID tags
      • Your new UWorld::System::… / UWorld::Resource::… tags.

  2. Post in this thread:

    • How the tags are structured (exact format).
    • How you generated them (short, non-code explanation).
    • Whether you’d rather:
      • Contribute to the main deck via AnkiHub edits, or
      • Publish a separate AnkiHub project.

  3. Ask the AnKing/AnkiHub team which integration path they prefer

    • That will determine whether you “share your master tag” by:
      • Submitting edits on the main deck, or
      • Creating a new AnkiHub project.

If you tell me which deck/version you’re using and whether you’d prefer “integrated into main deck” vs “separate tag layer,” I can outline the exact clicks/menus in AnkiHub you’d use for that route.

5

i am subscribed and using latest version of ankihub my python script will crate a master tag and under that hierarchial tags further but i cant suggest a change of every card to ankihub i just wanna suggest at same time

6

You’re right that manually suggesting changes for every single card one by one is not realistic. The key is:

  • AnkiHub works note‑by‑note, not “bulk tag change for the whole deck in one shot.”
  • But you can still push many changes at once by editing tags on your local deck first, then syncing.

Here’s how to think about it and what you can do:

1. What is possible (and what isn’t)

  • :white_check_mark: You can:

    • Use your Python script locally to:
      • Add a top‑level tag like UWorld_Master (or whatever you name it),
      • Add all your hierarchical tags under it (e.g. UWorld_Master::System::Cardiology, UWorld_Master::Resource::Sketchy, etc.)
      • Apply these to thousands of notes at once in your own collection.
    • Then use the AnkiHub add‑on to upload all those tag changes together as suggestions.

  • :cross_mark: You cannot:

    • Send “one single suggestion” that says “add this tag to X,000 notes.”
    • Avoid touching the underlying notes at all – tags are stored per note, so the changes must exist on each note.

What AnkiHub sees is: “this user changed tags on N notes” in one sync, not N separate manual suggestions.

2. Practical workflow to push everything at once

  1. Run your script on your local AnkiHub‑linked deck

    • Confirm:
      • All new tags live under one clean parent (e.g. UWorld_Master).
      • Tag format is consistent and readable.

  2. Verify a small sample first

    • In Anki’s Browser, search:
      • tag:UWorld_Master
    • Spot‑check:
      • Are the correct UWorld QID cards getting the right system/resource tags?

  3. Sync with AnkiHub (this is your “bulk suggestion”)

    • Open the AnkiHub add‑on and sync.
    • All tag changes you made locally will be uploaded in one go as suggested edits.
    • The maintainers can then:
      • Review/accept them,
      • Or ask for adjustments.

From your side, it’s still one action (run script → sync), even though internally it’s many note edits.

3. Important: coordinate with the team before doing it on the whole deck

Because your script will touch a lot of notes, it’s best to:

  • Start with one system as a pilot (e.g. all your UWorld_Master::System::Cardiology tags).
  • In this thread, post:
    • The exact parent tag name you’ll use (e.g. UWorld_Master),
    • Example child tags (UWorld_Master::System::Cardiology, UWorld_Master::Resource::Sketchy, etc.),
    • How many notes were modified in the pilot.

Then ask the maintainers:

“If I run this script on the whole deck and sync, AnkiHub will get tag edits on ~X notes in one batch. Are you okay with me uploading that as suggested edits under a single parent tag (e.g. UWorld_Master)?”

This gives them a chance to say “yes, go ahead” or suggest a different tag structure first.

4. If they don’t want it on the main deck

If the team prefers not to have that many new tags directly in the main project, then the alternative is:

  • Create a separate AnkiHub project that contains your tag layer.
  • Users who want your tagging subscribe to your project in addition to the main AnKing deck.

But the basic mechanism is the same: you script tags locally → sync → AnkiHub gets many tag changes at once.

If you tell me the exact parent tag name you’re planning (e.g. UWorld_Master vs something else), I can help you phrase a short message here to the maintainers so you can get a green light before running this on the full deck.

8

Hello,

Thank you for reaching out and for your idea! At the moment, we won’t be incorporating this into the deck however you could create an optional tag and add the tags there. That way any person who wants these tags could get them by subscribing to your optional tag

Here is some info on optional tags: 🏷️ Optional Tag Groups

9

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.