User blog:S3r0-Ph1i/Bureaucrat Nomination

Hi! So this message is being written since I feel I would be a good bureaucrat to serve the wiki. Since this is also an example of a nomination idea in light of the Pathway to User Rights document that was made as detailed here, it also provides an example of what may be a good nomination should others wish to elect themselves or others for any of the user rights available. So:

First, I’m not in this to be bureaucrat for personal glory, the account and the good that it can do for the wiki and the Seraph of the End series is all that counts. I understand it is not my wiki, I have never thought that, and would not want it to be. It’s everyone’s wiki, all are welcome to and should take part. Where user rights are not really best had for the sake of having them, it’s whether they can be exercised to be of benefit. At this point in time there is a benefit to a second bureaucrat being active.

At any point, having two bureaucrats helps with balance on a wiki. Additionally as the Pathway to User Rights document elaborates on, bureaucrats are long-term users who have helped the site in various capacities. I would like to be the second active bureaucrat. As past experiences show, in case one is not on for unforeseen future scenarios, there’s at least a backup to continue helping the site and providing a balanced view for future appointments. In the event a bureaucrat moves on, it is better that another one can remain rather than the wiki be adopted by a user who may not fully familiar with what works best for the site. There are technical, social, and wiki cohesion areas in mind as well.

How I Can Help
Technically speaking, the bureaucrat title is helpful in the area of making bots admins, such as Ph1i5-B0t, or others an admin for specific tasks. In one case of a wiki merge, Special:Import and Special:Export needed to be accessed by a bot who could use admin rights. For efficiency purposes, the more users who can help with this, the better. Instead of me placing a request on someone to add or remove rights to a bot, the bureaucrat role I have could allow me to do that myself to save time. Ph1i5-B0t can directly help with mass categorizing images such as from the chapters they are a part of. A user with the means to do this makes for a good bureaucrat where specific wiki expertise is concerned.

For user areas, as it happens, very generally speaking, bureaucrats are seen as those who can help others. If users see the bureaucrat title and think that is someone who can help, I’m already doing it. Answering questions in Discussions seems to have helped others who had points about the series and wiki. It is also in Discussions where categorising posts has kept them appropriately classified, with the relevant categories added that is beneficial. Fans and those with questions can have clarification, the series itself is supported by sharing news of the latest chapter via Announcements. Perhaps that makes for an additional good front for the wiki. It is a matter of viewpoint, do you prefer to see a bureaucrat who sets the wiki on fire (there's all kinds of behaviour on other wikis), or one who is helpful for the wiki, and those taking part on it?

In empowering others I’ve helped more than one user gain the secret badges that few know about, let alone attain. Helping them with providing page titles also significantly expands the wiki, and it is a quintessential collaboration is key exercise planned and carried out which is always so lovely! While it is all established, coding help can be provided. At the same time I’m very fond of encouraging others to develop areas as they see fit. It’s good to be guiding, but also good to know when to say to others that they have a good idea and this is their area to develop. That way it’s not me, for instance ruling with an iron fist that can stifle ingenuity, rather it is a firm community effort that allows others to develop at their own pace. Supporting others is paramount, yet taking the initiative oneself is also important, so both are done!

Being able to provide long-term commitment is handy. Where other wikis are inactive, not just among users, but with little to no editing, I can develop both areas. With what I have contributed, and with the capability to take part more, it very much seems like something to capitalize on. As well as using my existing admin tools to develop the site, it is my editing that may place me in good stead to become a bureaucrat. In addition to long-term assistance, it also seems sizeable contributions are helpful. The following is mentioned as I see in part that becoming the second bureaucrat comes from the sustained maintenance tasks of the wiki in general, and from sizeable contributions added. These both match the above and beyond criteria the bureaucrat role requests. Additionally, these show I represent the site well, another feature the role entails for what my bureaucrat position would be.

Maintenance
While the bureaucrat role does not directly assist with this area, as with the points above, it's very much a case of supporting the site overall. Knowing what works well for the wiki is certainly good conduct for a bureaucrat, so I have my examples of how this is done. Specific examples of how activities help the wiki, and how such behaviour is good for someone with user rights to show:

Discussions Assistance
As well as answering questions for what others would like to discuss, and taking part with adding posts myself, I also assist with classifying what is added. Helping to place posts into the right classification, such as polls can help others find the right areas to read and comment further on what they like (plus all the polls to take part in!) Additionally, categories can be added to posts, such as with the related ones concerning the chapter, manga it is from, and the characters viewable in the post. That ensures categories are organized, where everything pertaining to them, like with the Owari no Seraph manga, can be viewed.

Clearing
An area in progress, but a system of checking what needs to be removed should an item be marked for deletion has its benefits. Earlier history is prioritized for images for example. Images that were uploaded can be kept and later duplicates would be the ones removed, with a link placed in the deletion summary so it can be understood why an image is not required. Should an image be marked for deletion, it is ensured that galleries are checked where an image may potentially be added. Nothing is deleted for the sake of it, if it's beneficial for the page the note for deletion can be removed and it can be added there.

For articles, again deletion is not the way, rather Special:MergeHistory can be used. This remarkable MergeHistory addition that came with a MediaWiki update allowed for two different pages to be combined. Where Yoichi has his own article, there was also another similar named one created, which was then left for some time. When the anime articles were being made, rather than begin from that date, and delete this earlier page, it still concerned Yoichi and so the two pages were merged for the keeper article of Yoichi's experiences from the anime. Saves deleting, and secures contributor history, which is double good!

Mobile Main Page
Helping to update the mobile main page helps with accessing content on portable devices, and updates appear in Discussions, such as when a latest chapter is released for example. Featured content are major areas such as the story by chapter, anime, manga, and so forth.

Renaming
It is a practice to have legible titles for images for example. Renaming a random numbers and letter title to the character and where they are from works well. Further, this new title would replace the prior one in source mode on every page the image appears on. That way the source code matches the image name, and there's no need for redirects from the initial random numbers and letters title to its new name.

Wiki Merge
There was a separate wiki detailing the Seraph of the End Bloody Blades game. Where Fandom was going through a process of deleting wikis with little to no activity or views, rather than a wiki with hundreds of pages being lost, I helped establish the process of merging that wiki onto this singular wiki which covers everything. Importing articles was done to avoid the content being lost. It was a separate process in transferring images. Working with others, we could succeed in this group area transfer, and integrate the Bloody Blades Wiki here. That way instead of the many fantastic Bloody Blades cards and details being erased (which would make information even more scarce as the game has been retired) on a wiki to be deleted, they were secured here for all to enjoy further. Additionally, instead of users' hard work being lost on that wiki, all their contributions were secure too. I made sure to use the Special:Import and Special:Export wiki tools rather than copy and paste content so as not to invalidate the article history that others had formed. Where everything could at worse have vanished, or been transferred but without credit being given to users who constructed such great articles, it seems a best case scenario was attained, in essentially adding that wiki onto here as it was.

Notable Contributions
Where sustained maintenance over time is helpful, as well as knowing how to navigate a scenario that is not come across everyday to gain the only right outcome as with the wiki merge, I believe it's good to also show sizeable contributions to the most important area of all, namely building and developing the articles that make up the wiki. The secret Pounce! badge shows I've created one hundred pages, yet that milestone pales compared to the great many more articles I have founded. Directly, even more pages have been added where the badge process wasn't used. Indirectly, I've added even further ones since I've provided page titles to others to also help them attain the badge. Others may make the page since it helps them towards the badge, I add prepared details afterwards, it works to support users and the wiki. For other large scale projects, my nomination features:

Proof-reading and Refinement
I reformed main character pages such as this one (it would be easier to open the previous one in a new window to see the additions), which also helped ensure pages were character specific. For instance if there was point of view information concerning Shinoa on Yu's page, that was transferred, so that Yu's perspective was focused on solely for his article. Likewise, Shinoa had everything on her article that concerned her experiences. Amendments also ensures the major pages of the wiki were more reader friendly.

Rather than have one long list of quotes all in one area on a page, key ones are now transferred to be amongst the text. This helps to break up large blocks of text, and provide summarizing examples of major events pertaining to the area in question. Along with images, it is a third means of displaying information as well so articles are visually nicer (as appealing as columns of text and nothing else are!)

Story By Chapter Articles
Where other wikis simply do not have them, I formed the manga story by chapter page:


 * Owari no Seraph Manga Story by Chapter

So everyone may view what happens across the current 100+ chapters. There is a set amount of text to be an effective overview, that is also not too large for mobile views. The links to the chapters themselves is where the complete in-depth details may be found to support those pages as well. This was also done for the prequel manga:


 * Catastrophe at Sixteen Manga Story by Chapter

Of which further developments for the individual chapter pages are also planned. These resources document major events at a glance, and are a reminder of what chapter concerns which scenario. Notable insights such as which chapter feature images are colored are also easily identifiable.

Anime Articles for Characters
The largest development undertook to date was creating:


 * Anime pages for characters

To document their experiences across all the episodes they appeared in. Where there was one article per character, yet differences between the manga and anime, it could have been written on one page: "Narumi vanquishes the vampire noble with his trident (in the anime it is Yu that delivers the final shot on Lucal Wesker)" or "Sayuri fights by deploying multiple spell tags (in the anime she uses a sword consisting of combined spell tags)", however by having a manga and anime page, everything including all the fine points of differences could be catalogued as they happen. Additionally, both manga and anime images could be used to illustrate each respective article to ensure the wiki's impressive collection of images can be displayed to a greater extent.

The undertaking of documenting a select amount of characters and their experiences across the twenty four anime episodes was then commenced. Where multiple pages were being prepared all at once, with information from the anime detailed, what characters did, with anime images showing them doing it, then cataloging their quotes to show the contrast with their quotes in the manga, the anime content allowed for quite the amount of detail:


 * +217,649 for Yu's anime page

Read me: For the record don’t actually make massive edits like that in one go, let alone across 20+ pages, since others could experience computer crashes, some users have mentioned their computer physically melting in areas due to overheating. Where many pages can be open for writing, with anime episodes running, where laptops are kept on, with the lid closed and opened, over time due to the high amount of heating and cooling with everything active, they can become warped where they don't close properly. But they can close properly once the parts have cracked where the laptop can come apart. Anyway, then for large edits being added to a page, where proof-reading, adding images and positioning them amongst the text, there is the possibility of editing conflicts, to losing everything if one is not writing the information on a document or something. Other unlikely scenarios have a low chance of occurring, yet they can all still happen, but I know what I’m doing though so it’s fine.

Chapter Pages
More current developments are documenting what happens in each chapter. For the latest chapter, chapter 114, overview information of the entire chapter, and the characters within is helpful for at a glance information near the start. The Summary comprehensively details what occurs in this part of the story, with references to display where in the chapter this scenario may be viewed, and of course because it's documenting official information. Where I have committed to detailing the chapter pages, the additions introduced are gathering quotes on the article page. Documenting the actual source material on the chapter page is helpful, same as how images are all collected together in one place on their own galleries. Quotes there can then also be shared to individual character and relationship pages where appropriate, with the descriptive text altered so it is distinct.

The chapter notes section has also been renewed, which allows for observations to be noted. Where the upper article text concerns official information, an analysis of sorts afterwards can also help with understanding what transpired, and with connecting the chapter to wider events raised in previous releases. Collectively, the characters seen, everything that happens in the chapter, to quotes, and points summarizing what has occurred, it is all together in one area. Where a Seraph of the End chapter itself is artwork and speech to be enjoyed first and foremost, the wiki chapter article has its additional value in not having to search through many pages, it is all together in one place. The manner of writing can highlight what may have been overlooked in the chapter, in short they can foster a greater understanding of events.

Character Articles
Then character experiences are also detailed on each respective character page, such as with Saito for chapter 114. Each character's experiences from their point of view, and quotes as well helps show what they are doing at every point they appear throughout many separate chapters of story. Prepared for future scenarios since they have already been carried out, story sections can be transferred to their own page should the article overall become too long. It is both an activity to expand the wiki, and help other user collaborations that can be assisted with.

Relationships Pages
Where they were not as developed as they could have been, relationships articles have been expanded upon. Again, a before and after view for this page may display the amendments better, where proof-reading, arranging the relationships in order of prominence, and content additions are beneficial. Documenting how characters know and interact with one another is a specialized way of sharing informative details that can otherwise be missed in an overall account of events as on a chapter page. Images, both manga and anime ones can be used to illustrate areas on relationships pages where appropriate to show the characters, and is another means of making use of the great amount of images on the wiki.

Minor Characters
An area of expansion for the wiki was not overlooking that minor characters who appear in the series can be detailed. Where some wikis could hold the view that characters who appear once to not be seen again are too minor to detail, and so do not warrant a page, another view is taken. Nothing is too small to detail, and if it exists in Seraph of the End, it is to be documented. Characters who appear, however briefly, are still indicative of the world the series takes place in, and factor into interactions that concern more notable characters. Ultimately, they exist so are detailed. Very much a case of why dismiss something as insignificant or not worth it, when it is better to document it on an all covering encyclopedia.

Summary
The wiki is in a very good place, which is not something to take for granted. Where user activity can negatively impact other wikis, it is not the case here. Yet why settle for something great when it could be greater. Expanding the pool of bureaucrats to a better more sustainable number of two is in keeping with capitalising on what works well, then taking it further in a good way. Nothing is to be rectified, everything works well so it's not about returning something to a good standard, it's about raising it. I'm committed to ensuring these glory times can shine even brighter.

From everything discussed, those are the sizeable areas of editing related developments that have taken place. Examples of helping in other capacities such as wiki maintenance, also has its benefits for the wiki. Assisting other users in projects are excellent collaboration is key areas, then helping in various respects in Discussions also seems to be useful. If the bureaucrat role is involved with finalizing user rights, someone who knows what makes for constructive behaviour specialized for what works on the wiki makes sense. Similarly, a user who is representing the wiki well by answering questions, to helping in Discussions does come across as a good point of contact for the wiki. Yet that is for everyone else to decide!