TaRapedia talk:Mission project/Mission categories

Draft discussion
I have written up a draft for mission categorization. It is inspired by current practice and other discussions, but deviates enough from the status quo that it should be treated as new. Let the discussion begin. - Dashiva (talk) 18:35, 7 January 2008 (UTC)


 * From the draft it looks to me the area/instance categories are the same as their respective Mission lists. eg: Category:Alia Das missions contains same missions as are listed in Alia Das mission list article.
 * To answer the issue of categorization of (Location) mission list article, I vote for categorization under Category:(Location) only and add link to the list from heading of Category:(Location) missions.
 * Combining the two previous paragraphs it looks like each area/instance/zone/continent/planet category will have their own Mission list and vice versa. I don't know though if we will be able to rewrite the Mission list articles using DPL or want it to stay static. (DPL could be created using 2 levels: first will list all mission givers and second will list all mission given by this contact). Using static lists will give us opportunity to add comments and information about mission flow (which missions are required for others and which are followups and which are contradictory) but will be harder to keep in sync with the category.
 * → Zarevak 19:50, 7 January 2008 (UTC)


 * Another comment: On Wilderness mission list there is No subzone section. How do you want these missions to be categorized? If the Category:Wilderness missions will contain all mission from all the Areas the one mission with no subzone will get lost in the long list.
 * → Zarevak 20:10, 7 January 2008 (UTC)
 * PS: Using capitalized word Missions in category names to link to existing categories. Category names should not use capitalized word Missions as written in the draft and as discussed before.


 * Agreed on putting mission lists in the parent location instead. The missions with no specific area remain a problem, but that problem is found in the MissionGiverLocation value. Solving it will automatically make the mission categories work out as well, so I do not consider it a problem for adding new mission categories.


 * I'm tending towards creating a missioncategoryheader template similar to missionlistheader. Added new mission template yesterday, so will go ahead soon(tm) barring new developments.