Deep Links

Up
Home

First of all, you are welcome to deep link. That way you can perform customized database queries.

I must admit that I was not prepared for web designers cloning my internal links (e.g. http://www.kleier.net/cgi/player.php?pid=1161). Being really efficient they suffer from the drawback that player IDs (pid=…) are transient: they change every time I insert another player into the database. Because this will happen quite often, you should never rely on pids.

But rescue has come. I have implemented more readable keys. In the case of players they are pre (for prename) and sur (for surname). The following example illustrates how they can be used to get the table of Mark Lukich Kunin:

http://www.kleier.net/cgi/player.php?pre=Mark Lukich&sur=Kunin

Linking to tournament tables leads to similar problems. The fix is to replace the transient event IDs (eid) by place (for place) and date (for date). To link to the results of the Breda tournament on 2007-03-24, you should use:

http://www.kleier.net/cgi/tourn_table.php?place=Breda&date=2007-03-24

Try it out. It works, it can be memorized, and it will never get outdated.

At this time there are semi-permanent links to announced tournaments. In the long run I will fix it and use the same URL for announced and for evaluated tournaments. Till then you can link to the Wuppertal tournament in 2010 with:

http://www.kleier.net/announced/show_announced/index.php?place=Wuppertal&date=2010-04-10

There is one issue I have passed over intentionally. Sometimes —if the player name contains umlaut characters or spaces— the links do not work. This happens if your system still does not use UNICODE characters yet. As an interim solution you can convert the umlaut characters manually.

Examples of Umlaut Character Representations
Character	UNICODE Representation
Space	%20
Ø	%C3%98
ß	%C3%9F
ä	%C3%A4
å	%C3%A5
é	%C3%A9
ï	%C3%AF
ö	%C3%B6
ø	%C3%B8
ü	%C3%BC

Here are some examples of links containing hard-coded umlaut characters

Cool URIs don’t change!