Difference between revisions of "Understanding the CLIO Content Folder"

From CLIO

 
(5 intermediate revisions by the same user not shown)
Line 4: Line 4:
All of the data needed to operate the kiosk is stored locally on the kiosk in the web server’s directory.  The ‘content’ folder is located at the root directory of the CLIO web application.    
All of the data needed to operate the kiosk is stored locally on the kiosk in the web server’s directory.  The ‘content’ folder is located at the root directory of the CLIO web application.    


Each time the CLIO web application is loaded, it will retrieve a list of folders contained within this directory.  Each folder represents the unique identification name CLIO will use to refer to that Program.  For example, the "Getting Started" Program is stored within the "Default" folder and "Default" is the unique name that CLIO uses to refer to this Program in URLs and program functions.  An example description URL would be:   
Each time the CLIO web application is loaded, it will retrieve a list of folders contained within this directory.  Each folder represents the unique identification name CLIO will use to refer to that Program.  We highly recommend avoiding spaces in this name.  For example, the "Getting Started" Program is stored within the "Default" folder and "Default" is the unique name that CLIO uses to refer to this Program in URLs and program functions.  An example URL for the "Getting Started" program would be:   


<code>https://cliomuseums.org/clio/exhibit/?program=Default&activity=types</code>  
<code>https://cliomuseums.org/clio/exhibit/?program=Default&activity=types</code>  


Each Program folder contains a '''@Configuration.json''<nowiki/>' file containing descriptive metadata about this Program, such as it's friendly name or description.  CLIO will retrieve this information about each Program and use it to populate the Program setting menu.  This allows the Program to be changed on-the-fly though the Facilitator Mode interface, as well as descriptive URLs.  
Each Program folder contains an '''@About.json''<nowiki/>' file containing descriptive metadata about this Program, such as it's friendly name or description.  CLIO will retrieve this information about each Program and use it to populate the Program option in the Settings menu.  This allows the Program to be changed on-the-fly though the Facilitator Mode interface, as well as through descriptive URLs.
 
{{See|Understanding the CLIO URL Scheme}}


== Sample Programs ==
== Sample Programs ==

Latest revision as of 13:40, 15 December 2022

Google material book.png
Add a photo.png

Overview

All of the data needed to operate the kiosk is stored locally on the kiosk in the web server’s directory.  The ‘content’ folder is located at the root directory of the CLIO web application. 

Each time the CLIO web application is loaded, it will retrieve a list of folders contained within this directory. Each folder represents the unique identification name CLIO will use to refer to that Program. We highly recommend avoiding spaces in this name. For example, the "Getting Started" Program is stored within the "Default" folder and "Default" is the unique name that CLIO uses to refer to this Program in URLs and program functions. An example URL for the "Getting Started" program would be:

https://cliomuseums.org/clio/exhibit/?program=Default&activity=types

Each Program folder contains an '@About.json' file containing descriptive metadata about this Program, such as it's friendly name or description. CLIO will retrieve this information about each Program and use it to populate the Program option in the Settings menu.  This allows the Program to be changed on-the-fly though the Facilitator Mode interface, as well as through descriptive URLs.


Sample Programs

We include sample Programs in the CLIO toolkit based on previous projects:

  • Getting Started (Default): designed to help you get a better understanding of the toolkit using the different activity types.  
  • Example Activities (Examples): designed to show the different ways activities can be configured.
  • Habitable Worlds (HabitableWorlds): reinterpretation of the Roger Williams Natural History Museums exhibit.
  • Nature's Networks (NaturesNetworks): designed as a pop-up exhibit for the Burke Museum's BurkeMobile program.
  • Bird Diversity (NICOBirdDiversity): designed as a part of a remote lesson plan for the Slater Museum of Natural History.
  • Tooth Sleuth (NICOToothSleuth): designed as a part of a remote lesson plan for the Slater Museum of Natural History.
  • Evergreen (Evergreen): designed for use on kiosks around the Evergreen State College's Indigenous Arts Campus.
Documentation
Installation Look and Feel
Interaction Modes Developing Activity Types
Creating an Interactive Framework
Integrating CLIO Contribute