Investigate why the Claim count column in the MSOL Admin panel isn't going up

[threeqube]

On the admin panel, there is a column called claim. I assumed this was keeping track of all the badges that have been successfully claimed. I think this is an important metric to keep track of. Also how many badges are issued throughout the summer.

So far I've issued myself several badges and claimed them but the ticker isn't indicating this.

Would like to make sure we are accounting for both issue badge count as well as claim badge count.

[kayaelle]

The reason the count isn't working is that we're sort of working around open badger. We're not using the instances table anymore. Instead, the claimcodes are in the badge (they were already there) and whether or not each badge has been claimed is associated with each claim code. This could change as we get further into using the actual OB spec.

I'll investigate how to update this. Imagine it should only show the ones claimed by account holders? We're not tracking the non-account holder claims, just printing the pdf.

It may be best to sketch out what reports you'd like to see rather than hacking the existing ones. Would suggest tying that into an overall strategy for the product development.

[threeqube]

Agreed. I think we should have reporting for the following:

• issued count for each badge
• claim count for each badge
• total badges issued for the pilot
• total badges claimed for the pilot
• total number of MSOL accounts created
• total badges per account created
• how often was print badge used

Anything missing? Thoughts?

[threeqube]

Hey @kayaelle friendly check in on this.

[kayaelle]

@threeqube : some questions for you -

Would you define "accounts created" as the accounts where a user adds name, pw & agrees to terms or just that an email address has been added to the system (ie atleast one badge issued)?

Would you like to know how often a badge was printed by all awardees (generally how often anyone clicked on the print button) or how often a single awarded badge (per awardee) was printed or both?

For total badges issued for the pilot - this will be a mixture of account badges and just claim code badges. This will reflect some inaccurate data. For instance, if 50 students are awarded the same claim code, it will report one badge issued. Maybe we should talk about differentiating claim codes in the db. Perhaps if awarded bulk, it's a "bulk" type of claim code and otherwise it's an "individual" type of claim code.

Would add to badges report: #rejected, #unclaimed even though you can assume this from #issued-#claimed.

[threeqube]

Hi @kayaelle:

Would you define "accounts created" as the accounts where a user adds name, pw & agrees to terms or just that an email address has been added to the system (ie atleast one badge issued)?

The former. User adds name, pw & agrees to terms.

Would you like to know how often a badge was printed by all awardees (generally how often anyone clicked on the print button) or how often a single awarded badge (per awardee) was printed or both?

Both but if we need to choose, the former.

For total badges issued for the pilot - this will be a mixture of account badges and just claim code badges. This will reflect some inaccurate data. For instance, if 50 students are awarded the same claim code, it will report one badge issued. Maybe we should talk about differentiating claim codes in the db. Perhaps if awarded bulk, it's a "bulk" type of claim code and otherwise it's an "individual" type of claim code.

What's the work involved in differentiating claim codes in the db? I do feel like claim codes will be the exception rather than the norm during this pilot phase.

Would add to badges report: #rejected, #unclaimed even though you can assume this from #issued-#claimed.

:+1: Agreed, great points.