Just a quick few suggestions that Iām hoping you guys might add to your list of āto-dosā. Iām hoping they all align closely enough to each other such that I donāt need to do 3 separate forum posts. Our Malleus deck has grown quite significantly in terms of users and subsequently card submissions, which we are forever trying to deal with a backlog of. We have a core team of 8 Maintainers, and it would be nice to āassignā a maintainer to deal with certain batches of cards, so that itās easy to allocate and keep track of. Even if there was a counter that added up total pending submissions in some sort of āMaintainerā dashboard, with numbers of unassigned, assigned etc. submissions. It would also be nice to then have a toggle to filter this out on the AnkiHub web browser for each maintainer, so as to make the backend much easier than navigating 60 or so pages of cards yet to be reviewed (I am aware you can change the view from 10 to 100 cards on a pageā¦ but still).
As an adjunct to this, this review backlog is proving problematic due to the way new notetype submissions canāt easily be edited after submission for review. For example, imagine someone has submitted a batch of cards using a particular tagging structure. Itās then sat there for weeks while in the meantime we have updated our tagging structure to a new format which means that those old cards will all need to be updated to meet the new tagging structure. Currently itās extremely tedious to manually update this on every card, and in some cases we have been approving and then expecting the user to batch update this down the track which is suboptimal to the design of AnkiHub where you ideally gatekeep until the suggestion is ācorrectā and āappropriateā for syncronisation with the main deck. In some cases given the greater functionality of Anki with batch editing we have been approving batch cards to get around this and applying a āpeer reviewā tag within Anki. It would be nice to have some sort of functionality whereby users to can re-submit previously submitted cards to AnkiHub, such that only the most recent note ID submission or change-note submission remains on AnkiHub. I understand this is technically possible if we reject the notes on AnkiHub and then ask the user to resubmit, but due to our reviewer processes often involving discussions rather than outright rejections, it would be a nice feature. That way we could ask users to resubmit with the changes like tagging fixes and it will replace the existing submission and move to the top of the queue, saving maintainers a lot of time.
The other thing is Iām not sure if itās already a feature, but we are finding it quite tedious tagging every one of our maintainer individually (our total 8 maintainers) using the ā@ā feature - is there a way to create a āgroupā @ which pings everyone part of that maintainer group for example?
Yes this is possible, we do the same for the AnKing maintainers with a @. I believe I can create a @Malleus-Maintainers group and set you as the creator, then you can add whomever to this group and when you @ this group, it will ping everyone with a notification. Let me know if this is what youād like to do and I can create it for you
This is a great idea. This functionality kind of exists in Discourse but I believe only for admins of this space. For example, I can assign this post to a user and it will ping them everyday or every week to remind them. But Iām not sure if this can be extended to other non-admin users, Iāll see what is possible (cc @andrew). But I do agree a native AnkiHub specific feature on the website itself where you can keep track of these type of suggestions would be great. Iāve brought up to the developers before the idea of āfavoritingā a suggestion and keeping track of it so you can easily find it. We have over 600 pages of suggestions so itās crazy trying to keep track of everything. @TheAnKing has also wanted something similiar
Also something we struggle with and definitely takes a long time to fix manually. Unfortunately I donāt think this will be very high up on the dev to-do list so I canāt give you a time frame when this will be addressed, but thank you for reporting these issues!
Cheers for the prompt reply @Ahmed7! If you can make that Maintainer group that would be amazing and Iāll add the team! Appreciate your other replies - itās good to know some of these are on your radar, but I definitely understand these things take time to implement.
You should now be able to assign the Malleus-Maintainers group to a post on Discourse, so they can get pinged regarding it, or if you just want to keep track of certain suggestions
Also @Stapedius , try assigning specific maintainers and see if that also works
Appreciate this once again @andrew - we have played around with this but from what Iāve been told itās not quite what weāre after. Iāll tag @braviboron our lead maintainer to provide some details on our workflow and some features that might be useful and whether they could potentially be implemented.
@Malleus-Maintainers Thanks @andrew - we have been workshopping a new method to fix some of our issues. Let me get back to you in a short while with a more comprehensive review of how things could be tweaked for best use.
Sounds great. One thing @Ahmed7 pointed out is that there is at least one reason why what I showed in the video wouldnāt quite work as-is: the title of issues isnāt useful. I think that could be easily remedied by generating a short title for all suggestions. Looking forward to hearing back!
Ok so weāve done some playing around over the last few months and found a new workflow that works quite well for us. You may or may not appreciate an update for some new Ankihub features. No offence taken if not however!
But please donāt take any of the following as criticism - we love Ankihub, but have just found some ways to make it work a bit better for us, and you may want the feedback.
Our current method:
We auto-approve all maintainer cards and add a āto_do::peer_reviewā tag
Divide these cards up for review amongst our maintainers
Any discussions that need to be had about cards and edits are had on a Discord forum
Which allows everyone, i.e. all maintainers and users to see any discussion
You can tag people as required in those discussions
We still use Ankihub for non-maintainer suggestions and for edit card suggestions
The old vs new functionality on Ankihub is awesome for change card suggestions
Advantages of this method
Can easily count the number of cards for peer review
The discord obviates the deficiencies with the ā@malleus-maintainersā Ankihub feature that we couldnāt quite get to work as weād hoped
i.e. there are problems going back and forth from community forums to the community suggestions pages
Because all the cards are autoapproved, we can very easily edit cards in the browse window of Anki
Including by assigning cards to a maintainer for review in bulk by just making a tag like 'Peer_review::Assigned_to_xā
Advantages in Ankihub
The edit card submissions are great. Itās wonderful to see the before and after visually.
Disadvantages in Ankihub
Adding or changing tags is challenging in the Ankihub card submission review page
Itās hard to view cards compactly, like can be done in the Anki browse window
Canāt compare with cards already in the deck
The @[group of maintainers] function never worked absolutely perfectly
No easy way to assign maintainers to review cards
No way to edit or tag cards awaiting review en masse
No way to see what cards are already in the deck vs what is being suggested
Really would need an Anki online version for this
Or features that integrate the review functionality into Anki itself
Let us know if there are things we have failed to use correctly. Our current system works very pretty optimally, so weāre not really looking for changes, but like I said, you may be grateful for some user feedback.
