I decided to enter it into the system anyways. We should probably talk about how to handle these sorts of double entries at some point. We might need to re-think how we are processing them. Being able to overwrite the entry (so long as it's a #Ping Back) might be a good idea for simplicity's sake... or it could just endUP bogging our systems down. I would be interested in hearing your thoughts about this.
Are we doing data entry in the best way? (Where late or after the fact Mission Reports are reported during a separate Bonus Round.) Or would it be better to allow Commanders the chance to write over their Single #Ping's? (Meaning more work on our end if Commanders begin entering all of their Single #Ping's and then again once they convert some of them to #Ping Backs.)
There's really two ways that we can approach this...
This is a second entry of the same user but it's great work all the same. Thank you very much and keep up the excellent work
Nice catch Pappy!
I decided to enter it into the system anyways. We should probably talk about how to handle these sorts of double entries at some point. We might need to re-think how we are processing them. Being able to overwrite the entry (so long as it's a #Ping Back) might be a good idea for simplicity's sake... or it could just endUP bogging our systems down. I would be interested in hearing your thoughts about this.
Are we doing data entry in the best way? (Where late or after the fact Mission Reports are reported during a separate Bonus Round.) Or would it be better to allow Commanders the chance to write over their Single #Ping's? (Meaning more work on our end if Commanders begin entering all of their Single #Ping's and then again once they convert some of them to #Ping Backs.)
There's really two ways that we can approach this...
@wil.metcalfe
Comet Ranker