North Forge:Using this wiki: Difference between revisions

Latest revision as of 10:44, 2024 October 15

You have to have an account to edit this wiki. To get an account, contact anyone with admin rights to set one up. Adding users to the admin group should be approved by member council.

If you have ideas on how to improve the wiki, for the most part just do it. Edits that break functionality may be reverted or fixed; editors should communicate when that is necessary.

Mediawiki

https://workingwithmediawiki.com is an excellent resource for new and experienced wiki users.

Structure

for all	Tina The wiki structure content is outdated. Ttenbergen (talk) 00:34, 2024 October 14 (CDT)

For now the wiki has structured data for Tools, Rooms, Training Sessions, Trainers, PCs, Software and Discussions about content . If you think other things should be added, add them.

We initially discussed structured data at https://docs.google.com/drawings/d/16E_dQl49fSxUUn56r9HlNHrkBPIoHwUPkqT33hlPAwM/edit, this is not fully what has been implemented.

some stuff I started experimenting with

Template:Hazard / Breathing hazard / Template:Hazard type
North Forge:Broken
North Forge:Maintenance
Training
- How much of that do we want on here? Do we want the trainers? Do we want to use this as a trainee record? What would our privacy thoughts be on that part? At least a training outline would be good, that way future trainers will know what is covered during the course and trainers/trainees can make sure the trainer has covered everything.
Mediawiki extension Lockdown - This can be used to make parts of the wiki not overtly public, but think of it more like someone would have to stand on their toes to peek in than true privacy, wikis are not meant for that.
Test tool has some other things, such as Instructions:Test tool linked in, and a sub page Test tool/SWP.

for all	Additional file formats: I know what a wiki is supposed to do WRT documentation but can we also upload files like instruction manual PDFs so that for tools that don't have any training or documentation that there's still a user manual they can consult, even if the contents of the PDF aren't searchable by the wiki? There's a space for a link to the manual but every few months/years there seems to be a shakeout/reorg at some company and products go from "supported" to "archived" or are dropped entirely and the link no longer works. Thoughts? Mpatryluk (talk) 01:03, 2024 September 7 (CDT) I am worried that by allowing .doc and .pdf file formats we will end up with content uploaded that should be integrated. I was trying to preempt that fight by keeping those turned off. You make a good point about link rot. Simply uploading someone else's .pdf file holds copyright questions, too. Might need further discussion. Ttenbergen (talk) 22:07, 2024 September 7 (CDT)

Extensions etc

This wiki uses Mediawiki extension Cargo to encode structured data so it can be updated automatically on lists via queries. Feel free to add additional structured data. Chat with Tina if you would like to learn more.

It also uses Mediawiki extension PageForms to make the "edit with form" happen.

It also uses the Citizen skin. For now anyway, it has some bugs I don't like. I have also worked with the Chameleon skin, or we could revert to the mediawiki standard vector skin, or any other skin we want to try.

@@ Line 2: / Line 2: @@
 If you have ideas on how to improve the wiki, for the most part just do it. Edits that break functionality may be reverted or fixed; editors should communicate when that is necessary.
+== Mediawiki ==
+https://workingwithmediawiki.com is an excellent resource for new and experienced wiki users.
 == Structure ==
+{{Discuss | Tina
+The wiki structure content is outdated. [[User:Ttenbergen|Ttenbergen]] ([[User talk:Ttenbergen|talk]]) 00:34, 2024 October 14 (CDT)
+}}
 For now the wiki has structured data for [[Tools]], [[Rooms]], [[Training Sessions]], [[Trainers]], [[PCs]], [[Software]] and [[Questions|Discussions]] about content . If you think other things should be added, add them.
@@ Line 10: / Line 16: @@
 == some stuff I started experimenting with ==
 * [[Template:Hazard]] / [[Breathing hazard]] / [[Template:Hazard type]]
-* [[Broken]] / [[Template:Broken]] / [[Broken:0845025035]] A different namespace that can be edited without login; template only stores the broken info and it would be shown on the tool via query. I shelved this when I realized we needed to think further through how we would possibly transition to this, and that this might be better as a second or later step.
+* [[North Forge:Broken]]
-* [[Maintenance]] / [[Template:Maintenance log]] - I am not sure Jeff would be up for this. I would have to come up with a very-low-overhead solution. And we would still need to understand how it would be used and how it would work. The idea was to track both needed and performed maintenance in this, for both ad-hoc/break and regular maintenance. What tools take up a lot of our time?
+* [[North Forge:Maintenance]]
-{{discuss |
-*How do you keep track of what needs maintenance and when you do it now? Anything that can be run through OCR? [[User:Mpatryluk|Mpatryluk]] ([[User talk:Mpatryluk|talk]]) 01:08, 2024 September 7 (CDT)
-**I have some outlook tasks, Jeff has many things in his head. A lot of the maintenance is by looking at it and saying, yup, looks like it needs it. Break-fixes generally come from Slack broken. Jeff tracks tasks completed as part of some timekeeping app that can export data but it is pretty much non-structured. I track some tasks completed in outlook as part of scheduling the next round. [[User:Ttenbergen|Ttenbergen]] ([[User talk:Ttenbergen|talk]]) 22:05, 2024 September 7 (CDT)
-}}
 * [[Training]]
 ** How much of that do we want on here? Do we want the trainers? Do we want to use this as a trainee record? What would our privacy thoughts be on that part? At least a training outline would be good, that way future trainers will know what is covered during the course and trainers/trainees can make sure the trainer has covered everything.