Skip to content

Commit

Permalink
Merge pull request #116 from vash3g/RatingsOpsUpdates
Browse files Browse the repository at this point in the history
Update qualifications.html
  • Loading branch information
Michael Hiiva authored Aug 31, 2020
2 parents ab6fdfc + 4586806 commit 44e729a
Showing 1 changed file with 10 additions and 7 deletions.
17 changes: 10 additions & 7 deletions agagd/templates/static_pages/qualifications.html
Original file line number Diff line number Diff line change
Expand Up @@ -35,9 +35,10 @@ <h1>Qualifications for Rated Games</h1>
The following is a minimal example, reporting two even games played at a club.
</p>
<blockquote class="code">
TOURNEY Princeton Go Club Rated Games, Princeton, NJ, June 15-30, 2004<br>
Tourney Princeton Go Club Rated Games, Princeton, NJ, June 15-30, 2004<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;start=6/15/2004<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;finish=6/30/2004<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;location'Princeton, NJ'<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;rules=AGA<br>
PLAYERS<br>
&nbsp;489 Matthews, Paul 4k<br>
Expand All @@ -48,19 +49,18 @@ <h1>Qualifications for Rated Games</h1>
</blockquote>
<p>
The tournament or other event must be clearly identified,
including the event name, location, start and finish dates, and rules of play (e.g., AGA, Ing, Japanese).
including the event name, location, start and finish dates, and rules of play (e.g., AGA, Ing, Japanese). Headers similar to those above will best follow this format and have all information accurately recorded in the AGAGD.
</p>
<p>
Each player must be identified by an AGA ID number, full name, and rank used for the event. If an ID number is not available then use a temporary number distinct in the range 90000-99999. We often have players with the same names, so include a postal address, email address or other information sufficient to identify the new member.
The <a href="https://agagd.usgo.org">AGAGD</a> can be used to look up individual players. All players must be AGA members in good standing at the time of the event.
Each player must be identified by an AGA ID number, full name, and rank used for the event. You may NOT use a temporary member number when submitting. This will cause the tournament to be delayed until membership statuses are current. We often have players with the same names, so include a postal address, email address or other information sufficient to identify the new member.
The <a href="https://agagd.usgo.org">AGAGD</a> can be used to look up individual players. All players MUST be AGA members in good standing at the time of the event.
Players can <a href="https://www.usgo.org/members">join/renew and update membership data online</a>, and should be encouraged to do so before the event.
In case a player needs to join at the tournament site, the tournament registration form should include essential data needed for AGA membership;
this also applies to so called "non members" who must provide the same data as members so that they can be clearly identified. Members can sign up using the web form and generate an AGA ID innstanrtly.
this also applies to so called "non members" who must provide the same data as members so that they can be clearly identified. <b>Members can sign up using the web form and generate an AGA ID innstanrtly.</b>
Membership data can be sent together with other tournament data to <a href="mailto:[email protected]">[email protected]</a>.
</p>
<p>
Each game record comprises White's ID, followed by Black's ID, who won (B for Black, W for White),
the number of handicap stones, and the komi
Each game record comprises White's ID, followed by Black's ID, who won (B for Black, W for White), the number of handicap stones, and the komi
(recorded as integer equal to the number of prisoners Black would give White).
</p>
<p>
Expand Down Expand Up @@ -90,6 +90,9 @@ <h1>Qualifications for Rated Games</h1>
Generally, private matches and Internet games are not AGA rated because they usually do not meet these conditions.
</p>
</p>
<p>
Updated 8/30/2020
</p>



Expand Down

0 comments on commit 44e729a

Please sign in to comment.