Category talk:Vocabulary
I think it would be helpful to develop a template for use on all vocabulary pages that lists vocabulary in a table so that the lists are easier to read. A possible table format might be:
| 한국어 | English |
|---|---|
| 우체국 | post office |
| 우표 | postage stamp |
Within this table, words should be listed in alphabetical order.
Also, why are we capitalizing the English words in the definitions? I don't think they should be capitalized unless they are proper nouns.
- haesook 17:43, 7 June 2009 (UTC)
We should come up with a standard. It would also be nice to have a header to use on all of the vocabulary pages. --Mstrum 19:53, 10 June 2009 (UTC)
- If we make a table, maybe we should use a sortable table.. but if we make a table, what about sentence examples in the future?
I think sentence examples should probably be on individual vocabulary pages, what do you think? That way, when words are used on multiple vocabulary pages (most likely to happen) we don't have to worry about copying examples and things. --Mstrum 03:18, 16 June 2009 (UTC)
- Do you want to expand this project to a dictionary project as well? If so then that would definitely work. --Bluesoju 04:59, 16 June 2009 (UTC)
dictionary project?
add a dictionary project? sounds like my site. Everything is linked to search results. If when searching they click a textbox, then they will get hanja listings, else it's just the dictionary or the grammar ending sections. Searching proverbs is also a checkbox. 고사성어 results come up mixed into the ordinary search results. Then, the user can edit the search results ... there are no individual pages to construct, only entries to add or edit which are all accessible from the search results. This structure is centralized, information is held together by the software, and the software has created cross-referencing to simplify the amount of input necessary by me to create entries. For example, your hanja examples could be used to create examples of vocabulary. And, this is the problem here with koreanwikiproject site.
The problem is that, unlike ezcorean.com, here if I search for 창문 I get no results. I'm sure it's an example in the hanja section somewhere. But, the person doing vocabulary can't use the fact that it's already been created in your system to save his/her time.
Overall, I am tending to see that the wiki structure has increased the edits by users, and is user-friendly to edits, but that the information is becoming disorganized as koreanwikiproject lacks backend cohesion. Hanja pages are completely separate from vocabulary is completely separate from the slang page, for example. where is this all going to go? I think a programmer should fix this ASAP, if possible. But, as I said before, I am wiki-ignorant so I can't speak intelligibly on that issue.
My guess is that, like wiktionary project, you will end up with sweet large downloads of information which people then can use to create more useful sites or software because each entry is chock full of information, but which as a whole provides no functionality to actually help the language user learn the language inteactively.
I confess that I am worried about the future of koreanwikiproject being *useful* to users, and secondly, that the information is unorganized on the backend, and that the editors are creating duplicating work within the koreanwikiproject system itself.
These are my main concerns. As always, I wish your project the best. I thought it wise to offer my kind advice, and my best wishes to you here @ koreanwikiproject.com. Please accept my criticism/pointers in the spirit with which they were given.
Thank you, Joseph a.k.a. Joe
