Wiki Maintenance: Difference between revisions

From Swarm Cycle Wiki
Jump to navigationJump to search
(Update work done, work needed. -ZM)
(Assorted updates on ongoing projects -ZM)
 
(16 intermediate revisions by the same user not shown)
Line 1: Line 1:
(Temp note - editor software crashed while saving after update, slowly adding sections in until I find the culprit. [[User:ZM User|ZM User]] ([[User talk:ZM User|talk]]) 07:32, 11 May 2024 (PDT)) <br>
== Wiki Maintenance Notes ==
&nbsp;&nbsp; This is a discussion and notes page for ZM, Sgt. Stoner, Omachuck, and the others who maintain the Swarm Cycle Wiki. <br>
<br>
 
=== Article Improvement ===
&nbsp;&nbsp; '''Article Structure:''' This wiki has three general types of articles, plus some management-type articles that don't fit into any of the three.&nbsp; Each 'story' article should have the same information about that story as all other story articles have about theirs, organized the same way.&nbsp; Similarly, each 'author' article should have the same information about that author as all other author articles have about theirs, organized the same way.&nbsp; All of the 'subject' articles should have the same organization as all the other subject articles.&nbsp; This principle isn't as important as adding useful information to the wiki, but it should be in the back of each editor's mind as they work. <br>
&nbsp;&nbsp; Each article should have management template 'tags' at the top.&nbsp; Examples are 'Temp', 'Stub', and 'Duplicate'.&nbsp; These should be followed by the article text, and then below that several reference sections at the bottom of the article, in the same order, whenever appropriate.&nbsp; That way, readers can easily see if more info is available.&nbsp; Currently, that list of standard sections is: <br>
* "Story Statistics", for articles on specific Swarm Cycle stories
* "Story Usage Statistics" for articles on technical terms
* "Story Quotes" for articles on technical terms
* "See Also", a list of links to related articles
* "References", a list of links to information outside this wiki
&nbsp;&nbsp; We place all the 'Category' tags together at the bottom of the article, since that's where they are seen in a 'live' article.&nbsp; Sometimes we try to organize them into a coherent order, but we haven't decided what that order should be.&nbsp; Certainly, the 'Category:All' entry should be on a line by itself, on the very bottom. <br>
&nbsp;&nbsp; '''Ongoing Work:''' There are a lot of articles which are obviously incomplete.&nbsp; For instance, the [[Timeline]] page only shows 88 stories.&nbsp; As of 12/22/24, SOL has 323 stories listed, and we know of several more that we lost.&nbsp; Where do the other 235 stories belong on the timeline? <br>
&nbsp;&nbsp; The "List of Sleep-Trainer Modules" needs adding to, also.&nbsp; We have 38 general-use, 70 CMC, 74 general CN, 62 Castle-specific, and 18 CS for 260+ total.&nbsp; There should be many more.&nbsp; Certainly, if there are 62 for such a small and simple ship as a Castle there should be at least that many more for each class of ship we use.&nbsp; We list 12 other classes of warship... <br>
 
&nbsp;&nbsp; '''Categories:''' An article may have a list of 'Categories' at the bottom.&nbsp; Each category is a property which the article's subject has, and a reader may click on that category to see a list of other articles about that same property.&nbsp; For instance, the article on [[Castle]] is about a particular design or 'class' of ship.&nbsp; The bottom of the article lists five categories that the Castles are included in: 'Canon', 'Navy', 'Warships', 'Corvettes', and 'All'.&nbsp; The reader may click on those links to see lists of all articles that have been declared to be canon, or which are about the Confederacy Navy, or which include all Confederacy warships, or which include all corvettes, which is a functional label that means 'small patrol warship'. <br>
&nbsp;&nbsp; Anyone can edit an article to add other categories.&nbsp; Popular ones include 'Stubs' which means this article is very short, and 'List of Lists' which is a collection of all of the wiki's varied 'List of <this>' articles.&nbsp; Of course every article should be a member of the 'All' category. <br>
&nbsp;&nbsp; Some categories are special-purpose.&nbsp; The 'All' category includes all articles in the wiki.&nbsp; The reason for it is to allow any user to make an XML backup of the wiki's pages.&nbsp; The only reasonable backup method available to users is the 'Export' function, which allows you two options: you can export all pages on a list you provide _or_ you can export all articles in a particular category or list of categories.&nbsp; The 'All' category allows a user to easily do a backup of all articles simply by selecting Category:All.&nbsp; As of 1/31/26, all articles in this wiki are members of this category.&nbsp; All editors are requested to ensure that every new article is added to Category:All, if nothing else, so that we can easily do backups. [[User:ZM User|ZM User]] ([[User talk:ZM User|talk]]) 10:34, 31 January 2026 (PST)


== Wiki Maintenance Notes ==
&nbsp;&nbsp; '''Templates:''' A wiki can gain a lot of functionality by enabling templates, but as of mid-2024 they do not work here as they depend upon back-end processing not yet installed.&nbsp; Sgt. Stoner had taken the time to add a HUGE section on available templates here, but apparently there are enough differences between that wiki and this one with the latest version of WikiMedia that it crashes this copy of the editor every time I add it in.&nbsp; I still have it as a text file, if we can get any use from it. -ZM <br>
&nbsp;&nbsp; This is a discussion and notes page for ZM, Sgt. Stoner, and the others who maintain the Swarm Cycle Wiki. <br>  
<br>
<br>


=== Operation Duplication Elimination ===
=== Operation Duplication Elimination ===
* Moved all useful content from "Home" to [[Main Page]] and [[Unwritten Stories]] -done 4/30/24; I left the history section for now.&nbsp; On 5/2 I eliminated all links to "Home" and renamed the remaining history section [[Wiki History]]. -ZM
* If there's only one article listing stories (or authors), we'll never have conflicting updates where different articles say different things.&nbsp; And, if there's only one article listing stories (or authors), we don't need a category to list all the articles listing stories (or authors). -done 4/30/24 ZM, deleted Category:Story Listings
* Moved all useful content from "Join" to [[Contact Us]] -done 4/30/24 ZM, including the "How-To" section. -done 4/30/24 ZM, deleted "Join"
* If there's only one article listing stories, we'll never have conflicting updates where different articles say different things.&nbsp; And, if there's only one article listing stories, we don't need a category to list all the articles listing stories. -done 4/30/24 ZM, deleted Category:Story Listings
* If there's only one article listing authors, we'll never have conflicting updates where different articles say different things.&nbsp; And, if there's only one article listing authors, we don't need a category to list all the articles listing authors.
* I guess I don't understand the difference between a "listing article" and a "category".&nbsp; Exactly what added value do we get by having both
* I guess I don't understand the difference between a "listing article" and a "category".&nbsp; Exactly what added value do we get by having both
** a "Corvette" article which describes the class of ship and lists all known designs, and
** a "Corvette" article which describes the class of ship and lists all known designs, and
** a "Corvette" category which describes the class of ship and lists all known designs?
** a "Corvette" category which describes the class of ship and lists all known designs?
&nbsp; From where I sit, the two do the same thing.&nbsp; Duplication in a critical warship system is good, as it improves your chance of surviving damage.&nbsp; Duplication in a 600-article hobby wiki is stupid and leads to confusion when one is updated and the other is not.&nbsp; One or the other is going. -ZM
&nbsp; From where I sit, the two do the same thing.&nbsp; Duplication in a critical warship system is good, as it improves your chance of surviving damage.&nbsp; Duplication in a 600-article hobby wiki is stupid and leads to confusion when one is updated and the other is not.&nbsp; One or the other is going. -ZM
* Similarly, there is an article [[Characters]] and a category [[Category:Story Characters]] which do the same thing, which is to list assorted characters.&nbsp; One or the other should go.
<br>
<br>


=== Pages Still Needed ===
=== Pages Still Needed ===
&nbsp;&nbsp; As I go through the "Wanted Pages" list of bad links I'm finding several places we _should_ have an article, but we don't yet.&nbsp; I'm 'fixing' the bad link by replacing the double-brackets with triple-apostrophes.&nbsp; Instead of [[Hell]] we have '''Hell'''.&nbsp; I should probably list them all here as I find them: Dreadnaught, Atlanta, Plasma Torpedo, Artillery, list of pod freighters... <br>
&nbsp;&nbsp; As I go through the "Wanted Pages" list of bad links I'm finding several places we _should_ have an article, but we don't yet.&nbsp; I'm 'fixing' the bad link by replacing the double-brackets with triple-apostrophes.&nbsp; Of course, in one instance [[Hell|Heaven]] we don't really need that page.&nbsp; It's just an example of how to use links.&nbsp; I should probably list the individual pages we need here as I find them: Dreadnaught, Artillery... <br>
<br>
&nbsp;&nbsp; Anyone logged in can edit existing pages or even create new ones.&nbsp; We have several articles to help with this.&nbsp; [[Sample Article]] has an outline of the way info articles are organized in this wiki.&nbsp; The [[Wiki Editing Guidelines]] has advice on how to make your article look good and be helpful.&nbsp; The [[Wiki Test Page]] has a 'sandbox' section where you can try out different formatting codes and see how they look. <br>
<br>
&nbsp;&nbsp; We still have three big groups of 'needed pages':
* '''All stories''' - Every Swarm Cycle story should have its own page, filled with all the metadata that Sgt Stoner was working on.&nbsp; This is an automated task better left to someone who deals with scripts better than I do.&nbsp; As of 2025, Charlie Foxtrot has created stub articles for all the stories hosted on SOL.&nbsp; Meanwhile, I have made a page for all the "ZM" stuff including author info and story info at [[Zen Master]].&nbsp; All the metadata for each story will have to wait.&nbsp; There is a template for new story articles at [[Sample Story Article]]. -ZM
* '''All authors''' - Every writer who has published a Swarm Cycle story should have his own page.&nbsp; It should, at the very least, list all stories he/she has published, as well as a link to where it can be read or downloaded.&nbsp; If the story has been removed from the publication site (Silly Artie and Just Jack are good examples) this should be noted.&nbsp; This need is taken care of by the [[Library]].&nbsp; In many cases, we have both the 'author' article and the 'story' articles, but they are empty shells; they have absolutely no information about either one beyond their names.&nbsp; It would be nice if someone with nothing better to do could add info about author and stories.&nbsp; I've set up a combined [[Zen_Master|Zen Master and ZM Synopses]] article as an example to see how that idea works.&nbsp; On 4/30/24 I created several pages for authors who can't speak for themselves: Artie, JJ, Just Jack, Robert Auld, Tomken.
* '''All colonies''' - Every colony should have its own page.&nbsp; These would be great places for the various writers to tell other writers about 'their' colony and surrounding system.&nbsp; A script can create these and populate them with basic information pulled from the "ColonyList" page, but in many cases there really isn't anything there so there's no point in creating empty pages.&nbsp; Best to simply leave them on the "ColonyList" page until we have more detail to put in the dedicated pages.
<br>


&nbsp;&nbsp; We still have three big groups of 'needed pages':
=== Pages We DON'T Need ===
* All stories - Every Swarm Cycle story should have its own page, filled with all the metadata that Sgt Stoner was working on.&nbsp; This is an automated task better left to someone who deals with scripts better than I do.&nbsp; Meanwhile, I have made a page for all the "ZM" stuff including author info and story info at [[Zen Master]] and Charlie Foxtrot has created stub articles for all the stories hosted on SOL.&nbsp; All the metadata will have to wait. -ZM
* Duplicate lists of anything.&nbsp; If you have added info for a group of articles, add that info to those articles.&nbsp; Don't make new articles about the same things.
* All authors - Every writer who has published a Swarm Cycle story should have his own page.&nbsp; It should, at the very least, list all stories he/she has published, as well as a link to where it can be read or downloaded.&nbsp; If the story has been removed from the publication site (Silly Artie and Just Jack are good examples) this should be noted.&nbsp; This need is taken care of by the [[Library]].&nbsp; I don't see why we often have separate pages about an author and about their stories.&nbsp; I've set up a combined [[Zen_Master|Zen Master and ZM Synopses]] article as an example to see how it works.&nbsp; On 4/30/24 I created several pages for authors who can't speak for themselves: Artie, JJ, Just Jack, Robert Auld, Tomken.&nbsp; Still need: Lordshipmayhem, Zaffen, etc.
* The 'old' Confederacy stuff, their capital and the guard and the first fleet and all, should all be on one page.&nbsp; Or thrown out, it's heresy and spam.&nbsp; They don't have a military: no guard, no fleet.
* All colonies - Every colony should have its own page.&nbsp; These would be great places for the various writers to tell other writers about 'their' colony and surrounding system.&nbsp; A script can create these and populate them with basic information pulled from the "ColonyList" page, but in many cases there really isn't anything there so there's no point in creating empty pages.&nbsp; Best to simply leave them on the "ColonyList" page until we have more detail to put in the dedicated pages.
<br>


=== Helpful "Special Pages" ===
=== Helpful "Special Pages" ===
&nbsp;&nbsp; The Wiki software gives us several management tools.&amp;nbsp; Some pages are simply lists of problems. <br>
&nbsp;&nbsp; The Wiki software gives us several management tools.&amp;nbsp; Some pages are simply lists of problems.&nbsp; They can all be found off: [[Special:SpecialPages]]. <br>
&nbsp;&nbsp; Any broken redirects, where a page is redirected somewhere else but that new page doesn't exist, are listed here: [[http://swarm.freewiki.in/index.php/Special:BrokenRedirects]]. <br>
&nbsp;&nbsp; Any broken links, places where a link was made but it doesn't work, are listed here: [[http://swarm.freewiki.in/index.php/Special:Wantedpages]].&nbsp; The wiki software politely refers to them as 'wanted pages'.&nbsp; Many of them are simple typos but many more are actual pages we should have. <br>
<br>
<br>


=== Backups and Redirects ===
=== Backups and Redirects ===
&nbsp;&nbsp; Anyone can make an .XML text "backup" of the wiki:&nbsp; The wiki software has a built-in function at [[Special:Export]] for this, but it's awkward.&nbsp; The function is set up to "export" a particular page to a local file, but you can feed it a list, one entry per line, of all the pages in the wiki.&nbsp; Before you can do this you have to go to the "All Pages" page and convert that screen-list of all the pages in the wiki to a .txt file with the name of each wiki page on a separate line.&nbsp; Doing that once was a pain in the butt.&nbsp; Doing it every time I do a backup got old fast. <br>
&nbsp;&nbsp; Anyone can make an .XML text "backup" of the wiki:&nbsp; The wiki software has a built-in function at [[Special:Export]] for this, but it's awkward.&nbsp; The function is set up to "export" a particular page to a local file, but you can feed it a list, one entry per line, of all the pages in the wiki.&nbsp; Before you can do this you have to go to the "All Pages" page and convert that screen-list of all the pages in the wiki to a .txt file with the name of each wiki page on a separate line.&nbsp; Doing that once was a pain in the butt.&nbsp; Doing it every time I do a backup got old fast. <br>
&nbsp;&nbsp; Anyone with server admin rights can do a complete database backup in several different ways.&nbsp; The wiki software manual at https://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki has details on several methods.&nbsp; Some of them require all users to be logged out.&nbsp; If the admin forces all users off, any editing being done at that time is lost. <br>
&nbsp;&nbsp; The easy answer to that is to ensure that all articles are members of the Category:All which allows someone to simply select "All" in the category field, click on "Add", and get your complete backup of all articles.&nbsp; Note that this still does not back up the rest of the wike, like the categories, the graphics, etc.&nbsp; That's why we're still trying to make "Wiki Mk3" as good as the "Wiki Mk2" that we lost in 2024. <br>
&nbsp;&nbsp; ZM: Since I'm (as of late April 2024) hosting the wiki now, I can do a complete site backup, including the complete MySQL database.&nbsp; I will periodically do that and put the SQL.gz file in our DropBox account.&nbsp; Supposedly, if anything ever happens to me and my wife stops paying for my hobby hosting stuff, anyone can create a new wiki on the host of their choice, upload the latest SQL.gz file to it, and be back in business.&nbsp; I have no intention of ever actually doing this as a test, but anyone else can if they want. <br>
&nbsp;&nbsp; Anyone with server admin rights can do a complete database backup in several different ways.&nbsp; The wiki software manual at https://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki has details on several methods.&nbsp; All are awkward.&nbsp; Some of them require all users to be logged out.&nbsp; If the admin forces all users off, any editing being done at that time is lost. <br>
&nbsp;&nbsp; ZM: Since I'm (as of late April 2024) hosting the wiki now, I can do a site backup, including the complete MySQL database.&nbsp; I will periodically do that and put the SQL.gz file in our DropBox account.&nbsp; Only issue is that the hosting company limits us to twice a month, no earlier than 15 days after the last one.&nbsp; Supposedly, if anything ever happens to me and my wife stops paying for my hobby hosting stuff, anyone can create a new wiki on the host of their choice, upload the latest SQL.gz file to it, and be back in business.&nbsp; I have no intention of ever actually doing this here as a test, but anyone else can if they want.&nbsp; I'd love to hear how it went. <br>
<br>
<br>


=== Script Management ===
=== Script Management ===
&nbsp;&nbsp; Sgt Stoner wrote a series of scripts that added a lot of functionality and cross-referencing to the wiki.&nbsp; Naturally, the initial run showed several issues that would have been corrected in V2 but he had a computer crash and that effort ground to a halt.&nbsp; One thing his scripts did, for every page containing info on a particular story, was provide a list at the bottom of the page of Swarm-Cycle terms used in that story.&nbsp; This list included links to the page for that term, and in many cases that page does not exist.&nbsp; At one point the "Wanted Pages" list had more broken links (1600+) than we had actual pages in our wiki (~700)- and this was in large part due to links that only existed in these lists of interesting terms. <br>
&nbsp;&nbsp; Sgt. Stoner wrote a series of scripts that added a lot of functionality and cross-referencing to the wiki.&nbsp; Naturally, the initial run showed several issues that would have been corrected in V2 but he had a computer crash and that effort ground to a halt.&nbsp; In the hope that he can get back to that effort someday, here is a list of corrections for V2 of his script system: (This list has been moved to the DropBox "Wiki Maintenance" folder.) <br>
&nbsp;&nbsp; In most cases we should have those pages, but in others we already have them.&nbsp; They just aren't named what he expected.&nbsp; A lot of them are collection pages listing everything known about several examples of a group.&nbsp; As we learn more about those items many of them may get their own pages, but it is senseless to create separate pages for a series of items when we don't know anything to put in those pages.&nbsp; For example, simply redirecting all the bad links in "Ship weapons (Story Usage)" to "Warship Weapons" fixed 80 of them. <br>
&nbsp;&nbsp; While someone could invest the time in manually re-directing all of those links, if those scripts are ever run again the manual corrections would be over-written with the bad links a second time.&nbsp; It would be better fix the scripts, then run them again and have the scripts fix all the errors.&nbsp; In the hope that he can get back to that effort someday, here is a list of corrections for V2 of his script system: (This list has been moved to the DropBox "Wiki Maintenance" folder.) <br>
<br>
<br>


=== Categories ===
=== Secure Pages ===
SGTStoner: Anyone adding pages should put at the bottom <nowiki>[[Category:Needs_Category]]</nowiki> to tip admin staff off that they need sorting. <br>
&nbsp;&nbsp; Several of the wiki's pages seem to be magnets for vandalism.&nbsp; Those pages have been protected; only people listed as management in the wiki host's system can edit them.&nbsp; Naturally, those few people never get around to needed updates.&nbsp; We need more management people. <br>
&nbsp;&nbsp; A category doesn't really exist until it has a member.&nbsp; Also, there must be some text in the description/text box or it isn't created.&nbsp; It appears easiest to add the new category to a member article, then click on the red link to create it. -ZM <br>
<br>
<br>


=== Secure Pages ===
=== How-To Notes ===
&nbsp;&nbsp; Several of the wiki's pages seem to be magnets for vandalism.&nbsp; Those pages have been protected; only people listed as management in the wiki host's system can edit them.&nbsp; Naturally, those few people never get around to needed updates.&nbsp; We need more management people. <br>
* Wiki pages are linked by <nowiki>[[This]]</nowiki> or <nowiki>[[Go here|Show this]]</nowiki>.
* Templates are called by <nowiki>{{This}}</nowiki>.
* Categories are joined by <nowiki>[[Category:This]]</nowiki>.
** Anyone adding pages should put at the bottom <nowiki>[[Category:Needs_Category]]</nowiki> to tip admin staff off that they need sorting.
** A category doesn't really exist until it has a member.&nbsp; Also, there must be some text in the description/text box or it isn't created.&nbsp; It appears easiest to add the new category to a member article, save your changes, and then click on the red link to create it. -ZM
* To see any of these codes (like here on this page) instead of them 'working', you surround the text with < nowiki > Whatever < /nowiki > without the spaces.
* To delete a redirected page, click on it.&nbsp; You get sent to the replacement page, but now when you click on the back-link you go to the original page in "edit" mode.&nbsp; From there, you can delete it.
<br>
<br>


Line 55: Line 80:


[[Category:Wiki Maintenance]] [[Category:Discussion]]
[[Category:Wiki Maintenance]] [[Category:Discussion]]
[[Category:All]]

Latest revision as of 10:34, 31 January 2026

Wiki Maintenance Notes

   This is a discussion and notes page for ZM, Sgt. Stoner, Omachuck, and the others who maintain the Swarm Cycle Wiki.

Article Improvement

   Article Structure: This wiki has three general types of articles, plus some management-type articles that don't fit into any of the three.  Each 'story' article should have the same information about that story as all other story articles have about theirs, organized the same way.  Similarly, each 'author' article should have the same information about that author as all other author articles have about theirs, organized the same way.  All of the 'subject' articles should have the same organization as all the other subject articles.  This principle isn't as important as adding useful information to the wiki, but it should be in the back of each editor's mind as they work.
   Each article should have management template 'tags' at the top.  Examples are 'Temp', 'Stub', and 'Duplicate'.  These should be followed by the article text, and then below that several reference sections at the bottom of the article, in the same order, whenever appropriate.  That way, readers can easily see if more info is available.  Currently, that list of standard sections is:

  • "Story Statistics", for articles on specific Swarm Cycle stories
  • "Story Usage Statistics" for articles on technical terms
  • "Story Quotes" for articles on technical terms
  • "See Also", a list of links to related articles
  • "References", a list of links to information outside this wiki

   We place all the 'Category' tags together at the bottom of the article, since that's where they are seen in a 'live' article.  Sometimes we try to organize them into a coherent order, but we haven't decided what that order should be.  Certainly, the 'Category:All' entry should be on a line by itself, on the very bottom.
   Ongoing Work: There are a lot of articles which are obviously incomplete.  For instance, the Timeline page only shows 88 stories.  As of 12/22/24, SOL has 323 stories listed, and we know of several more that we lost.  Where do the other 235 stories belong on the timeline?
   The "List of Sleep-Trainer Modules" needs adding to, also.  We have 38 general-use, 70 CMC, 74 general CN, 62 Castle-specific, and 18 CS for 260+ total.  There should be many more.  Certainly, if there are 62 for such a small and simple ship as a Castle there should be at least that many more for each class of ship we use.  We list 12 other classes of warship...

   Categories: An article may have a list of 'Categories' at the bottom.  Each category is a property which the article's subject has, and a reader may click on that category to see a list of other articles about that same property.  For instance, the article on Castle is about a particular design or 'class' of ship.  The bottom of the article lists five categories that the Castles are included in: 'Canon', 'Navy', 'Warships', 'Corvettes', and 'All'.  The reader may click on those links to see lists of all articles that have been declared to be canon, or which are about the Confederacy Navy, or which include all Confederacy warships, or which include all corvettes, which is a functional label that means 'small patrol warship'.
   Anyone can edit an article to add other categories.  Popular ones include 'Stubs' which means this article is very short, and 'List of Lists' which is a collection of all of the wiki's varied 'List of <this>' articles.  Of course every article should be a member of the 'All' category.
   Some categories are special-purpose.  The 'All' category includes all articles in the wiki.  The reason for it is to allow any user to make an XML backup of the wiki's pages.  The only reasonable backup method available to users is the 'Export' function, which allows you two options: you can export all pages on a list you provide _or_ you can export all articles in a particular category or list of categories.  The 'All' category allows a user to easily do a backup of all articles simply by selecting Category:All.  As of 1/31/26, all articles in this wiki are members of this category.  All editors are requested to ensure that every new article is added to Category:All, if nothing else, so that we can easily do backups. ZM User (talk) 10:34, 31 January 2026 (PST)

   Templates: A wiki can gain a lot of functionality by enabling templates, but as of mid-2024 they do not work here as they depend upon back-end processing not yet installed.  Sgt. Stoner had taken the time to add a HUGE section on available templates here, but apparently there are enough differences between that wiki and this one with the latest version of WikiMedia that it crashes this copy of the editor every time I add it in.  I still have it as a text file, if we can get any use from it. -ZM

Operation Duplication Elimination

  • If there's only one article listing stories (or authors), we'll never have conflicting updates where different articles say different things.  And, if there's only one article listing stories (or authors), we don't need a category to list all the articles listing stories (or authors). -done 4/30/24 ZM, deleted Category:Story Listings
  • I guess I don't understand the difference between a "listing article" and a "category".  Exactly what added value do we get by having both
    • a "Corvette" article which describes the class of ship and lists all known designs, and
    • a "Corvette" category which describes the class of ship and lists all known designs?

  From where I sit, the two do the same thing.  Duplication in a critical warship system is good, as it improves your chance of surviving damage.  Duplication in a 600-article hobby wiki is stupid and leads to confusion when one is updated and the other is not.  One or the other is going. -ZM

  • Similarly, there is an article Characters and a category which do the same thing, which is to list assorted characters.  One or the other should go.


Pages Still Needed

   As I go through the "Wanted Pages" list of bad links I'm finding several places we _should_ have an article, but we don't yet.  I'm 'fixing' the bad link by replacing the double-brackets with triple-apostrophes.  Of course, in one instance Heaven we don't really need that page.  It's just an example of how to use links.  I should probably list the individual pages we need here as I find them: Dreadnaught, Artillery...

   Anyone logged in can edit existing pages or even create new ones.  We have several articles to help with this.  Sample Article has an outline of the way info articles are organized in this wiki.  The Wiki Editing Guidelines has advice on how to make your article look good and be helpful.  The Wiki Test Page has a 'sandbox' section where you can try out different formatting codes and see how they look.

   We still have three big groups of 'needed pages':

  • All stories - Every Swarm Cycle story should have its own page, filled with all the metadata that Sgt Stoner was working on.  This is an automated task better left to someone who deals with scripts better than I do.  As of 2025, Charlie Foxtrot has created stub articles for all the stories hosted on SOL.  Meanwhile, I have made a page for all the "ZM" stuff including author info and story info at Zen Master.  All the metadata for each story will have to wait.  There is a template for new story articles at Sample Story Article. -ZM
  • All authors - Every writer who has published a Swarm Cycle story should have his own page.  It should, at the very least, list all stories he/she has published, as well as a link to where it can be read or downloaded.  If the story has been removed from the publication site (Silly Artie and Just Jack are good examples) this should be noted.  This need is taken care of by the Library.  In many cases, we have both the 'author' article and the 'story' articles, but they are empty shells; they have absolutely no information about either one beyond their names.  It would be nice if someone with nothing better to do could add info about author and stories.  I've set up a combined Zen Master and ZM Synopses article as an example to see how that idea works.  On 4/30/24 I created several pages for authors who can't speak for themselves: Artie, JJ, Just Jack, Robert Auld, Tomken.
  • All colonies - Every colony should have its own page.  These would be great places for the various writers to tell other writers about 'their' colony and surrounding system.  A script can create these and populate them with basic information pulled from the "ColonyList" page, but in many cases there really isn't anything there so there's no point in creating empty pages.  Best to simply leave them on the "ColonyList" page until we have more detail to put in the dedicated pages.


Pages We DON'T Need

  • Duplicate lists of anything.  If you have added info for a group of articles, add that info to those articles.  Don't make new articles about the same things.
  • The 'old' Confederacy stuff, their capital and the guard and the first fleet and all, should all be on one page.  Or thrown out, it's heresy and spam.  They don't have a military: no guard, no fleet.


Helpful "Special Pages"

   The Wiki software gives us several management tools.&nbsp; Some pages are simply lists of problems.  They can all be found off: Special:SpecialPages.

Backups and Redirects

   Anyone can make an .XML text "backup" of the wiki:  The wiki software has a built-in function at Special:Export for this, but it's awkward.  The function is set up to "export" a particular page to a local file, but you can feed it a list, one entry per line, of all the pages in the wiki.  Before you can do this you have to go to the "All Pages" page and convert that screen-list of all the pages in the wiki to a .txt file with the name of each wiki page on a separate line.  Doing that once was a pain in the butt.  Doing it every time I do a backup got old fast.
   The easy answer to that is to ensure that all articles are members of the Category:All which allows someone to simply select "All" in the category field, click on "Add", and get your complete backup of all articles.  Note that this still does not back up the rest of the wike, like the categories, the graphics, etc.  That's why we're still trying to make "Wiki Mk3" as good as the "Wiki Mk2" that we lost in 2024.
   Anyone with server admin rights can do a complete database backup in several different ways.  The wiki software manual at https://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki has details on several methods.  All are awkward.  Some of them require all users to be logged out.  If the admin forces all users off, any editing being done at that time is lost.
   ZM: Since I'm (as of late April 2024) hosting the wiki now, I can do a site backup, including the complete MySQL database.  I will periodically do that and put the SQL.gz file in our DropBox account.  Only issue is that the hosting company limits us to twice a month, no earlier than 15 days after the last one.  Supposedly, if anything ever happens to me and my wife stops paying for my hobby hosting stuff, anyone can create a new wiki on the host of their choice, upload the latest SQL.gz file to it, and be back in business.  I have no intention of ever actually doing this here as a test, but anyone else can if they want.  I'd love to hear how it went.

Script Management

   Sgt. Stoner wrote a series of scripts that added a lot of functionality and cross-referencing to the wiki.  Naturally, the initial run showed several issues that would have been corrected in V2 but he had a computer crash and that effort ground to a halt.  In the hope that he can get back to that effort someday, here is a list of corrections for V2 of his script system: (This list has been moved to the DropBox "Wiki Maintenance" folder.)

Secure Pages

   Several of the wiki's pages seem to be magnets for vandalism.  Those pages have been protected; only people listed as management in the wiki host's system can edit them.  Naturally, those few people never get around to needed updates.  We need more management people.

How-To Notes

  • Wiki pages are linked by [[This]] or [[Go here|Show this]].
  • Templates are called by {{This}}.
  • Categories are joined by [[Category:This]].
    • Anyone adding pages should put at the bottom [[Category:Needs_Category]] to tip admin staff off that they need sorting.
    • A category doesn't really exist until it has a member.  Also, there must be some text in the description/text box or it isn't created.  It appears easiest to add the new category to a member article, save your changes, and then click on the red link to create it. -ZM
  • To see any of these codes (like here on this page) instead of them 'working', you surround the text with < nowiki > Whatever < /nowiki > without the spaces.
  • To delete a redirected page, click on it.  You get sent to the replacement page, but now when you click on the back-link you go to the original page in "edit" mode.  From there, you can delete it.




(Someday this will be a navigation template.  It will provide a bar across the bottom of each article with useful navigation links.  Until then, this is just a placeholder to get rid of all the red "broken link" indicators. -ZM User (talk) 10:00, 3 May 2024 (PDT))