The {{Rank}} template has gotten a lot of great use in the Wiki and as more features get added, it seems to be more difficult to maintain the three different sets of data (the main data, the Wiki editor table, and the Map editor table). As I reviewed the current template and related tables, I found a few missing entries from the Map editor table. For these reasons I have gone in and rebuilt the original template into a template suite creating the following benefits:
-
All current uses of the template in the Wiki continue to work with no change.
-
Additional outputs from the template have been added to enable both of the tables to be generated directly from the template code.
-
With a single source of data creating the template and both tables, it will be virtually impossible for anything to be out of sync.
-
The only exception would be if someone edits the core data and says a parameter is available, but forgets to add it to the same data row being edited. This might not make sense until you review the details of how the template suite works, but once you see it it should be clear.
-
There are now template features that enable a Wiki editor to use the description field from the Map editor (or Wiki editor) table(s) in other Wiki pages including the rank value for that feature embedded in the description. Of course, Wiki editors can still create their own sentences and embed the Rank value as was originally available.
-
The two different tables still use the original formatting in the first column were the Wiki editor table starts with the parameter to call each feature and the Map editor table starts with a category name for each feature.
-
Both tables also leverage the original description formats where the Wiki editor table does not include the value in the sentence and the Map editor table does include the value.
-
The two tables now include Map editor sortable options. I looked for a method to have each table presorted for their own view, but there is no Wikimedia solution at this time. Details can be read here.
-
Two features have descriptions that are dependent upon another feature’s value. I was able to keep that automation embedded, but because of the underlying complexity of the template operation, I had to use a slight Wiki editing trick on those two values when embedded in the table. If anyone ever needs to change those two values, the template comments show the Wiki editor exactly where to go to update those two values without the possibility that we will have anything out of sync.
Updated documentation for the new template controls for Wiki editors is still in progress, but most of that documentation is for anyone needing to change how the template works. As I said, the original operation of the template does not change, so that documentation is still accurate.
Please let me know if anyone has any questions or concerns.