\documentclass[10pt]{article}

\usepackage{fullpage}
\usepackage{setspace}
\usepackage{parskip}
\usepackage{titlesec}
\usepackage[section]{placeins}
\usepackage{xcolor}
\usepackage{breakcites}
\usepackage{lineno}
\usepackage{hyphenat}





\PassOptionsToPackage{hyphens}{url}
\usepackage[colorlinks = true,
            linkcolor = blue,
            urlcolor  = blue,
            citecolor = blue,
            anchorcolor = blue]{hyperref}
\usepackage{etoolbox}
\makeatletter
\patchcmd\@combinedblfloats{\box\@outputbox}{\unvbox\@outputbox}{}{%
  \errmessage{\noexpand\@combinedblfloats could not be patched}%
}%
\makeatother


\usepackage{natbib}




\renewenvironment{abstract}
  {{\bfseries\noindent{\abstractname}\par\nobreak}\footnotesize}
  {\bigskip}

\titlespacing{\section}{0pt}{*3}{*1}
\titlespacing{\subsection}{0pt}{*2}{*0.5}
\titlespacing{\subsubsection}{0pt}{*1.5}{0pt}


\usepackage{authblk}


\usepackage{graphicx}
\usepackage[space]{grffile}
\usepackage{latexsym}
\usepackage{textcomp}
\usepackage{longtable}
\usepackage{tabulary}
\usepackage{booktabs,array,multirow}
\usepackage{amsfonts,amsmath,amssymb}
\providecommand\citet{\cite}
\providecommand\citep{\cite}
\providecommand\citealt{\cite}
% You can conditionalize code for latexml or normal latex using this.
\newif\iflatexml\latexmlfalse
\providecommand{\tightlist}{\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}%

\AtBeginDocument{\DeclareGraphicsExtensions{.pdf,.PDF,.eps,.EPS,.png,.PNG,.tif,.TIF,.jpg,.JPG,.jpeg,.JPEG}}

\usepackage[utf8]{inputenc}
\usepackage[english]{babel}



\usepackage{float}








\begin{document}

\title{Using a Labwiki for Longevity and Transfer of Knowledge in Undergraduate
Research}



\author[1]{Maria Nagan}%
\affil[1]{Stony Brook University}%


\vspace{-1em}



  
  \date{March 13, 2025}


\begingroup
\let\center\flushleft
\let\endcenter\endflushleft
\maketitle
\endgroup





\selectlanguage{english}
\begin{abstract}
Continuity in research group collective knowledge is critical for
running a successful research program but in an undergraduate research
lab, this can be particularly challenging. A wiki site dedicated to the
research laboratory, a lab wiki, can bridge gaps in student-to-student
knowledge transfer and contribute to longevity of a research program. A
lab wiki is an organized, easily accessible, collaborative resource that
can contain tutorials, group-specific directions, links to resources and
guides to writing papers or proposals. The wiki language is easy for
students to pick up and contributes to their participation in preserving
group knowledge. This tutorial introduces the concept of a lab wiki, the
advantages of it, example content and practical implementation advice.%
\end{abstract}%



\sloppy




\textbf{Introduction}

A subset of faculty choose to design their research programs exclusively
around undergraduate student involvement\textsuperscript{1} and a
research-group specific wiki site can make student-to-student knowledge
transfer more efficient. Undergraduate research has been deemed one of
the high-impact practices,\textsuperscript{2} Through close
faculty-student mentorship, it provides a personal education that trains
students in the art of inquiry and encourages intellectual
independence.\textsuperscript{3-6} Successful undergraduate research
programs abound including the computational chemistry consortium of
faculty known as MERCURY.\textsuperscript{7} Undergraduate research is
challenging for many reasons,\textsuperscript{8-10} and students know
less disciplinary content when they begin research. Oftentimes, a
faculty member must teach a student everything about the research
because students haven't had the prerequisite course work. Sustaining an
undergraduate research program therefore becomes highly dependent on a
steady transfer of knowledge between the faculty member and the students
or amongst students.

One of the largest impediments to maintaining group productivity is
short student research group membership. To lengthen the research
training period, some faculty let students join their research group as
early as freshman year or in a pre-frosh program. In the best of
circumstances, students are in research groups for 4 years plus a summer
before or after college. On the other end of the spectrum, students may
join a research group for an academic year or a summer. In the ideal
scenario, someone in the group besides the principal investigator always
knows a portion of the collective group knowledge to pass on to new
students. In undergraduate research labs, sometimes interests of
incoming students do not overlap with outgoing students or there are few
overlapping students. In addition, students who are knowledgeable might
spend all their time training other students in the lab and not have
adequate time to accomplish their own work. Traditionally gaps in
knowledge transfer have been covered by maintaining a paper repository
of protocols, a lab manual for the group, a series of How-To-PowerPoints
deposited in a communal drive, or theses and supplementary materials of
undergraduate theses.

Collective knowledge can also be maintained with a laboratory wiki, a
wiki website customized for your laboratory. The author's group has had
a laboratory wiki, lab wiki for short, since 2006. It has survived two
institution moves and a rotation of group projects spanning disparate
methods and applications. Over 50 students have contributed to the lab
wiki. At first the lab wiki just contained the group's short list of
tutorials such as a short guide to Unix, Vi text editing, how to submit
jobs to the queue and some data analysis tips. As students gained
expertise in topics, they were asked to write a tutorials or lab wiki
pages on their topic of expertise. Now the lab wiki the central resource
for maintaining and passing on research group knowledge.

\textbf{Advantages, Uses and Users}

The wiki platform allows for collaborative content sharing and editing
for anyone who has access to the site. Users can add content with very
little programming knowledge.\textsuperscript{11} Examples of wiki
language can be learned by going to a public wiki such as Wikipedia,
finding the desired formatting, and mimicking it. Students don't have to
learn a new language such as html, reducing the barrier to
participation. In addition, the lab wiki format is conducive
specifically to computational research because command-line syntax or
code for short programs are autoformatted in a separate gray box by just
putting a space before each line of text. The ease of writing a wiki
page makes it possible for novice students to contribute to the group
knowledge. The lab wiki also includes edit histories for each page.
Student mistakes can be backed out; nothing is permanent and mistakes
can be easily fixed. Because MediaWiki is mainstream open software,
updates with operating system are made by a third party. The broader
wiki community also continually develops extensions. It is a searchable,
collective project.

Wikis have been used in a variety of educational
contexts.\textsuperscript{12-15} Here, the lab wiki is both an
educational tool and a repository of research group knowledge. It can
contain tutorial materials for certain research steps, background for
computational theory/methods, guides for using specific programs, group
scripts, weblinks to key resources as well as introductions to basic
science and specific projects. These are all items that graduate
students might be expected to find themselves after being referred to a
few recent papers. Undergraduate students need more guidance and a lab
wiki provides an intuitive interface with structure. Others also use a
lab wiki as a repository of group documents. These might be group
meeting presentations, proposals or theses. As students are ready to
learn a soft skill such as a proposal, these documents serve as
examples. New students can also become oriented to the project by
reading the introduction of a thesis or group meeting presentation.
Repositories on a lab wiki do require disk space considerations on the
server and some flags need to be customized (see Practical
Implementation).

A research lab wiki serves a number of different groups. The faculty
member and new undergraduate students who join the lab have an organized
repository for research group collective knowledge. New students find
the lab wiki accessible and easy to navigate. As students progress in a
project, they have access to group collective knowledge through the lab
wiki. More advanced students involved in creating the wiki sites are
also actively engaged in constructing group
knowledge.\textsuperscript{13} Pedagogically, undergraduate students
gain confidence from writing the tutorials because they are held up as
experts on a topic and the process additionally serves as a vehicle to
reinforce knowledge. The lab wiki can similarly be shared with other
faculty or colleagues who aren't familiar with the logistics of a
particular technique and its contents are already organized.

A lab wiki can be password protected. This way only those with a
username and password can edit the site or read the site. Individual
standard users can be created but that can make management cumbersome.
Some labs choose to create different access levels. For instance, one
group username can be created for all group members with edit
capabilities. Or novice members, transient members or classroom students
could receive a username with read-only access. Password protection
gives the research group optional privacy for sensitive information such
as group meeting presentations and proposals but still encourages
collaboration.

\textbf{Creating Lab Wiki Content}

Content creation becomes a community effort with a lab wiki and should
be managed. On the author's lab wiki, all undergraduate research
students have edit capabilities. If there is uncertainty in material,
students are advised to add content rather than delete content. However,
the principal investigator ultimately serves as the editor. In the
unlikely event that an erroneous entry is created, and the previous
version of the page should be restored, lab wiki page edit histories are
saved. For each lab wiki page, select the histories tab. By choosing the
previous version, the previous page is restored. In this way, management
is minimal, students feel freedom to contribute and disasters are
correctable.

The Main Page of the lab wiki is a table of contents to the site. This
is the first page that a user encounters. It can be made into an
organized list (Figure 1). After four headers are made, the header
titles are automatically made into a list. Each blue item under Contents
is a Topic Heading. Contents can be organized by general topic much like
chapters in a book. Under each Topic Heading is a set of wiki pages. The
introductory material for new students may come first, followed by more
project-specific information, specialized methods and guides for
creating dissemination materials such as papers or posters.

The lab wiki can serve as a transfer knowledge mechanism from a faculty
member to a student, where parts of the lab wiki are referred to in an
in-person meeting. For example, the lab wiki can contain sets of
directions commonly given such as a checklist for new group members,
beginner basic science information and resources as well as links to key
project articles. The Checklist for New Members (Figure 2) is a list of
tasks such as attending fire safety training, obtaining keys and who to
talk to about obtaining accounts on various machines. In addition, all
new members have beginning tasks and software they must learn before
they can be productive. These are listed and directions for the
assignments are given on the lab wiki. Additional resources are listed
in the assignments.

The lab wiki also contains tutorials, resources and descriptions in
small tractable portions that undergraduate students can digest at their
own pace. For instance, the Intro to Computers section (Figure 3)
started out with information on common commands in Unix and Vi Text
Editor. However, as the group grew, students began to have conceptual
issues about working remotely and where their files could be found.
Tutorials describing a file path, remotely logging into a computer and
how to transfer files between computers were created. Some of this can
commonly be found on the internet or through books but the advantage of
the lab wiki is that it can be customized with lab-specific information,
such as the research group's directory structure or the addresses of
specific computers.

Individual research steps can also be easily explained in a lab wiki
format. If a student is going to go through a common process, the lab
wiki can have a page for each step of the process. For example, if an
undergraduate needed to build an explicit water system in the software
Amber, the steps in Building Systems (Figure 4) would be followed. Most
of these beginning tutorials were written by the faculty member but as
students worked through the steps, modifications to the wiki page were
made by undergraduate students.

Preservation of research group knowledge is a significant advantage of
the lab wiki. Analysis methods and scripts are often created for a
specific project. Through a tutorial on the lab wiki, analysis types can
be preserved. For instance, a student in the group might develop inputs
for monitoring water residence lifetimes in a particular system. Then if
that student graduates and another project needs similar analysis, there
is no student-student transfer of knowledge. A thesis, which may have a
general description of the analysis philosophy, may not have detailed
inputs and scripts used to create the end result. A lab wiki tutorial
explaining the analysis philosophy but also giving step-by-step
instructions might be more productive.

The lab wiki can also be used as a repository with examples of student
theses, presentations and posters. By seeing examples, students are able
to see what is acceptable and also variation in quality. These can be
used a templates for future students. The lab wiki also organizes
sometimes haphazard student files into a coherent, accessible list. If
organized by project, a poster would much easier to find in a wiki page
list than in each student's user space.

There might also be a proposal writing section on the lab wiki. In this
section, there might be a guide to writing proposals or directions for a
specific call for proposals. For example, if there is a local on-campus
call for summer research proposals, there might be guidelines and
examples of successful proposals. Sometimes departments teach a
writing-enhanced course in which the students write proposals. A link to
NSF or NIH proposal guidelines could be made, but for undergraduate
students a guide with explicit page lengths and descriptions of each
section are more useful. Externally funded proposals from the faculty
member could also be posted in this section. Oftentimes, students find
these useful when trying to get oriented to a project and to see the
future directions of the project.

\textbf{Practical Implementation}

Making a lab wiki requires wiki software and usually a database. The
author's lab wiki site is hosted locally. To host your own website,
Apache HTTP software installed on a Mac mini or Linux machine is a
common method. To easily point lab members to a website, a domain name
should also be purchased or obtained from the Information Technology
(IT) department. The author uses MediaWiki\textsuperscript{16} and MySQL
database,\textsuperscript{17} both of which are freeware. Nowadays,
there are many options for wiki software, supported by different
database types\textsuperscript{18,19} with even LaTeX compatibility.
Besides MediaWiki, common free wiki software is also available through
TikiWiki\textsuperscript{20} and DokuWiki\textsuperscript{21}, which
doesn't require a database. Some companies will host your wiki for a
monthly fee, such as SiteGround, TMD hosting, A2 hosting, cloudways and
greengeeks. As well, Learning Management Software such as Blackboard and
Moodle have wiki creation tools. A class centered on research would need
to be created and then propagated every semester. These wikis are not as
versatile as one managed on your own, but it also requires less
administrative knowledge. Syntax and formatting examples given here are
specific to MediaWiki and analogous options are available through other
wiki software.

In MediaWiki, the LocalSettings.php file contains the configuration
settings for the wiki site, including how it interacts with the
internet. To set up your wiki, customize variables such as the
\$wgSitename and database settings.

\begin{quote}
\#\# Set the ScriptPath to where people should go to find your wiki
(https://your\_website/labwiki) \$wgSitename =
''Set\_to\_Name\_of\_Wiki''; \$wgScriptPath = ''/labwiki''; \#\# The
protocol and server name to use in fully-qualified URLs \$wgServer =
''https://set\_to\_your\_website\_address''; \#\# Database settings
\$wgDBtype = ''mysql''; \$wgDBserver = ''localhost''; \$wgDBname =
''dbname\_here''; \$wgDBuser = ''admin''; \$wgDBpassword =
''set\_to\_admin\_password\_for\_database'';
\end{quote}

To make the wiki password protected, edit the \$wgGroupPermissions.
Different groups can be created with different permissions. For example,
the wikireader group has read-only access but the research group can
make new pages and edit material. After a username is made, it can be
assigned to a preexisting group, logged in as an administrator, under
Special Pages and User Rights Management.

\begin{quote}
\#// Block everyone from creating an account, including reading and
editing \$wgGroupPermissions{[}'*'{]}{[}'createaccount'{]} = false;
\$wgGroupPermissions{[}'*'{]}{[}'edit'{]} = false;
\$wgGroupPermissions{[}'*'{]}{[}'read'{]} = false; \#// Read-only
accounts \$wgGroupPermissions{[}'wikireader' {]}{[}'move'{]} = true;
\$wgGroupPermissions{[}'wikireader' {]}{[}'read'{]} = true;
\$wgGroupPermissions{[}'wikireader' {]}{[}'edit'{]} = false;
\$wgGroupPermissions{[}'wikireader' {]}{[}'createpage'{]} = false;
\$wgGroupPermissions{[}'wikireader' {]}{[}'createtalk'{]} = false;
\$wgGroupPermissions{[}'wikireader' {]}{[}'upload'{]} = false;
\$wgGroupPermissions{[}'wikireader' {]}{[}'reupload'{]} = false;
\$wgGroupPermissions{[}'wikireader' {]}{[}'reupload-shared'{]} = false;
\$wgGroupPermissions{[}'wikireader' {]}{[}'minoredit'{]} = false; \#//
Editing accounts \#\#\$wgGroupPermissions{[}'research' {]}{[}'move'{]} =
true; \#\#\$wgGroupPermissions{[}'research' {]}{[}'read'{]} = true;
\#\#\$wgGroupPermissions{[}'research' {]}{[}'edit'{]} = true;
\#\$wgGroupPermissions{[}'research' {]}{[}'createpage'{]} = true;
\#\$wgGroupPermissions{[}'research' {]}{[}'createtalk'{]} = true;
\#\$wgGroupPermissions{[}'research' {]}{[}'upload'{]} = true;
\#\$wgGroupPermissions{[}'research' {]}{[}'reupload'{]} = true;
\#\$wgGroupPermissions{[}'research' {]}{[}'reupload-shared'{]} = true;
\#\$wgGroupPermissions{[}'research' {]}{[}'minoredit'{]} = true;
\end{quote}

To make a new Topic Heading use the syntax of putting two equal signs on
both sides of the header. To make a new wiki page under each topic,
place double brackets around the title of each new page. A `*' inserts a
bullet point and to nest a bullet point under another one, use `**'. The
syntax below is used to making the Main Page Contents (Figure 1).

\begin{quote}
==\textless{}big\textgreater{}'''Welcome to the Nagan Lab
Wiki'''\textless{}/big\textgreater{}== This is the Nagan group's lab
wiki. It contains information to carry out Dr. Nagan's computational
research. All Nagan group members can view/add content to the lab wiki.
If you need an account, email Dr. Nagan (maria.nagan@stonybrook.edu).
==New Nagan Group Member Assignments== *{[}{[}Checklist for New Nagan
Group Members{]}{]} *{[}{[}Download a PDB from the PDB Databank and
Learn VMD{]}{]} *{[}{[}Learn vi and Unix{]}{]} ==Intro to Computers== *
{[}{[}Unix{]}{]} * {[}{[}Vi Text Editor{]}{]} * {[}{[}File Path{]}{]} *
{[}{[}Working from Home - ssh{]}{]} ==Introduction to Biomolecules== *
{[}{[}Central Dogma of Molecular Biology{]}{]} * {[}{[}Nucleic Acid
Structure{]}{]} ** {[}{[}2D and 3D RNA Structure{]}{]} ** {[}{[}RNA
Structure Parameters{]}{]} * {[}{[}Amino Acids and Protein
Structure{]}{]} * {[}{[}RNA Recognition{]}{]} ==Visualization==
*{[}{[}VMD{]}{]} *{[}{[}Chimera{]}{]}
\end{quote}

Numbered lists can also be made by using a ``\#'' instead of a ``*'' in
the example above. To edit the newly created pages, select the new page
and choose to edit the page. Basic formatting such as bold and italics
can be found in the GUI formatting bar in edit mode (Figure 5). There
are also tools to insert internal links or new pages, external links,
new topics, pictures and media.

Both links to internal pages on the lab wiki and external links to
websites are useful tools to direct readers to more information. To
insert a link to an internal page, put double brackets around the page
name. If the page name is piped to a set of words, then insert a
``\textbar{}'' between the lab wiki page name and the words to display.
Surround the whole internal link with double brackets.

\begin{quote}
==Additional Help== *For more information about the specifics of the pdb
file, see {[}{[}pdb file\textbar{} What is a pdb file?{]}{]} *For a
tutorial on how to use VMD, see {[}{[}VMD{]}{]}.
\end{quote}

Linking to an external page requires placement of single brackets around
the web page address. By default, the web address link becomes a number.
If the actual web address should be displayed or link text, then include
a space between the link and the link text.

\begin{quote}
==Manuals== The most current Amber manual can be found at
{[}https://ambermd.org https://ambermd.org{]}
\end{quote}

Files can be uploaded to the wiki and then referred to in links;
although the types of files extensions may need to be expanded. The
allowed filetypes can be customized to include for example word
processing files, image files, presentation files and spreadsheets.
ImageMagick\textsuperscript{22} is common freeware that can edit images
but also make thumbnails for the wiki. To turn it on, set the variable
to \$wgUseImageMagick = true and set the \$wgImageMagickConvertCommand
to the correct path.

\begin{quote}
\#\# To enable image uploads, make sure the 'uploads' directory \#\# is
writable, then set this to true: \$wgUploadPath =
''\$wgScriptPath/uploads''; \$wgUploadDirectory = ''\$IP/uploads'';
\$wgEnableUploads = true; \$wgUseImageMagick = true;
\$wgImageMagickConvertCommand = ''/usr/bin/convert''; \#Override the
default with a bundle of filetypes: \$wgFileExtensions = array( 'png',
'gif', 'jpg', 'jpeg', 'ogg', 'zip', 'tar', 'gz', 'doc', 'ppt', 'txt',
'csh', 'xls', 'pdf', 'pdb', 'xyz', 'top', 'crd', 'frcmod', 'lib', 'scr',
'perl', 'awk', 'in', 'out', 'com', 'xlsx', 'docx', 'pptx', 'ai', 'psd'
);
\end{quote}

The maximum file size limit may also need to be increased beyond the 500
KB default and enough disk space on the web hosting machine should be
ensured. To change the maximum file size, edit /etc/php.ini and change
the upload\_max\_filesize value to the desired value. Then restart
apache.

Links to images, media and files can be accomplished through the word
image, file or media followed by a colon and the name of the uploaded
file. Media displays a link to the actual file name. For images,
formatting options such as centering or resizing specifications can be
incorporated after a ``\textbar{}'', all surrounded by double brackets.

\begin{quote}
The Amber19 Tools Manual: {[}{[}media:Amber19\_and\_Tools.pdf{]}{]}
{[}{[}image:dna\_rna.jpeg\textbar{}center{]}{]}
\end{quote}

Wiki management capabilities can be found under Special Pages. Here,
user accounts can be created, blocked and assigned to groups. As well,
there is a list of all pages and maintenance reports. Pages with broken
links and uploaded file lists can also be seen here.

\textbf{Challenges}

There are a few challenges of keeping up your own lab wiki site. After
setup, the largest barrier to lab wiki success is upkeep of the content.
If protocols change, then the tutorials need to be updated. This author
encourages everyone in the group to constantly update the wiki, but the
majority of the upkeep falls on the principal investigator. As students
work through tutorials or follow directions, students find errors in the
wiki pages or find better ways to accomplish the same task. At group
meeting, if a student finds an error, a shortcut or a preferred syntax,
small edits are encouraged within the week. About a month before the end
of the semester, students who have mastered a particular task, are asked
write a tutorial or update a tutorial. This is part of their
end-of-semester product. It is also difficult to delete users because
MediaWiki associates users with wiki contributions. One solution is to
block a user, which renders the user read-only access. The other option
is to merge the username into another username; this action also
transfers the page contributions. Because MediaWiki is commonly used,
there are often solutions posted online. If one chooses to maintain a
local webserver and wiki site, security is always a concern. If a wiki
site needs to be moved to another server, it does take effort. Both the
wiki site (tar the folder of the wiki) and the database should be backed
up and then be reconfigured for the new webserver.

\textbf{Conclusion}

Lab wikis are tools in preserving group research knowledge, that are
particularly helpful to success of an undergraduate research lab. A lab
wiki can contain tutorials and links to resources, explained in a
step-wise fashion amenable to undergraduate students. Customized,
specific directions can be incorporated, that ease the barrier to
learning the technology. The wiki format is easy for students to master,
increasing their ability to contribute collaboratively to group
knowledge. As well, the lab wiki can serve as a repository for previous
student works and faculty proposals. In the lab wiki format, it is an
organized list, rather than files buried in inaccessible folders.
Complicated methods can also be enumerated easily in detail on lab wiki.
When there are discontinuities in student-to-student knowledge transfer,
a lab wiki can fill the gap.

\textbf{References}

1. Karukstis, K. K. \emph{Scholarship and Practice of Undergraduate
Research} \textbf{2020,} \emph{3,} 46.

2. Kuh, G. D. High-Impact Educational Practices: What They Are, Who Has
Access to Them, and Why They Matter; \emph{Association of American
Colleges and Universities} , \textbf{2008.}

3. Elgren, T.; Hensel, N. \emph{Peer Review} \textbf{2006,} \emph{8,} 4.

4. Kinzie, J.; Husic, D. \emph{Peer Review} \textbf{2010,} \emph{12} .

5. Linn, M. C.; Palmer, E.; Baranger, A.; Gerard, E.; Stone,
E.\emph{Science} \textbf{2015,} \emph{347,} 1261757.

6. Lopatto, D. CBE Life Sci Educ \textbf{2007,} \emph{6,} 297.

7. Shields, G. C. Scholarship and Practice of Undergraduate
Research\textbf{2020,} \emph{3,} 5.

8. \emph{Best Practices for Supporting and Expanding Undergraduate
Research in Chemistry} ; American Chemical Society, \textbf{2018.}

9. Malachowski, M. R.; Dwyer, T. J. \emph{CUR Quarterly}
\textbf{2011,}\emph{32,} 23.

10. Wenderholm, E. ACM \emph{SIGCSE Bulletin} \textbf{2004,}
\emph{36,}73.

11. Leuf, B.; Cunningham, W. \emph{The Wiki way: Quick collaboration on
the web} ; Addison Wesley: Upper Saddle River, NJ, \textbf{2001.}

12. Altanopoulou, P.; Tselios, N.; Katsanos, C.; Georgoutsou, M.;
Panagiotaki, M. A. \emph{Educ. Technol. Soc.} \textbf{2015,}
\emph{18,}511.

13. Boulos, M. N.; Maramba, I.; Wheeler, S. \emph{BMC Med.
Educ.}\textbf{2006,} \emph{6,} 41.

14. Cole, M. \emph{Computers \& Education} \textbf{2009,} \emph{52,}141.

15. Parker, K. R.; Chao, J. T. \emph{Interdisciplinary Journal of
Knowledge and Learning Objects} \textbf{2007,} \emph{3,} 57.

16. MediaWiki, 2019, https://www.mediawiki.org/wiki/Download, (accessed:
February 2020)

17. MySQL, 2020, https://dev.mysql.com/downloads/mysql/, (accessed:
February 2020).

18. https://en.wikipedia.org/wiki/List\_of\_wiki\_software, (accessed:
January 2020).

19. https://en.wikipedia.org/wiki/Comparison\_of\_wiki\_software,
(accessed:

20. TikiWiki, http://tikiwiki.org (accessed: March 2020).

21. DokuWiki, http://dokuwiki.org/dokuwiki (accessed: March 2020).

22. Lemstra, D.; McConville, E. \emph{ImageMagick} , 2020,
https://imagemagick.org.



\textbf{Figure Legends}

Figure 1. Example Main Page of the author's lab wiki.

Figure 2. New Nagan Group Member Assignments

Figure 3. Intro to Computers

Figure 4. Building Systems

Figure 5. GUI formatting bar in edit mode.\selectlanguage{english}
\begin{figure}[H]
\begin{center}
\includegraphics[width=0.70\columnwidth]{figures/image1/image1}

\end{center}
\end{figure}

Nagan, Figure 1\selectlanguage{english}
\begin{figure}[H]
\begin{center}
\includegraphics[width=0.70\columnwidth]{figures/image2/image2}

\end{center}
\end{figure}

Nagan, Figure 2\selectlanguage{english}
\begin{figure}[H]
\begin{center}
\includegraphics[width=0.70\columnwidth]{figures/image3/image3}

\end{center}
\end{figure}

Nagan, Figure 3\selectlanguage{english}
\begin{figure}[H]
\begin{center}
\includegraphics[width=0.70\columnwidth]{figures/image4/image4}

\end{center}
\end{figure}

Nagan, Figure 4\selectlanguage{english}
\begin{figure}[H]
\begin{center}
\includegraphics[width=0.70\columnwidth]{figures/image5/image5}

\end{center}
\end{figure}

Nagan, Figure 5

\selectlanguage{english}
\FloatBarrier
\end{document}

