Search Help

The IAGO Game Report Database includes a Level 1 CQL parser. We understand that this might seem a little overwhelming at first, but it is actually quite straightforward once you understand what information is available. Simple lists of games tied to a specific player, site, or game are available from the appropriate information pages and do not require you to learn how the main search engine functions.

If you have any questions or problems, if you have suggestions for new indices, or if you need some special report, please contact Aaron.

With the exception of boolean indices (of which there is currently only one), search requests take the form of: index relation term. All searching is case insensitive. Currently, specific sorting is not available.

Grouping

You can use parentheses () and the keywords AND, OR, and NOT to group queries in arbitrarily complex ways. One note: The keyword NOT is actually short for AND NOT. This means that you cannot ask: NOT game=abande. You would have to ask game<>abande or game=* not game=abande.

Wildcards

When using the equality relation ( = ), you can use wildcards. * represents any number of unknown characters (eg. game=ab* would find all reports for games starting with the letters ab). ? represents a single unknown character (eg. d?g would match dog and dig).

Relations

The following relation operators are allowed for all indices: =, <>, exact, any, all.

  • = honours wildcards.
  • <> is the opposite of = but does not currently honour wildcards.
  • exact also ignores wildcards and instead tries to find the term exactly as entered.
  • any takes 2 or more search terms enclosed in quotation marks. It is a shorthand for OR (eg. game any “abande attangle” is the same as saying game=abande OR game=attangle). Wildcards are accepted.
  • all takes 2 or more search terms enclosed in quotation marks. It is a shorthand for AND (eg. player any “Bob Bill” is the same as saying player=Bob AND player=Bill). Wildcards are accepted.

For numeric indices, you can also use: >, <, < =, >=.

Indices

The “index” is the field you are searching on. There are various types of indices:

  • Boolean
    • There is only one boolean index: moderated. It does not require a search term or relation. One would simply say game=abande and moderated or game=abande not moderated.
  • Text
    • Most indices are text-based and use any of the universal relation operators.
      • game: This searches both the official ID and full name of a game (such as homeworlds, Alfred's Wyke, etc).
      • site: This searches the official ID, full name, and URL of a registered site (eg. sdg, games.wtanaka.com, etc).
      • siteref: This searches the ID that each site gives to each of its games.
      • player: This searches the <player> elements of the reports.
      • player.iagoid: This finds game reports related to a specific IAGO user id.
      • date.start, date.end, date.submitted: These indices search the start, end, and submitted dates for each report. Dates are in the form YYYY-MM-DD. Wildcards are honoured.
      • event.type, event.name, event.iagoid: These indices search the <event> element of the game report.
  • Numeric
    • num.moves: This index counts the number of <move> elements in a report.
    • num.teams: This index counts the number of <team> elements in a report.
    • num.players: This index counts the total number of /team/player elements in a report.
  • Full-Text
    • Full-text indices are a beast unto themselves. They are handled by a separate system. The only relational operator permitted is = and the search term (enclosed in quotation marks) is passed as-is to the full text search engine. If you wish to include quotation marks in the full-text search, you must put a backslash (\) before it (ie. fulltext.chat = “\”hi there\”” would look for the specific phrase “hi there” in the game chat). If you need to do something particularly complex, you may want to read the documentation for the full-text engine.
      • fulltext.chat: Indexes all the <chat> elements.
      • fulltext.moves: Indexes each and every move (eg. “a1-a2”).
      • fulltext.comments.moves: Indexes the per-move comments (if any).
      • fulltext.comments.report: Indexes the <comments> element.
 
/home/html/iago/HTML/wiki/data/pages/formal/search.txt · Last modified: 2010/03/08 01:15 by aaron
 
Except where otherwise noted, content on this wiki is licensed under the following license:CC Attribution-Noncommercial-Share Alike 3.0 Unported
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki