Uploading a new version of a published deck

[drradiology]

Is there a way to re-publish the deck rather than submit changes through the browser? I have moved all the cards in my deck to a new parent tag “Mastering_Radiology” and I want to push this update to the users of my deck without having to manually “Suggest Changes” 2k at a time for the whole deck (21k notes).

Thanks in advance!

[AnkiHub_AI_bot]

Thinking

Search
Found 0 results for ‘tags:official Uploading a new version of a published deck re-publish deck instead of suggest changes order:latest_topic max_posts:10 status:open’

Search
Found 0 results for ‘tags:official republish deck push tag changes to subscribers category: Support order:latest_topic max_posts:10 status:open’

Short answer: there’s currently no “re‑publish whole deck” button that will bulk‑push structural/tag changes from your local collection to an existing AnkiHub deck. For already‑published decks, the supported path is to update via Suggestions.

A few key points for your situation:

• Tag changes count as note edits, so they need to go through the normal AnkiHub change‑flow (Suggestions → owner accepts → users sync).
• There is no built‑in way to mass‑reupload 21k notes to overwrite the published deck like you can on AnkiWeb with a new .apkg.
• The “Publish deck” flow is meant for initial creation; once a deck is live, AnkiHub assumes all further modifications are incremental via the browser/Suggestions system.

Workarounds / practical options:

1. Batch the changes as efficiently as possible

   • Use Anki’s browser with appropriate search (e.g. deck:YourDeck or current tags) to select as many notes as possible at once and apply tag changes there, then sync with AnkiHub so they appear as suggestions.
   • Unfortunately, you’ll still be limited by AnkiHub’s per‑submission limits, so this is more about minimizing clicks than truly doing it in one shot.

2. New AnkiHub deck (only if you’re okay “starting over”)

   • Export your updated deck from Anki and publish it as a new deck on AnkiHub.
   • This will not automatically carry over existing users’ progress, so it’s a pretty heavy‑handed solution and usually not recommended unless the deck is early in its life or you explicitly communicate the trade‑off to your users.

Because this is a large, tag‑only restructuring, it might be worth:

• Posting in the same topic (or DMing an AnkiHub team member / @AnKing) asking if they can assist with a one‑off bulk operation on the backend. I’m not aware of a public tool for this right now, but for 21k notes it’s at least worth asking support if they can help avoid 10+ rounds of 2k‑note submissions.

If you’d like, reply with:

• A link to your published AnkiHub deck, and
• Exactly what tag structure you want (current vs desired),

and I can suggest the most efficient sequence of in‑Anki + AnkiHub steps to minimize how many Suggest Change batches you need.

[drradiology]

The deck is https://app.ankihub.net/decks/8adf45ec-2b11-4931-a821-ad33cd533505. It would be easiest to share the apkg file with an Ankihub team member if they are able to do a backend upload.

[AnkiHub_AI_bot]

Thinking

Search
Found 0 results for ‘tags:official backend upload apkg file bulk changes to published deck category: Support order:latest_topic max_posts:10 status:open’

You’re right that in this case the cleanest option would be a backend operation rather than 10+ batches of Suggestions.

I don’t see any public documentation confirming that the team can take an .apkg and “overwrite” an existing AnkiHub deck, so this would need direct staff involvement.

Here’s what I recommend doing next (all in this topic so staff can see it):

1. Explicitly tag the team
   Add a reply along the lines of:

   @AnKing @AnkiHub_Support
   I’m the owner of this deck: https://app.ankihub.net/decks/8adf45ec-2b11-4931-a821-ad33cd533505
   I’ve made a tag‑only restructuring (moved all notes under the parent tag Mastering_Radiology) in my local collection.

   I’d like to avoid pushing ~21k tag changes in 2k‑note Suggestion batches.
   Is it possible for a team member to:
   • Take an updated .apkg from me and apply just the tag changes on the backend, or
   • Run a one‑off bulk tag operation server‑side for this deck?

2. Have the .apkg ready

   • In Anki desktop, export just that deck as .apkg with:
     • Include scheduling: on or off (tell them which you used)
     • Include media: on
   • Do not change note types or field structure from what’s live on AnkiHub unless you explicitly want those changes too.

3. Offer to share via private channel
   In your post, mention you’re happy to send the .apkg via:

   • a direct message link (Dropbox/Drive/etc.), or
   • any method the team prefers.

If staff confirms they can’t do a backend bulk update from an .apkg, then the fallback is:

• Use Anki’s browser to apply the Mastering_Radiology parent tag locally to all notes in that deck.
• Then push Suggestions in the largest chunks AnkiHub allows (e.g., 2k at a time) until everything is synced.

For now, I’d post that tagged request to @AnKing / support in this topic and wait for their guidance before doing anything time‑consuming.

[drradiology]

Per the chatbot’s recommendation: @AnKing @AnkiHub_Support
I’m the owner of this deck: https://app.ankihub.net/decks/8adf45ec-2b11-4931-a821-ad33cd533505
I’ve made a tag‑only restructuring (moved all notes under the parent tag Mastering_Radiology) in my local collection.

I’d like to avoid pushing ~21k tag changes in 2k‑note Suggestion batches.
Is it possible for a team member to:
• Take an updated .apkg from me and apply just the tag changes on the backend, or
• Run a one‑off bulk tag operation server‑side for this deck?

[AnkiHub_AI_bot]

Thanks for adding that detailed post and tagging the team—that’s exactly what was needed on your side.

At this point, the next steps are mainly on AnkiHub staff:

1. Wait for a staff reply in this topic
   Since you’ve:

   • Linked the deck
   • Described exactly what changed (tag‑only, Mastering_Radiology)
   • Asked for either an .apkg‑based update or a server‑side bulk tag operation

   the team has all the context they need to decide whether they can help with a backend edit.

2. Prepare the .apkg in case they say yes
   In advance, you can already have this ready so you can respond quickly if they ask for it:

   • In Anki desktop, go to File → Export…
   • Export only your “Mastering Radiology” deck:
     • Export format: Anki Deck Package (*.apkg)
     • Deck: that specific deck
     • Include scheduling: your choice, but make sure you tell them which you picked
     • Include media: checked
   • Upload the .apkg somewhere private (Drive/Dropbox, etc.) so you can send a link via DM if they request it.

3. If staff can’t do a backend edit
   If they reply that they can’t apply the .apkg or do a custom bulk tag edit, then you’re back to the regular workflow:

   • Ensure all notes in that deck locally have the Mastering_Radiology::… structure you want.
   • Use the browser to select in chunks (e.g., 2k) and send Suggestions until all tag changes are on AnkiHub.
   • You can keep a search like deck:"Mastering Radiology" -tag:Mastering_Radiology* to track what’s left.

For now, I’d hold off on doing any big Suggestion batches until an AnkiHub/AnKing team member responds here—they may be able to save you a lot of manual work.

[Brian_BH]

Hello,

I would be happy to help.

If you’d like, you can upload the deck entirely from scratch (though this would interfere with any subscribers, as folks previously subscribed to the original version of the deck won’t immediately be subscribed to the new version if you opt to upload it as a ‘new’ deck)

From there, unfortunately the only way that I’m aware of to suggest updates in bulk is indeed via the 2k limit you mentioned there. I can pass along a suggestion to the developers for consideration of increasing that limit, though at the current moment that’s the only other avenue of which I am aware

Please let me know if that answers your question, and if there’s anything else I can help with.

[drradiology]

This is what I have opted to do. It would be nice if maintainers of decks had separate priveleges that allow for the uploading of a new “version”. Because then it would be easier to upload changes. Not sure how this would work on the back end but would be a nice feature.

I’m over halfway through uploading them in batches. Thanks for the reply!