I propose changing this language to “awarding a badge to a set of users”, as group has a specific meaning in Discourse and a bunch of random email addresses in a CSV isn’t it .
When bulk-adding users to a group, the system expects a list of user names. When bulk-adding users to a badge, the system expects a .csv file with e-mail addresses.
Personally I prefer the list of usernames, as it’s a lot easier to get those from the forums without jumping through admin-y hoops, and I’ve got some Excel tricks that can spit out a copy-and-pastable list. I used to bulk-assign badges by bulk-adding a list to a temporary group, then changing the badge query to assign to that whole group. When ‘award a badge to a set of users’ popped up I’d hoped to cut out a step…
Is there any way to make the list-of-users method a valid alternative way to bulk-assign badges?
If the first item in the list has an “@”, then import by email, otherwise, import by username.
Also, we could be a little more lenient when it comes to the format of that list.
We could just require the emails/usernames to be on their own line and then do a split("\n"), remove any empty lines, remove any trailing “,” and remove any pair of single/double quotes (eg. gsub(/^['"]|['"]$/, "")).
I know it’s hard and starts to risk mission-creep, but I wonder if over time the admin UI could aim towards more consistency across all Admin bulk operations? For example when:
Awarding Badges in bulk: Select badge then upload a CSV of users’ email addresses
Adding users to a Group in bulk: Select group then paste a list of usernames or emails, one per line
Inviting users to Discourse in bulk: Upload a CSV containing users’ email addresses (optionally specifying groups(s) to add them to and the initial post to show them)
Clearly these have areas of commonality but also areas of definite disparity where they are not doing the same thing. So how easy it is to work towards a consistent UI paradigm for all Admin bulk actions, I don’t know. But I thought I’d raise the issue here since it is being discussed.
Of all three variants, I’d say the nicest at the moment is the Bulk Add To Group ‘Paste a list of usernames or emails, one per line’.
Quite often I want to Invite several users (say 5-10) and the one-by-one invite method is a bit irritatingly slow, but the CSV invite method is a bit faffy and requires me to fire up another program, or edit CSV manually. Even if the CSV upload was kept for the really BIG bulk invites, it would be great to have an Invite Users dialog like the Bulk Add To Group one. Of course it could only accept email addresses, one per line, but this would be fine.
Though still not as simply as pasting a list of usernames into a box, that’s a great step forward from needing e-mails! Are there any plans to unify the bulk handling of adding users to groups or badges? I’m not a programmer, but that sounds like re-usable code to me
If the badge’s “Can be granted multiple times” checkbox is checked (found in the bottom section of the badge admin page), you should be able to award the badge multiple times in this way.
I have it enabled, but with a CSV import (even only a list of usernames of people that already have the badge) it does not grant it again. I have to manually grant the badge to the user before it shows up as being granted multiple times.
É possível conceder um distintivo manualmente a apenas uma ou duas pessoas em vez de fazer upload de um CSV?
Por algum motivo, o distintivo “entusiasta”, que requer login por 10 dias consecutivos, não está funcionando para alguém que fez login por 12 dias consecutivos.
Eu acho que esse distintivo é bastante confiável, mas às vezes a diferença entre fusos horários e UTC pode fazer com que pareça o contrário.
Não acho que você possa conceder manualmente esse distintivo no momento, mas criar um CSV com o(s) nome(s) de usuário leva apenas um segundo ou dois. Acabei de fazer um teste usando o Google Sheets no meu celular, e foi muito rápido.
.
