Do you know if there has been any consideration on the developer/owner side regarding more user-friendly interfaces via my.scouting? It sounds from many comments like the issue of where the data lives is secondary to how it’s displayed, which is the most common user-side beef with database queries (besides “Why can’t I see…with my permissions?”) around my office.
As a user, if I’m in Scoutbook and I click a button that says “Leader Training” and it pops up the UI I’m expecting, I don’t see any reason I would care that it’s hosted at my.scouting in the same way as the reports we can currently see via My.Scouting Training Manager or Trained Leader Status.
I suspect that, if the BSA was willing to generate an interface that looked more like the old training status report from Scoutbook and less like the current Trained Leader Status report at my.scouting, these types of requests would go away.
At the unit level, there is a lot of extraneous data displayed that makes it more difficult to wade through the information to determine what each leader needs to complete to become Trained. For example, a typical unit leader checking their leaders’ training status does not need to see the following columns in the report:
- Sevice Area
- Gender Accepted
- Chartered Org Name
At the same time, seeing the laundry list of training codes is fine for someone at the council/district level trying to chase global trends, but for a user trying to figure out what training his or her leaders need to take, the codes make it difficult to sort out what training needs taking, since the training codes themselves don’t show up in the names of the training at BSA Learn Center.
Admittedly, if someone selects the full training program form his or her my.scouting account, and then just chugs through until everything appears done, then they’re going to tick all of the boxes. That said, the more obfuscated the interface, the less likely adult leaders are to know what they need to do. If it’s a lot of work for the devs at BSA to maintain a list of what training codes associate with what training video title, and count for what position, how much more difficult is it for every unit trainer to keep track of it.
Admittedly, what I’m talking about isn’t a Scoutbook feature request, per se. However, if you know that the BSA already rejected the idea of enhancing the UI at my.scouting, there’s not a lot of mileage in trying to drive change there, either. If they haven’t already said no, then the focus of the conversation can change from “Let’s bring training reports back to Scoutbook” to “Let’s define the feature set that we as volunteers need so that the BSA can determine whether or not to support that feature set at my.scouting.”, and then passing that list of requested features along to the folks at email@example.com.