See adding pages.
I have linked all the orphans that have been created over the past months, mostly names but also a few other pages. The authors are among the new enthusiasts here at SL :)
Please make sure you link a new page from an existing one, rather than just using the URL as a creation mechanism.
Take a professional article like Xu Yidi.
I see the most ordinary user scenario as being that a person sees Xu Yidi mentioned somewhere like Go4Go, GoRatings?, or in a tournament player list. They would then either search for Xu Yidi in the search bar or else go to the URL directly.
What is the point of linking to the Chinese professionals page? To state that he is a Chinese professional? That's already on the article.
And what benefit is it to have Xu Yidi linked on the Chinese professionals page? I find it hard to envisage a situation in which a user monotonously clicks through hundreds of pros on the list, except in the case that they're maintaining those articles.
The main point of the pros list is, imo, to provide lookup in oriental scripts. If so, fine, but simply linking Xu Yidi to the list by means of a link in the daughter page is not going to provide that facility, which requires an entry on the parent page.
First of all, it's a wiki discipline. These are the rules of the game, laid out 20 years ago and SL has been built that way.
But why is that so? What makes the rule a good rule?
The essence of a wiki is that all items are interlinked and made modular, so that it is fully self referential and complementary.
Fair point.
Currently we have
- the lists of Japanese, Chinese, Taiwanese and Korean professionals courtesy of DuEm?'s rip from Wikipedia
- the older lists of Japanese, Chinese and Korean names
- Go4Go Korean to address the particularly tangled topic of Korean romanisation. (I see that Korean Romanisation Discussion? was deleted, which seems a bit extreme. I don't remember being consulted on that...)
They all suffer from issues like incompleteness, incorrect romanisation, and rank ordering.
I think that a stable list of professionals needs to be ordered flatly by native script order: kana for the Japanese, hangul order for the Koreans, pinyin alphabetical order for the Chinese, and Wade-Giles alphabetical order for the Taiwanese. The Go4Go romanisations also have to be incorporated somehow, either as aliases or as columns or abbreviations in the page.
However, this would be a big project, and so we necessarily persist with the flawed but workable pages already here.
I think we should also consider outsourcing to the U-Go database in such a list, since they seem to have quite good authority control.
So an enty for Lee Sedol might look like
Ulrich's database is outdated and hasn't been maintained. If you're interested, you can contact him and perhaps work together to work on the database.
Anyways, I just want to say thanks for the work. It can be tough to single-handedly maintain the player's profile pages on SL. Someone certainly will find them useful later.
Anyways, since it's basically you're the only one who's doing this, just pick any reasonable format. People can always edit or fix the mistakes later.
Another option for indexes of names would be that every such name has keyword "Professional" / "Korean" for example and then the index just displays the pages with those keywords, in alphabetic order.
We can do this by using the Keyword template and using special search.
Are there auto-generated category pages on SL?
I know that MediaWiki? and some of those other wiki software have categories.
Ah, I see what Dieter means! I think that would be similar to what I was thinking of!
For example, Wikipedia has these auto-generated category pages: https://en.wikipedia.org/wiki/Category:Japanese_Go_players
I'll show how keywords work
I have added the keyword Korea to both these pages, using the template.
Here I did the same with keyword Professional
I'm still figuring out how to search multiple keywords. Intuitively I would
{{ special:search | parameter=Keyword:1 | value = Professional | parameter=Keyword:2 | value = Korea }}
But that doesn't work
We could use KoreanProfessional as a keyword of course.