OBBLM administrator Wishlist

[GoogleCodeExporter]

I know that OBBLM is strongly date-prone, due to the fact all events,
match_data, SPP and the like are aggregated on the fly based on their
date/time fields in corresponding tables, but...

... what if data are inserted into the portal en-mass after a day of playing?
... what if I everyday create 3/4 Matches in an Open Tournament and insert
data en-mass after a couple of days?

The result is that I have no control above the correct order those matches
are inserted into my DB.

SO, after 1.5 years of usage, I strongly ask a function that allows, at
least at Global Admin Privileges, to edit the date_created & date_played
fields in the matches Table.

EVERY TIME our League admin insert some match report, I have to go to the
DB and correct by-hands all those 'date/time' data to be sure everithing
will match.

I strongly ask this to be present in the final release, if not possible to
add this feature in Match creation procedure or Match report HTML form when
compiled by users.

Thanks in advance

Original issue reported on code.google.com by Fabio.Mo...@gmail.com on 15 Feb 2010 at 5:39

[GoogleCodeExporter]

Sorry Fabio, but I can't.

When you manually change "matches" table's "date_played" fields you are 
tampering
with the OBBLM data chronology. 
For your own sake I would STRONGLY suggest you don't do this. 
You could end up forcing OBBLM to set incorrectly player statuses and (with the 
new
0.8) incorrect player skill selections too.

WHY is it a problem that the "date_played" field of matches is recorded as the
date(+time) for when the match report was submitted?

Original comment by Nimda...@gmail.com on 15 Feb 2010 at 10:00

[GoogleCodeExporter]

As long as you submit the matches in order, the date played really doesn't 
matter. 
If you want to know when it really was played, you can add it to the comment 
field...

Original comment by funnyfin...@hotmail.com on 16 Feb 2010 at 6:04

[GoogleCodeExporter]

Fabio writes:

Mates, I'm currently checking BY-HAND every single Match posted on my portal, 
forcing
my Site Admins (7 people over 45 Coaches) to write a comment in the Match Report
stating the date/time the match has been played, because having more than 5 
matches
played EVERY GIVEN DAY it's easy to make a mistake while inserting those 
matches in
the correct order.

Currently, based on the information I'm given this way, I modify the 
date_created and
date_played for every match in the 'matches' Table once a week, to be sure the 
data
are correctly ordered... ('players' table is modified accordingly if new 
players are
added between matches)

I'm using OBBLM yet since 2 years, and probably I know better the MANAGING 
tricks
than those who wrote the code itself (i'm not kidding).

Then, IF I ask this, under the LEAGUE/GLOBAL ADMIN restrictions, it's becuse 
this
could LARGELY EASE the management of a LEAGUE ADMIN with very wide Leagues, 
like mines.

I'm not here to have you lose time running after my every single request, but 
IF I
post an Issue, try to understand WHY I asked it, before telling to me things I 
cannot
IGNORE using the system by so long time...

Sorry for the slightly polemic mood, but it seemed to me that all of you REALLY
misunderstood the REAL problem... ADMINS can FAIL like every other PEOPLE on 
this planet.

TY in advance

Fabio Monty Montanari

Original comment by Nimda...@gmail.com on 18 Feb 2010 at 8:27

[GoogleCodeExporter]

Annoying, I just wrote a long response and hit "close window" instead of 
submitting.
Argh! ...anyway, Fabio, let me recap...

I'm sorry if we came of badly Fabio, let me try to get things straight :-).

In your league, teams play multiple games per night?
Also, all matches are submitted at ONCE at the end of the night in a random 
order?
If yes, what do you do then, if, say, a team's player gets a MNG in the team's
_second_ match, but the match is submitted as the teams _first_ match - this 
enforces
a incorrect MNG status in the match report for the team's first game! How do you
prevent this?
I don't see how you can get OBBLM working if you do not submit matches in the 
correct
order - especially if you only check once a week for errors?

Now, the thing is that in order to use OBBLM properly you are REQUIRED to 
insert the
match reports in the correct played order, for any team. This is THE condition 
for
using OBBLM. It simply does not work if you submit reports in a wrong order.
You have to see this from my point of view too - I can't possibly support this 
"hack"
(i.e. adding date_played changing support) into my own system leaving the system
unstable and in a debug nightmare. The date_played field in "matches" is not 
meant to
be changed, ever. It's for internal usage.

If you are editing date_played to fix incorrect submission order, then I can
understand you. But could you not then have your coaches write down the play 
order or
make them submit in correct order?
If you on the other hand edit date_played merely to make it represent the 
_actual_
played date, then I would have to tell you to interpret the field differently.
Really, date_played is the submission date of the report. If you want to record 
the
real date played, you should write it in the match summary text.

Original comment by Nimda...@gmail.com on 20 Feb 2010 at 12:56

[GoogleCodeExporter]

Maybe it would actually make sense to add a field for the date on which a game 
was in
fact played in addition to the field that is currently called "date_played" and 
in
reality represents the date on which the game was entered into OBBLM. This field
could have a default value of current date, but can be changed by the coach 
entering
the game. 

This however could lead to coaches belieing that the order of the entering 
games does
not matter.

I agree that there is really no clean way of entering games to the system in a
different order, as this would mean, that the OBBLM would have to be able to 
guess
the effects of the first game which has not been yet entered in order to have 
the
correct values in the second game.

Original comment by drpepper...@googlemail.com on 21 Feb 2010 at 11:02

[GoogleCodeExporter]

Exactly. Well said.

Original comment by Nimda...@gmail.com on 22 Feb 2010 at 6:47

[GoogleCodeExporter]

Closing this.

Original comment by Nimda...@gmail.com on 6 Mar 2010 at 2:58

• Changed state: WontFix