From Olmec Jaguar

Contents 1 Current Version 2 Version 18 2.1 Initial Ideas 2.1.1 Initial Ideas from Allan Sellers 2.1.2 Ideas from Alan Bishop 2.1.3 Ideas from Craig Bucknall 2.2 Design 2.2.1 Comment Types 2.2.2 Comment Attributes 2.2.2.1 Actor code within the commentary 2.2.3 Design Table 2.2.4 Web page design

Current Version

The current version, version 17, handles commentary in this manner:

• There are 10 commentary types in the current game:
  • red
  • shot - defensive stop
  • shot - goal
  • shot - offside
  • shot - off target
  • shot - save
  • yellow - first card
  • yellow - first card - homer ref
  • yellow - first card - strict ref
  • yellow - second card
• The commentary is loaded into separate tables in the database (one table per comment type).
• The simulator loads the commentary and uses it as needed.
• We have (had) an Olmec page that allows folks to add new suggestions.

Version 18

Initial Ideas

THIS SECTION SHOULD BE REMOVED ONCE WE'VE WORKED OUT THE DESIGN.

Initial Ideas from Allan Sellers

• Load all comments into one table, use different "comment types" as a field to differentiate them.
• Have a "frequency" value for each comment (1 = rare; 10 = common).
• Re-create the page to allow managers to suggest comments.
• Give 1-3 people per league the security level to approve comments. Once done it would go into the comment table that all leagues use (for that language).
• For non-english language, the process would be to have Al "truncate" (delete) the contents of the table and then that league could populate their comment table with the process in the previous bullet point.
• Have a "conditional field" for comments. This might better account for things like: "A GK might get a booking for some things...but probably not for shoving the opposing GK" (unless he has Rene Higuita Syndrome). This one has possibilities too like if its the GKs 10th save of a game...call that out...or if its a player's 15th goal of the season...call that out...or if you're an english announcer and a player scores their first goal of the season you, apparently, HAVE to say "he's opened his account".

Some additional ideas...

1) Right now commentary is pretty "vanilla". It could apply to any type of player at any time during the game. 2) Can you start to develop "attributes" of what should be considered in a comment. What comes to mind is:

 a) Comment Type (which we have now like yellow card, offside, etc).
 b) Time of match (for some comments it doesn't matter...for some perhaps it does)
 c) Position of "protagonist".  Was it a GK who was carded or a FW?  How would that change the comment?
 d) Score of match - It could be we want to say something like "Mike Morton is hot about his team giving up a late first half goal in a scoreless match". 
 e) Any "thresholds"...for example if a player just hit 10 goals or we now know they'll be missing the next match.
 f) Frequency of comment used

Optionally to account for some of the above we could have a comment type that is called "reaction-goal" or "reaction-red card" that would be invoked after the event to express the "excitement/outrage" of coaches/fans, for example. That may better handle things like "time of event, score, etc)...

Ideas from Alan Bishop

Alan sent me these as an email and they're good for getting the discussion going...

Initial thoughts on this would be...

1) There would be an general 'Commentary Addition' Page available to all who are logged in. Here you can view some recent approved additions and enter new suggestions, simple help (link to wiki?) would also be available. Any logged in user could then submit a new commentary 'idea' via a text box or series of choices. This submitted record could sit in the current commentary table. The table would need a new 'Approved Flag' column with a default of 'N'. May also be an idea to have a 'Submitted By', 'Submitted Date' all filled on on submission. An 'Approved by' and 'Approved By' Date might also be useful.

2) There would then be an admin page available to a selected admin community who could then approve, edit or delete any existing or proposed commentary records. Promoting a 'Commentary' record to approved would simply set the 'Approved Flag' to 'Y' and set the 'Approved By' to whoever approves it and the 'Approved Date' to current date and time.

An edit option would be available which would simply allow the admin to edit any existing commentary record. There would also be a delete option which would remove the record from the table.

To get going on something like the above I would need to know

a) What format(s) do we use for different commentary types?

b) Current desc of commentary table

c) Confirmation of login code/method to replicate normal user login

d) How do admins currently access 'admin' pages so I can replicate admin login?

Ideas from Craig Bucknall

These are my initial thoughts on commentary categories that aren't mentioned on the wiki page:

1) Penalties

2) Free kicks (without yellow/red cards)

3) Corners

4) Kick off (eg 'Team A will get proceedings under way, kicking right to left in the first half')

I don't know if the above is what you're thinking of, if not, let me know and I'll see if there's anything else I can come up with.

Commentary ideas:

Corners

'Player 1 lofts a high ball to the back post...Defender A rises well, beating Forward 1 to the ball and clearing with a good header.'

'Player 1 with a short ball to Player 2, who provides a pinpoint cross onto the head of the unmarked Forward 2...Forward 2 with a powerful header into the roof of the net...Goal!!!' No chance for Keeper 1 there, he berates his defence for their slack marking'

Design

Comment Types

Identify what the comment type is and what situation is is used in.

Comment Attributes

- Identify the other characteristics of a comment (see ideas above) - Identify the "actors" in each comment (scorer, teamabb, coach, etc)

Actor code within the commentary

Each comment will include various elements such as the player who took a shot, the defending goalkeeper, etc. These act as placeholders such that the proper shooter, goalkeeper, etc will be used for a given situation by the simulator to put in the name, coach, city, and so on. This list should be added to during the design phase with other ideas for "actors".

%shooter example: Thierry Henry

%passer example: Fredrik Ljungberg

%gk example: Roy Carroll

%defDF example: Gary Neville

%offAbb example: (ARS)

%defAbb example: (MAN)

%offCity example: North London

%defCity example: Manchester

%offTeamGoals example: 2

%defTeamGoals example: 1

%pasNationality example: Swede

%goalieNationality example: Irishman

%shootNationality example: Frenchman

%offNickname example: Gunners

%defNickname example: Red Devils

%offCoach example: Arsene Wenger

%defCoach example: Sir Alex Ferguson

%yc example: Roy Keane

%rc example: Ryan Giggs

%yellowNationality example: Irishman

%redNationality example: Welshman

Design Table

Based on the attributes design the table needed to store the comments

Web page design

Put in the features/capabilities for the web page so suggestions can be made to add/change/delete comments and have a few people act as "editors/approvers" of comments before they hit the database.