<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://classes.engineering.wustl.edu/cse256a/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Caitlin.Kelleher</id>
	<title>CSE256A Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://classes.engineering.wustl.edu/cse256a/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Caitlin.Kelleher"/>
	<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Special:Contributions/Caitlin.Kelleher"/>
	<updated>2026-11-18T08:52:03Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.34.4</generator>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Information_Foraging_Studio&amp;diff=295</id>
		<title>Information Foraging Studio</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Information_Foraging_Studio&amp;diff=295"/>
		<updated>2025-09-03T19:06:15Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=THIS IS OUT OF DATE, USE CANVAS VERSION FOR CSE 2506=&lt;br /&gt;
&lt;br /&gt;
After completing this studio, you should have the basic technical skills necessary to complete the Information Foraging Project. &lt;br /&gt;
Note that you can successfully complete this project simply by rearranging information within HTML. However, some students have wanted to make changes to the visual design and interactive behaviors of the site. So, this studio gives you a taste of how to do all of these things. By the end, you should hopefully be comfortable making changes to the nursery school site and have an idea about how to implement the changes you envision.&lt;br /&gt;
&lt;br /&gt;
=General model=&lt;br /&gt;
For those who have never done any web programming before, we'll end up touching three kinds of files:&lt;br /&gt;
* Html contains static information and its' organization (*.HTML)&lt;br /&gt;
* Css allows you to set the visual properties and control how different website elements look (*.CSS)&lt;br /&gt;
* JavaScript enables your site to have interactivity and respond to what users do (*.js)&lt;br /&gt;
&lt;br /&gt;
=Running the Nursery School Site=&lt;br /&gt;
# Open a terminal window or the terminal in your code editor.&lt;br /&gt;
# Navigate to your repository folder. This should be something like: information-foraging-&amp;lt;YOUR_GITHUB_ID&amp;gt;.&lt;br /&gt;
# Start a local webserver by typing in (from your repository directory):&lt;br /&gt;
&amp;lt;pre&amp;gt;npm run dev&amp;lt;/pre&amp;gt;. The nursery school site should be opened for you in a web browser.&lt;br /&gt;
&lt;br /&gt;
=Finding Content in HTML=&lt;br /&gt;
[[File:ComeVisitStart.jpg|border|right|300px]]&lt;br /&gt;
Today's web browsers provide developer tools that can be handy in finding things you want to modify in the nursery school site. For purposes of this studio, we'll assume you are using Chrome. We're going to start by changing the &amp;quot;Visit Our School&amp;quot; call to action in the center of index.HTML. In some cases, you can just search for text in the page within VSCode. In other cases, you may need to navigate around more in the HTML structure. For this, the developer tools can be extremely helpful.&lt;br /&gt;
&lt;br /&gt;
[[File:OpenDeveloperTools.jpg|border|right|300px]]&lt;br /&gt;
'''Opening the Developer Tools: '''First, we'll open the developer tools. From the three dots menu all the way on the top right, choose &amp;quot;More tools&amp;quot; and then &amp;quot;Developer tools.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
[[File:DeveloperToolsRight.jpg|border|right|300px]]&lt;br /&gt;
'''A Quick Tour of the Element Pane:'''Now, you should see a panel open on the right hand side. The elements area of the developer tools shows the structure of the HTML document open in Chrome. Using the element pane, you can look at the structure of the information in the document. In HTML, different types of information are enclosed in tags. For example, a link looks like this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;a class=&amp;quot;site-title&amp;quot; href=&amp;quot;/information-foraging/files/index.HTML&amp;quot;&amp;gt;Nursery School&amp;lt;/a&amp;gt; &amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*The '''&amp;lt;a&amp;gt;''' and '''&amp;lt;/a&amp;gt;''' define the beginning and end of the link information. &lt;br /&gt;
*Inside the '''&amp;lt;a&amp;gt;''' tag, there are some properties defined: the address to link to (href) and a class that can link to CSS formatting instructions.&lt;br /&gt;
*Between '''&amp;lt;a&amp;gt;''' and '''&amp;lt;/a&amp;gt;''', we see the link text that appears on the page: Nursery School&lt;br /&gt;
&lt;br /&gt;
If you want to find a specific item on the page there are two ways to do so:&lt;br /&gt;
# You can hover over elements in the element pane, and they will get highlighted in the page. Note that HTML is hierarchical, so you may need to tunnel into child elements to find what you need.&lt;br /&gt;
# You can also right click on the element you want to find and choose '''Inspect''' from the pop-up menu.&lt;br /&gt;
&lt;br /&gt;
'''Task: ''' Use the developer tools to find the visit call to action. &lt;br /&gt;
&lt;br /&gt;
'''Question: ''' What is the opening HTML tag for the entire gray region?  Note: this should be something like: &amp;lt;tagType propertyName=&amp;quot;propertyValue&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Changing Menu Names=&lt;br /&gt;
Some of the HTML elements are replicated in a number of pages. To enable you to make changes to them in a single place, they are dynamically loaded for you. But, you'll have to find them in a different location than the rest of your HTML files. Here is a quick run down for how to use them [[Modular HTML Components]].&lt;br /&gt;
&lt;br /&gt;
'''Task: '''Inspect the menu item &amp;quot;Parent Resources&amp;quot; and take a look at it's ancestors.&lt;br /&gt;
&lt;br /&gt;
'''Question: ''' What is the ts-load element that it descends from?&lt;br /&gt;
&lt;br /&gt;
When you find a ts-load element, that means it is one of the special dynamically loaded ones. The data name property gives you the name of the HTML file to go looking for. However, you need to find it in 'scripts/ts/dynamic-dom/html.&lt;br /&gt;
&lt;br /&gt;
'''Task: '''Change the menu item &amp;quot;Parent Resources&amp;quot; to &amp;quot;Recommended Reading&amp;quot;. When you save the file, your local version should automatically refresh and you should be able to see your new text.&lt;br /&gt;
&lt;br /&gt;
'''Question: ''' What does the html for the menu header look like now?&lt;br /&gt;
&lt;br /&gt;
=Finding and Modifying CSS Properties=&lt;br /&gt;
When you select an HTML element in the Elements pane, you can see its relevant CSS styling information in the pane immediately below. Note that these can also be hierarchical, so the Styles scrollpane shows you all of the relevant CSS for the selected element. Many of the names are self-explanatory, but searching for &amp;quot;&amp;lt;HTML TagName&amp;gt; &amp;lt;propertyName&amp;gt;&amp;quot; is a good way to find documentation and examples. So, for example, a search for &amp;quot;p line-height&amp;quot; explains that it's basically a way to change the line spacing, specified in pixels.&lt;br /&gt;
&lt;br /&gt;
Sometimes, the properties currently used in CSS won't do what you want. You can also look up how which properties are available for a given HTML element. Searching for &amp;quot;&amp;lt;HTML TagName&amp;gt; properties&amp;quot; like &amp;quot;p properties&amp;quot; can help you determine what kinds of styling options are available.&lt;br /&gt;
&lt;br /&gt;
'''Troubleshooting: ''' Browsers like to cache .CSS files and are often fairly aggressive about not reloading them. So, if you change things and they don't show up when you reload the page, you may need to clear your cache information. On Chrome you can do this from the three dots menu. Select '''More tools''' and then '''Clear browsing data.'''&lt;br /&gt;
&lt;br /&gt;
'''Task: ''' Currently, there's an 80 pixel border around &amp;quot;Visit Our School&amp;quot;, the &amp;quot;Our students...&amp;quot; sentence and the &amp;quot;Contact Us&amp;quot; button. Figure out how to change it to a 60 pixel border. Then, make it so that &amp;quot;Our students...&amp;quot; text has a larger inset from the border (i.e. make the text occupy a narrower space and the gray space to the left and right is larger).  Note: To accomplish this, you will need to change one existing CSS property value and add at least one new one. &lt;br /&gt;
&lt;br /&gt;
'''Question: '''What are the modified CSS specifications needed to accomplish this? (Just the ones for classes you changed.)&lt;br /&gt;
&lt;br /&gt;
=Defining New CSS Properties=&lt;br /&gt;
CSS styles are hierarchical, with more specific formatting rules taking precedence over more general ones. So, for example if a specification for a paragraph element sets a font and font color and then a paragraph element for a specific class sets different values for these things, the specific class's values win for that class. For more details, check out: [https://developer.mozilla.org/en-US/docs/Web/CSS/Specificity Specificity] and [https://developer.mozilla.org/en-US/docs/Web/CSS/Cascade The Cascade].&lt;br /&gt;
&lt;br /&gt;
==An Example Style That Cascaded==&lt;br /&gt;
'''Task: ''' Use the web developer tools to find the HTML element for &amp;quot;Classroom News&amp;quot; and look at it's styling. &lt;br /&gt;
&lt;br /&gt;
'''Question:''' Where is the CSS specification that defines which font is used (e.g. Arial, Times New Roman, etc)? Hint: if you've found the right thing, you should see that the font property is inherited.&lt;br /&gt;
&lt;br /&gt;
==Making a New Style==&lt;br /&gt;
'''Task: ''' Suppose you wanted to make the Classroom News header stand out more. Define a new style specification to make it's font size twice as big as the standard font size. This change should not effect the Announcements header next to it. '''Hint: '''You may need to assign a class to the relevant HTML and define a style for that class.&lt;br /&gt;
&lt;br /&gt;
'''Question:''' What does your CSS code look like?&lt;br /&gt;
&lt;br /&gt;
=JavaScript=&lt;br /&gt;
Sometimes, it's helpful to change the visual properties of something as a user interacts with a page. One example of this is a sticky header. A sticky header does something very simple: it defines two different styles for a given html element. Then it uses a simple listener to figure out when the header isn't visible on the screen. If the header is visible, it uses the normal style with the header on top of the body element. If it isn't, then it uses a different style that displays the header at the top of the screen, even if it is over part of the body element. &lt;br /&gt;
&lt;br /&gt;
'''Task: ''' Follow this tutorial on how to create a sticky tutorial and adapt it to work with the Nursery School site. [https://www.w3schools.com/howto/howto_js_sticky_header.asp Sticky Header Tutorial]&lt;br /&gt;
&lt;br /&gt;
Some hints: You'll need to determine which html element is the header - use the one that shows the menu of navigation options. Then, you'll need to figure out how to make a sticky style that can be used for that element. Finally, you'll need to add the javascript. You can insert it directly in the page. Or, you can make a new js file and instead insert that page.&lt;br /&gt;
&lt;br /&gt;
'''Question: ''' What is the id for the html element associated with the header?&lt;br /&gt;
&lt;br /&gt;
'''Question: ''' What is the css definition for sticky as defined for your header element?&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Cognitive_Load_Theory_Assignment:_Set&amp;diff=294</id>
		<title>Cognitive Load Theory Assignment: Set</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Cognitive_Load_Theory_Assignment:_Set&amp;diff=294"/>
		<updated>2024-12-10T16:34:16Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: /* Rubric */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Teaching Set ==&lt;br /&gt;
In the final short project, we're going to develop a new tutorial system for a card game called [https://en.wikipedia.org/wiki/Set_(card_game) Set]. We'll spend some time in class going over the rules and getting used to it. In your tutorial system, you should explicitly consider how you will incorporate the ideas of intrinsic, extraneous, and germane load in order to help players more quickly get up to speed on playing it.&lt;br /&gt;
&lt;br /&gt;
Specifically, you should break down your tutorial into 2 levels that focus on different skills. Note that your levels do not necessarily have to cover all of the skills that would be useful in playing set. However, they should represent a progression from simple towards more complex. Each level should explicitly consider its use of intrinsic, extraneous, and germane load.&lt;br /&gt;
&lt;br /&gt;
Then, for each of your levels, you should build a UX storyboard that captures the experience from introducing a new skill to mastery of that skill. The following are a good introduction to the idea of storyboarding in the UX space:&lt;br /&gt;
&lt;br /&gt;
*[https://www.nngroup.com/videos/ux-storyboard/ How to Create a UX Storyboard] &lt;br /&gt;
*[https://www.youtube.com/watch?v=GukAT_S8WH8 The Best UX Design Storyboarding Technique (Design Sprint Hack)]&lt;br /&gt;
&lt;br /&gt;
Before designing your final storyboard (phase 3), this project requires both brainstorming and rough prototyping phases (phases 1 and 2).&lt;br /&gt;
&lt;br /&gt;
Phase 1) First, brainstorm and describe 5 skills each for two levels (choose from beginning, intermediate, and advanced SET players).&lt;br /&gt;
&lt;br /&gt;
Phase 2) Then, select one skill from each of your two difficulty levels and roughly sketch out how your level might work. In drawing out your sketches, please follow the process outlined in the second video. Your step 1 should be an introduction to a new skill, and your step 6 should be the demonstration of that new skill. You should clearly identify what the elements are on your screen.&lt;br /&gt;
&lt;br /&gt;
Phase 3) Then, using Google Slides, create a high-fidelity mock-up of the pages in your tutorial system that covers the user story in your rough prototype. I would also recommend getting a little bit more concrete with your examples, since the learning tasks and how they are presented is a key part of this design. For each step in your two levels, you should also explicitly call out the ways in which you are considering intrinsic, extraneous, and germane load.&lt;br /&gt;
&lt;br /&gt;
On the demo day, I'll ask each group to share one of their two levels.&lt;br /&gt;
&lt;br /&gt;
== Rubric ==&lt;br /&gt;
The rubric for this assignment is as follows:&lt;br /&gt;
*  5 skills each for two of beginning, intermediate, and advanced SET players are identified and described. 10 pts (1pt x 5 skills x 2 levels)&lt;br /&gt;
*1 skill from each level is roughly sketched (see storyboarding videos). 20 pts (10pts x 2 levels)&lt;br /&gt;
*Each level includes clear demonstration of the introduction to a new skill, and clear demonstration of that new skill 30 pts (15 pts x 2 levels)&lt;br /&gt;
*Each level explicitly and accurately identifies and manages the sources of the three types of cognitive load. 30 pts (5pts x 2 levels x 3 load types) &lt;br /&gt;
*1 level (and high fidelity mock up) is clearly presented in class. 10 pts&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Cognitive_Load_Theory_Assignment:_Set&amp;diff=293</id>
		<title>Cognitive Load Theory Assignment: Set</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Cognitive_Load_Theory_Assignment:_Set&amp;diff=293"/>
		<updated>2024-12-10T16:31:36Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: /* Rubric */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Teaching Set ==&lt;br /&gt;
In the final short project, we're going to develop a new tutorial system for a card game called [https://en.wikipedia.org/wiki/Set_(card_game) Set]. We'll spend some time in class going over the rules and getting used to it. In your tutorial system, you should explicitly consider how you will incorporate the ideas of intrinsic, extraneous, and germane load in order to help players more quickly get up to speed on playing it.&lt;br /&gt;
&lt;br /&gt;
Specifically, you should break down your tutorial into 2 levels that focus on different skills. Note that your levels do not necessarily have to cover all of the skills that would be useful in playing set. However, they should represent a progression from simple towards more complex. Each level should explicitly consider its use of intrinsic, extraneous, and germane load.&lt;br /&gt;
&lt;br /&gt;
Then, for each of your levels, you should build a UX storyboard that captures the experience from introducing a new skill to mastery of that skill. The following are a good introduction to the idea of storyboarding in the UX space:&lt;br /&gt;
&lt;br /&gt;
*[https://www.nngroup.com/videos/ux-storyboard/ How to Create a UX Storyboard] &lt;br /&gt;
*[https://www.youtube.com/watch?v=GukAT_S8WH8 The Best UX Design Storyboarding Technique (Design Sprint Hack)]&lt;br /&gt;
&lt;br /&gt;
Before designing your final storyboard (phase 3), this project requires both brainstorming and rough prototyping phases (phases 1 and 2).&lt;br /&gt;
&lt;br /&gt;
Phase 1) First, brainstorm and describe 5 skills each for two levels (choose from beginning, intermediate, and advanced SET players).&lt;br /&gt;
&lt;br /&gt;
Phase 2) Then, select one skill from each of your two difficulty levels and roughly sketch out how your level might work. In drawing out your sketches, please follow the process outlined in the second video. Your step 1 should be an introduction to a new skill, and your step 6 should be the demonstration of that new skill. You should clearly identify what the elements are on your screen.&lt;br /&gt;
&lt;br /&gt;
Phase 3) Then, using Google Slides, create a high-fidelity mock-up of the pages in your tutorial system that covers the user story in your rough prototype. I would also recommend getting a little bit more concrete with your examples, since the learning tasks and how they are presented is a key part of this design. For each step in your two levels, you should also explicitly call out the ways in which you are considering intrinsic, extraneous, and germane load.&lt;br /&gt;
&lt;br /&gt;
On the demo day, I'll ask each group to share one of their two levels.&lt;br /&gt;
&lt;br /&gt;
== Rubric ==&lt;br /&gt;
The rubric for this assignment is as follows:&lt;br /&gt;
*  5 skills each for two of beginning, intermediate, and advanced SET players are identified and described. 10 pts (1pt x 5 skills x 2 levels)&lt;br /&gt;
*1 skill from each level is roughly sketched (see storyboarding videos). 20 pts (10pts x 2 levels)&lt;br /&gt;
*Each level includes clear demonstration of the introduction to a new skill, and clear demonstration of that new skill 30 pts (15 pts x 2 levels)&lt;br /&gt;
*Each level explicitly and accurately identifies sources of the three types of cognitive load. 30 pts (5pts x 2 levels x 3 load types) &lt;br /&gt;
*1 level (and high fidelity mock up) is clearly presented in class. 10 pts&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Finishing_Up&amp;diff=292</id>
		<title>Finishing Up</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Finishing_Up&amp;diff=292"/>
		<updated>2024-09-25T02:48:35Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;# They will finish either by stating ‘I’m finished’ or when the timer goes off, whichever comes first.&lt;br /&gt;
# If this is your last task, stop recording. Otherwise, pause.&lt;br /&gt;
# Capture the user data for this task.&lt;br /&gt;
## '''For Information Foraging:''' After your user presses the submit button, open the developer console and you should see the data you need to copy. Be sure to copy from '{ all the way to the closing }' and save a record of this. When you copy it into the submission form, be sure that you have both the opening and closing brace. Double check that the task name corresponds with the task your user just completed.&lt;br /&gt;
## '''For Problem Solving:''' Open the developer console and type &amp;quot;'''JSON.stringify(userData)'''&amp;quot;. This should spit out a record of their activities in the file permissions interface. Be sure to copy from '{ all the way to the closing }' and save a record of this.&lt;br /&gt;
# At this point, ask them if they have any questions or comments. Answer questions. Record the comments to pass back to the relevant group.&lt;br /&gt;
# Thank them for their help.&lt;br /&gt;
# If you are testing again with the same site, refresh the page.&lt;br /&gt;
# If they are willing to do multiple tasks, then go back to Step 0.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Record_Demographics&amp;diff=291</id>
		<title>Record Demographics</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Record_Demographics&amp;diff=291"/>
		<updated>2024-02-21T15:30:54Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The goal in recruiting participants is to get people who do not already have experience with the sites you are working on. As such, '''you cannot do the user testing tasks yourself'''. Most students end up recruiting fellow students they know or looking for people who are killing time somewhere (&amp;quot;While you wait for your coffee, would you like to...&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
Ask potential participants the following questions:&lt;br /&gt;
&lt;br /&gt;
For Information Foraging:&lt;br /&gt;
#Have you ever looked at the Nursery School website?&lt;br /&gt;
#Are you an HCI minor?&lt;br /&gt;
&lt;br /&gt;
For Problem Solving:&lt;br /&gt;
#Have you ever set up detailed permissions for a document that specify actions (read, write, etc) and users? &lt;br /&gt;
## Note: Sharing a google doc or similar with view/edit/comment is not disqualifying.&lt;br /&gt;
#Are you an HCI minor?&lt;br /&gt;
&lt;br /&gt;
'''If participants answer no to both, then you they are appropriate participants.''' Ideally, we want a diverse group of users so try to recruit people with differing backgrounds.&lt;br /&gt;
&lt;br /&gt;
Please also note your participant's major and year (freshman, sophomore, etc).&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=MediaWiki:Sidebar&amp;diff=290</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=MediaWiki:Sidebar&amp;diff=290"/>
		<updated>2024-02-20T15:58:18Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
* navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
*Environment Setup&lt;br /&gt;
**Software_to_Install|Software to Install&lt;br /&gt;
**Node_Setup|Node.js Setup&lt;br /&gt;
**Clone_Your_Repository|Clone Your Repository&lt;br /&gt;
**Running_Sites_Locally|Running Sites Locally&lt;br /&gt;
* Assignments&lt;br /&gt;
** Information_Foraging_Assignment:_Nursery_School|Information Foraging: Nursery School&lt;br /&gt;
** GenderMag_Assignment:_File_Permissions|Problem Solving: File Permissions&lt;br /&gt;
** Cognitive_Load_Theory_Assignment:_Set|Cognitive Load Theory: Set&lt;br /&gt;
*User Testing&lt;br /&gt;
**Preparing_for_a_User_Test|Preparing for a User Test&lt;br /&gt;
**Record_Demographics|Record Demographics&lt;br /&gt;
**User_Instructions|User Instructions&lt;br /&gt;
**Recording_Observations|Recording Observations&lt;br /&gt;
**Finishing_Up|Finishing Up&lt;br /&gt;
**Submission_Mechanics|Submission Mechanics&lt;br /&gt;
&lt;br /&gt;
* SEARCH&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=MediaWiki:Sidebar&amp;diff=289</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=MediaWiki:Sidebar&amp;diff=289"/>
		<updated>2024-02-20T15:56:55Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
* navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
*Environment Setup&lt;br /&gt;
**Software_to_Install|Software to Install&lt;br /&gt;
**Node_Setup|Node.js Setup&lt;br /&gt;
**Clone_Your_Repository|Clone Your Repository&lt;br /&gt;
**Running_Sites_Locally|Running Sites Locally&lt;br /&gt;
* Assignments&lt;br /&gt;
** Information_Foraging_Assignment:_Nursery_School|Information Foraging: Nursery School&lt;br /&gt;
** GenderMag_Assignment:_File_Permissions|GenderMag: File Permissions&lt;br /&gt;
** Cognitive_Load_Theory_Assignment:_Set|Cognitive Load Theory: Set&lt;br /&gt;
*User Testing&lt;br /&gt;
**Preparing_for_a_User_Test|Preparing for a User Test&lt;br /&gt;
**Record_Demographics|Record Demographics&lt;br /&gt;
**User_Instructions|User Instructions&lt;br /&gt;
**Recording_Observations|Recording Observations&lt;br /&gt;
**Finishing_Up|Finishing Up&lt;br /&gt;
**Submission_Mechanics|Submission Mechanics&lt;br /&gt;
&lt;br /&gt;
* SEARCH&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Information_Foraging_Assignment:_Nursery_School&amp;diff=288</id>
		<title>Information Foraging Assignment: Nursery School</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Information_Foraging_Assignment:_Nursery_School&amp;diff=288"/>
		<updated>2024-02-18T18:02:43Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: /* Setting Up Pages */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Task Description=&lt;br /&gt;
Washington University hosts and on-site nursery school for children ages 2.5-5 years old. In this&lt;br /&gt;
project, we are going to work to improve nursery school site visitors’ ability to find relevant&lt;br /&gt;
information using Information Foraging Theory. Information Foraging Theory describes how&lt;br /&gt;
users search for information using different cues.&lt;br /&gt;
&lt;br /&gt;
Specifically, we will study the following scenarios:&lt;br /&gt;
# '''Math:''' You are a parent considering sending your child to Washington University Nursery School. You’ve learned that the curriculum is play-based and you want to know how learning is incorporated into a play-based context. You have some ideas about how language learning might happen, but are less sure about math. Find some examples of how math learning is incorporated at Washington University Nursery School.&lt;br /&gt;
# '''School Day: '''  You are investigating pre-school options for your 4 year old. Both you and your spouse work, so you need to fully understand what scheduling constraints each option involves. One of your schools of interest is the Washington University Nursery School. When does school start and end each day? What is the longest period of time that your child can be there?&lt;br /&gt;
# '''Teacher Tenure: ''' You are investigating pre-school options for your 3.5 year old. You’ve been told that one of the hallmarks of a good program is teachers who have been there for a long time. You want your child to attend in the mornings only. Which teachers would your child have and how long have they been at the school?&lt;br /&gt;
# '''Summer Camp: ''' You are starting to look at summer camp options and have heard good things about Washington University Nursery School for young children. What are the daily camp hours? Are there any extended day opportunities?&lt;br /&gt;
# '''Discipline: ''' You are investigating pre-school options for your spirited 3 year old and want to understand their approach to discipline. How do teachers at Washington University approach discipline?&lt;br /&gt;
# '''Spanish Song: '''  Your daughter is in the Teddy Bear class at Washington University Nursery School. She came home this week singing a song in Spanish about shapes, but you are pretty sure that she has some of the words wrong. What are the correct lyrics?&lt;br /&gt;
#'''Books: ''' It is mid-December, 2020 and you are thinking about things to do over your daughter's upcoming school break. She is 3 years old and attends the Washington University Nursery School and is in the Teddy Bear classroom. You are planning a trip to the library and want to check out some books that connect with something she is doing in school. What are some potential book topics that relate to something that is going on in her classroom this week?&lt;br /&gt;
#'''Admission-2: ''' You are a parent with a child who has just been accepted to attend as a full time student at the Washington University Nursery School. You want to accept the offer of admission. Figure out what you need to do at this time to finalize your child’s place at the school.&lt;br /&gt;
#'''Deposit: ''' You are a parent with a child who has just been accepted to attend as a full time student at the Washington University Nursery School. You need to pay one month of tuition as a deposit. Find out how much one month of tuition is and whether or not it is possible to pay online.&lt;br /&gt;
#'''Personalized Help: '''You are moving to St. Louis from Beijing and looking for a Pre-K program for your daughter, age 5. She is very close to her friends and you are worried that the move might be hard on her. She may need some extra support from her new teachers learning English, adapting to American culture, and making new friends. How does the Washington University Nursery School staff approach providing extra help to students who need it? (note: answer is the curriculum overview where it talks about how to provide extra help for individual students)&lt;br /&gt;
#'''Communication: '''You are looking at Nursery Schools for your soon to be 3 year old. He has never been in school or daycare before and you are somewhat worried about the transition. You'd like to ensure that you'll be able to have strong communication at his new school. How does the Washington University Nursery School handle communicating with parents? (note: answer is in the parent handbook under communication)&lt;br /&gt;
#'''Science: '''It’s mid-December and your son, age 4, came home all excited about science class. They learned a new word, but he can’t actually remember the word they learned about. What was the topic of his recent science class?&lt;br /&gt;
#'''Parent/Teacher Conferences: '''You are selecting a pre-school, but want to be sure that your daughter will be ready for kindergarten when it’s time. How does the nursery school assess children’s knowledge, support their growth, and share the results with parents?&lt;br /&gt;
#'''Orientation: '''You have recently accepted a position for your child for the coming school year at the Washington University Nursery School. Up to this point, your child has been at home and you are somewhat worried about the transition. How does the nursery school support kids’ transitions into school?&lt;br /&gt;
&lt;br /&gt;
=Grading=&lt;br /&gt;
For each project, you will get assigned three tasks to test for that round. For the first round, these will be randomly chosen. For subsequent rounds, we will carry two of your previous tasks forward. You can submit up to three versions (see deadlines on the calendar). For each task, we'll assign a score that captures the degree to which participants completed it correctly (got the right answer) and efficiently (took the fastest path to get there). To get credit for a task, you need to outperform the baseline score by 20% for that task. Overall project grades will be:&lt;br /&gt;
* 93: 3 tasks that perform &amp;gt;20% over the baseline, spread across any iteration.&lt;br /&gt;
* 88: 2 tasks that perform &amp;gt;20% over the baseline, spread across any iteration.&lt;br /&gt;
* 83: 1 task that performs &amp;gt;20% over the baseline, in any iteration.&lt;br /&gt;
&lt;br /&gt;
Then you can earn bonus points as follows:&lt;br /&gt;
&lt;br /&gt;
* +7: all three tasks in a single iteration (Note: only your largest multi-task bonus will count)&lt;br /&gt;
* +3: two tasks in a single iteration (Note: only your largest multi-task bonus will count)&lt;br /&gt;
* +2: one of the top 3 performing tasks in the class (Note: you can earn this bonus for multiple tasks)&lt;br /&gt;
&lt;br /&gt;
=Prerequisite Readings=&lt;br /&gt;
The goal of this assignment is use the ideas of information foraging to improve users' abilities to find information on the Washington University Nursery School site. As you work on your redesign you should be thinking about the information search process and trying to restructure and reorganize the information such that users can navigate it more easily.&lt;br /&gt;
&lt;br /&gt;
# [http://people.ischool.berkeley.edu/~hearst/research/scattergather.html Scatter/Gather]&lt;br /&gt;
# [https://devaka.ru/wp-content/uploads/2008/11/UIR-1995-07-Pirolli-CHI95-Foraging.pdf Information Foraging in Information Access Environments]&lt;br /&gt;
&lt;br /&gt;
=Getting Started=&lt;br /&gt;
==Cloning the Information Foraging Baseline Code==&lt;br /&gt;
We are hosting our repositories using github this semester. That means you will get a new repository for each of our three projects. When you accept an assignment through github classroom, it will create a repository for you based on the template that we've defined as the starting point for everyone.&lt;br /&gt;
&lt;br /&gt;
# First, accept the assignment from github. Once the assignment is ready to go live, we will update the link here.&lt;br /&gt;
# Navigate to your cloned repository on github. You can get there by reloading the &amp;quot;generating your repository&amp;quot; page. Git hub will give you a link when it's ready. It should have a url something like: &amp;lt;nowiki&amp;gt;https://github.com/cse-256-f22/information_foraging-YOUR_GITHUB_ID-wustl&amp;lt;/nowiki&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==Setting Up Pages==&lt;br /&gt;
To see what your version of the nursery school site looks like, you can view it through github pages. This will also be how your user-testerss will view and interact with your site, so it's important to get going even if you plan to develop fully locally.&lt;br /&gt;
# Go the the settings tab&lt;br /&gt;
# Click on pages in the left-hand list of options &lt;br /&gt;
# Select 'deploy from a branch' and the branch you want users to see (likely main).&lt;br /&gt;
# Enable github Pages by hitting save&lt;br /&gt;
# Once you hit save, github will add a link to your hosted pages so that you can see them.&lt;br /&gt;
&lt;br /&gt;
Note that it can take a while (sometimes ~30 minutes) for the site to get updated. Other times, it can be within a minute or two. Once you have it enabled, when you push changes to your repository, that should trigger a site refresh.&lt;br /&gt;
&lt;br /&gt;
=Baseline Code=&lt;br /&gt;
Your repository contains the baseline version of the Nursery School site. Your assignment is to adapt that codebase to improve users' task performance. Within your top level repository directory you will find a subfolder called '''files''' that contains all of the HTML and CSS files you should need to edit for this project. If you would like to edit the JS of your site then do so in the '''scripts/ts/dynamic-dom''' folder.&lt;br /&gt;
&lt;br /&gt;
To run the site locally, do these steps:&lt;br /&gt;
# Open a terminal window or the terminal in your code editor.&lt;br /&gt;
# Navigate to your repository folder. This should be something like: information-foraging-&amp;lt;YOUR_GITHUB_ID&amp;gt;-wustl.&lt;br /&gt;
# Type in:&lt;br /&gt;
 '''npm install'''&lt;br /&gt;
 '''npm run dev'''&lt;br /&gt;
# This will open the Nursery School site running at http://localhost:3000/ in a web browser.&lt;br /&gt;
## You may notice a couple of alerts that pop up in your browser. This is because the URL is missing some information that the site expects to be there. If you would like these alerts not to show up, then use something like this URL in your browser instead: http://localhost:3000/?wustl_key=riley.mccuen.testing&amp;amp;sandbox=false&amp;amp;project=information-foraging&amp;amp;iteration=1&amp;amp;tag=books&lt;br /&gt;
## Feel free to configure the query string in in that url if you would like, but either way it should get rid of the alerts that show up on page reload.&lt;br /&gt;
# When you want to stop the web server you can press 'CTRL+C' and the server should shut down.&lt;br /&gt;
&lt;br /&gt;
=Introductory Studio=&lt;br /&gt;
The goal of this studio is to introduce you to the basic set of skills that you will need in order to begin modifying the nursery school site. While you won't emerge at the end of this knowing everything there is to know about HTML, CSS, and JavaScript, this should give you enough to be able to modify the starting code we've given you.&lt;br /&gt;
&lt;br /&gt;
[[Information Foraging Studio]]&lt;br /&gt;
&lt;br /&gt;
=Adding Javascript to Your Site=&lt;br /&gt;
When you find yourself wanting to add javascript there is one way we recommend doing it ('''NOTE''' if you do not do it this way it may not work as expected). &lt;br /&gt;
# Create a new file in the information-foraging/scripts/ts/dynamic-dom/ directory in your repository. If you are only using javascript then feel free to make a .js file, but it is recommended to use typescript which would be a .ts file. Both types of files will be included if used and imported properly. ('''NOTE''' regardless of whether or not you use TS you need to include it in the '''ts'''/dynamic-dom/ directory and import it into dynamic-dom.ts otherwise the build script will not bundle it.)&lt;br /&gt;
# Write your code in that new file.&lt;br /&gt;
# Import that file into dynamic-dom.ts and initialize it using a static initializer like you see is being done with the accordion and slideshow elements.&lt;br /&gt;
## Alternatively, if you only have a small amount of code and do not think that you need a whole new file then you can put your code directly in the information-foraging/scripts/ts/dynamic-dom/dynamic-dom.ts file.&lt;br /&gt;
# If your code is in script tags inlined into the html or not initialized through the dynamic-dom.ts file it will either not show up on your page or cause numerous runtime errors. Keep in mind, if you open your developer's console in your browser and there are red errors then that means your code is broken and needs to be fixed.&lt;br /&gt;
# Your code will need to be rebuilt in order to see these changes on your site.&lt;br /&gt;
Here is how you should write your code and import it, there is an example for both a .js file and .ts file but you only need to have one of them:&lt;br /&gt;
&lt;br /&gt;
This is for the javascript version in the file /information-foraging/scripts/ts/dynamic-dom/sticky.js&lt;br /&gt;
 export function setupSticky() {&lt;br /&gt;
    // TODO: Copy and paste your sticky code in here!!&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
This is for the typescript version in the file /information-foraging/scripts/ts/dynamic-dom/sticky.ts&lt;br /&gt;
 export function setupSticky() {&lt;br /&gt;
    // TODO: Copy and paste your sticky code in here!!&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
Now that you have your code in sticky.(j|t)s, put the bolded code below in the file /information-foraging/scripts/ts/dynamic-dom/dynamic-dom.ts:&lt;br /&gt;
 import { Accordion } from './accordion';&lt;br /&gt;
 import { Slideshow } from './slideshow';&lt;br /&gt;
 '''import { setupStickey } from './stickey';'''&lt;br /&gt;
 &lt;br /&gt;
 // Put all function calls that need to be made on every page load inside the setupAll function body.&lt;br /&gt;
 export function PutStudentPageLoadOperationsInsideThisStudentBody() {&lt;br /&gt;
     // TODO: Put all operations that you want to happen on ever page load in this function.&lt;br /&gt;
     // For example you could write: Sticky.setup()&lt;br /&gt;
     '''setupStickey();'''&lt;br /&gt;
 }&lt;br /&gt;
Like the comment says you can ''Put all function calls that need to be made on every page load inside the setupAll function body'' or you can put it into the PutStudentPageLoadOperationsInsideThisStudentBody function, either way it will work and is up to you.&lt;br /&gt;
&lt;br /&gt;
=Testing Your Site=&lt;br /&gt;
&lt;br /&gt;
To test your site, you need to do two things: &lt;br /&gt;
# Commit and push your code to Github. It may take a couple of minutes, but your changes will eventually be reflected in your Github pages site.&lt;br /&gt;
&amp;lt;!-- # Submit a sandbox hit that you can try out. ([[Submitting Sandbox HITs]])--&amp;gt;&lt;br /&gt;
# If you open your developer's console in your browser and see red errors, then something is broken and will be broken when you submit your hits. You must fix it.&lt;br /&gt;
&lt;br /&gt;
==Uploading to Github Pages==&lt;br /&gt;
To test or submit your project, you'll first need to upload your to Github.&lt;br /&gt;
&lt;br /&gt;
# If you've made changes to javascript and/or typescript code, please rebuild your code to get the new changes. (see [[Node Setup]] - step 6)&lt;br /&gt;
# Test your site locally via localhost (see [[Running Sites Locally]])&lt;br /&gt;
# Commit and push your changes (see [https://code.visualstudio.com/docs/editor/versioncontrol Version Control in VS Code])&lt;br /&gt;
# It will take a few minutes but your Github pages site will eventually reflect your changes.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- ==Making a Sandbox HIT==&lt;br /&gt;
If you want to see what your MTurk workers will see, you can submit a sandbox hit. &lt;br /&gt;
&lt;br /&gt;
# This page offers a walkthrough on how to do that. ([[Submitting Sandbox HITs]])&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot (14).png|thumb|Worker Sandbox with relevant ui elements highlighted.]] --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Ground Rules=&lt;br /&gt;
&lt;br /&gt;
The nursery school has selected what content they make available on their website. We may not entirely agree with that selection, but it is our job to figure out how to present it in a way that enables end users to find the information they need. So, it is fair game (and encouraged) to reorganize the structure of the information. However, you may not remove access to information, even if it is not needed for the tasks we are testing. Further, I reserve the right to introduce new tasks without warning. Your best strategy is to holistically work towards a well structured site with good information scent.&lt;br /&gt;
&lt;br /&gt;
=Best Practice Videos=&lt;br /&gt;
It seems pretty clear from looking at the sites you guys created that everyone has gotten the basic ideas around increasing the information density related to a given topic by grouping related information and increasing the information scent through the use of the right words and surrounding content. In going through the comments and the top solutions, I was looking to pull out some best practices that might not have been as obvious to give you one more set of tools that can help you think about information foraging into the future. These are a set of quick videos discussing some best practices in the context of the Nursery School Site.&lt;br /&gt;
&lt;br /&gt;
#[https://drive.google.com/file/d/1M7SRGYxawdlQrGtgNsKmC_MNmZzoifZV/view?usp=sharing Visible Exits]&lt;br /&gt;
#[https://drive.google.com/file/d/1HydDPrebZfj8d5yOHJiOl7IcSh4_VqB0/view?usp=sharing Intrapage Scent]&lt;br /&gt;
#[https://drive.google.com/file/d/1rpw0dRaADY7MzDwp6F6aIqNf_PxJyQFF/view?usp=sharing Promote High-Value Information]&lt;br /&gt;
#[https://drive.google.com/file/d/1FjGN5NNVvsW2fQTnR60a-zyh_tr2evZz/view?usp=sharing Overfitting]&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Finishing_Up&amp;diff=287</id>
		<title>Finishing Up</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Finishing_Up&amp;diff=287"/>
		<updated>2024-02-14T02:24:17Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;# They will finish either by stating ‘I’m finished’ or when the timer goes off, whichever comes first.&lt;br /&gt;
# If this is your last task, stop recording. Otherwise, pause.&lt;br /&gt;
# Capture the user data for this task.&lt;br /&gt;
## '''For Information Foraging:''' The data that you need should have been automatically placed in your copy buffer, so you should just be able to copy it to a text document. If for some reason that doesn't work, open the developer console and you should see the data you need to copy. Be sure to copy from '{ all the way to the closing }' and save a record of this. When you copy it into the submission form, be sure that you have both the opening and closing brace.&lt;br /&gt;
## '''For Problem Solving:''' Open the developer console and type &amp;quot;'''JSON.stringify(userData)'''&amp;quot;. This should spit out a record of their activities in the file permissions interface. Be sure to copy from '{ all the way to the closing }' and save a record of this.&lt;br /&gt;
# At this point, ask them if they have any questions or comments. Answer questions. Record the comments to pass back to the relevant group.&lt;br /&gt;
# Thank them for their help.&lt;br /&gt;
# If you are testing again with the same site, refresh the page.&lt;br /&gt;
# If they are willing to do multiple tasks, then go back to Step 0.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=User_Instructions&amp;diff=286</id>
		<title>User Instructions</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=User_Instructions&amp;diff=286"/>
		<updated>2024-02-14T02:21:32Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;You'll want to introduce your participant to what they will be doing and establish the ground rules. Sometimes it helps to prepare a simple script or even just a short set of bullet points to make sure that you say everything you need to. &lt;br /&gt;
&lt;br /&gt;
'''We should be able to hear this in your zoom recording!'''&lt;br /&gt;
&lt;br /&gt;
== An Information Foraging Example ==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;I am working on a class project to improve the Wash U Nursery School’s website. As part of this, I need to observe people trying to use the site to find the answers to common questions. Would you be willing to help? I’ll ask you to complete three tasks, each one will take no more than 2 minutes.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
If, yes:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Great, thank you. I’m going to show you the website and task. Once you start, I won’t be able to answer any questions until you are finished. But, please talk aloud as you work, your thought process is really valuable in trying to understand what is and isn’t working&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Start zoom recording.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;This is the nursery school site. At the top of the page is a box that shows the task you should complete and provides a textbox where you can enter the answer that you find. Go ahead and read the task and let me know when you have finished reading.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Now that you've read the task, please use the Nursery School site to find an answer. Please look through the site only to find information needed for the task. Feel free to start when you’re ready. If you like, you can collapse or expand the task description using this drop down. I’ll let you know when 2 minutes are up. If you finish before that, please tell me 'I am finished'&amp;quot;&lt;br /&gt;
&lt;br /&gt;
When they are finished (or when the timer goes off), please ask the user to type in their best answer into the text box and press submit. If they did not find the answer, it’s fine to just write 'couldn’t find it' and press submit.&lt;br /&gt;
&lt;br /&gt;
== A Problem Solving Example ==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;I am working on a class project to improve an interface for setting file sharing permissions. As part of this, I need to observe people trying to use the interface to set permissions to allow appropriate reading/modification access for different users and scenarios. Would you be willing to help? I’ll ask you to complete three tasks, each one will take no more than 3 minutes.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
If, yes:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Great, thank you. I’m going to show you the interface and task. Once you start, I won’t be able to answer any questions until you are finished. But, please talk aloud as you work, your thought process is really valuable in trying to understand what is and isn’t working&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Start zoom recording.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;This is the file permissions interface. At the bottom of the page is a box that shows the task you should complete and provides a textbox where you can enter the answer that you find. Go ahead and read the task and let me know when you have finished reading.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Now that you've read the task, please set the permissions as well as you can using the interface. You may need to explore the current settings in order to determine what you need to add or change. Feel free to start when you’re ready. I’ll let you know when 3 minutes are up. If you finish before that, please tell me 'I am finished'&amp;quot;&lt;br /&gt;
&lt;br /&gt;
When they are finished (or when the timer goes off), please ask the user to type in their best answer into the text box. If they did not find the answer, it’s fine to just write 'couldn’t find it'.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=MediaWiki:Sidebar&amp;diff=285</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=MediaWiki:Sidebar&amp;diff=285"/>
		<updated>2024-01-22T13:27:35Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
* navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
*Environment Setup&lt;br /&gt;
**Software_to_Install|Software to Install&lt;br /&gt;
**Node_Setup|Node.js Setup&lt;br /&gt;
**Clone_Your_Repository|Clone Your Repository&lt;br /&gt;
**Running_Sites_Locally|Running Sites Locally&lt;br /&gt;
**Testing_Your_Site|Testing Your Site&lt;br /&gt;
* Assignments&lt;br /&gt;
** Information_Foraging_Assignment:_Nursery_School|Information Foraging: Nursery School&lt;br /&gt;
** GenderMag_Assignment:_File_Permissions|GenderMag: File Permissions&lt;br /&gt;
** Cognitive_Load_Theory_Assignment:_Set|Cognitive Load Theory: Set&lt;br /&gt;
*User Testing&lt;br /&gt;
**Preparing_for_a_User_Test|Preparing for a User Test&lt;br /&gt;
**Record_Demographics|Record Demographics&lt;br /&gt;
**User_Instructions|User Instructions&lt;br /&gt;
**Recording_Observations|Recording Observations&lt;br /&gt;
**Finishing_Up|Finishing Up&lt;br /&gt;
**Submission_Mechanics|Submission Mechanics&lt;br /&gt;
&lt;br /&gt;
* SEARCH&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Main_Page&amp;diff=284</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Main_Page&amp;diff=284"/>
		<updated>2024-01-22T13:26:15Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: /* Environment Setup */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Environment Setup=&lt;br /&gt;
[[Software_to_Install|Software to Install]]&lt;br /&gt;
&lt;br /&gt;
[[Clone_Your_Repository|Clone Your Repository]]&lt;br /&gt;
&lt;br /&gt;
[[Node_Setup|Node.js Setup]]&lt;br /&gt;
&lt;br /&gt;
[[Running_Sites_Locally|Running Sites Locally]]&lt;br /&gt;
&lt;br /&gt;
=Assignments=&lt;br /&gt;
[[Information_Foraging_Assignment:_Nursery_School|Information Foraging: Nursery School]]&lt;br /&gt;
&lt;br /&gt;
[[Problem_Solving_Assignment:_File_Permissions|Problem Solving: File Permissions]]&lt;br /&gt;
&lt;br /&gt;
[[Cognitive_Load_Theory_Assignment:_Set|Cognitive Load Theory: Set]]&lt;br /&gt;
&lt;br /&gt;
=User Testing=&lt;br /&gt;
[[Preparing_for_a_User_Test|Preparing for a User Test]]&lt;br /&gt;
&lt;br /&gt;
[[Record_Demographics|Record Demographics]]&lt;br /&gt;
&lt;br /&gt;
[[User_Instructions|User Instructions]]&lt;br /&gt;
&lt;br /&gt;
[[Recording_Observations|Recording Observations]]&lt;br /&gt;
&lt;br /&gt;
[[Finishing_Up|Finishing Up]]&lt;br /&gt;
&lt;br /&gt;
[[Submission_Mechanics|Submission Mechanics]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]&lt;br /&gt;
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Problem_Solving_Assignment:_File_Permissions&amp;diff=283</id>
		<title>Problem Solving Assignment: File Permissions</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Problem_Solving_Assignment:_File_Permissions&amp;diff=283"/>
		<updated>2023-10-30T18:50:30Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: /* Baseline Code */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Task Description=&lt;br /&gt;
The goal of this assignment is to use a problem solving analysis to improve a File Permissions interface that is highly similar to the one used in Windows 10. We've developed a series of tasks that combine different kinds of tasks and system states to evaluate the overall system effectiveness. For each scenario, you will see a simplified file system management interface. In this project, you users will be given a scenario and asked to modify the file permissions to achieve a goal presented in that scenario. &lt;br /&gt;
&lt;br /&gt;
Specifically, we'll evaluate the following scenarios:&lt;br /&gt;
&lt;br /&gt;
==Easy==&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_remove_direct_permission.html Remove some permissions from employee (V1)] (remove_direct_permission) Baseline = 0.96; Passing Score &amp;gt;= 1.15&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_add_new_user.html Add permissions for a new employee] (add_new_user) Baseline = 1.27; Passing Score &amp;gt;= 1.52&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_add_full_permissions.html Add permissions for a manager] (add_full_permissions) Baseline = 1.96; Passing Score &amp;gt;= 2.35&lt;br /&gt;
&lt;br /&gt;
==Medium==&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_remove_inherited_permission.html Remove some permissions from employee (V2)] (remove_inherited_permission) Baseline =  1.63; Passing Score &amp;gt;= 1.95&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_intern_permissions.html Add permissions for an intern] (intern_permissions) Baseline = 0.9; Passing Score &amp;gt;= 1.08&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_remove_user_with_inheritance.html Remove ALL permissions from employee] (remove_user_with_inheritance) Baseline = 1.34; Passing Score &amp;gt;= 1.60&lt;br /&gt;
&lt;br /&gt;
==Hard==&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_restrict_group_member.html Remove some permissions from employee (V3)] (restrict_group_member) Baseline = 0.97; Passing Score &amp;gt;= 1.16&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_let_ta_modify.html Fix permissions for a teaching assistant] (let_ta_modify) Baseline = 0; Passing Score &amp;gt;= 0.2&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_lost_inheritance.html Fix permissions for all users] (wrapper_lost_inheritance) Baseline = 1.13; Passing Score &amp;gt;= 1.35&lt;br /&gt;
&lt;br /&gt;
=Grading=&lt;br /&gt;
&lt;br /&gt;
For each project, you will get assigned three tasks to test for that round: one each from easy, medium, and hard. For the first round, these will be randomly chosen. For subsequent rounds, we will carry two of your previous tasks forward. You can submit up to three versions (see deadlines on the calendar). For each task, we'll assign a score that captures the degree to which participants granted the correct permissions (what percent of the correct permissions do they have) and didn't grant the incorrect permissions (what percentage of the permissions that they shouldn't have that they don't) and efficiently (took the fastest path to get there). To get credit for a task, you need to outperform the baseline score by 20% for that task. Overall project grades will be:&lt;br /&gt;
&lt;br /&gt;
* 93: 3 tasks that perform &amp;gt;20% over the baseline, spread across any iteration.&lt;br /&gt;
* 88: 2 tasks that perform &amp;gt;20% over the baseline, spread across any iteration.&lt;br /&gt;
* 83: 1 task that performs &amp;gt;20% over the baseline, in any iteration.&lt;br /&gt;
Then you can earn bonus points as follows:&lt;br /&gt;
&lt;br /&gt;
* +7: all three tasks in a single iteration&lt;br /&gt;
* +3: two tasks in a single iteration&lt;br /&gt;
* +2: one of the top 3 performing tasks in the class (Note: you can earn this bonus for multiple tasks)&lt;br /&gt;
&lt;br /&gt;
=Prerequisite Readings=&lt;br /&gt;
=Baseline Code=&lt;br /&gt;
Your repository contains the baseline version of the file permissions interface. Your assignment is to adapt that codebase to improve users' task performance using the facets of problem solving. Within your top level repository directory, you will find the HTML files and JS files you'll need to edit. There are also wrappers HTML files that you can use to see the different scenarios (you shouldn't edit these).&lt;br /&gt;
&lt;br /&gt;
To run the site locally, follow the directions in [[Running Sites Locally]].&lt;br /&gt;
&lt;br /&gt;
Note:&lt;br /&gt;
# index.html loads the interface with no scenario, but since the scenario is tied to the interface, this isn't really a useful view. For development purposes, you may want to try starting with '''student_index.html''' which gives you a list of the scenarios to click on.&lt;br /&gt;
&lt;br /&gt;
=Introductory Studio=&lt;br /&gt;
&lt;br /&gt;
[[Problem Solving Studio]]&lt;br /&gt;
&lt;br /&gt;
=Testing Your Solutions=&lt;br /&gt;
&lt;br /&gt;
To determine whether your solution to a given scenario is correct you can:&lt;br /&gt;
# Complete the steps necessary to change the permissions to a state you believe is correct.&lt;br /&gt;
# Open the developer console in your browser.&lt;br /&gt;
# Type in '''validate_and_get_logs()'''. If your solution is correct, this will generate a long text blurb that will be what you need to include with your submission quiz. If your solution is not correct, you will get a list of erroneous permissions.&lt;br /&gt;
# You can also type in '''show_correct_permissions()''' to see what the correct set of permissions is.&lt;br /&gt;
&lt;br /&gt;
=Testing Your Site=&lt;br /&gt;
&lt;br /&gt;
To test your site, you need to do two things: &lt;br /&gt;
#Set up Github Pages &lt;br /&gt;
# Commit and push your code to Github. It may take a couple of minutes, but your changes will eventually be reflected in your Github pages site.&lt;br /&gt;
# Make sure that this is consistent with your localhost version. &lt;br /&gt;
&lt;br /&gt;
==Setting Up Pages==&lt;br /&gt;
To see what your version of the file permissions interface to users, you can view it through github pages. &lt;br /&gt;
# From your github repository, go the the settings tab and scroll down to the bottom.&lt;br /&gt;
# Change the repository visibility to 'public.'&lt;br /&gt;
# Enable github Pages. Select the 'main' branch and the 'root' directory to serve pages from. &lt;br /&gt;
# Once you hit save, github will add a link to your hosted pages so that you can see them.&lt;br /&gt;
&lt;br /&gt;
==Uploading to Github Pages==&lt;br /&gt;
To submit your project, you'll first need to upload your to Github.&lt;br /&gt;
&lt;br /&gt;
# If you've made changes to javascript and/or typescript code, please rebuild your code to get the new changes. (see [[Node Setup]] - step 6)&lt;br /&gt;
# Test your site locally via localhost (see [[Running Sites Locally]])&lt;br /&gt;
# Commit and push your changes (see [https://code.visualstudio.com/docs/editor/versioncontrol Version Control in VS Code])&lt;br /&gt;
# It will take a few minutes but your Github pages site will eventually reflect your changes.&lt;br /&gt;
&lt;br /&gt;
=Submission=&lt;br /&gt;
&lt;br /&gt;
For Iterations 1-3:&lt;br /&gt;
# Just as with testing, the first step in submitting your project is to push your changes to your github repo. &lt;br /&gt;
# Then, please fill out the canvas submission form for the current iteration. This serves as your declaration that we should test your project. We will randomly choose three of the tasks to test. For future iterations, we’ll keep two tasks the same and then choose a different third task. This is intended to keep disincentivize degenerate designs while also giving you an opportunity to iterate.&lt;br /&gt;
&lt;br /&gt;
Note: when filling out the submission form, it will ask you for your log data. If you have not changed the basic flow of the interface (your changes add supplemental information but don't change what a user needs to do), you can answer &amp;quot;same&amp;quot; for all of these questions. &lt;br /&gt;
&lt;br /&gt;
If you have made changes, then you'll need to do the following:&lt;br /&gt;
&lt;br /&gt;
#For each changed scenario, navigate to the corresponding wrapper_*.html page in your version of the interface. &lt;br /&gt;
#Solve the scenario in as few clicks as possible in your interface. &lt;br /&gt;
#Once you think you have achieved the correct permissions required in the scenario, open the JavaScript console in your browser and type in  validate_and_get_logs(). This will output one of two things:&lt;br /&gt;
&lt;br /&gt;
If your solution is correct (i.e. it resulted in the right permissions to solve the scenario), a large text block will be printed out. These are the logs which give us the correct path for scoring users' attempts. '''This is the text you need to copy and paste into the submission question for each scenario.''' &lt;br /&gt;
&lt;br /&gt;
If your solution is incorrect, in that the effective permissions state is not the one that solves this scenario, a series of errors and warnings will be printed out instead. The warnings list out what specifically is wrong with the current effective permission state: which permissions are allowed but should be denied according to the scenario, and vice versa. Try to understand why this is wrong and correct the problem.&lt;br /&gt;
 &lt;br /&gt;
Since accurate scoring depends on having the shortest/most efficent path, we highly recommend starting over and solving the scenario from scratch once you figure out how to get the correct answer. Otherwise your &amp;quot;shortest path&amp;quot; logs will include all of your trial-and-error.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=User_Instructions&amp;diff=282</id>
		<title>User Instructions</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=User_Instructions&amp;diff=282"/>
		<updated>2023-10-03T02:26:43Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: /* An Information Foraging Example */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;You'll want to introduce your participant to what they will be doing and establish the ground rules. Sometimes it helps to prepare a simple script or even just a short set of bullet points to make sure that you say everything you need to. &lt;br /&gt;
&lt;br /&gt;
== An Information Foraging Example ==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;I am working on a class project to improve the Wash U Nursery School’s website. As part of this, I need to observe people trying to use the site to find the answers to common questions. Would you be willing to help? I’ll ask you to complete three tasks, each one will take no more than 2 minutes.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
If, yes:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Great, thank you. I’m going to show you the website and task. Once you start, I won’t be able to answer any questions until you are finished. But, please talk aloud as you work, your thought process is really valuable in trying to understand what is and isn’t working&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Start zoom recording.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;This is the nursery school site. At the top of the page is a box that shows the task you should complete and provides a textbox where you can enter the answer that you find. Go ahead and read the task and let me know when you have finished reading.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Now that you've read the task, please use the Nursery School site to find an answer. Please look through the site only to find information needed for the task. Feel free to start when you’re ready. If you like, you can collapse or expand the task description using this drop down. I’ll let you know when 2 minutes are up. If you finish before that, please tell me 'I am finished'&amp;quot;&lt;br /&gt;
&lt;br /&gt;
When they are finished (or when the timer goes off), please ask the user to type in their best answer into the text box and press submit. If they did not find the answer, it’s fine to just write 'couldn’t find it' and press submit.&lt;br /&gt;
&lt;br /&gt;
== A Problem Solving Example ==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;I am working on a class project to improve an interface for setting file sharing permissions. As part of this, I need to observe people trying to use the interface to set permissions to allow appropriate reading/modification access for different users and scenarios. Would you be willing to help? I’ll ask you to complete three tasks, each one will take no more than 3 minutes.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
If, yes:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Great, thank you. I’m going to show you the interface and task. Once you start, I won’t be able to answer any questions until you are finished. But, please talk aloud as you work, your thought process is really valuable in trying to understand what is and isn’t working&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Start zoom recording.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;This is the file permissions interface. At the bottom of the page is a box that shows the task you should complete and provides a textbox where you can enter the answer that you find. Go ahead and read the task and let me know when you have finished reading.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Now that you've read the task, please set the permissions as well as you can using the interface. You may need to explore the current settings in order to determine what you need to add or change. Feel free to start when you’re ready. I’ll let you know when 3 minutes are up. If you finish before that, please tell me 'I am finished'&amp;quot;&lt;br /&gt;
&lt;br /&gt;
When they are finished (or when the timer goes off), please ask the user to type in their best answer into the text box. If they did not find the answer, it’s fine to just write 'couldn’t find it'.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Software_to_Install&amp;diff=281</id>
		<title>Software to Install</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Software_to_Install&amp;diff=281"/>
		<updated>2023-09-01T14:58:18Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The list below is the recommended list of software to install. While there are other possible configurations that will support the kinds of web programming we'll do in this class, we'll be best able to help if you stick to the configuration that we've been working with.&lt;br /&gt;
&lt;br /&gt;
# [https://git-scm.com/downloads Git] You'll use Git for source code control. &lt;br /&gt;
# [https://code.visualstudio.com/download VSCode] VSCode is the recommended IDE. This will leverage the version of Git that is installed on your machine.&lt;br /&gt;
## [https://eslint.org/docs/latest/use/getting-started ESLint Extension] This extension is optional, but highly recommended to develop Typescript/Javascript code in VSCode more efficiently.&lt;br /&gt;
## [https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode Code Formatter] This is another optional extension but can help with formatting TS, JS, JSON, HTML, and CSS files during development.&lt;br /&gt;
# [https://nodejs.org/en/download/ Node.js] The Node.js runtime is used to build and bundle your projects as well as handle dependencies for them.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Cognitive_Load_Theory_Assignment:_Set&amp;diff=280</id>
		<title>Cognitive Load Theory Assignment: Set</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Cognitive_Load_Theory_Assignment:_Set&amp;diff=280"/>
		<updated>2023-04-19T14:45:43Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: /* Teaching Set */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Teaching Set ==&lt;br /&gt;
In the final short project, we're going to develop a new tutorial system for a card game called [https://en.wikipedia.org/wiki/Set_(card_game) Set]. We'll spend some time in class going over the rules and getting used to it. In your tutorial system, you should explicitly consider how you will incorporate the ideas of intrinsic, extraneous, and germane load in order to help players more quickly get up to speed on playing it.&lt;br /&gt;
&lt;br /&gt;
Specifically, you should break down your tutorial into 2 levels that focus on different skills. Note that your levels do not necessarily have to cover all of the skills that would be useful in playing set. However, they should represent a progression from simple towards more complex. Each level should explicitly consider its use of intrinsic, extraneous, and germane load.&lt;br /&gt;
&lt;br /&gt;
Then, for each of your levels, you should build a UX storyboard that captures the experience from introducing a new skill to mastery of that skill. The following are a good introduction to the idea of storyboarding in the UX space:&lt;br /&gt;
&lt;br /&gt;
*[https://www.nngroup.com/videos/ux-storyboard/ How to Create a UX Storyboard] &lt;br /&gt;
*[https://www.youtube.com/watch?v=GukAT_S8WH8 The Best UX Design Storyboarding Technique (Design Sprint Hack)]&lt;br /&gt;
&lt;br /&gt;
Before designing your final storyboard (phase 3), this project requires both brainstorming and rough prototyping phases (phases 1 and 2).&lt;br /&gt;
&lt;br /&gt;
Phase 1) First, brainstorm and describe 5 skills each for two levels (choose from beginning, intermediate, and advanced SET players).&lt;br /&gt;
&lt;br /&gt;
Phase 2) Then, select one skill from each of your two difficulty levels and roughly sketch out how your level might work. In drawing out your sketches, please follow the process outlined in the second video. Your step 1 should be an introduction to a new skill, and your step 6 should be the demonstration of that new skill. You should clearly identify what the elements are on your screen.&lt;br /&gt;
&lt;br /&gt;
Phase 3) Then, using Google Slides, create a high-fidelity mock-up of the pages in your tutorial system that covers the user story in your rough prototype. I would also recommend getting a little bit more concrete with your examples, since the learning tasks and how they are presented is a key part of this design. For each step in your two levels, you should also explicitly call out the ways in which you are considering intrinsic, extraneous, and germane load.&lt;br /&gt;
&lt;br /&gt;
On the demo day, I'll ask each group to share one of their two levels.&lt;br /&gt;
&lt;br /&gt;
== Rubric ==&lt;br /&gt;
The rubric for this assignment is as follows:&lt;br /&gt;
*  5 skills each for two of beginning, intermediate, and advanced SET players are identified and described. 10 pts (1pt x 5 skills x 2 levels)&lt;br /&gt;
*1 skill from each level is roughly sketched (see storyboarding videos). 20 pts (10pts x 2 levels)&lt;br /&gt;
*Each level includes clear demonstration of the introduction to a new skill, and clear demonstration of that new skill 30 pts (15 pts x 2 levels)&lt;br /&gt;
*Each level explicitly and accurately identifies sources of the three types of cognitive load. 30 pts (5pts x 2 levels x 3 load types) &lt;br /&gt;
*1 level is clearly presented in class. 10 pts&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Cognitive_Load_Theory_Assignment:_Set&amp;diff=279</id>
		<title>Cognitive Load Theory Assignment: Set</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Cognitive_Load_Theory_Assignment:_Set&amp;diff=279"/>
		<updated>2023-04-19T14:43:42Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Teaching Set ==&lt;br /&gt;
In the final short project, we're going to develop a new tutorial system for a card game called [https://en.wikipedia.org/wiki/Set_(card_game) Set]. We'll spend some time in class going over the rules and getting used to it. In your tutorial system, you should explicitly consider how you will incorporate the ideas of intrinsic, extraneous, and germane load in order to help players more quickly get up to speed on playing it.&lt;br /&gt;
&lt;br /&gt;
Specifically, you should break down your tutorial into 3 levels that focus on different skills. Note that your levels do not necessarily have to cover all of the skills that would be useful in playing set. However, they should represent a progression from simple towards more complex. Each level should explicitly consider its use of intrinsic, extraneous, and germane load.&lt;br /&gt;
&lt;br /&gt;
Then, for each of your levels, you should build a UX storyboard that captures the experience from introducing a new skill to mastery of that skill. The following are a good introduction to the idea of storyboarding in the UX space:&lt;br /&gt;
&lt;br /&gt;
*[https://www.nngroup.com/videos/ux-storyboard/ How to Create a UX Storyboard] &lt;br /&gt;
*[https://www.youtube.com/watch?v=GukAT_S8WH8 The Best UX Design Storyboarding Technique (Design Sprint Hack)]&lt;br /&gt;
&lt;br /&gt;
Before designing your final storyboard (phase 3), this project requires both brainstorming and rough prototyping phases (phases 1 and 2).&lt;br /&gt;
&lt;br /&gt;
Phase 1) First, brainstorm and describe 5 skills each for two levels (choose from beginning, intermediate, and advanced SET players).&lt;br /&gt;
&lt;br /&gt;
Phase 2) Then, select one skill from each of your two difficulty levels and roughly sketch out how your level might work. In drawing out your sketches, please follow the process outlined in the second video. Your step 1 should be an introduction to a new skill, and your step 6 should be the demonstration of that new skill. You should clearly identify what the elements are on your screen.&lt;br /&gt;
&lt;br /&gt;
Phase 3) Then, using Google Slides, create a high-fidelity mock-up of the pages in your tutorial system that covers the user story in your rough prototype. I would also recommend getting a little bit more concrete with your examples, since the learning tasks and how they are presented is a key part of this design. For each step in your two levels, you should also explicitly call out the ways in which you are considering intrinsic, extraneous, and germane load.&lt;br /&gt;
&lt;br /&gt;
On the demo day, I'll ask each group to share one of their two levels.&lt;br /&gt;
&lt;br /&gt;
== Rubric ==&lt;br /&gt;
The rubric for this assignment is as follows:&lt;br /&gt;
*  5 skills each for two of beginning, intermediate, and advanced SET players are identified and described. 10 pts (1pt x 5 skills x 2 levels)&lt;br /&gt;
*1 skill from each level is roughly sketched (see storyboarding videos). 20 pts (10pts x 2 levels)&lt;br /&gt;
*Each level includes clear demonstration of the introduction to a new skill, and clear demonstration of that new skill 30 pts (15 pts x 2 levels)&lt;br /&gt;
*Each level explicitly and accurately identifies sources of the three types of cognitive load. 30 pts (5pts x 2 levels x 3 load types) &lt;br /&gt;
*1 level is clearly presented in class. 10 pts&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Cognitive_Load_Theory_Assignment:_Set&amp;diff=278</id>
		<title>Cognitive Load Theory Assignment: Set</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Cognitive_Load_Theory_Assignment:_Set&amp;diff=278"/>
		<updated>2023-04-19T14:42:57Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: /* Teaching Set */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Teaching Set ==&lt;br /&gt;
In the final short project, we're going to develop a new tutorial system for a card game called [https://en.wikipedia.org/wiki/Set_(card_game) Set]. We'll spend some time in class going over the rules and getting used to it. In your tutorial system, you should explicitly consider how you will incorporate the ideas of intrinsic, extraneous, and germane load in order to help players more quickly get up to speed on playing it.&lt;br /&gt;
&lt;br /&gt;
Specifically, you should break down your tutorial into 3 levels that focus on different skills. Note that your levels do not necessarily have to cover all of the skills that would be useful in playing set. However, they should represent a progression from simple towards more complex. Each level should explicitly consider its use of intrinsic, extraneous, and germane load.&lt;br /&gt;
&lt;br /&gt;
Then, for each of your levels, you should build a UX storyboard that captures the experience from introducing a new skill to mastery of that skill. The following are a good introduction to the idea of storyboarding in the UX space:&lt;br /&gt;
&lt;br /&gt;
*[https://www.nngroup.com/videos/ux-storyboard/ How to Create a UX Storyboard] &lt;br /&gt;
*[https://www.youtube.com/watch?v=GukAT_S8WH8 The Best UX Design Storyboarding Technique (Design Sprint Hack)]&lt;br /&gt;
&lt;br /&gt;
Before designing your final storyboard (phase 3), this project requires both brainstorming and rough prototyping phases (phases 1 and 2).&lt;br /&gt;
&lt;br /&gt;
Phase 1) First, brainstorm and describe 5 skills each for two levels (choose from beginning, intermediate, and advanced SET players).&lt;br /&gt;
&lt;br /&gt;
Phase 2) Then, select one skill from each of your two difficulty levels and roughly sketch out how your level might work. In drawing out your sketches, please follow the process outlined in the second video. Your step 1 should be an introduction to a new skill, and your step 6 should be the demonstration of that new skill. You should clearly identify what the elements are on your screen.&lt;br /&gt;
&lt;br /&gt;
Phase 3) Then, using Google Slides, create a high-fidelity mock-up of the pages in your tutorial system that covers the user story in your rough prototype. I would also recommend getting a little bit more concrete with your examples, since the learning tasks and how they are presented is a key part of this design. For each step in your two levels, you should also explicitly call out the ways in which you are considering intrinsic, extraneous, and germane load.&lt;br /&gt;
&lt;br /&gt;
On the demo day, I'll ask each group to share one of their two levels.&lt;br /&gt;
&lt;br /&gt;
The rubric for this assignment is as follows:&lt;br /&gt;
*  5 skills each for two of beginning, intermediate, and advanced SET players are identified and described. 10 pts (1pt x 5 skills x 2 levels)&lt;br /&gt;
*1 skill from each level is roughly sketched (see storyboarding videos). 20 pts (10pts x 2 levels)&lt;br /&gt;
*Each level includes clear demonstration of the introduction to a new skill, and clear demonstration of that new skill 30 pts (15 pts x 2 levels)&lt;br /&gt;
*Each level explicitly and accurately identifies sources of the three types of cognitive load. 30 pts (5pts x 2 levels x 3 load types) &lt;br /&gt;
*1 level is clearly presented in class. 10 pts&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Finishing_Up&amp;diff=277</id>
		<title>Finishing Up</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Finishing_Up&amp;diff=277"/>
		<updated>2023-04-02T16:31:19Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;# They will finish either by stating ‘I’m finished’ or when the timer goes off, whichever comes first.&lt;br /&gt;
# If this is your last task, stop recording. Otherwise, pause.&lt;br /&gt;
# Capture the user data for this task.&lt;br /&gt;
## '''For Information Foraging:''' Open the developer console and type &amp;quot;'''JSON.stringify(data)'''&amp;quot;. This should spit out a record of their activities on the website. Be sure to copy from '{ all the way to the closing }' and save a record of this.&lt;br /&gt;
## '''For Problem Solving:''' Open the developer console and type &amp;quot;'''JSON.stringify(userData)'''&amp;quot;. This should spit out a record of their activities in the file permissions interface. Be sure to copy from '{ all the way to the closing }' and save a record of this.&lt;br /&gt;
# At this point, ask them if they have any questions or comments. Answer questions. Record the comments to pass back to the relevant group.&lt;br /&gt;
# Thank them for their help.&lt;br /&gt;
# If you are testing again with the same site, refresh the page.&lt;br /&gt;
# If they are willing to do multiple tasks, then go back to Step 0.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=User_Instructions&amp;diff=276</id>
		<title>User Instructions</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=User_Instructions&amp;diff=276"/>
		<updated>2023-04-02T16:26:45Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: /* An Problem Solving Example */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;You'll want to introduce your participant to what they will be doing and establish the ground rules. Sometimes it helps to prepare a simple script or even just a short set of bullet points to make sure that you say everything you need to. &lt;br /&gt;
&lt;br /&gt;
== An Information Foraging Example ==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;I am working on a class project to improve the Wash U Nursery School’s website. As part of this, I need to observe people trying to use the site to find the answers to common questions. Would you be willing to help? I’ll ask you to complete three tasks, each one will take no more than 2 minutes.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
If, yes:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Great, thank you. I’m going to show you the website and task. Once you start, I won’t be able to answer any questions until you are finished. But, please talk aloud as you work, your thought process is really valuable in trying to understand what is and isn’t working&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Start zoom recording.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;This is the nursery school site. At the top of the page is a box that shows the task you should complete and provides a textbox where you can enter the answer that you find. Go ahead and read the task and let me know when you have finished reading.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Now that you've read the task, please use the Nursery School site to find an answer. Please look through the site only to find information needed for the task. Feel free to start when you’re ready. I’ll let you know when 2 minutes are up. If you finish before that, please tell me 'I am finished'&amp;quot;&lt;br /&gt;
&lt;br /&gt;
When they are finished (or when the timer goes off), please ask the user to type in their best answer into the text box. If they did not find the answer, it’s fine to just write 'couldn’t find it'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== A Problem Solving Example ==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;I am working on a class project to improve an interface for setting file sharing permissions. As part of this, I need to observe people trying to use the interface to set permissions to allow appropriate reading/modification access for different users and scenarios. Would you be willing to help? I’ll ask you to complete three tasks, each one will take no more than 3 minutes.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
If, yes:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Great, thank you. I’m going to show you the interface and task. Once you start, I won’t be able to answer any questions until you are finished. But, please talk aloud as you work, your thought process is really valuable in trying to understand what is and isn’t working&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Start zoom recording.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;This is the file permissions interface. At the bottom of the page is a box that shows the task you should complete and provides a textbox where you can enter the answer that you find. Go ahead and read the task and let me know when you have finished reading.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Now that you've read the task, please set the permissions as well as you can using the interface. You may need to explore the current settings in order to determine what you need to add or change. Feel free to start when you’re ready. I’ll let you know when 3 minutes are up. If you finish before that, please tell me 'I am finished'&amp;quot;&lt;br /&gt;
&lt;br /&gt;
When they are finished (or when the timer goes off), please ask the user to type in their best answer into the text box. If they did not find the answer, it’s fine to just write 'couldn’t find it'.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=User_Instructions&amp;diff=275</id>
		<title>User Instructions</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=User_Instructions&amp;diff=275"/>
		<updated>2023-04-02T16:26:22Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;You'll want to introduce your participant to what they will be doing and establish the ground rules. Sometimes it helps to prepare a simple script or even just a short set of bullet points to make sure that you say everything you need to. &lt;br /&gt;
&lt;br /&gt;
== An Information Foraging Example ==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;I am working on a class project to improve the Wash U Nursery School’s website. As part of this, I need to observe people trying to use the site to find the answers to common questions. Would you be willing to help? I’ll ask you to complete three tasks, each one will take no more than 2 minutes.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
If, yes:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Great, thank you. I’m going to show you the website and task. Once you start, I won’t be able to answer any questions until you are finished. But, please talk aloud as you work, your thought process is really valuable in trying to understand what is and isn’t working&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Start zoom recording.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;This is the nursery school site. At the top of the page is a box that shows the task you should complete and provides a textbox where you can enter the answer that you find. Go ahead and read the task and let me know when you have finished reading.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Now that you've read the task, please use the Nursery School site to find an answer. Please look through the site only to find information needed for the task. Feel free to start when you’re ready. I’ll let you know when 2 minutes are up. If you finish before that, please tell me 'I am finished'&amp;quot;&lt;br /&gt;
&lt;br /&gt;
When they are finished (or when the timer goes off), please ask the user to type in their best answer into the text box. If they did not find the answer, it’s fine to just write 'couldn’t find it'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== An Problem Solving Example ==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;I am working on a class project to improve an interface for setting file sharing permissions. As part of this, I need to observe people trying to use the interface to set permissions to allow appropriate reading/modification access for different users and scenarios. Would you be willing to help? I’ll ask you to complete three tasks, each one will take no more than 3 minutes.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
If, yes:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Great, thank you. I’m going to show you the interface and task. Once you start, I won’t be able to answer any questions until you are finished. But, please talk aloud as you work, your thought process is really valuable in trying to understand what is and isn’t working&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Start zoom recording.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;This is the file permissions interface. At the bottom of the page is a box that shows the task you should complete and provides a textbox where you can enter the answer that you find. Go ahead and read the task and let me know when you have finished reading.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Now that you've read the task, please set the permissions as well as you can using the interface. You may need to explore the current settings in order to determine what you need to add or change. Feel free to start when you’re ready. I’ll let you know when 3 minutes are up. If you finish before that, please tell me 'I am finished'&amp;quot;&lt;br /&gt;
&lt;br /&gt;
When they are finished (or when the timer goes off), please ask the user to type in their best answer into the text box. If they did not find the answer, it’s fine to just write 'couldn’t find it'.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Record_Demographics&amp;diff=274</id>
		<title>Record Demographics</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Record_Demographics&amp;diff=274"/>
		<updated>2023-04-02T16:21:05Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Ask potential participants the following questions:&lt;br /&gt;
&lt;br /&gt;
For Information Foraging:&lt;br /&gt;
#Have you ever looked at the Nursery School website?&lt;br /&gt;
#Are you an HCI minor?&lt;br /&gt;
&lt;br /&gt;
For Problem Solving:&lt;br /&gt;
#Have you ever set up detailed permissions for a document that specify actions (read, write, etc) and users? &lt;br /&gt;
## Note: Sharing a google doc or similar with view/edit/comment is not disqualifying.&lt;br /&gt;
#Are you an HCI minor?&lt;br /&gt;
&lt;br /&gt;
If participants answer no to both, then you they are appropriate participants. Ideally, we want a diverse group of users so try to recruit people with differing backgrounds.&lt;br /&gt;
&lt;br /&gt;
Please also note your participant's major and year (freshman, sophomore, etc).&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Preparing_for_a_User_Test&amp;diff=273</id>
		<title>Preparing for a User Test</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Preparing_for_a_User_Test&amp;diff=273"/>
		<updated>2023-04-02T16:15:34Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;# Open a browser and navigate to the site/task you are testing.&lt;br /&gt;
# Open zoom - You'll need to record your user test so that we can recreate any data that gets missed. (I recommend recording to your local machine.)&lt;br /&gt;
# Share screen with your browser so that what it will see is site you are testing.&lt;br /&gt;
# Make sure that you can see the task your participant is supposed to see (and verify it's the correct one).&lt;br /&gt;
# Get a timer ready (I typically use my phone)&lt;br /&gt;
## Info Foraging: Users should have 2 minutes per task &lt;br /&gt;
## Problem Solving: Users should have 3 minutes per task&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Problem_Solving_Assignment:_File_Permissions&amp;diff=272</id>
		<title>Problem Solving Assignment: File Permissions</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Problem_Solving_Assignment:_File_Permissions&amp;diff=272"/>
		<updated>2023-03-31T15:04:45Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: /* Submission */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Task Description=&lt;br /&gt;
The goal of this assignment is to use a problem solving analysis to improve a File Permissions interface that is highly similar to the one used in Windows 10. We've developed a series of tasks that combine different kinds of tasks and system states to evaluate the overall system effectiveness. For each scenario, you will see a simplified file system management interface. In this project, you users will be given a scenario and asked to modify the file permissions to achieve a goal presented in that scenario. &lt;br /&gt;
&lt;br /&gt;
Specifically, we'll evaluate the following scenarios:&lt;br /&gt;
&lt;br /&gt;
==Easy==&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_remove_direct_permission.html Remove some permissions from employee (V1)] (remove_direct_permission) Baseline = 0.96; Passing Score &amp;gt;= 1.15&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_add_new_user.html Add permissions for a new employee] (add_new_user) Baseline = 1.27; Passing Score &amp;gt;= 1.52&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_add_full_permissions.html Add permissions for a manager] (add_full_permissions) Baseline = 1.96; Passing Score &amp;gt;= 2.35&lt;br /&gt;
&lt;br /&gt;
==Medium==&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_remove_inherited_permission.html Remove some permissions from employee (V2)] (remove_inherited_permission) Baseline =  1.63; Passing Score &amp;gt;= 1.95&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_intern_permissions.html Add permissions for an intern] (intern_permissions) Baseline = 0.9; Passing Score &amp;gt;= 1.08&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_remove_user_with_inheritance.html Remove ALL permissions from employee] (remove_user_with_inheritance) Baseline = 1.34; Passing Score &amp;gt;= 1.60&lt;br /&gt;
&lt;br /&gt;
==Hard==&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_restrict_group_member.html Remove some permissions from employee (V3)] (restrict_group_member) Baseline = 0.97; Passing Score &amp;gt;= 1.16&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_let_ta_modify.html Fix permissions for a teaching assistant] (let_ta_modify) Baseline = 0; Passing Score &amp;gt;= 0.2&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_lost_inheritance.html Fix permissions for all users] (wrapper_lost_inheritance) Baseline = 1.13; Passing Score &amp;gt;= 1.35&lt;br /&gt;
&lt;br /&gt;
=Grading=&lt;br /&gt;
&lt;br /&gt;
For each project, you will get assigned three tasks to test for that round: one each from easy, medium, and hard. For the first round, these will be randomly chosen. For subsequent rounds, we will carry two of your previous tasks forward. You can submit up to three versions (see deadlines on the calendar). For each task, we'll assign a score that captures the degree to which participants granted the correct permissions (what percent of the correct permissions do they have) and didn't grant the incorrect permissions (what percentage of the permissions that they shouldn't have that they don't) and efficiently (took the fastest path to get there). To get credit for a task, you need to outperform the baseline score by 20% for that task. Overall project grades will be:&lt;br /&gt;
&lt;br /&gt;
* 93: 3 tasks that perform &amp;gt;20% over the baseline, spread across any iteration.&lt;br /&gt;
* 88: 2 tasks that perform &amp;gt;20% over the baseline, spread across any iteration.&lt;br /&gt;
* 83: 1 task that performs &amp;gt;20% over the baseline, in any iteration.&lt;br /&gt;
Then you can earn bonus points as follows:&lt;br /&gt;
&lt;br /&gt;
* +7: all three tasks in a single iteration&lt;br /&gt;
* +3: two tasks in a single iteration&lt;br /&gt;
* +2: one of the top 3 performing tasks in the class (Note: you can earn this bonus for multiple tasks)&lt;br /&gt;
&lt;br /&gt;
=Prerequisite Readings=&lt;br /&gt;
=Baseline Code=&lt;br /&gt;
Your repository contains the baseline version of the file permissions interface. Your assignment is to adapt that codebase to improve users' task performance using the ideas presented in Gender Mag. Within your top level repository directory, you should find a subfolder called '''gender-mag.''' Inside this folder, you will find the HTML files and JS files you'll need to edit. There are also wrappers HTML files that you can use to see the different scenarios.&lt;br /&gt;
&lt;br /&gt;
To run the site locally, follow the directions in [[Running Sites Locally]].&lt;br /&gt;
&lt;br /&gt;
Note:&lt;br /&gt;
# index.html loads the interface with no scenario, but since the scenario is tied to the interface, this isn't really a useful view. For development purposes, you may want to try starting with '''student_index.html''' which gives you a list of the scenarios to click on.&lt;br /&gt;
&lt;br /&gt;
=Introductory Studio=&lt;br /&gt;
&lt;br /&gt;
[[Problem Solving Studio]]&lt;br /&gt;
&lt;br /&gt;
=Testing Your Solutions=&lt;br /&gt;
&lt;br /&gt;
To determine whether your solution to a given scenario is correct you can:&lt;br /&gt;
# Complete the steps necessary to change the permissions to a state you believe is correct.&lt;br /&gt;
# Open the developer console in your browser.&lt;br /&gt;
# Type in '''validate_and_get_logs()'''. If your solution is correct, this will generate a long text blurb that will be what you need to include with your submission quiz. If your solution is not correct, you will get a list of erroneous permissions.&lt;br /&gt;
# You can also type in '''show_correct_permissions()''' to see what the correct set of permissions is.&lt;br /&gt;
&lt;br /&gt;
=Testing Your Site=&lt;br /&gt;
&lt;br /&gt;
To test your site, you need to do two things: &lt;br /&gt;
#Set up Github Pages &lt;br /&gt;
# Commit and push your code to Github. It may take a couple of minutes, but your changes will eventually be reflected in your Github pages site.&lt;br /&gt;
# Make sure that this is consistent with your localhost version. &lt;br /&gt;
&lt;br /&gt;
==Setting Up Pages==&lt;br /&gt;
To see what your version of the file permissions interface to users, you can view it through github pages. &lt;br /&gt;
# From your github repository, go the the settings tab and scroll down to the bottom.&lt;br /&gt;
# Change the repository visibility to 'public.'&lt;br /&gt;
# Enable github Pages. Select the 'main' branch and the 'root' directory to serve pages from. &lt;br /&gt;
# Once you hit save, github will add a link to your hosted pages so that you can see them.&lt;br /&gt;
&lt;br /&gt;
==Uploading to Github Pages==&lt;br /&gt;
To submit your project, you'll first need to upload your to Github.&lt;br /&gt;
&lt;br /&gt;
# If you've made changes to javascript and/or typescript code, please rebuild your code to get the new changes. (see [[Node Setup]] - step 6)&lt;br /&gt;
# Test your site locally via localhost (see [[Running Sites Locally]])&lt;br /&gt;
# Commit and push your changes (see [https://code.visualstudio.com/docs/editor/versioncontrol Version Control in VS Code])&lt;br /&gt;
# It will take a few minutes but your Github pages site will eventually reflect your changes.&lt;br /&gt;
&lt;br /&gt;
=Submission=&lt;br /&gt;
&lt;br /&gt;
For Iterations 1-3:&lt;br /&gt;
# Just as with testing, the first step in submitting your project is to push your changes to your github repo. &lt;br /&gt;
# Then, please fill out the canvas submission form for the current iteration. This serves as your declaration that we should test your project. We will randomly choose three of the tasks to test. For future iterations, we’ll keep two tasks the same and then choose a different third task. This is intended to keep disincentivize degenerate designs while also giving you an opportunity to iterate.&lt;br /&gt;
&lt;br /&gt;
Note: when filling out the submission form, it will ask you for your log data. If you have not changed the basic flow of the interface (your changes add supplemental information but don't change what a user needs to do), you can answer &amp;quot;same&amp;quot; for all of these questions. &lt;br /&gt;
&lt;br /&gt;
If you have made changes, then you'll need to do the following:&lt;br /&gt;
&lt;br /&gt;
#For each changed scenario, navigate to the corresponding wrapper_*.html page in your version of the interface. &lt;br /&gt;
#Solve the scenario in as few clicks as possible in your interface. &lt;br /&gt;
#Once you think you have achieved the correct permissions required in the scenario, open the JavaScript console in your browser and type in  validate_and_get_logs(). This will output one of two things:&lt;br /&gt;
&lt;br /&gt;
If your solution is correct (i.e. it resulted in the right permissions to solve the scenario), a large text block will be printed out. These are the logs which give us the correct path for scoring users' attempts. '''This is the text you need to copy and paste into the submission question for each scenario.''' &lt;br /&gt;
&lt;br /&gt;
If your solution is incorrect, in that the effective permissions state is not the one that solves this scenario, a series of errors and warnings will be printed out instead. The warnings list out what specifically is wrong with the current effective permission state: which permissions are allowed but should be denied according to the scenario, and vice versa. Try to understand why this is wrong and correct the problem.&lt;br /&gt;
 &lt;br /&gt;
Since accurate scoring depends on having the shortest/most efficent path, we highly recommend starting over and solving the scenario from scratch once you figure out how to get the correct answer. Otherwise your &amp;quot;shortest path&amp;quot; logs will include all of your trial-and-error.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Problem_Solving_Assignment:_File_Permissions&amp;diff=271</id>
		<title>Problem Solving Assignment: File Permissions</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Problem_Solving_Assignment:_File_Permissions&amp;diff=271"/>
		<updated>2023-03-31T15:03:21Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: /* Submission */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Task Description=&lt;br /&gt;
The goal of this assignment is to use a problem solving analysis to improve a File Permissions interface that is highly similar to the one used in Windows 10. We've developed a series of tasks that combine different kinds of tasks and system states to evaluate the overall system effectiveness. For each scenario, you will see a simplified file system management interface. In this project, you users will be given a scenario and asked to modify the file permissions to achieve a goal presented in that scenario. &lt;br /&gt;
&lt;br /&gt;
Specifically, we'll evaluate the following scenarios:&lt;br /&gt;
&lt;br /&gt;
==Easy==&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_remove_direct_permission.html Remove some permissions from employee (V1)] (remove_direct_permission) Baseline = 0.96; Passing Score &amp;gt;= 1.15&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_add_new_user.html Add permissions for a new employee] (add_new_user) Baseline = 1.27; Passing Score &amp;gt;= 1.52&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_add_full_permissions.html Add permissions for a manager] (add_full_permissions) Baseline = 1.96; Passing Score &amp;gt;= 2.35&lt;br /&gt;
&lt;br /&gt;
==Medium==&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_remove_inherited_permission.html Remove some permissions from employee (V2)] (remove_inherited_permission) Baseline =  1.63; Passing Score &amp;gt;= 1.95&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_intern_permissions.html Add permissions for an intern] (intern_permissions) Baseline = 0.9; Passing Score &amp;gt;= 1.08&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_remove_user_with_inheritance.html Remove ALL permissions from employee] (remove_user_with_inheritance) Baseline = 1.34; Passing Score &amp;gt;= 1.60&lt;br /&gt;
&lt;br /&gt;
==Hard==&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_restrict_group_member.html Remove some permissions from employee (V3)] (restrict_group_member) Baseline = 0.97; Passing Score &amp;gt;= 1.16&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_let_ta_modify.html Fix permissions for a teaching assistant] (let_ta_modify) Baseline = 0; Passing Score &amp;gt;= 0.2&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_lost_inheritance.html Fix permissions for all users] (wrapper_lost_inheritance) Baseline = 1.13; Passing Score &amp;gt;= 1.35&lt;br /&gt;
&lt;br /&gt;
=Grading=&lt;br /&gt;
&lt;br /&gt;
For each project, you will get assigned three tasks to test for that round: one each from easy, medium, and hard. For the first round, these will be randomly chosen. For subsequent rounds, we will carry two of your previous tasks forward. You can submit up to three versions (see deadlines on the calendar). For each task, we'll assign a score that captures the degree to which participants granted the correct permissions (what percent of the correct permissions do they have) and didn't grant the incorrect permissions (what percentage of the permissions that they shouldn't have that they don't) and efficiently (took the fastest path to get there). To get credit for a task, you need to outperform the baseline score by 20% for that task. Overall project grades will be:&lt;br /&gt;
&lt;br /&gt;
* 93: 3 tasks that perform &amp;gt;20% over the baseline, spread across any iteration.&lt;br /&gt;
* 88: 2 tasks that perform &amp;gt;20% over the baseline, spread across any iteration.&lt;br /&gt;
* 83: 1 task that performs &amp;gt;20% over the baseline, in any iteration.&lt;br /&gt;
Then you can earn bonus points as follows:&lt;br /&gt;
&lt;br /&gt;
* +7: all three tasks in a single iteration&lt;br /&gt;
* +3: two tasks in a single iteration&lt;br /&gt;
* +2: one of the top 3 performing tasks in the class (Note: you can earn this bonus for multiple tasks)&lt;br /&gt;
&lt;br /&gt;
=Prerequisite Readings=&lt;br /&gt;
=Baseline Code=&lt;br /&gt;
Your repository contains the baseline version of the file permissions interface. Your assignment is to adapt that codebase to improve users' task performance using the ideas presented in Gender Mag. Within your top level repository directory, you should find a subfolder called '''gender-mag.''' Inside this folder, you will find the HTML files and JS files you'll need to edit. There are also wrappers HTML files that you can use to see the different scenarios.&lt;br /&gt;
&lt;br /&gt;
To run the site locally, follow the directions in [[Running Sites Locally]].&lt;br /&gt;
&lt;br /&gt;
Note:&lt;br /&gt;
# index.html loads the interface with no scenario, but since the scenario is tied to the interface, this isn't really a useful view. For development purposes, you may want to try starting with '''student_index.html''' which gives you a list of the scenarios to click on.&lt;br /&gt;
&lt;br /&gt;
=Introductory Studio=&lt;br /&gt;
&lt;br /&gt;
[[Problem Solving Studio]]&lt;br /&gt;
&lt;br /&gt;
=Testing Your Solutions=&lt;br /&gt;
&lt;br /&gt;
To determine whether your solution to a given scenario is correct you can:&lt;br /&gt;
# Complete the steps necessary to change the permissions to a state you believe is correct.&lt;br /&gt;
# Open the developer console in your browser.&lt;br /&gt;
# Type in '''validate_and_get_logs()'''. If your solution is correct, this will generate a long text blurb that will be what you need to include with your submission quiz. If your solution is not correct, you will get a list of erroneous permissions.&lt;br /&gt;
# You can also type in '''show_correct_permissions()''' to see what the correct set of permissions is.&lt;br /&gt;
&lt;br /&gt;
=Testing Your Site=&lt;br /&gt;
&lt;br /&gt;
To test your site, you need to do two things: &lt;br /&gt;
#Set up Github Pages &lt;br /&gt;
# Commit and push your code to Github. It may take a couple of minutes, but your changes will eventually be reflected in your Github pages site.&lt;br /&gt;
# Make sure that this is consistent with your localhost version. &lt;br /&gt;
&lt;br /&gt;
==Setting Up Pages==&lt;br /&gt;
To see what your version of the file permissions interface to users, you can view it through github pages. &lt;br /&gt;
# From your github repository, go the the settings tab and scroll down to the bottom.&lt;br /&gt;
# Change the repository visibility to 'public.'&lt;br /&gt;
# Enable github Pages. Select the 'main' branch and the 'root' directory to serve pages from. &lt;br /&gt;
# Once you hit save, github will add a link to your hosted pages so that you can see them.&lt;br /&gt;
&lt;br /&gt;
==Uploading to Github Pages==&lt;br /&gt;
To submit your project, you'll first need to upload your to Github.&lt;br /&gt;
&lt;br /&gt;
# If you've made changes to javascript and/or typescript code, please rebuild your code to get the new changes. (see [[Node Setup]] - step 6)&lt;br /&gt;
# Test your site locally via localhost (see [[Running Sites Locally]])&lt;br /&gt;
# Commit and push your changes (see [https://code.visualstudio.com/docs/editor/versioncontrol Version Control in VS Code])&lt;br /&gt;
# It will take a few minutes but your Github pages site will eventually reflect your changes.&lt;br /&gt;
&lt;br /&gt;
=Submission=&lt;br /&gt;
&lt;br /&gt;
For Iterations 1-3:&lt;br /&gt;
# Just as with testing, the first step in submitting your project is to push your changes to your github repo. &lt;br /&gt;
# Keep in mind that your project will be tested by actual users on Mechanical Turk. If it breaks and they can't get paid, they may well rate you poorly as a requestor which can create challenges for you to get good data going forward. Please test your submission on Github pages and via a sandbox hit before you declare it ready to go.&lt;br /&gt;
# After you've tested your submission, please make sure that you have $10 in your Mechanical Turk account.&lt;br /&gt;
# Last, please fill out the canvas submission form for the current iteration. This serves as your declaration that we should test your project. We will randomly choose three of the tasks to test. For future iterations, we’ll keep two tasks the same and then choose a different third task. This is intended to keep disincentivize degenerate designs while also giving you an opportunity to iterate.&lt;br /&gt;
&lt;br /&gt;
Note: when filling out the submission form, it will ask you for your log data. If you have not changed the basic flow of the interface (your changes add supplemental information but don't change what a user needs to do), you can answer &amp;quot;same&amp;quot; for all of these questions. &lt;br /&gt;
&lt;br /&gt;
If you have made changes, then you'll need to do the following:&lt;br /&gt;
&lt;br /&gt;
#For each changed scenario, navigate to the corresponding wrapper_*.html page in your version of the interface. &lt;br /&gt;
#Solve the scenario in as few clicks as possible in your interface. &lt;br /&gt;
#Once you think you have achieved the correct permissions required in the scenario, open the JavaScript console in your browser and type in  validate_and_get_logs(). This will output one of two things:&lt;br /&gt;
&lt;br /&gt;
If your solution is correct (i.e. it resulted in the right permissions to solve the scenario), a large text block will be printed out. These are the logs which give us the correct path for scoring MTurkers' attempts. '''This is the text you need to copy and paste into the submission question for each scenario.''' &lt;br /&gt;
&lt;br /&gt;
If your solution is incorrect, in that the effective permissions state is not the one that solves this scenario, a series of errors and warnings will be printed out instead. The warnings list out what specifically is wrong with the current effective permission state: which permissions are allowed but should be denied according to the scenario, and vice versa. Try to understand why this is wrong and correct the problem.&lt;br /&gt;
 &lt;br /&gt;
Since accurate scoring depends on having the shortest/most efficent path, we highly recommend starting over and solving the scenario from scratch once you figure out how to get the correct answer. Otherwise your &amp;quot;shortest path&amp;quot; logs will include all of your trial-and-error.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Problem_Solving_Assignment:_File_Permissions&amp;diff=270</id>
		<title>Problem Solving Assignment: File Permissions</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Problem_Solving_Assignment:_File_Permissions&amp;diff=270"/>
		<updated>2023-03-31T14:52:15Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: /* Baseline Code */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Task Description=&lt;br /&gt;
The goal of this assignment is to use a problem solving analysis to improve a File Permissions interface that is highly similar to the one used in Windows 10. We've developed a series of tasks that combine different kinds of tasks and system states to evaluate the overall system effectiveness. For each scenario, you will see a simplified file system management interface. In this project, you users will be given a scenario and asked to modify the file permissions to achieve a goal presented in that scenario. &lt;br /&gt;
&lt;br /&gt;
Specifically, we'll evaluate the following scenarios:&lt;br /&gt;
&lt;br /&gt;
==Easy==&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_remove_direct_permission.html Remove some permissions from employee (V1)] (remove_direct_permission) Baseline = 0.96; Passing Score &amp;gt;= 1.15&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_add_new_user.html Add permissions for a new employee] (add_new_user) Baseline = 1.27; Passing Score &amp;gt;= 1.52&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_add_full_permissions.html Add permissions for a manager] (add_full_permissions) Baseline = 1.96; Passing Score &amp;gt;= 2.35&lt;br /&gt;
&lt;br /&gt;
==Medium==&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_remove_inherited_permission.html Remove some permissions from employee (V2)] (remove_inherited_permission) Baseline =  1.63; Passing Score &amp;gt;= 1.95&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_intern_permissions.html Add permissions for an intern] (intern_permissions) Baseline = 0.9; Passing Score &amp;gt;= 1.08&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_remove_user_with_inheritance.html Remove ALL permissions from employee] (remove_user_with_inheritance) Baseline = 1.34; Passing Score &amp;gt;= 1.60&lt;br /&gt;
&lt;br /&gt;
==Hard==&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_restrict_group_member.html Remove some permissions from employee (V3)] (restrict_group_member) Baseline = 0.97; Passing Score &amp;gt;= 1.16&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_let_ta_modify.html Fix permissions for a teaching assistant] (let_ta_modify) Baseline = 0; Passing Score &amp;gt;= 0.2&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_lost_inheritance.html Fix permissions for all users] (wrapper_lost_inheritance) Baseline = 1.13; Passing Score &amp;gt;= 1.35&lt;br /&gt;
&lt;br /&gt;
=Grading=&lt;br /&gt;
&lt;br /&gt;
For each project, you will get assigned three tasks to test for that round: one each from easy, medium, and hard. For the first round, these will be randomly chosen. For subsequent rounds, we will carry two of your previous tasks forward. You can submit up to three versions (see deadlines on the calendar). For each task, we'll assign a score that captures the degree to which participants granted the correct permissions (what percent of the correct permissions do they have) and didn't grant the incorrect permissions (what percentage of the permissions that they shouldn't have that they don't) and efficiently (took the fastest path to get there). To get credit for a task, you need to outperform the baseline score by 20% for that task. Overall project grades will be:&lt;br /&gt;
&lt;br /&gt;
* 93: 3 tasks that perform &amp;gt;20% over the baseline, spread across any iteration.&lt;br /&gt;
* 88: 2 tasks that perform &amp;gt;20% over the baseline, spread across any iteration.&lt;br /&gt;
* 83: 1 task that performs &amp;gt;20% over the baseline, in any iteration.&lt;br /&gt;
Then you can earn bonus points as follows:&lt;br /&gt;
&lt;br /&gt;
* +7: all three tasks in a single iteration&lt;br /&gt;
* +3: two tasks in a single iteration&lt;br /&gt;
* +2: one of the top 3 performing tasks in the class (Note: you can earn this bonus for multiple tasks)&lt;br /&gt;
&lt;br /&gt;
=Prerequisite Readings=&lt;br /&gt;
=Baseline Code=&lt;br /&gt;
Your repository contains the baseline version of the file permissions interface. Your assignment is to adapt that codebase to improve users' task performance using the ideas presented in Gender Mag. Within your top level repository directory, you should find a subfolder called '''gender-mag.''' Inside this folder, you will find the HTML files and JS files you'll need to edit. There are also wrappers HTML files that you can use to see the different scenarios.&lt;br /&gt;
&lt;br /&gt;
To run the site locally, follow the directions in [[Running Sites Locally]].&lt;br /&gt;
&lt;br /&gt;
Note:&lt;br /&gt;
# index.html loads the interface with no scenario, but since the scenario is tied to the interface, this isn't really a useful view. For development purposes, you may want to try starting with '''student_index.html''' which gives you a list of the scenarios to click on.&lt;br /&gt;
&lt;br /&gt;
=Introductory Studio=&lt;br /&gt;
&lt;br /&gt;
[[Problem Solving Studio]]&lt;br /&gt;
&lt;br /&gt;
=Testing Your Solutions=&lt;br /&gt;
&lt;br /&gt;
To determine whether your solution to a given scenario is correct you can:&lt;br /&gt;
# Complete the steps necessary to change the permissions to a state you believe is correct.&lt;br /&gt;
# Open the developer console in your browser.&lt;br /&gt;
# Type in '''validate_and_get_logs()'''. If your solution is correct, this will generate a long text blurb that will be what you need to include with your submission quiz. If your solution is not correct, you will get a list of erroneous permissions.&lt;br /&gt;
# You can also type in '''show_correct_permissions()''' to see what the correct set of permissions is.&lt;br /&gt;
&lt;br /&gt;
=Testing Your Site=&lt;br /&gt;
&lt;br /&gt;
To test your site, you need to do two things: &lt;br /&gt;
#Set up Github Pages &lt;br /&gt;
# Commit and push your code to Github. It may take a couple of minutes, but your changes will eventually be reflected in your Github pages site.&lt;br /&gt;
# Make sure that this is consistent with your localhost version. &lt;br /&gt;
&lt;br /&gt;
==Setting Up Pages==&lt;br /&gt;
To see what your version of the file permissions interface to users, you can view it through github pages. &lt;br /&gt;
# From your github repository, go the the settings tab and scroll down to the bottom.&lt;br /&gt;
# Change the repository visibility to 'public.'&lt;br /&gt;
# Enable github Pages. Select the 'main' branch and the 'root' directory to serve pages from. &lt;br /&gt;
# Once you hit save, github will add a link to your hosted pages so that you can see them.&lt;br /&gt;
&lt;br /&gt;
==Uploading to Github Pages==&lt;br /&gt;
To submit your project, you'll first need to upload your to Github.&lt;br /&gt;
&lt;br /&gt;
# If you've made changes to javascript and/or typescript code, please rebuild your code to get the new changes. (see [[Node Setup]] - step 6)&lt;br /&gt;
# Test your site locally via localhost (see [[Running Sites Locally]])&lt;br /&gt;
# Commit and push your changes (see [https://code.visualstudio.com/docs/editor/versioncontrol Version Control in VS Code])&lt;br /&gt;
# It will take a few minutes but your Github pages site will eventually reflect your changes.&lt;br /&gt;
&lt;br /&gt;
=Submission=&lt;br /&gt;
For Iteration 0, you only need to push your changes to github and submit the canvas quiz stating that you've done so.&lt;br /&gt;
&lt;br /&gt;
For Iterations 1-3:&lt;br /&gt;
# Just as with testing, the first step in submitting your project is to push your changes to your github repo. &lt;br /&gt;
# Keep in mind that your project will be tested by actual users on Mechanical Turk. If it breaks and they can't get paid, they may well rate you poorly as a requestor which can create challenges for you to get good data going forward. Please test your submission on Github pages and via a sandbox hit before you declare it ready to go.&lt;br /&gt;
# After you've tested your submission, please make sure that you have $10 in your Mechanical Turk account.&lt;br /&gt;
# Last, please fill out the canvas submission form for the current iteration. This serves as your declaration that we can safely submit real HITs for you. We will randomly choose three of the tasks to test. For future iterations, we’ll keep two tasks the same and then choose a different third task. This is intended to keep disincentivize degenerate designs while also giving you an opportunity to iterate.&lt;br /&gt;
&lt;br /&gt;
Note: when filling out the submission form, it will ask you for your log data. If you have not changed the basic flow of the interface (your changes add supplemental information but don't change what a user needs to do), you can answer &amp;quot;same&amp;quot; for all of these questions. &lt;br /&gt;
&lt;br /&gt;
If you have made changes, then you'll need to do the following:&lt;br /&gt;
&lt;br /&gt;
#For each changed scenario, navigate to the corresponding wrapper_*.html page in your version of the interface. &lt;br /&gt;
#Solve the scenario in as few clicks as possible in your interface. &lt;br /&gt;
#Once you think you have achieved the correct permissions required in the scenario, open the JavaScript console in your browser and type in  validate_and_get_logs(). This will output one of two things:&lt;br /&gt;
&lt;br /&gt;
If your solution is correct (i.e. it resulted in the right permissions to solve the scenario), a large text block will be printed out. These are the logs which give us the correct path for scoring MTurkers' attempts. '''This is the text you need to copy and paste into the submission question for each scenario.''' &lt;br /&gt;
&lt;br /&gt;
If your solution is incorrect, in that the effective permissions state is not the one that solves this scenario, a series of errors and warnings will be printed out instead. The warnings list out what specifically is wrong with the current effective permission state: which permissions are allowed but should be denied according to the scenario, and vice versa. Try to understand why this is wrong and correct the problem.&lt;br /&gt;
 &lt;br /&gt;
Since accurate scoring depends on having the shortest/most efficent path, we highly recommend starting over and solving the scenario from scratch once you figure out how to get the correct answer. Otherwise your &amp;quot;shortest path&amp;quot; logs will include all of your trial-and-error.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Problem_Solving_Assignment:_File_Permissions&amp;diff=269</id>
		<title>Problem Solving Assignment: File Permissions</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Problem_Solving_Assignment:_File_Permissions&amp;diff=269"/>
		<updated>2023-03-31T14:51:41Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: /* Testing Your Site */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Task Description=&lt;br /&gt;
The goal of this assignment is to use a problem solving analysis to improve a File Permissions interface that is highly similar to the one used in Windows 10. We've developed a series of tasks that combine different kinds of tasks and system states to evaluate the overall system effectiveness. For each scenario, you will see a simplified file system management interface. In this project, you users will be given a scenario and asked to modify the file permissions to achieve a goal presented in that scenario. &lt;br /&gt;
&lt;br /&gt;
Specifically, we'll evaluate the following scenarios:&lt;br /&gt;
&lt;br /&gt;
==Easy==&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_remove_direct_permission.html Remove some permissions from employee (V1)] (remove_direct_permission) Baseline = 0.96; Passing Score &amp;gt;= 1.15&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_add_new_user.html Add permissions for a new employee] (add_new_user) Baseline = 1.27; Passing Score &amp;gt;= 1.52&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_add_full_permissions.html Add permissions for a manager] (add_full_permissions) Baseline = 1.96; Passing Score &amp;gt;= 2.35&lt;br /&gt;
&lt;br /&gt;
==Medium==&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_remove_inherited_permission.html Remove some permissions from employee (V2)] (remove_inherited_permission) Baseline =  1.63; Passing Score &amp;gt;= 1.95&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_intern_permissions.html Add permissions for an intern] (intern_permissions) Baseline = 0.9; Passing Score &amp;gt;= 1.08&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_remove_user_with_inheritance.html Remove ALL permissions from employee] (remove_user_with_inheritance) Baseline = 1.34; Passing Score &amp;gt;= 1.60&lt;br /&gt;
&lt;br /&gt;
==Hard==&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_restrict_group_member.html Remove some permissions from employee (V3)] (restrict_group_member) Baseline = 0.97; Passing Score &amp;gt;= 1.16&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_let_ta_modify.html Fix permissions for a teaching assistant] (let_ta_modify) Baseline = 0; Passing Score &amp;gt;= 0.2&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_lost_inheritance.html Fix permissions for all users] (wrapper_lost_inheritance) Baseline = 1.13; Passing Score &amp;gt;= 1.35&lt;br /&gt;
&lt;br /&gt;
=Grading=&lt;br /&gt;
&lt;br /&gt;
For each project, you will get assigned three tasks to test for that round: one each from easy, medium, and hard. For the first round, these will be randomly chosen. For subsequent rounds, we will carry two of your previous tasks forward. You can submit up to three versions (see deadlines on the calendar). For each task, we'll assign a score that captures the degree to which participants granted the correct permissions (what percent of the correct permissions do they have) and didn't grant the incorrect permissions (what percentage of the permissions that they shouldn't have that they don't) and efficiently (took the fastest path to get there). To get credit for a task, you need to outperform the baseline score by 20% for that task. Overall project grades will be:&lt;br /&gt;
&lt;br /&gt;
* 93: 3 tasks that perform &amp;gt;20% over the baseline, spread across any iteration.&lt;br /&gt;
* 88: 2 tasks that perform &amp;gt;20% over the baseline, spread across any iteration.&lt;br /&gt;
* 83: 1 task that performs &amp;gt;20% over the baseline, in any iteration.&lt;br /&gt;
Then you can earn bonus points as follows:&lt;br /&gt;
&lt;br /&gt;
* +7: all three tasks in a single iteration&lt;br /&gt;
* +3: two tasks in a single iteration&lt;br /&gt;
* +2: one of the top 3 performing tasks in the class (Note: you can earn this bonus for multiple tasks)&lt;br /&gt;
&lt;br /&gt;
=Prerequisite Readings=&lt;br /&gt;
=Baseline Code=&lt;br /&gt;
Your repository contains the baseline version of the file permissions interface. Your assignment is to adapt that codebase to improve users' task performance using the ideas presented in Gender Mag. Within your top level repository directory, you should find a subfolder called '''gender-mag.''' Inside this folder, you will find the HTML files and JS files you'll need to edit. There are also wrappers HTML files that you can use to see the different scenarios.&lt;br /&gt;
&lt;br /&gt;
To run the site locally, follow the directions in [[Running Sites Locally]].&lt;br /&gt;
&lt;br /&gt;
Two things to note:&lt;br /&gt;
# index.html loads the interface with no scenario, but since the scenario is tied to the interface, this isn't really a useful view. For development purposes, you may want to try starting with '''student_index.html''' which gives you a list of the scenarios to click on.&lt;br /&gt;
# By default, there is a survey that we'll ask mTurk workers to take that gets at their alignments with the different gender-mag facets. At development time, it's pretty annoying to have to click through it every time. To turn this off, you can go to view_baseline.js. Then, on the first line of the file set '''show_starter_dialogs = false'''&lt;br /&gt;
&lt;br /&gt;
=Introductory Studio=&lt;br /&gt;
&lt;br /&gt;
[[Problem Solving Studio]]&lt;br /&gt;
&lt;br /&gt;
=Testing Your Solutions=&lt;br /&gt;
&lt;br /&gt;
To determine whether your solution to a given scenario is correct you can:&lt;br /&gt;
# Complete the steps necessary to change the permissions to a state you believe is correct.&lt;br /&gt;
# Open the developer console in your browser.&lt;br /&gt;
# Type in '''validate_and_get_logs()'''. If your solution is correct, this will generate a long text blurb that will be what you need to include with your submission quiz. If your solution is not correct, you will get a list of erroneous permissions.&lt;br /&gt;
# You can also type in '''show_correct_permissions()''' to see what the correct set of permissions is.&lt;br /&gt;
&lt;br /&gt;
=Testing Your Site=&lt;br /&gt;
&lt;br /&gt;
To test your site, you need to do two things: &lt;br /&gt;
#Set up Github Pages &lt;br /&gt;
# Commit and push your code to Github. It may take a couple of minutes, but your changes will eventually be reflected in your Github pages site.&lt;br /&gt;
# Make sure that this is consistent with your localhost version. &lt;br /&gt;
&lt;br /&gt;
==Setting Up Pages==&lt;br /&gt;
To see what your version of the file permissions interface to users, you can view it through github pages. &lt;br /&gt;
# From your github repository, go the the settings tab and scroll down to the bottom.&lt;br /&gt;
# Change the repository visibility to 'public.'&lt;br /&gt;
# Enable github Pages. Select the 'main' branch and the 'root' directory to serve pages from. &lt;br /&gt;
# Once you hit save, github will add a link to your hosted pages so that you can see them.&lt;br /&gt;
&lt;br /&gt;
==Uploading to Github Pages==&lt;br /&gt;
To submit your project, you'll first need to upload your to Github.&lt;br /&gt;
&lt;br /&gt;
# If you've made changes to javascript and/or typescript code, please rebuild your code to get the new changes. (see [[Node Setup]] - step 6)&lt;br /&gt;
# Test your site locally via localhost (see [[Running Sites Locally]])&lt;br /&gt;
# Commit and push your changes (see [https://code.visualstudio.com/docs/editor/versioncontrol Version Control in VS Code])&lt;br /&gt;
# It will take a few minutes but your Github pages site will eventually reflect your changes.&lt;br /&gt;
&lt;br /&gt;
=Submission=&lt;br /&gt;
For Iteration 0, you only need to push your changes to github and submit the canvas quiz stating that you've done so.&lt;br /&gt;
&lt;br /&gt;
For Iterations 1-3:&lt;br /&gt;
# Just as with testing, the first step in submitting your project is to push your changes to your github repo. &lt;br /&gt;
# Keep in mind that your project will be tested by actual users on Mechanical Turk. If it breaks and they can't get paid, they may well rate you poorly as a requestor which can create challenges for you to get good data going forward. Please test your submission on Github pages and via a sandbox hit before you declare it ready to go.&lt;br /&gt;
# After you've tested your submission, please make sure that you have $10 in your Mechanical Turk account.&lt;br /&gt;
# Last, please fill out the canvas submission form for the current iteration. This serves as your declaration that we can safely submit real HITs for you. We will randomly choose three of the tasks to test. For future iterations, we’ll keep two tasks the same and then choose a different third task. This is intended to keep disincentivize degenerate designs while also giving you an opportunity to iterate.&lt;br /&gt;
&lt;br /&gt;
Note: when filling out the submission form, it will ask you for your log data. If you have not changed the basic flow of the interface (your changes add supplemental information but don't change what a user needs to do), you can answer &amp;quot;same&amp;quot; for all of these questions. &lt;br /&gt;
&lt;br /&gt;
If you have made changes, then you'll need to do the following:&lt;br /&gt;
&lt;br /&gt;
#For each changed scenario, navigate to the corresponding wrapper_*.html page in your version of the interface. &lt;br /&gt;
#Solve the scenario in as few clicks as possible in your interface. &lt;br /&gt;
#Once you think you have achieved the correct permissions required in the scenario, open the JavaScript console in your browser and type in  validate_and_get_logs(). This will output one of two things:&lt;br /&gt;
&lt;br /&gt;
If your solution is correct (i.e. it resulted in the right permissions to solve the scenario), a large text block will be printed out. These are the logs which give us the correct path for scoring MTurkers' attempts. '''This is the text you need to copy and paste into the submission question for each scenario.''' &lt;br /&gt;
&lt;br /&gt;
If your solution is incorrect, in that the effective permissions state is not the one that solves this scenario, a series of errors and warnings will be printed out instead. The warnings list out what specifically is wrong with the current effective permission state: which permissions are allowed but should be denied according to the scenario, and vice versa. Try to understand why this is wrong and correct the problem.&lt;br /&gt;
 &lt;br /&gt;
Since accurate scoring depends on having the shortest/most efficent path, we highly recommend starting over and solving the scenario from scratch once you figure out how to get the correct answer. Otherwise your &amp;quot;shortest path&amp;quot; logs will include all of your trial-and-error.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=User_Instructions&amp;diff=268</id>
		<title>User Instructions</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=User_Instructions&amp;diff=268"/>
		<updated>2023-03-06T20:11:35Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;You'll want to introduce your participant to what they will be doing and establish the ground rules. Sometimes it helps to prepare a simple script or even just a short set of bullet points to make sure that you say everything you need to. For example:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;I am working on a class project to improve the Wash U Nursery School’s website. As part of this, I need to observe people trying to use the site to find the answers to common questions. Would you be willing to help? I’ll ask you to complete three tasks, each one will take no more than 2 minutes.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
If, yes:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Great, thank you. I’m going to show you the website and task. Once you start, I won’t be able to answer any questions until you are finished. But, please talk aloud as you work, your thought process is really valuable in trying to understand what is and isn’t working&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Start zoom recording.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;This is the nursery school site. At the top of the page is a box that shows the task you should complete and provides a textbox where you can enter the answer that you find. Go ahead and read the task and let me know when you have finished reading.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Now that you've read the task, please use the Nursery School site to find an answer. Please look through the site only to find information needed for the task. Feel free to start when you’re ready. I’ll let you know when 2 minutes are up. If you finish before that, please tell me 'I am finished'&amp;quot;&lt;br /&gt;
&lt;br /&gt;
When they are finished (or when the timer goes off), please ask the user to type in their best answer into the text box. If they did not find the answer, it’s fine to just write 'couldn’t find it'.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Recording_Observations&amp;diff=267</id>
		<title>Recording Observations</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Recording_Observations&amp;diff=267"/>
		<updated>2023-03-06T20:06:47Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Bring out your best poker face. Don’t say anything, don’t react in any way to what happens, just let them do what they are going to do.&lt;br /&gt;
&lt;br /&gt;
Since we are using logs to capture user behavior, it's helpful to jot down some notes on what they struggle with. Quotes that give some indication of what they are thinking are especially helpful. You can submit these are the notes and observations for each task.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=GenderMag_Studio&amp;diff=266</id>
		<title>GenderMag Studio</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=GenderMag_Studio&amp;diff=266"/>
		<updated>2023-03-06T02:48:17Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: Caitlin.Kelleher moved page GenderMag Studio to Problem Solving Studio&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Problem Solving Studio]]&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Problem_Solving_Studio&amp;diff=265</id>
		<title>Problem Solving Studio</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Problem_Solving_Studio&amp;diff=265"/>
		<updated>2023-03-06T02:48:16Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: Caitlin.Kelleher moved page GenderMag Studio to Problem Solving Studio&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;File Permissions tutorial&lt;br /&gt;
=Intro and References=&lt;br /&gt;
&lt;br /&gt;
You will be working in '''view.js'''; most of your code can go where it says &amp;quot;Define your dialogs and panels here&amp;quot; at the top.&lt;br /&gt;
You will also need to look at '''view_helper.js''', '''controller.js''', and '''model.js''' for some of the functions you'll be using.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:References&lt;br /&gt;
&lt;br /&gt;
::The File Permissions code uses the jquery and jquery-ui libraries. You may find it useful to refer to the following documentation and/or tutorials (though you don't need to read through them right this moment):&lt;br /&gt;
&lt;br /&gt;
::jquery:&lt;br /&gt;
::*https://www.impressivewebs.com/jquery-tutorial-for-beginners/&lt;br /&gt;
::*https://oscarotero.com/jquery/&lt;br /&gt;
::jquery-ui:&lt;br /&gt;
::*https://jqueryui.com/&lt;br /&gt;
::The file permissions code also uses two icon libraries (oops!), so you can use icons from either one of these:&lt;br /&gt;
::*https://useiconic.com/open&lt;br /&gt;
::*https://fontawesome.com/icons?d=gallery&amp;amp;m=free&lt;br /&gt;
&lt;br /&gt;
=Modifying Your Live Site=&lt;br /&gt;
Sometimes it is handy to be able to try out potential changes to your site before you actually modify the code. The next few steps will guide you through making a live change to the appearance of the permissions button.&lt;br /&gt;
&lt;br /&gt;
==Step 1: Finding the button classes==&lt;br /&gt;
First, we want to dig into the buttons that we want to modify a little bit.&lt;br /&gt;
#Right-click on the permissions button (with the lock icon) next to any file, and choose &amp;quot;Inspect&amp;quot; or &amp;quot;Inspect Element&amp;quot;.&lt;br /&gt;
#Examine the &amp;lt;button&amp;gt; element. It has a class attribute, which contains a list of 4 space-separated classes. &lt;br /&gt;
&lt;br /&gt;
'''Question: '''What are the 4 classes of the button element?&lt;br /&gt;
&lt;br /&gt;
==Step 2: Selecting elements of a particular class==&lt;br /&gt;
Next, we want to be able to select all of the buttons so that we can make a dynamic change to them. The 3 classes that start with ui-* are used to define the button's appearance. The 4th class defines this element as a permissions button, and that is the one we're interested in.&lt;br /&gt;
&lt;br /&gt;
#In the dev console, type in $('.classname'), where classname is the actual name of that 4th class. This is a jquery selector which selects all the elements with that class.&lt;br /&gt;
&lt;br /&gt;
'''Question: '''What was the resulting output?&lt;br /&gt;
&lt;br /&gt;
(Hint: it should not be an error or undefined,and it should have a non-zero number of results)&lt;br /&gt;
&lt;br /&gt;
==Bonus Info on Selectors==&lt;br /&gt;
In the jquery selector syntax:&lt;br /&gt;
* Starting with '.' selects elements with a given class, e.g. $('.my_class')&lt;br /&gt;
* Starting with '#' selects elements with a given id, e.g. $('#my_id')&lt;br /&gt;
* If you don't start with a special character, you will select all instances of that HTML tag, e.g. $('div') selects all &amp;lt;div&amp;gt; elements.&lt;br /&gt;
&lt;br /&gt;
==Step 3: ==&lt;br /&gt;
Now we will use the same jquery selector to change all the elements with that class.&lt;br /&gt;
&lt;br /&gt;
#In the dev console, type in $('.classname').append('Permissions')&lt;br /&gt;
&lt;br /&gt;
'''Question: '''What happened?&lt;br /&gt;
(Something should have happened to the web page; specifically to all the permission&lt;br /&gt;
buttons)&lt;br /&gt;
&lt;br /&gt;
=Effective Permissions Panel=&lt;br /&gt;
Now that we've experimented with live changes, we're going to delve into creating new UI components. Specifically, we're going to add a new panel that shows the effective permissions for a user and file/directory that takes into account permissions inherited through ancestors and groups.&lt;br /&gt;
&lt;br /&gt;
==Step 1: make the panel==&lt;br /&gt;
First, we will make an Effective Permissions panel using the  '''define_new_effective_permissions''' function in  '''view_helper.js '''. Read the function definition and the comment above it.&lt;br /&gt;
&lt;br /&gt;
Call this function in  '''view.js ''', and  '''store the result in a variable '''.&lt;br /&gt;
&lt;br /&gt;
*You should choose a meaningful  '''id_prefix ''': think of it the same way you think about choosing a good variable name.&lt;br /&gt;
The ids of all the elements inside this new panel will start with the  '''id_prefix ''' you choose. And the ids are what will get logged when users click those elements.&lt;br /&gt;
*And yes, you do want to add the info column for this exercise.&lt;br /&gt;
&lt;br /&gt;
:::Nothing should happen yet. (we still have to put the panel onto the page)&lt;br /&gt;
&lt;br /&gt;
==Step 2: show the panel==&lt;br /&gt;
'''define_new_effective_permissions''' creates the effective permissions panel but doesn't put it onto the page.&lt;br /&gt;
&lt;br /&gt;
'''append''' the result to the element with id '''sidepanel''' &lt;br /&gt;
&lt;br /&gt;
*to select an element with a given id, use '''#''' :&lt;br /&gt;
&amp;lt;pre&amp;gt;$('#element_id')&amp;lt;/pre&amp;gt;&lt;br /&gt;
*then use the '''append''' function the same way we did in the warm-up.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
::'''Tip: '''Throughout this tutorial, when part of a code snippet is in non-bold italics, e.g.''element_id''&lt;br /&gt;
&lt;br /&gt;
::It represents a '''placeholder''' which should be replaced with something appropriate, e.g. '''the id of the element you are trying to select'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you reload the file permissions page(any page for any of the scenarios), you should now see an effective permissions table show up in the side panel, next to the files! It is not displaying any information, because we haven't specified which file and user to display info for.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Question:''' What is the code necessary to build and display the effective permissions panel?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''In the dev console''', try setting the '''filepath''' and '''username''' attributes of your new panel:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;$('#my_id_prefix').attr('filepath', '/C')&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
::The attr function in jquery lets you set or get an HTML attribute of the elements you selected. So after you execute the code above, the affected element will look something like this:&lt;br /&gt;
::&amp;lt;pre&amp;gt;&amp;lt;div id=&amp;quot;my_id_prefix&amp;quot; filepath=&amp;quot;/C&amp;quot;&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
::'''attr''' with two parameters '''sets''' the attribute; '''attr''' with one parameter '''gets''' the attribute.&lt;br /&gt;
&lt;br /&gt;
::See the documentation for details: https://api.jquery.com/attr/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Nothing should happen yet. (both filepath and username have to be set before something happens)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now do the same to set the 'username' attribute to 'administrator'. The effective permissions panel should get populated with all checkboxes! (the administrator has full permissions on /C for all the scenarios).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Inspect''' the element of the effective permissions panel. it should now have the attributes you just set, and should look something like:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;div ...  filepath=&amp;quot;/C&amp;quot; username=&amp;quot;administrator&amp;quot;&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
::'''Tip:''' You can also edit the attributes directly in the Elements view of the dev console - just double-click on the attribute to edit its value.&lt;br /&gt;
&lt;br /&gt;
::This should have the same exact effect as calling '''.attr''' in the console.&lt;br /&gt;
&lt;br /&gt;
'''Question:''' Which permissions does the administrator have for /C?&lt;br /&gt;
&lt;br /&gt;
==Step 2.5: Try a different filepath==&lt;br /&gt;
In order to be able to test more interesting things, pick a more relevant filepath than &amp;quot;/C&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Choose one of the files that are relevant to the scenario you are testing this on: for example, if this is one of the scenarios about restricting the permissions for '''important_file.txt''', you can use the filepath for '''important_file.txt'''.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To quickly get the correct path for a given file, you can '''Inspect''' the permissions button for that file again, and look for the path attribute on that button. For example, the &amp;lt;button&amp;gt; element for '''important_file.txt''' looks something like this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;button ... path=&amp;quot;/C/presentation_documents/important_file.txt&amp;quot; ...&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Question: '''What does the html look like for your effective permissions panel now?&lt;br /&gt;
&lt;br /&gt;
==Step 3: add a user selector==&lt;br /&gt;
We want to add an interface element to allow us to select a user.&lt;br /&gt;
&lt;br /&gt;
Use the '''define_new_user_select_field''' function in '''view_helper.js''' to create such an element. for the third parameter, just use a blank function like so:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;function(selected_user) { }&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This function will be called whenever a new user is selected, and the parameter '''selected_user''' will contain the name of the newly selected user. (We'll put something useful inside it in the next step)&lt;br /&gt;
&lt;br /&gt;
'''append''' the user select field you just created to the same sidepanel element.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
::'''Tip: '''The order you append things in is the order they will appear in. The order you append things doesn't have to be the same as the order you define them. I like to define and configure a group of objects first, and then append them all. You can also try '''prepend''' to add things to the beginning instead of the end.&lt;br /&gt;
&lt;br /&gt;
::See also:&lt;br /&gt;
::https://api.jquery.com/append/&lt;br /&gt;
::https://api.jquery.com/prepend/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Try it out. There should be a (blank) field and a button. when you click on the button, a user selection dialog appears. When you select a user and click OK, the user appears in the field!&lt;br /&gt;
&lt;br /&gt;
But '''NOTHING else should happen yet. (we have to manually connect the user selector with the effective permissions panel)'''&lt;br /&gt;
&lt;br /&gt;
'''Question: '''What is your js code to create and add the user selection button/dialog?&lt;br /&gt;
&lt;br /&gt;
==Step 4: Connect the user selector and the effective permissions==&lt;br /&gt;
Whenever a user gets selected, we want to change the '''username''' attribute of our effective permissions panel to whoever was selected.&lt;br /&gt;
&lt;br /&gt;
The code to do that goes inside that blank '''function(selected_user){}''' you just made earlier. (Note: you can use as many newlines as you want inside the {})&lt;br /&gt;
&lt;br /&gt;
Use the same exact line of code that you used before to set the user to 'administrator', but set it to the '''selected_user''' parameter instead of''' 'administrator'.'''&lt;br /&gt;
&lt;br /&gt;
For the purpose of this tutorial, just hardcode the file path attribute. Use the same line of code as you used in the console to set the filepath - just put it somewhere in your code in view.js, so that the filepath gets set when the page loads.&lt;br /&gt;
&lt;br /&gt;
That should do it! Try selecting users to see their permissions for the file path you hard-coded in.&lt;br /&gt;
&lt;br /&gt;
'''Question:''' What does the completed line to create the user select field look like?&lt;br /&gt;
&lt;br /&gt;
==Recap==&lt;br /&gt;
&lt;br /&gt;
*We created an effective permissions panel.&lt;br /&gt;
:It listens for when its own '''filepath''' and '''username''' attributes change, and automatically loads the effective permissions for the given file and user.&lt;br /&gt;
*We then created a user-selector element.&lt;br /&gt;
:It gave us a UI for selecting a user.&lt;br /&gt;
*We connected the user selector to the effective permissions.&lt;br /&gt;
:We did this by changing the  '''username''' attribute of the '''effective permissions panel''' each time a user was selected in the '''user selector'''.&lt;br /&gt;
*Finally, we hardcoded a filepath attribute for the effective permissions panel.&lt;br /&gt;
:Now the effective permissions panel displays the permissions for that hard-coded file, for any user we choose through the user selector.&lt;br /&gt;
&lt;br /&gt;
=Permissions Explanation=&lt;br /&gt;
Now let's make those 'i' icons do something! Specifically, we will make each one open a dialog with an explanation of '''why''' the effective permission for a given file, user, and permission type is set that way.&lt;br /&gt;
&lt;br /&gt;
==Step 1: Define the dialog==&lt;br /&gt;
We will define '''a single dialog''' for the explanations, and open/close it programmatically, populating it with the right info. I strongly recommend following this pattern for this application: define '''a single dialog''' for each type of thing you want to show, instead of creating and destroying them on the fly.&lt;br /&gt;
&lt;br /&gt;
Use the function '''define_new_dialog''' in '''view_helper.js'''  to define a new (blank) dialog. This will return a jquery-ui dialog object.&lt;br /&gt;
&lt;br /&gt;
::'''Tip:''' The third parameter of the function in class '''Dialog''' just gets passed along to the jquery-ui dialog as the set of options to use in the dialog. It can be used to set things such as height/width of the dialog, buttons that are part of the dialog, etc.&lt;br /&gt;
&lt;br /&gt;
::If you don't want to set any extra options, you can just omit that parameter.&lt;br /&gt;
&lt;br /&gt;
::See https://jqueryui.com/dialog/ for examples and documentation&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Nothing should happen yet. (the dialog is invisible until we open it)'''&lt;br /&gt;
&lt;br /&gt;
==Step 2: Open the dialog on click==&lt;br /&gt;
Unlike a standard jquery-ui dialog, this one is configured to start out closed by default: we usually only want to open up dialogs when the user clicks on something.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In this case, we want to open the dialog each time one of the 'info' icons is clicked:&lt;br /&gt;
&lt;br /&gt;
Inspect one of these icons to see what classes they are using.&lt;br /&gt;
&lt;br /&gt;
*The classes that start with fa make that element magically turn into an Font Awesome icon.&lt;br /&gt;
*The other class is the one we will use to select all of these specific icons.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Using a class selector, select all the 'info' icons and attach a click listener to them:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;$('.my_class').click(function(){&lt;br /&gt;
&lt;br /&gt;
    // stuff that should happen on click goes here&lt;br /&gt;
&lt;br /&gt;
})&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
First, let's test that this on-click function works as expected. Add a line of code inside of that function to log a simple message, e.g.:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;console.log('clicked!')&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Check that it's working: does it say 'clicked!' in the console whenever you click any of the &amp;quot;info&amp;quot; icons?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now  that we know the click listener is working, add another line of code inside of it to open our blank dialog. (see comment for '''Dialog''' class for how to open jquery-ui dialogs).&lt;br /&gt;
&lt;br /&gt;
Test it out again: does a blank dialog show up each time you click one of the info icons?&lt;br /&gt;
&lt;br /&gt;
'''Question:''' What does your initial click listener look like?&lt;br /&gt;
&lt;br /&gt;
==Step 3: Log useful information==&lt;br /&gt;
Each time this dialog is opened, we'll want to put information about the current user, filename, and '''permission''' into it.&lt;br /&gt;
&lt;br /&gt;
First, try logging these three things to the dev console using console.log() inside the on-click function:&lt;br /&gt;
&lt;br /&gt;
*We can get the current username and filepath from the effective permissions element, like so:&lt;br /&gt;
::&amp;lt;pre&amp;gt;$('#my_id_prefix').attr('filepath')&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
::&amp;lt;pre&amp;gt;$('#my_id_prefix').attr('username')&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
::(recall that attr with two parameters '''sets''' the attribute; attr with one parameter '''gets''' the attribute.)&lt;br /&gt;
&lt;br /&gt;
*The relevant permission type is conveniently stored in the attribute '''permission_name''' of the 'info' icon we just clicked!&lt;br /&gt;
::Inside the click function, '''$( this )''' will get us the icon we just clicked.&lt;br /&gt;
&lt;br /&gt;
is it working? reload the page and click on some of the 'info' icons. Look at the dev console: is it outputting what you expect?&lt;br /&gt;
&lt;br /&gt;
'''Question:''' What does your full console log method look like (please include its class selector)?&lt;br /&gt;
&lt;br /&gt;
==Step 4: Get and display explanation==&lt;br /&gt;
&lt;br /&gt;
Now you have the username, filepath, and permission type inside the click function.&lt;br /&gt;
&lt;br /&gt;
*Use the function '''allow_user_action''' from '''model.js'''  to get whether the action is allowed, and the explanation for why.&lt;br /&gt;
**There is a bit of a '''gotcha''' here: what you have is a '''filepath''' and a '''username'''; what you need for this function is a '''file object''' and a '''user object'''.&lt;br /&gt;
:::*Use the object '''path_to_file''' (defined in controller.js ) to get the file object for a given path, e.g.:&lt;br /&gt;
:::&amp;lt;pre&amp;gt;my_file_obj_var = path_to_file[my_filename_var]&amp;lt;/pre&amp;gt;&lt;br /&gt;
:::*Likewise, use the object '''all_users''' to get the user object for a given username.&lt;br /&gt;
*Use the '''get_explanation_text''' function (in '''view_helper.js''') to go from explanation object to a string of (mostly) human-readable text.&lt;br /&gt;
*Add the explanation text to the dialog you just opened.&lt;br /&gt;
:You can use '''append()''' as before, though you might then have to '''empty()''' the dialog each time (otherwise the explanations just keep stacking…).&lt;br /&gt;
:Or you can try '''text()''' or '''html()''' to replace the contents each time.&lt;br /&gt;
**See jquery documentation for details and examples:&lt;br /&gt;
::https://api.jquery.com/append/&lt;br /&gt;
::https://api.jquery.com/empty/&lt;br /&gt;
::https://api.jquery.com/text&lt;br /&gt;
::https://api.jquery.com/html/&lt;br /&gt;
&lt;br /&gt;
That should do it! Some interesting types of permissions to look at the explanation for:&lt;br /&gt;
&lt;br /&gt;
*A &amp;quot;take ownership&amp;quot; permission for an administrator&lt;br /&gt;
*Any permission for anyone that's not an administrator on /C&lt;br /&gt;
*An inherited permission (this will only exist for some tasks)&lt;br /&gt;
*A permission set for a group, looking through the effective permissions of a member of that group (this will only exist for a couple of the tasks)&lt;br /&gt;
&lt;br /&gt;
'''Question:''' What does your final click handler look like?&lt;br /&gt;
&lt;br /&gt;
==Recap==&lt;br /&gt;
&lt;br /&gt;
*We defined a new empty '''dialog'''&lt;br /&gt;
*We added a '''click listener''' so that this dialog would open whenever any of the &amp;quot;info&amp;quot; icons are clicked&lt;br /&gt;
*We gathered the relevant information about what was clicked -  the '''file''', user, and '''permission name''' - and generated an explanation for that file/user/permission&lt;br /&gt;
*We put that explanation in the dialog, overwriting anything that was previously there.&lt;br /&gt;
&lt;br /&gt;
=Challenges / bonus ideas=&lt;br /&gt;
*Try changing '''getExplanationText''', or making your own function, to make the explanation text more human-readable&lt;br /&gt;
*Try setting the dialog options so that it has an &amp;quot;OK&amp;quot; button, and the dialog closes when you click that button (see https://jqueryui.com/dialog/ )&lt;br /&gt;
*Remember how you added text to the permissions button in the warm-up? Add that code to your '''view.js''' to make it permanent.&lt;br /&gt;
*Add a second button next to the permissions button for each file; make it so that when that button is clicked, the filepath attribute for our effective permissions panel is changed to that file.&lt;br /&gt;
**What happens when you click that button on a folder? Why doesn't that happen with the permissions button?&lt;br /&gt;
***it's because I fixed it. Look for the '''$('.permbutton')'''.click definition inside '''view.js.'''&lt;br /&gt;
****make sure you copy that emitter line too!&lt;br /&gt;
*Look through the other functions in  '''view_helper.js'''. There are define_* helpers for all or most of the major components for the baseline UI. Think about how you might use them in your UI. Is there something else you'd like to have, or something you're not sure how to do? tell me or post on Piazza.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Submission_Mechanics&amp;diff=264</id>
		<title>Submission Mechanics</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Submission_Mechanics&amp;diff=264"/>
		<updated>2023-02-08T03:45:26Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: Created page with &amp;quot;Submissions will happen via Canvas. You'll get a group &amp;quot;assignment&amp;quot; that will give you the urls to test and a link to a quiz where you will be able to fill in all of the data...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Submissions will happen via Canvas. You'll get a group &amp;quot;assignment&amp;quot; that will give you the urls to test and a link to a quiz where you will be able to fill in all of the data you collect. Be sure to save both the zoom recording and the data output. If we have to recreate your user tests or re-run them, you will lose credit for them.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Finishing_Up&amp;diff=263</id>
		<title>Finishing Up</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Finishing_Up&amp;diff=263"/>
		<updated>2023-02-08T03:43:10Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;# They will finish either by stating ‘I’m finished’ or when the timer goes off, whichever comes first.&lt;br /&gt;
# If this is you last task, stop recording. Otherwise, pause.&lt;br /&gt;
# Open the developer console and type &amp;quot;JSON.stringify(data)&amp;quot;. This should spit out a record of their activities on the website. Be sure to copy from '{ all the way to the closing }' and save a record of this.&lt;br /&gt;
# At this point, ask them if they have any questions or comments. Answer questions. Record the comments to pass back to the relevant group.&lt;br /&gt;
# Thank them for their help.&lt;br /&gt;
# If you are testing again with the same site, refresh the page.&lt;br /&gt;
# If they are willing to do multiple tasks, then go back to Step 0.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Finishing_Up&amp;diff=262</id>
		<title>Finishing Up</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Finishing_Up&amp;diff=262"/>
		<updated>2023-02-08T03:37:53Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: Created page with &amp;quot;# They will finish either by stating ‘I’m finished’ or when the timer goes off, whichever comes first. # If this is you last task, stop recording. Otherwise, pause. # At...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;# They will finish either by stating ‘I’m finished’ or when the timer goes off, whichever comes first.&lt;br /&gt;
# If this is you last task, stop recording. Otherwise, pause.&lt;br /&gt;
# At this point, ask them if they have any questions or comments. Answer questions. Record the comments to pass back to the relevant group.&lt;br /&gt;
# Thank them for their help.&lt;br /&gt;
# If they are willing to do multiple tasks, then go back to Step 0.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Recording_Observations&amp;diff=261</id>
		<title>Recording Observations</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Recording_Observations&amp;diff=261"/>
		<updated>2023-02-08T03:34:56Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: Created page with &amp;quot;Bring out your best poker face. Don’t say anything, don’t react in any way to what happens, just let them do what they are going to do.  While they work, write down all th...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Bring out your best poker face. Don’t say anything, don’t react in any way to what happens, just let them do what they are going to do.&lt;br /&gt;
&lt;br /&gt;
While they work, write down all the page navigation that happen and their approximate times:&lt;br /&gt;
&lt;br /&gt;
* Index.html 0&lt;br /&gt;
* Page2.html 15s&lt;br /&gt;
* Page3.html 48s&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=User_Instructions&amp;diff=260</id>
		<title>User Instructions</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=User_Instructions&amp;diff=260"/>
		<updated>2023-02-08T03:31:23Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;You'll want to introduce your participant to what they will be doing and establish the ground rules. Sometimes it helps to prepare a simple script or even just a short set of bullet points to make sure that you say everything you need to. For example:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;I am working on a class project to improve the Wash U Nursery School’s website. As part of this, I need to observe people trying to use the site to find the answers to common questions. Would you be willing to help? I’ll ask you to complete three tasks, each one will take no more than 2 minutes.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
If, yes:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Great, thank you. I’m going to show you the website and task. Once you start, I won’t be able to answer any questions until you are finished. But, please talk aloud as you work, your thought process is really valuable in trying to understand what is and isn’t working&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Start zoom recording.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;This is the nursery school site. At the top of the page is a box that shows the task you should complete and provides a textbox where you can enter the answer that you find. If you can’t find the answer by the end, it’s fine to just write 'couldn’t find it'.&lt;br /&gt;
&lt;br /&gt;
Feel free to start when you’re ready. I’ll let you know when 2 minutes are up. If you finish before that, please tell me 'I am finished'&amp;quot;&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=User_Instructions&amp;diff=259</id>
		<title>User Instructions</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=User_Instructions&amp;diff=259"/>
		<updated>2023-02-08T03:29:30Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: Created page with &amp;quot;You'll want to introduce your participant to what they will be doing and establish the ground rules. Sometimes it helps to prepare a simple script or even just a short set of...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;You'll want to introduce your participant to what they will be doing and establish the ground rules. Sometimes it helps to prepare a simple script or even just a short set of bullet points to make sure that you say everything you need to. For example:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;I am working on a class project to improve the Wash U Nursery School’s website. As part of this, I need to observe people trying to use the site to find the answers to common questions. Would you be willing to help? I’ll ask you to complete three tasks, each one will take no more than 2 minutes.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
If, yes:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Great, thank you. I’m going to show you the website and task. Once you start, I won’t be able to answer any questions until you are finished. But, please talk aloud as you work, your thought process is really valuable in trying to understand what is and isn’t working&amp;quot;&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Record_Demographics&amp;diff=258</id>
		<title>Record Demographics</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Record_Demographics&amp;diff=258"/>
		<updated>2023-02-08T03:26:49Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Ask potential participants the following questions:&lt;br /&gt;
&lt;br /&gt;
#Have you ever looked at the Nursery School website?&lt;br /&gt;
#Are you an HCI minor?&lt;br /&gt;
&lt;br /&gt;
If participants answer no to both, then you they are appropriate participants. Ideally, we want a diverse group of users so try to recruit people with differing backgrounds.&lt;br /&gt;
&lt;br /&gt;
Please also your participant's major and year (freshman, sophomore, etc).&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Record_Demographics&amp;diff=257</id>
		<title>Record Demographics</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Record_Demographics&amp;diff=257"/>
		<updated>2023-02-08T03:25:44Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: Created page with &amp;quot;Ask potential participants the following questions:  #Have you ever looked at the Nursery School website? #Are you an HCI minor?  If participants answer no to both, then you t...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Ask potential participants the following questions:&lt;br /&gt;
&lt;br /&gt;
#Have you ever looked at the Nursery School website?&lt;br /&gt;
#Are you an HCI minor?&lt;br /&gt;
&lt;br /&gt;
If participants answer no to both, then you they are appropriate participants. Ideally, we want a diverse group of users so try to recruit people with differing backgrounds.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Preparing_for_a_User_Test&amp;diff=256</id>
		<title>Preparing for a User Test</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Preparing_for_a_User_Test&amp;diff=256"/>
		<updated>2023-02-08T03:23:22Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: Created page with &amp;quot;# Open a browser and navigate to the site/task you are testing. # Open zoom - You'll need to record your user test so that we can recreate any data that gets missed. (I recomm...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;# Open a browser and navigate to the site/task you are testing.&lt;br /&gt;
# Open zoom - You'll need to record your user test so that we can recreate any data that gets missed. (I recommend recording to your local machine.)&lt;br /&gt;
# Share screen with your browser so that what it will see is site you are testing.&lt;br /&gt;
# Make sure that you can see the task your participant is supposed to see (and verify it's the correct one).&lt;br /&gt;
# Get a 2 minute timer ready (I typically use my phone)&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Information_Foraging_Assignment:_Nursery_School&amp;diff=255</id>
		<title>Information Foraging Assignment: Nursery School</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Information_Foraging_Assignment:_Nursery_School&amp;diff=255"/>
		<updated>2023-02-08T03:10:05Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: /* Submission */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Task Description=&lt;br /&gt;
Washington University hosts and on-site nursery school for children ages 2.5-5 years old. In this&lt;br /&gt;
project, we are going to work to improve nursery school site visitors’ ability to find relevant&lt;br /&gt;
information using Information Foraging Theory. Information Foraging Theory describes how&lt;br /&gt;
users search for information using different cues.&lt;br /&gt;
&lt;br /&gt;
Specifically, we will study the following scenarios:&lt;br /&gt;
# '''Math:''' You are a parent considering sending your child to Washington University Nursery School. You’ve learned that the curriculum is play-based and you want to know how learning is incorporated into a play-based context. You have some ideas about how language learning might happen, but are less sure about math. Find some examples of how math learning is incorporated at Washington University Nursery School.&lt;br /&gt;
# '''School Day: '''  You are investigating pre-school options for your 4 year old. Both you and your spouse work, so you need to fully understand what scheduling constraints each option involves. One of your schools of interest is the Washington University Nursery School. When does school start and end each day? What is the longest period of time that your child can be there?&lt;br /&gt;
# '''Teacher Tenure: ''' You are investigating pre-school options for your 3.5 year old. You’ve been told that one of the hallmarks of a good program is teachers who have been there for a long time. You want your child to attend in the mornings only. Which teachers would your child have and how long have they been at the school?&lt;br /&gt;
# '''Summer Camp: ''' You are starting to look at summer camp options and have heard good things about Washington University Nursery School for young children. What are the daily camp hours? Are there any extended day opportunities?&lt;br /&gt;
# '''Discipline: ''' You are investigating pre-school options for your spirited 3 year old and want to understand their approach to discipline. How do teachers at Washington University approach discipline?&lt;br /&gt;
# '''Spanish Song: '''  Your daughter is in the Teddy Bear class at Washington University Nursery School. She came home this week singing a song in Spanish about shapes, but you are pretty sure that she has some of the words wrong. What are the correct lyrics?&lt;br /&gt;
#'''Books: ''' It is mid-December, 2020 and you are thinking about things to do over your daughter's upcoming school break. She is 3 years old and attends the Washington University Nursery School and is in the Teddy Bear classroom. You are planning a trip to the library and want to check out some books that connect with something she is doing in school. What are some potential book topics that relate to something that is going on in her classroom this week?&lt;br /&gt;
#'''Admission-2: ''' You are a parent with a child who has just been accepted to attend as a full time student at the Washington University Nursery School. You want to accept the offer of admission. Figure out what you need to do at this time to finalize your child’s place at the school.&lt;br /&gt;
#'''Deposit: ''' You are a parent with a child who has just been accepted to attend as a full time student at the Washington University Nursery School. You need to pay one month of tuition as a deposit. Find out how much one month of tuition is and whether or not it is possible to pay online.&lt;br /&gt;
#'''Personalized Help: '''You are moving to St. Louis from Beijing and looking for a Pre-K program for your daughter, age 5. She is very close to her friends and you are worried that the move might be hard on her. She may need some extra support from her new teachers learning English, adapting to American culture, and making new friends. How does the Washington University Nursery School staff approach providing extra help to students who need it? (note: answer is the curriculum overview where it talks about how to provide extra help for individual students)&lt;br /&gt;
#'''Communication: '''You are looking at Nursery Schools for your soon to be 3 year old. He has never been in school or daycare before and you are somewhat worried about the transition. You'd like to ensure that you'll be able to have strong communication at his new school. How does the Washington University Nursery School handle communicating with parents? (note: answer is in the parent handbook under communication)&lt;br /&gt;
#'''Science: '''It’s mid-December and your son, age 4, came home all excited about science class. They learned a new word, but he can’t actually remember the word they learned about. What was the topic of his recent science class?&lt;br /&gt;
#'''Parent/Teacher Conferences: '''You are selecting a pre-school, but want to be sure that your daughter will be ready for kindergarten when it’s time. How does the nursery school assess children’s knowledge, support their growth, and share the results with parents?&lt;br /&gt;
#'''Orientation: '''You have recently accepted a position for your child for the coming school year at the Washington University Nursery School. Up to this point, your child has been at home and you are somewhat worried about the transition. How does the nursery school support kids’ transitions into school?&lt;br /&gt;
&lt;br /&gt;
=Grading=&lt;br /&gt;
For each project, you will get assigned three tasks to test for that round. For the first round, these will be randomly chosen. For subsequent rounds, we will carry two of your previous tasks forward. You can submit up to three versions (see deadlines on the calendar). For each task, we'll assign a score that captures the degree to which participants completed it correctly (got the right answer) and efficiently (took the fastest path to get there). To get credit for a task, you need to outperform the baseline score by 20% for that task. Overall project grades will be:&lt;br /&gt;
* 93: 3 tasks that perform &amp;gt;20% over the baseline, spread across any iteration.&lt;br /&gt;
* 88: 2 tasks that perform &amp;gt;20% over the baseline, spread across any iteration.&lt;br /&gt;
* 83: 1 task that performs &amp;gt;20% over the baseline, in any iteration.&lt;br /&gt;
&lt;br /&gt;
Then you can earn bonus points as follows:&lt;br /&gt;
&lt;br /&gt;
* +7: all three tasks in a single iteration (Note: only your largest multi-task bonus will count)&lt;br /&gt;
* +3: two tasks in a single iteration (Note: only your largest multi-task bonus will count)&lt;br /&gt;
* +2: one of the top 3 performing tasks in the class (Note: you can earn this bonus for multiple tasks)&lt;br /&gt;
&lt;br /&gt;
=Prerequisite Readings=&lt;br /&gt;
The goal of this assignment is use the ideas of information foraging to improve users' abilities to find information on the Washington University Nursery School site. As you work on your redesign you should be thinking about the information search process and trying to restructure and reorganize the information such that users can navigate it more easily.&lt;br /&gt;
&lt;br /&gt;
# [http://people.ischool.berkeley.edu/~hearst/research/scattergather.html Scatter/Gather]&lt;br /&gt;
# [https://devaka.ru/wp-content/uploads/2008/11/UIR-1995-07-Pirolli-CHI95-Foraging.pdf Information Foraging in Information Access Environments]&lt;br /&gt;
&lt;br /&gt;
=Getting Started=&lt;br /&gt;
==Cloning the Information Foraging Baseline Code==&lt;br /&gt;
We are hosting our repositories using github this semester. That means you will get a new repository for each of our three projects. When you accept an assignment through github classroom, it will create a repository for you based on the template that we've defined as the starting point for everyone.&lt;br /&gt;
&lt;br /&gt;
# First, accept the assignment from github. Once the assignment is ready to go live, we will update the link here.&lt;br /&gt;
# Navigate to your cloned repository on github. You can get there by reloading the &amp;quot;generating your repository&amp;quot; page. Git hub will give you a link when it's ready. It should have a url something like: &amp;lt;nowiki&amp;gt;https://github.com/cse-256-f22/information_foraging-YOUR_GITHUB_ID-wustl&amp;lt;/nowiki&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==Setting Up Pages==&lt;br /&gt;
To see what your version of the nursery school site looks like, you can view it through github pages. This will also be how mTurk users will view and interact with your site, so it's important to get going even if you plan to develop fully locally.&lt;br /&gt;
# Go the the settings tab and scroll down to the bottom.&lt;br /&gt;
# Change the repository visibility to 'public.'&lt;br /&gt;
# Enable github Pages. Select the 'main' branch and the 'root' directory to serve pages from. &lt;br /&gt;
# Once you hit save, github will add a link to your hosted pages so that you can see them.&lt;br /&gt;
&lt;br /&gt;
=Baseline Code=&lt;br /&gt;
Your repository contains the baseline version of the Nursery School site. Your assignment is to adapt that codebase to improve users' task performance. Within your top level repository directory you will find a subfolder called '''files''' that contains all of the HTML and CSS files you should need to edit for this project. If you would like to edit the JS of your site then do so in the '''scripts/ts/dynamic-dom''' folder.&lt;br /&gt;
&lt;br /&gt;
To run the site locally, do these steps:&lt;br /&gt;
# Open a terminal window or the terminal in your code editor.&lt;br /&gt;
# Navigate to your repository folder. This should be something like: information-foraging-&amp;lt;YOUR_GITHUB_ID&amp;gt;-wustl.&lt;br /&gt;
# Type in:&lt;br /&gt;
 '''npm install'''&lt;br /&gt;
 '''npm run dev'''&lt;br /&gt;
# This will open the Nursery School site running at http://localhost:3000/ in a web browser.&lt;br /&gt;
## You may notice a couple of alerts that pop up in your browser. This is because the URL is missing some information that the site expects to be there. If you would like these alerts not to show up, then use something like this URL in your browser instead: http://localhost:3000/?wustl_key=riley.mccuen.testing&amp;amp;sandbox=false&amp;amp;project=information-foraging&amp;amp;iteration=1&amp;amp;tag=books&lt;br /&gt;
## Feel free to configure the query string in in that url if you would like, but either way it should get rid of the alerts that show up on page reload.&lt;br /&gt;
# When you want to stop the web server you can press 'CTRL+C' and the server should shut down.&lt;br /&gt;
&lt;br /&gt;
=Introductory Studio=&lt;br /&gt;
The goal of this studio is to introduce you to the basic set of skills that you will need in order to begin modifying the nursery school site. While you won't emerge at the end of this knowing everything there is to know about HTML, CSS, and JavaScript, this should give you enough to be able to modify the starting code we've given you.&lt;br /&gt;
&lt;br /&gt;
[[Information Foraging Studio]]&lt;br /&gt;
&lt;br /&gt;
=Adding Javascript to Your Site=&lt;br /&gt;
When you find yourself wanting to add javascript there is one way we recommend doing it ('''NOTE''' if you do not do it this way it may not work as expected). &lt;br /&gt;
# Create a new file in the information-foraging/scripts/ts/dynamic-dom/ directory in your repository. If you are only using javascript then feel free to make a .js file, but it is recommended to use typescript which would be a .ts file. Both types of files will be included if used and imported properly. ('''NOTE''' regardless of whether or not you use TS you need to include it in the '''ts'''/dynamic-dom/ directory and import it into dynamic-dom.ts otherwise the build script will not bundle it.)&lt;br /&gt;
# Write your code in that new file.&lt;br /&gt;
# Import that file into dynamic-dom.ts and initialize it using a static initializer like you see is being done with the accordion and slideshow elements.&lt;br /&gt;
## Alternatively, if you only have a small amount of code and do not think that you need a whole new file then you can put your code directly in the information-foraging/scripts/ts/dynamic-dom/dynamic-dom.ts file.&lt;br /&gt;
# If your code is in script tags inlined into the html or not initialized through the dynamic-dom.ts file it will either not show up on your page or cause numerous runtime errors. Keep in mind, if you open your developer's console in your browser and there are red errors then that means your code is broken and needs to be fixed.&lt;br /&gt;
# Your code will need to be rebuilt in order to see these changes on your site.&lt;br /&gt;
Here is how you should write your code and import it, there is an example for both a .js file and .ts file but you only need to have one of them:&lt;br /&gt;
&lt;br /&gt;
This is for the javascript version in the file /information-foraging/scripts/ts/dynamic-dom/sticky.js&lt;br /&gt;
 export function setupSticky() {&lt;br /&gt;
    // TODO: Copy and paste your sticky code in here!!&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
This is for the typescript version in the file /information-foraging/scripts/ts/dynamic-dom/sticky.ts&lt;br /&gt;
 export function setupSticky() {&lt;br /&gt;
    // TODO: Copy and paste your sticky code in here!!&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
Now that you have your code in sticky.(j|t)s, put the bolded code below in the file /information-foraging/scripts/ts/dynamic-dom/dynamic-dom.ts:&lt;br /&gt;
 import { Accordion } from './accordion';&lt;br /&gt;
 import { Slideshow } from './slideshow';&lt;br /&gt;
 '''import { setupStickey } from './stickey';'''&lt;br /&gt;
 &lt;br /&gt;
 // Put all function calls that need to be made on every page load inside the setupAll function body.&lt;br /&gt;
 export function PutStudentPageLoadOperationsInsideThisStudentBody() {&lt;br /&gt;
     // TODO: Put all operations that you want to happen on ever page load in this function.&lt;br /&gt;
     // For example you could write: Sticky.setup()&lt;br /&gt;
     '''setupStickey();'''&lt;br /&gt;
 }&lt;br /&gt;
Like the comment says you can ''Put all function calls that need to be made on every page load inside the setupAll function body'' or you can put it into the PutStudentPageLoadOperationsInsideThisStudentBody function, either way it will work and is up to you.&lt;br /&gt;
&lt;br /&gt;
=Testing Your Site=&lt;br /&gt;
&lt;br /&gt;
To test your site, you need to do two things: &lt;br /&gt;
# Commit and push your code to Github. It may take a couple of minutes, but your changes will eventually be reflected in your Github pages site.&lt;br /&gt;
&amp;lt;!-- # Submit a sandbox hit that you can try out. ([[Submitting Sandbox HITs]])--&amp;gt;&lt;br /&gt;
# If you open your developer's console in your browser and see red errors, then something is broken and will be broken when you submit your hits. You must fix it.&lt;br /&gt;
&lt;br /&gt;
==Uploading to Github Pages==&lt;br /&gt;
To test or submit your project, you'll first need to upload your to Github.&lt;br /&gt;
&lt;br /&gt;
# If you've made changes to javascript and/or typescript code, please rebuild your code to get the new changes. (see [[Node Setup]] - step 6)&lt;br /&gt;
# Test your site locally via localhost (see [[Running Sites Locally]])&lt;br /&gt;
# Commit and push your changes (see [https://code.visualstudio.com/docs/editor/versioncontrol Version Control in VS Code])&lt;br /&gt;
# It will take a few minutes but your Github pages site will eventually reflect your changes.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- ==Making a Sandbox HIT==&lt;br /&gt;
If you want to see what your MTurk workers will see, you can submit a sandbox hit. &lt;br /&gt;
&lt;br /&gt;
# This page offers a walkthrough on how to do that. ([[Submitting Sandbox HITs]])&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot (14).png|thumb|Worker Sandbox with relevant ui elements highlighted.]] --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Ground Rules=&lt;br /&gt;
&lt;br /&gt;
The nursery school has selected what content they make available on their website. We may not entirely agree with that selection, but it is our job to figure out how to present it in a way that enables end users to find the information they need. So, it is fair game (and encouraged) to reorganize the structure of the information. However, you may not remove access to information, even if it is not needed for the tasks we are testing. Further, I reserve the right to introduce new tasks without warning. Your best strategy is to holistically work towards a well structured site with good information scent.&lt;br /&gt;
&lt;br /&gt;
=Best Practice Videos=&lt;br /&gt;
It seems pretty clear from looking at the sites you guys created that everyone has gotten the basic ideas around increasing the information density related to a given topic by grouping related information and increasing the information scent through the use of the right words and surrounding content. In going through the comments and the top solutions, I was looking to pull out some best practices that might not have been as obvious to give you one more set of tools that can help you think about information foraging into the future. These are a set of quick videos discussing some best practices in the context of the Nursery School Site.&lt;br /&gt;
&lt;br /&gt;
#[https://drive.google.com/file/d/1M7SRGYxawdlQrGtgNsKmC_MNmZzoifZV/view?usp=sharing Visible Exits]&lt;br /&gt;
#[https://drive.google.com/file/d/1HydDPrebZfj8d5yOHJiOl7IcSh4_VqB0/view?usp=sharing Intrapage Scent]&lt;br /&gt;
#[https://drive.google.com/file/d/1rpw0dRaADY7MzDwp6F6aIqNf_PxJyQFF/view?usp=sharing Promote High-Value Information]&lt;br /&gt;
#[https://drive.google.com/file/d/1FjGN5NNVvsW2fQTnR60a-zyh_tr2evZz/view?usp=sharing Overfitting]&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=MediaWiki:Sidebar&amp;diff=254</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=MediaWiki:Sidebar&amp;diff=254"/>
		<updated>2023-02-01T19:08:04Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
* navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
*Environment Setup&lt;br /&gt;
**Software_to_Install|Software to Install&lt;br /&gt;
**Node_Setup|Node.js Setup&lt;br /&gt;
**Clone_Your_Repository|Clone Your Repository&lt;br /&gt;
**Account_Setup|Account Setup&lt;br /&gt;
**Running_Sites_Locally|Running Sites Locally&lt;br /&gt;
**Testing_Your_Site|Testing Your Site&lt;br /&gt;
* Assignments&lt;br /&gt;
** Information_Foraging_Assignment:_Nursery_School|Information Foraging: Nursery School&lt;br /&gt;
** GenderMag_Assignment:_File_Permissions|GenderMag: File Permissions&lt;br /&gt;
** Cognitive_Load_Theory_Assignment:_Set|Cognitive Load Theory: Set&lt;br /&gt;
*User Testing&lt;br /&gt;
**Preparing_for_a_User_Test|Preparing for a User Test&lt;br /&gt;
**Record_Demographics|Record Demographics&lt;br /&gt;
**User_Instructions|User Instructions&lt;br /&gt;
**Recording_Observations|Recording Observations&lt;br /&gt;
**Finishing_Up|Finishing Up&lt;br /&gt;
**Submission_Mechanics|Submission Mechanics&lt;br /&gt;
&lt;br /&gt;
* SEARCH&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Main_Page&amp;diff=253</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Main_Page&amp;diff=253"/>
		<updated>2023-02-01T19:05:21Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Environment Setup=&lt;br /&gt;
[[Software_to_Install|Software to Install]]&lt;br /&gt;
&lt;br /&gt;
[[Clone_Your_Repository|Clone Your Repository]]&lt;br /&gt;
&lt;br /&gt;
[[Node_Setup|Node.js Setup]]&lt;br /&gt;
&lt;br /&gt;
[[Account_Setup|Account Setup]]&lt;br /&gt;
&lt;br /&gt;
[[Running_Sites_Locally|Running Sites Locally]]&lt;br /&gt;
&lt;br /&gt;
=Assignments=&lt;br /&gt;
[[Information_Foraging_Assignment:_Nursery_School|Information Foraging: Nursery School]]&lt;br /&gt;
&lt;br /&gt;
[[Problem_Solving_Assignment:_File_Permissions|Problem Solving: File Permissions]]&lt;br /&gt;
&lt;br /&gt;
[[Cognitive_Load_Theory_Assignment:_Set|Cognitive Load Theory: Set]]&lt;br /&gt;
&lt;br /&gt;
=User Testing=&lt;br /&gt;
[[Preparing_for_a_User_Test|Preparing for a User Test]]&lt;br /&gt;
&lt;br /&gt;
[[Record_Demographics|Record Demographics]]&lt;br /&gt;
&lt;br /&gt;
[[User_Instructions|User Instructions]]&lt;br /&gt;
&lt;br /&gt;
[[Recording_Observations|Recording Observations]]&lt;br /&gt;
&lt;br /&gt;
[[Finishing_Up|Finishing Up]]&lt;br /&gt;
&lt;br /&gt;
[[Submission_Mechanics|Submission Mechanics]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]&lt;br /&gt;
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]&lt;br /&gt;
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Clone_Your_Repository&amp;diff=252</id>
		<title>Clone Your Repository</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Clone_Your_Repository&amp;diff=252"/>
		<updated>2023-01-28T03:26:41Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: /* Repository Invites */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These instructions will guide you through setting up your repository and running the Nursery School codebase using Git, VSCode, and a localhost server. You are not required to use this setup, but we’ll probably be better able to help with any problems that arise if you do.&lt;br /&gt;
&lt;br /&gt;
=Repository Invites=&lt;br /&gt;
This semester, we are going to use Github classroom to create assignment repositories. We have added everyone to the github classroom. To avoid making the assignment link public to the world, see the Information Foraging Studio Prep [https://classes.engineering.wustl.edu/cse256a/index.php?title=Node_Setup assignment] that steps you through how to accept the assignment and clone your repository.&lt;br /&gt;
&lt;br /&gt;
=Setting up Your Repository through VSCode =&lt;br /&gt;
You can clone your repository in VSCode using the instructions on the following page: [https://code.visualstudio.com/docs/editor/versioncontrol#_cloning-a-repository Cloning a Repository]&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Problem_Solving_Assignment:_File_Permissions&amp;diff=238</id>
		<title>Problem Solving Assignment: File Permissions</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Problem_Solving_Assignment:_File_Permissions&amp;diff=238"/>
		<updated>2022-11-13T20:15:29Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: /* Top 3 Solutions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Task Description=&lt;br /&gt;
The goal of this assignment is to use a GenderMag analysis to improve a File Permissions interface that is highly similar to the one used in Windows 10. We've developed a series of tasks that combine different kinds of tasks and system states to evaluate the overall system effectiveness. For each scenario, you will see a simplified file system management interface. In this project, you users will be given a scenario and asked to modify the file permissions to achieve a goal presented in that scenario. &lt;br /&gt;
&lt;br /&gt;
Specifically, we'll evaluate the following scenarios:&lt;br /&gt;
&lt;br /&gt;
==Easy==&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_remove_direct_permission.html Remove some permissions from employee (V1)] (remove_direct_permission) Baseline = 0.96; Passing Score &amp;gt;= 1.15&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_add_new_user.html Add permissions for a new employee] (add_new_user) Baseline = 1.27; Passing Score &amp;gt;= 1.52&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_add_full_permissions.html Add permissions for a manager] (add_full_permissions) Baseline = 1.96; Passing Score &amp;gt;= 2.35&lt;br /&gt;
&lt;br /&gt;
==Medium==&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_remove_inherited_permission.html Remove some permissions from employee (V2)] (remove_inherited_permission) Baseline =  1.63; Passing Score &amp;gt;= 1.95&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_intern_permissions.html Add permissions for an intern] (intern_permissions) Baseline = 0.9; Passing Score &amp;gt;= 1.08&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_remove_user_with_inheritance.html Remove ALL permissions from employee] (remove_user_with_inheritance) Baseline = 1.34; Passing Score &amp;gt;= 1.60&lt;br /&gt;
&lt;br /&gt;
==Hard==&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_restrict_group_member.html Remove some permissions from employee (V3)] (restrict_group_member) Baseline = 0.97; Passing Score &amp;gt;= 1.16&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_let_ta_modify.html Fix permissions for a teaching assistant] (let_ta_modify) Baseline = 0; Passing Score &amp;gt;= 0.2&lt;br /&gt;
# [https://yana-nursery.s3.us-east-2.amazonaws.com/permissions-draft/wrapper_lost_inheritance.html Fix permissions for all users] (wrapper_lost_inheritance) Baseline = 1.13; Passing Score &amp;gt;= 1.35&lt;br /&gt;
&lt;br /&gt;
=Grading=&lt;br /&gt;
&lt;br /&gt;
For each project, you will get assigned three tasks to test for that round: one each from easy, medium, and hard. For the first round, these will be randomly chosen. For subsequent rounds, we will carry two of your previous tasks forward. You can submit up to three versions (see deadlines on the calendar). For each task, we'll assign a score that captures the degree to which participants granted the correct permissions (what percent of the correct permissions do they have) and didn't grant the incorrect permissions (what percentage of the permissions that they shouldn't have that they don't) and efficiently (took the fastest path to get there). To get credit for a task, you need to outperform the baseline score by 20% for that task. Overall project grades will be:&lt;br /&gt;
&lt;br /&gt;
* 93: 3 tasks that perform &amp;gt;20% over the baseline, spread across any iteration.&lt;br /&gt;
* 88: 2 tasks that perform &amp;gt;20% over the baseline, spread across any iteration.&lt;br /&gt;
* 83: 1 task that performs &amp;gt;20% over the baseline, in any iteration.&lt;br /&gt;
Then you can earn bonus points as follows:&lt;br /&gt;
&lt;br /&gt;
* +7: all three tasks in a single iteration&lt;br /&gt;
* +3: two tasks in a single iteration&lt;br /&gt;
* +2: one of the top 3 performing tasks in the class (Note: you can earn this bonus for multiple tasks)&lt;br /&gt;
&lt;br /&gt;
=Prerequisite Readings=&lt;br /&gt;
=Baseline Code=&lt;br /&gt;
Your repository contains the baseline version of the file permissions interface. Your assignment is to adapt that codebase to improve users' task performance using the ideas presented in Gender Mag. Within your top level repository directory, you should find a subfolder called '''gender-mag.''' Inside this folder, you will find the HTML files and JS files you'll need to edit. There are also wrappers HTML files that you can use to see the different scenarios.&lt;br /&gt;
&lt;br /&gt;
To run the site locally, follow the directions in [[Running Sites Locally]].&lt;br /&gt;
&lt;br /&gt;
Two things to note:&lt;br /&gt;
# index.html loads the interface with no scenario, but since the scenario is tied to the interface, this isn't really a useful view. For development purposes, you may want to try starting with '''student_index.html''' which gives you a list of the scenarios to click on.&lt;br /&gt;
# By default, there is a survey that we'll ask mTurk workers to take that gets at their alignments with the different gender-mag facets. At development time, it's pretty annoying to have to click through it every time. To turn this off, you can go to view_baseline.js. Then, on the first line of the file set '''show_starter_dialogs = false'''&lt;br /&gt;
&lt;br /&gt;
=Introductory Studio=&lt;br /&gt;
&lt;br /&gt;
[[GenderMag Studio]]&lt;br /&gt;
&lt;br /&gt;
=Testing Your Solutions=&lt;br /&gt;
&lt;br /&gt;
To determine whether your solution to a given scenario is correct you can:&lt;br /&gt;
# Complete the steps necessary to change the permissions to a state you believe is correct.&lt;br /&gt;
# Open the developer console in your browser.&lt;br /&gt;
# Type in '''validate_and_get_logs()'''. If your solution is correct, this will generate a long text blurb that will be what you need to include with your submission quiz. If your solution is not correct, you will get a list of erroneous permissions.&lt;br /&gt;
# You can also type in '''show_correct_permissions()''' to see what the correct set of permissions is.&lt;br /&gt;
&lt;br /&gt;
=Testing Your Site=&lt;br /&gt;
&lt;br /&gt;
To test your site, you need to do two things: &lt;br /&gt;
#Set up Github Pages &lt;br /&gt;
# Commit and push your code to Github. It may take a couple of minutes, but your changes will eventually be reflected in your Github pages site.&lt;br /&gt;
# Submit a sandbox hit that you can try out. ([[Submitting Sandbox HITs]])&lt;br /&gt;
# If you open your developer's console in your browser and see red errors, then something is broken and will be broken when you submit your hits. You must fix it.&lt;br /&gt;
&lt;br /&gt;
==Setting Up Pages==&lt;br /&gt;
To see what your version of the file permissions interface, you can view it through github pages. This will also be how mTurk users will view and interact with your site, so it's important to get going even if you plan to develop fully locally.&lt;br /&gt;
# From your github repository, go the the settings tab and scroll down to the bottom.&lt;br /&gt;
# Change the repository visibility to 'public.'&lt;br /&gt;
# Enable github Pages. Select the 'main' branch and the 'root' directory to serve pages from. &lt;br /&gt;
# Once you hit save, github will add a link to your hosted pages so that you can see them.&lt;br /&gt;
&lt;br /&gt;
==Uploading to Github Pages==&lt;br /&gt;
To test or submit your project, you'll first need to upload your to Github.&lt;br /&gt;
&lt;br /&gt;
# If you've made changes to javascript and/or typescript code, please rebuild your code to get the new changes. (see [[Node Setup]] - step 6)&lt;br /&gt;
# Test your site locally via localhost (see [[Running Sites Locally]])&lt;br /&gt;
# Commit and push your changes (see [https://code.visualstudio.com/docs/editor/versioncontrol Version Control in VS Code])&lt;br /&gt;
# It will take a few minutes but your Github pages site will eventually reflect your changes.&lt;br /&gt;
&lt;br /&gt;
==Making a Sandbox HIT==&lt;br /&gt;
If you want to see what your MTurk workers will see, you can submit a sandbox hit. &lt;br /&gt;
&lt;br /&gt;
# This page offers a walkthrough on how to do that. ([[Submitting Sandbox HITs]])&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot (14).png|thumb|Worker Sandbox with relevant ui elements highlighted.]]&lt;br /&gt;
&lt;br /&gt;
=Submission=&lt;br /&gt;
For Iteration 0, you only need to push your changes to github and submit the canvas quiz stating that you've done so.&lt;br /&gt;
&lt;br /&gt;
For Iterations 1-3:&lt;br /&gt;
# Just as with testing, the first step in submitting your project is to push your changes to your github repo. &lt;br /&gt;
# Keep in mind that your project will be tested by actual users on Mechanical Turk. If it breaks and they can't get paid, they may well rate you poorly as a requestor which can create challenges for you to get good data going forward. Please test your submission on Github pages and via a sandbox hit before you declare it ready to go.&lt;br /&gt;
# After you've tested your submission, please make sure that you have $10 in your Mechanical Turk account.&lt;br /&gt;
# Last, please fill out the canvas submission form for the current iteration. This serves as your declaration that we can safely submit real HITs for you. We will randomly choose three of the tasks to test. For future iterations, we’ll keep two tasks the same and then choose a different third task. This is intended to keep disincentivize degenerate designs while also giving you an opportunity to iterate.&lt;br /&gt;
&lt;br /&gt;
Note: when filling out the submission form, it will ask you for your log data. If you have not changed the basic flow of the interface (your changes add supplemental information but don't change what a user needs to do), you can answer &amp;quot;same&amp;quot; for all of these questions. &lt;br /&gt;
&lt;br /&gt;
If you have made changes, then you'll need to do the following:&lt;br /&gt;
&lt;br /&gt;
#For each changed scenario, navigate to the corresponding wrapper_*.html page in your version of the interface. &lt;br /&gt;
#Solve the scenario in as few clicks as possible in your interface. &lt;br /&gt;
#Once you think you have achieved the correct permissions required in the scenario, open the JavaScript console in your browser and type in  validate_and_get_logs(). This will output one of two things:&lt;br /&gt;
&lt;br /&gt;
If your solution is correct (i.e. it resulted in the right permissions to solve the scenario), a large text block will be printed out. These are the logs which give us the correct path for scoring MTurkers' attempts. '''This is the text you need to copy and paste into the submission question for each scenario.''' &lt;br /&gt;
&lt;br /&gt;
If your solution is incorrect, in that the effective permissions state is not the one that solves this scenario, a series of errors and warnings will be printed out instead. The warnings list out what specifically is wrong with the current effective permission state: which permissions are allowed but should be denied according to the scenario, and vice versa. Try to understand why this is wrong and correct the problem.&lt;br /&gt;
 &lt;br /&gt;
Since accurate scoring depends on having the shortest/most efficent path, we highly recommend starting over and solving the scenario from scratch once you figure out how to get the correct answer. Otherwise your &amp;quot;shortest path&amp;quot; logs will include all of your trial-and-error.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Information_Foraging_Assignment:_Nursery_School&amp;diff=237</id>
		<title>Information Foraging Assignment: Nursery School</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Information_Foraging_Assignment:_Nursery_School&amp;diff=237"/>
		<updated>2022-11-13T20:12:14Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: /* Top Solutions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Task Description=&lt;br /&gt;
Washington University hosts and on-site nursery school for children ages 2.5-5 years old. In this&lt;br /&gt;
project, we are going to work to improve nursery school site visitors’ ability to find relevant&lt;br /&gt;
information using Information Foraging Theory. Information Foraging Theory describes how&lt;br /&gt;
users search for information using different cues.&lt;br /&gt;
&lt;br /&gt;
Specifically, we will study the following scenarios:&lt;br /&gt;
# '''Math:''' You are a parent considering sending your child to Washington University Nursery School. You’ve learned that the curriculum is play-based and you want to know how learning is incorporated into a play-based context. You have some ideas about how language learning might happen, but are less sure about math. Find some examples of how math learning is incorporated at Washington University Nursery School.&lt;br /&gt;
# '''School Day: '''  You are investigating pre-school options for your 4 year old. Both you and your spouse work, so you need to fully understand what scheduling constraints each option involves. One of your schools of interest is the Washington University Nursery School. When does school start and end each day? What is the longest period of time that your child can be there?&lt;br /&gt;
# '''Teacher Tenure: ''' You are investigating pre-school options for your 3.5 year old. You’ve been told that one of the hallmarks of a good program is teachers who have been there for a long time. You want your child to attend in the mornings only. Which teachers would your child have and how long have they been at the school?&lt;br /&gt;
# '''Summer Camp: ''' You are starting to look at summer camp options and have heard good things about Washington University Nursery School for young children. What are the daily camp hours? Are there any extended day opportunities?&lt;br /&gt;
# '''Discipline: ''' You are investigating pre-school options for your spirited 3 year old and want to understand their approach to discipline. How do teachers at Washington University approach discipline?&lt;br /&gt;
# '''Spanish Song: '''  Your daughter is in the Teddy Bear class at Washington University Nursery School. She came home this week singing a song in Spanish about shapes, but you are pretty sure that she has some of the words wrong. What are the correct lyrics?&lt;br /&gt;
#'''Books: ''' It is mid-December, 2020 and you are thinking about things to do over your daughter's upcoming school break. She is 3 years old and attends the Washington University Nursery School and is in the Teddy Bear classroom. You are planning a trip to the library and want to check out some books that connect with something she is doing in school. What are some potential book topics that relate to something that is going on in her classroom this week?&lt;br /&gt;
#'''Admission-2: ''' You are a parent with a child who has just been accepted to attend as a full time student at the Washington University Nursery School. You want to accept the offer of admission. Figure out what you need to do at this time to finalize your child’s place at the school.&lt;br /&gt;
#'''Deposit: ''' You are a parent with a child who has just been accepted to attend as a full time student at the Washington University Nursery School. You need to pay one month of tuition as a deposit. Find out how much one month of tuition is and whether or not it is possible to pay online.&lt;br /&gt;
#'''Personalized Help: '''You are moving to St. Louis from Beijing and looking for a Pre-K program for your daughter, age 5. She is very close to her friends and you are worried that the move might be hard on her. She may need some extra support from her new teachers learning English, adapting to American culture, and making new friends. How does the Washington University Nursery School staff approach providing extra help to students who need it? &lt;br /&gt;
(note: answer is the curriculum overview where it talks about how to provide extra help for individual students)&lt;br /&gt;
#'''Communication: '''You are looking at Nursery Schools for your soon to be 3 year old. He has never been in school or daycare before and you are somewhat worried about the transition. You'd like to ensure that you'll be able to have strong communication at his new school. How does the Washington University Nursery School handle communicating with parents? (note: answer is in the parent handbook under communication)&lt;br /&gt;
#'''Science: '''It’s mid-December and your son, age 4, came home all excited about science class. They learned a new word, but he can’t actually remember the word they learned about. What was the topic of his recent science class?&lt;br /&gt;
#'''Parent/Teacher Conferences: '''You are selecting a pre-school, but want to be sure that your daughter will be ready for kindergarten when it’s time. How does the nursery school assess children’s knowledge, support their growth, and share the results with parents?&lt;br /&gt;
#'''Orientation: '''You have recently accepted a position for your child for the coming school year at the Washington University Nursery School. Up to this point, your child has been at home and you are somewhat worried about the transition. How does the nursery school support kids’ transitions into school?&lt;br /&gt;
&lt;br /&gt;
=Grading=&lt;br /&gt;
For each project, you will get assigned three tasks to test for that round. For the first round, these will be randomly chosen. For subsequent rounds, we will carry two of your previous tasks forward. You can submit up to three versions (see deadlines on the calendar). For each task, we'll assign a score that captures the degree to which participants completed it correctly (got the right answer) and efficiently (took the fastest path to get there). To get credit for a task, you need to outperform the baseline score by 20% for that task. Overall project grades will be:&lt;br /&gt;
* 93: 3 tasks that perform &amp;gt;20% over the baseline, spread across any iteration.&lt;br /&gt;
* 88: 2 tasks that perform &amp;gt;20% over the baseline, spread across any iteration.&lt;br /&gt;
* 83: 1 task that performs &amp;gt;20% over the baseline, in any iteration.&lt;br /&gt;
&lt;br /&gt;
Then you can earn bonus points as follows:&lt;br /&gt;
&lt;br /&gt;
* +7: all three tasks in a single iteration (Note: only your largest multi-task bonus will count)&lt;br /&gt;
* +3: two tasks in a single iteration (Note: only your largest multi-task bonus will count)&lt;br /&gt;
* +2: one of the top 3 performing tasks in the class (Note: you can earn this bonus for multiple tasks)&lt;br /&gt;
&lt;br /&gt;
=Prerequisite Readings=&lt;br /&gt;
The goal of this assignment is use the ideas of information foraging to improve users' abilities to find information on the Washington University Nursery School site. As you work on your redesign you should be thinking about the information search process and trying to restructure and reorganize the information such that users can navigate it more easily.&lt;br /&gt;
&lt;br /&gt;
# [http://people.ischool.berkeley.edu/~hearst/research/scattergather.html Scatter/Gather]&lt;br /&gt;
# [https://devaka.ru/wp-content/uploads/2008/11/UIR-1995-07-Pirolli-CHI95-Foraging.pdf Information Foraging in Information Access Environments]&lt;br /&gt;
&lt;br /&gt;
=Getting Started=&lt;br /&gt;
==Cloning the Information Foraging Baseline Code==&lt;br /&gt;
We are hosting our repositories using github this semester. That means you will get a new repository for each of our three projects. When you accept an assignment through github classroom, it will create a repository for you based on the template that we've defined as the starting point for everyone.&lt;br /&gt;
&lt;br /&gt;
# First, accept the assignment from github. Once the assignment is ready to go live, we will update the link here.&lt;br /&gt;
# Navigate to your cloned repository on github. You can get there by reloading the &amp;quot;generating your repository&amp;quot; page. Git hub will give you a link when it's ready. It should have a url something like: &amp;lt;nowiki&amp;gt;https://github.com/cse-256-f22/information_foraging-YOUR_GITHUB_ID-wustl&amp;lt;/nowiki&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==Setting Up Pages==&lt;br /&gt;
To see what your version of the nursery school site looks like, you can view it through github pages. This will also be how mTurk users will view and interact with your site, so it's important to get going even if you plan to develop fully locally.&lt;br /&gt;
# Go the the settings tab and scroll down to the bottom.&lt;br /&gt;
# Change the repository visibility to 'public.'&lt;br /&gt;
# Enable github Pages. Select the 'main' branch and the 'root' directory to serve pages from. &lt;br /&gt;
# Once you hit save, github will add a link to your hosted pages so that you can see them.&lt;br /&gt;
&lt;br /&gt;
=Baseline Code=&lt;br /&gt;
Your repository contains the baseline version of the Nursery School site. Your assignment is to adapt that codebase to improve users' task performance. Within your top level repository directory you will find a subfolder called '''files''' that contains all of the HTML and CSS files you should need to edit for this project. If you would like to edit the JS of your site then do so in the '''scripts/ts/dynamic-dom''' folder.&lt;br /&gt;
&lt;br /&gt;
To run the site locally, do these steps:&lt;br /&gt;
# Open a terminal window or the terminal in your code editor.&lt;br /&gt;
# Navigate to your repository folder. This should be something like: information-foraging-&amp;lt;YOUR_GITHUB_ID&amp;gt;-wustl.&lt;br /&gt;
# Type in:&lt;br /&gt;
npm run dev&lt;br /&gt;
# This will open the Nursery School site running at http://localhost:3000/ in a web browser.&lt;br /&gt;
## You may notice a couple of alerts that pop up in your browser. This is because the URL is missing some information that the site expects to be there. If you would like these alerts not to show up, then use something like this URL in your browser instead: http://localhost:3000/?wustl_key=riley.mccuen.testing&amp;amp;sandbox=false&amp;amp;project=information-foraging&amp;amp;iteration=1&amp;amp;tag=books&lt;br /&gt;
## Feel free to configure the query string in in that url if you would like, but either way it should get rid of the alerts that show up on page reload.&lt;br /&gt;
# When you want to stop the web server you can press 'CTRL+C' and the server should shut down.&lt;br /&gt;
&lt;br /&gt;
=Introductory Studio=&lt;br /&gt;
The goal of this studio is to introduce you to the basic set of skills that you will need in order to begin modifying the nursery school site. While you won't emerge at the end of this knowing everything there is to know about HTML, CSS, and JavaScript, this should give you enough to be able to modify the starting code we've given you.&lt;br /&gt;
&lt;br /&gt;
[[Information Foraging Studio]]&lt;br /&gt;
&lt;br /&gt;
=Adding Javascript to Your Site=&lt;br /&gt;
When you find yourself wanting to add javascript there is one way we recommend doing it ('''NOTE''' if you do not do it this way it may not work as expected). &lt;br /&gt;
# Create a new file in the information-foraging/scripts/ts/dynamic-dom/ directory in your repository. If you are only using javascript then feel free to make a .js file, but it is recommended to use typescript which would be a .ts file. Both types of files will be included if used and imported properly. ('''NOTE''' regardless of whether or not you use TS you need to include it in the '''ts'''/dynamic-dom/ directory and import it into dynamic-dom.ts otherwise the build script will not bundle it.)&lt;br /&gt;
# Write your code in that new file.&lt;br /&gt;
# Import that file into dynamic-dom.ts and initialize it using a static initializer like you see is being done with the accordion and slideshow elements.&lt;br /&gt;
## Alternatively, if you only have a small amount of code and do not think that you need a whole new file then you can put your code directly in the information-foraging/scripts/ts/dynamic-dom/dynamic-dom.ts file.&lt;br /&gt;
# If your code is in script tags inlined into the html or not initialized through the dynamic-dom.ts file it will either not show up on your page or cause numerous runtime errors. Keep in mind, if you open your developer's console in your browser and there are red errors then that means your code is broken and needs to be fixed.&lt;br /&gt;
# Your code will need to be rebuilt in order to see these changes on your site.&lt;br /&gt;
Here is how you should write your code and import it, there is an example for both a .js file and .ts file but you only need to have one of them:&lt;br /&gt;
&lt;br /&gt;
This is for the javascript version in the file /information-foraging/scripts/ts/dynamic-dom/sticky.js&lt;br /&gt;
 export function setupSticky() {&lt;br /&gt;
    // TODO: Copy and paste your sticky code in here!!&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
This is for the typescript version in the file /information-foraging/scripts/ts/dynamic-dom/sticky.ts&lt;br /&gt;
 export function setupSticky() {&lt;br /&gt;
    // TODO: Copy and paste your sticky code in here!!&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
Now that you have your code in sticky.(j|t)s, put the bolded code below in the file /information-foraging/scripts/ts/dynamic-dom/dynamic-dom.ts:&lt;br /&gt;
 import { Accordion } from './accordion';&lt;br /&gt;
 import { Slideshow } from './slideshow';&lt;br /&gt;
 '''import { setupStickey } from './stickey';'''&lt;br /&gt;
 &lt;br /&gt;
 // Put all function calls that need to be made on every page load inside the setupAll function body.&lt;br /&gt;
 export function PutStudentPageLoadOperationsInsideThisStudentBody() {&lt;br /&gt;
     // TODO: Put all operations that you want to happen on ever page load in this function.&lt;br /&gt;
     // For example you could write: Sticky.setup()&lt;br /&gt;
     '''setupStickey();'''&lt;br /&gt;
 }&lt;br /&gt;
Like the comment says you can ''Put all function calls that need to be made on every page load inside the setupAll function body'' or you can put it into the PutStudentPageLoadOperationsInsideThisStudentBody function, either way it will work and is up to you.&lt;br /&gt;
&lt;br /&gt;
=Testing Your Site=&lt;br /&gt;
&lt;br /&gt;
To test your site, you need to do two things: &lt;br /&gt;
# Commit and push your code to Github. It may take a couple of minutes, but your changes will eventually be reflected in your Github pages site.&lt;br /&gt;
# Submit a sandbox hit that you can try out. ([[Submitting Sandbox HITs]])&lt;br /&gt;
# If you open your developer's console in your browser and see red errors, then something is broken and will be broken when you submit your hits. You must fix it.&lt;br /&gt;
&lt;br /&gt;
==Uploading to Github Pages==&lt;br /&gt;
To test or submit your project, you'll first need to upload your to Github.&lt;br /&gt;
&lt;br /&gt;
# If you've made changes to javascript and/or typescript code, please rebuild your code to get the new changes. (see [[Node Setup]] - step 6)&lt;br /&gt;
# Test your site locally via localhost (see [[Running Sites Locally]])&lt;br /&gt;
# Commit and push your changes (see [https://code.visualstudio.com/docs/editor/versioncontrol Version Control in VS Code])&lt;br /&gt;
# It will take a few minutes but your Github pages site will eventually reflect your changes.&lt;br /&gt;
&lt;br /&gt;
==Making a Sandbox HIT==&lt;br /&gt;
If you want to see what your MTurk workers will see, you can submit a sandbox hit. &lt;br /&gt;
&lt;br /&gt;
# This page offers a walkthrough on how to do that. ([[Submitting Sandbox HITs]])&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot (14).png|thumb|Worker Sandbox with relevant ui elements highlighted.]]&lt;br /&gt;
&lt;br /&gt;
=Submission=&lt;br /&gt;
For Iteration 0, you only need to upload your current site to Github and submit the canvas quiz stating that you've done so.&lt;br /&gt;
&lt;br /&gt;
For Iterations 1-3:&lt;br /&gt;
# Just as with testing, the first step in submitting your project is to upload your files to Github. &lt;br /&gt;
# Keep in mind that your project will be tested by actual users on Mechanical Turk. If it breaks and they can't get paid, they may well rate you poorly as a requestor which can create challenges for you to get good data going forward. Please test your submission on AWS and via a sandbox hit before you declare it ready to go.&lt;br /&gt;
# After you've tested your submission, please make sure that you have $10 in your Mechanical Turk account.&lt;br /&gt;
# Last, please fill out the canvas submission form for the current iteration. This serves as your declaration that we can safely submit real HITs for you. The submission will also ask you to specify the correct paths for each of your tasks. Note: you can only submit a single correct path for each task. We will randomly choose three of the tasks to test. For future iterations, we’ll keep two tasks the same and then choose a different third task. This is intended to keep disincentivize degenerate designs while also giving you an opportunity to iterate.&lt;br /&gt;
&lt;br /&gt;
=Best Practice Videos=&lt;br /&gt;
It seems pretty clear from looking at the sites you guys created that everyone has gotten the basic ideas around increasing the information density related to a given topic by grouping related information and increasing the information scent through the use of the right words and surrounding content. In going through the comments and the top solutions, I was looking to pull out some best practices that might not have been as obvious to give you one more set of tools that can help you think about information foraging into the future. These are a set of quick videos discussing some best practices in the context of the Nursery School Site.&lt;br /&gt;
&lt;br /&gt;
#[https://drive.google.com/file/d/1M7SRGYxawdlQrGtgNsKmC_MNmZzoifZV/view?usp=sharing Visible Exits]&lt;br /&gt;
#[https://drive.google.com/file/d/1HydDPrebZfj8d5yOHJiOl7IcSh4_VqB0/view?usp=sharing Intrapage Scent]&lt;br /&gt;
#[https://drive.google.com/file/d/1rpw0dRaADY7MzDwp6F6aIqNf_PxJyQFF/view?usp=sharing Promote High-Value Information]&lt;br /&gt;
#[https://drive.google.com/file/d/1FjGN5NNVvsW2fQTnR60a-zyh_tr2evZz/view?usp=sharing Overfitting]&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Clone_Your_Repository&amp;diff=236</id>
		<title>Clone Your Repository</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Clone_Your_Repository&amp;diff=236"/>
		<updated>2022-09-01T14:16:36Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: /* Repository Invites */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These instructions will guide you through setting up your repository and running the Nursery School codebase using Git, VSCode, and a localhost server. You are not required to use this setup, but we’ll probably be better able to help with any problems that arise if you do.&lt;br /&gt;
&lt;br /&gt;
=Repository Invites=&lt;br /&gt;
This semester, we are going to use Github classroom to create assignment repositories. We have added everyone to the github classroom. To avoid making the assignment link public to the world, we've created a page on [https://wustl.instructure.com/courses/91003/pages/information-foraging-project-setup Canvas] that steps you through how to accept the assignment and clone your repository. You can also navigate to the Canvas Modules and look at the first page in the Information Foraging Tasks Module.&lt;br /&gt;
&lt;br /&gt;
=Setting up Your Repository through VSCode =&lt;br /&gt;
You can clone your repository in VSCode using the instructions on the following page: [https://code.visualstudio.com/docs/editor/versioncontrol#_cloning-a-repository Cloning a Repository]&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Testing_Your_Site&amp;diff=235</id>
		<title>Testing Your Site</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Testing_Your_Site&amp;diff=235"/>
		<updated>2022-08-04T16:58:43Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;After you have finished building your site and testing it locally you should always test it using Amazon's MTurk Sandbox.&lt;br /&gt;
The MTurk Sandbox is essentially a clone of the environment that MTurk workers use, except it is explicitly for requesters to test their HITs.&lt;br /&gt;
When you submit to the sandbox and and accept the HIT you get to see how your HIT will actually look to the workers who will eventually do your hit.&lt;br /&gt;
Now that you have a little bit better understanding of what testing on the MTurk Sandbox means, here is how to do it:&lt;br /&gt;
&amp;lt;ol&amp;gt; &lt;br /&gt;
  &amp;lt;li&amp;gt; You will need to set up a credentials file that will be used by a javascript script in your repository to submit your HIT. &amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;ol&amp;gt; &lt;br /&gt;
    &amp;lt;li&amp;gt; Create a JSON file at the highest level of your repository named aws-credentials.json. For example if your repository was named information-foraging-foo.bar then your file should be located at information-foraging-foo.bar/aws-credentials.json. &amp;lt;/li&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt; Now copy and paste the code below into that file:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;accessKeyId&amp;quot;: &amp;quot;your access key id here&amp;quot;,&lt;br /&gt;
    &amp;quot;secretAccessKey&amp;quot;: &amp;quot;your secret access key here&amp;quot;,&lt;br /&gt;
    &amp;quot;region&amp;quot;: &amp;quot;us-east-1&amp;quot;,&lt;br /&gt;
    &amp;quot;endpoint&amp;quot;: &amp;quot;https://mturk-requester-sandbox.us-east-1.amazonaws.com&amp;quot;&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
    &amp;lt;/li&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt; Now that you have that code in the file, replace the part that says 'your access key id here' with the AWS Access ID that you set up earlier and do the same thing for the part that says 'your secret access key here'. Your file should now look like:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;accessKeyId&amp;quot;: &amp;quot;ABCDEFGHIJ12345LMN10&amp;quot;,&lt;br /&gt;
    &amp;quot;secretAccessKey&amp;quot;: &amp;quot;rp92mk719cIjFAJFIEFDqyBlPhAxBvhjatO0lJEp&amp;quot;,&lt;br /&gt;
    &amp;quot;region&amp;quot;: &amp;quot;us-east-1&amp;quot;,&lt;br /&gt;
    &amp;quot;endpoint&amp;quot;: &amp;quot;https://mturk-requester-sandbox.us-east-1.amazonaws.com&amp;quot;&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
    &amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;/ol&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt; Now that you have set up your aws-credentials.json file there is one more configuration step that you need to take care of. You must put your websites home page url into your projects package.json file. You can see the package.json file is also at the top level of your repository. &amp;lt;/li&amp;gt;&lt;br /&gt;
    &amp;lt;ol&amp;gt;&lt;br /&gt;
      &amp;lt;li&amp;gt; Open up package.json and look for the key: &amp;quot;url&amp;quot;. It should look something like this:&lt;br /&gt;
        &amp;lt;pre&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;name&amp;quot;: &amp;quot;information-foraging&amp;quot;,&lt;br /&gt;
... more json fields here -- do not touch them please ...&lt;br /&gt;
  &amp;quot;url&amp;quot;: &amp;quot;put your repository's home page url here&amp;quot;,&lt;br /&gt;
... more json fields here -- do not touch them please ...&lt;br /&gt;
}&lt;br /&gt;
        &amp;lt;/pre&amp;gt;&lt;br /&gt;
      &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; Replace the value (&amp;quot;put your repository's home page url here&amp;quot;) of that attribute with the url that points to your project's Github pages homepage. Your package.json should now look something like this: &lt;br /&gt;
        &amp;lt;pre&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;name&amp;quot;: &amp;quot;information-foraging&amp;quot;,&lt;br /&gt;
... more json fields here -- do not touch them please ...&lt;br /&gt;
  &amp;quot;url&amp;quot;: &amp;quot;https://cse256-sp2021.github.io/information-foraging/&amp;quot;,&lt;br /&gt;
... more json fields here -- do not touch them please ...&lt;br /&gt;
}&lt;br /&gt;
        &amp;lt;/pre&amp;gt;&lt;br /&gt;
      &amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;/ol&amp;gt;&lt;br /&gt;
  &amp;lt;li&amp;gt; Now that you have configured your project you can go ahead and submit a hit. Open a terminal and run this command: 'npm run sandbox'. &amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;ol&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt; That command will send a HIT to the MTurk sandbox on your behalf. Now log into the MTurk Sandbox Worker site and you should see a big list of HITs. &amp;lt;/li&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt; If you sort the HITs by the time that they were created you should eventually see your HIT come up. Be patient as it can take about a minute to be published. &amp;lt;/li&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt; You will know it is your hit because the requester listed on the far left side will be your MTurk requester account username. &amp;lt;/li&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt; Select accept and work for your HIT and then you can complete a HIT based on your website. &amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Running_Sites_Locally&amp;diff=234</id>
		<title>Running Sites Locally</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Running_Sites_Locally&amp;diff=234"/>
		<updated>2022-08-04T16:51:51Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;There are some custom scripts developed that provide an easy way to to test your submissions locally as you work on your assignments.&lt;br /&gt;
&lt;br /&gt;
# Open a terminal window or the terminal in your code editor (I recommend doing this directly in VSCode).&lt;br /&gt;
# Navigate to your repository folder. This will vary by project. Information foraging should be something like: information-foraging-&amp;lt;YOUR_GITHUB_ID&amp;gt;-wustl.&lt;br /&gt;
# Make sure that all the necessary dependencies have been installed for your project. You can do this by running:&lt;br /&gt;
&amp;lt;pre&amp;gt;npm install&amp;lt;/pre&amp;gt;&lt;br /&gt;
# NOTE: You only need to install dependencies once for each project.&lt;br /&gt;
# Next, start a local webserver from your project directory by running:&lt;br /&gt;
&amp;lt;pre&amp;gt;npm run dev&amp;lt;/pre&amp;gt;&lt;br /&gt;
# It may take a few seconds, but this should automatically open your website in your browser. Feel free to make changes to any of your code and the webserver will watch for updates that you make. If it notices new updates it will recompile your application and push the new copy to your web browser automatically.&lt;br /&gt;
## To ignore those pesky alerts that keep popping up make sure to use this URL and feel free to configure it differently according to the instructions below: http://localhost:3000/?wustl_key=riley.mccuen&amp;amp;sandbox=true&amp;amp;project=information-foraging&amp;amp;iteration=1&amp;amp;tag=books&lt;br /&gt;
## You will notice that the beginning of the url is the same as the regular url (http://localhost:3000) and everything after that is called the query string. If you would like to change the task that is being displayed on your page then feel free to edit query string parameter called tag.&lt;br /&gt;
## Valid values for tag can be found in your repository in at this location: &amp;lt;your repository path&amp;gt;/scenarios/scenarios.json. You can see the valid tags are all of the &amp;quot;tag&amp;quot; attributes of the objects in the array.&lt;br /&gt;
## An example url for the task with the tag of &amp;quot;math&amp;quot; would be the following url: http://localhost:3000/?wustl_key=riley.mccuen&amp;amp;sandbox=true&amp;amp;project=information-foraging&amp;amp;iteration=1&amp;amp;tag=math&lt;br /&gt;
# When you are done using your webserver, you can turn it off by clicking on your terminal and then 'CTRL+C'.&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
	<entry>
		<id>https://classes.engineering.wustl.edu/cse256a/index.php?title=Information_Foraging_Assignment:_Nursery_School&amp;diff=233</id>
		<title>Information Foraging Assignment: Nursery School</title>
		<link rel="alternate" type="text/html" href="https://classes.engineering.wustl.edu/cse256a/index.php?title=Information_Foraging_Assignment:_Nursery_School&amp;diff=233"/>
		<updated>2022-08-04T16:44:24Z</updated>

		<summary type="html">&lt;p&gt;Caitlin.Kelleher: /* Baseline Code */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Task Description=&lt;br /&gt;
Washington University hosts and on-site nursery school for children ages 2.5-5 years old. In this&lt;br /&gt;
project, we are going to work to improve nursery school site visitors’ ability to find relevant&lt;br /&gt;
information using Information Foraging Theory. Information Foraging Theory describes how&lt;br /&gt;
users search for information using different cues.&lt;br /&gt;
&lt;br /&gt;
Specifically, we will study the following scenarios:&lt;br /&gt;
# '''Math:''' You are a parent considering sending your child to Washington University Nursery School. You’ve learned that the curriculum is play-based and you want to know how learning is incorporated into a play-based context. You have some ideas about how language learning might happen, but are less sure about math. Find some examples of how math learning is incorporated at Washington University Nursery School.&lt;br /&gt;
# '''School Day: '''  You are investigating pre-school options for your 4 year old. Both you and your spouse work, so you need to fully understand what scheduling constraints each option involves. One of your schools of interest is the Washington University Nursery School. When does school start and end each day? What is the longest period of time that your child can be there?&lt;br /&gt;
# '''Teacher Tenure: ''' You are investigating pre-school options for your 3.5 year old. You’ve been told that one of the hallmarks of a good program is teachers who have been there for a long time. You want your child to attend in the mornings only. Which teachers would your child have and how long have they been at the school?&lt;br /&gt;
# '''Summer Camp: ''' You are starting to look at summer camp options and have heard good things about Washington University Nursery School for young children. What are the daily camp hours? Are there any extended day opportunities?&lt;br /&gt;
# '''Discipline: ''' You are investigating pre-school options for your spirited 3 year old and want to understand their approach to discipline. How do teachers at Washington University approach discipline?&lt;br /&gt;
# '''Spanish Song: '''  Your daughter is in the Teddy Bear class at Washington University Nursery School. She came home this week singing a song in Spanish about shapes, but you are pretty sure that she has some of the words wrong. What are the correct lyrics?&lt;br /&gt;
#'''Books: ''' It is mid-December, 2020 and you are thinking about things to do over your daughter's upcoming school break. She is 3 years old and attends the Washington University Nursery School and is in the Teddy Bear classroom. You are planning a trip to the library and want to check out some books that connect with something she is doing in school. What are some potential book topics that relate to something that is going on in her classroom this week?&lt;br /&gt;
#'''Admission-2: ''' You are a parent with a child who has just been accepted to attend as a full time student at the Washington University Nursery School. You want to accept the offer of admission. Figure out what you need to do at this time to finalize your child’s place at the school.&lt;br /&gt;
#'''Deposit: ''' You are a parent with a child who has just been accepted to attend as a full time student at the Washington University Nursery School. You need to pay one month of tuition as a deposit. Find out how much one month of tuition is and whether or not it is possible to pay online.&lt;br /&gt;
#'''Personalized Help: '''You are moving to St. Louis from Beijing and looking for a Pre-K program for your daughter, age 5. She is very close to her friends and you are worried that the move might be hard on her. She may need some extra support from her new teachers learning English, adapting to American culture, and making new friends. How does the Washington University Nursery School staff approach providing extra help to students who need it? &lt;br /&gt;
(note: answer is the curriculum overview where it talks about how to provide extra help for individual students)&lt;br /&gt;
#'''Communication: '''You are looking at Nursery Schools for your soon to be 3 year old. He has never been in school or daycare before and you are somewhat worried about the transition. You'd like to ensure that you'll be able to have strong communication at his new school. How does the Washington University Nursery School handle communicating with parents? (note: answer is in the parent handbook under communication)&lt;br /&gt;
#'''Science: '''It’s mid-December and your son, age 4, came home all excited about science class. They learned a new word, but he can’t actually remember the word they learned about. What was the topic of his recent science class?&lt;br /&gt;
#'''Parent/Teacher Conferences: '''You are selecting a pre-school, but want to be sure that your daughter will be ready for kindergarten when it’s time. How does the nursery school assess children’s knowledge, support their growth, and share the results with parents?&lt;br /&gt;
#'''Orientation: '''You have recently accepted a position for your child for the coming school year at the Washington University Nursery School. Up to this point, your child has been at home and you are somewhat worried about the transition. How does the nursery school support kids’ transitions into school?&lt;br /&gt;
&lt;br /&gt;
=Grading=&lt;br /&gt;
For each project, you will get assigned three tasks to test for that round. For the first round, these will be randomly chosen. For subsequent rounds, we will carry two of your previous tasks forward. You can submit up to three versions (see deadlines on the calendar). For each task, we'll assign a score that captures the degree to which participants completed it correctly (got the right answer) and efficiently (took the fastest path to get there). To get credit for a task, you need to outperform the baseline score by 20% for that task. Overall project grades will be:&lt;br /&gt;
* 93: 3 tasks that perform &amp;gt;20% over the baseline, spread across any iteration.&lt;br /&gt;
* 88: 2 tasks that perform &amp;gt;20% over the baseline, spread across any iteration.&lt;br /&gt;
* 83: 1 task that performs &amp;gt;20% over the baseline, in any iteration.&lt;br /&gt;
&lt;br /&gt;
Then you can earn bonus points as follows:&lt;br /&gt;
&lt;br /&gt;
* +7: all three tasks in a single iteration (Note: only your largest multi-task bonus will count)&lt;br /&gt;
* +3: two tasks in a single iteration (Note: only your largest multi-task bonus will count)&lt;br /&gt;
* +2: one of the top 3 performing tasks in the class (Note: you can earn this bonus for multiple tasks)&lt;br /&gt;
&lt;br /&gt;
=Prerequisite Readings=&lt;br /&gt;
The goal of this assignment is use the ideas of information foraging to improve users' abilities to find information on the Washington University Nursery School site. As you work on your redesign you should be thinking about the information search process and trying to restructure and reorganize the information such that users can navigate it more easily.&lt;br /&gt;
&lt;br /&gt;
# [http://people.ischool.berkeley.edu/~hearst/research/scattergather.html Scatter/Gather]&lt;br /&gt;
# [https://devaka.ru/wp-content/uploads/2008/11/UIR-1995-07-Pirolli-CHI95-Foraging.pdf Information Foraging in Information Access Environments]&lt;br /&gt;
&lt;br /&gt;
=Getting Started=&lt;br /&gt;
==Cloning the Information Foraging Baseline Code==&lt;br /&gt;
We are hosting our repositories using github this semester. That means you will get a new repository for each of our three projects. When you accept an assignment through github classroom, it will create a repository for you based on the template that we've defined as the starting point for everyone.&lt;br /&gt;
&lt;br /&gt;
# First, accept the assignment from github. Once the assignment is ready to go live, we will update the link here.&lt;br /&gt;
# Navigate to your cloned repository on github. You can get there by reloading the &amp;quot;generating your repository&amp;quot; page. Git hub will give you a link when it's ready. It should have a url something like: &amp;lt;nowiki&amp;gt;https://github.com/cse-256-f22/information_foraging-YOUR_GITHUB_ID-wustl&amp;lt;/nowiki&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==Setting Up Pages==&lt;br /&gt;
To see what your version of the nursery school site looks like, you can view it through github pages. This will also be how mTurk users will view and interact with your site, so it's important to get going even if you plan to develop fully locally.&lt;br /&gt;
# Go the the settings tab and scroll down to the bottom.&lt;br /&gt;
# Change the repository visibility to 'public.'&lt;br /&gt;
# Enable github Pages. Select the 'main' branch and the 'root' directory to serve pages from. &lt;br /&gt;
# Once you hit save, github will add a link to your hosted pages so that you can see them.&lt;br /&gt;
&lt;br /&gt;
=Baseline Code=&lt;br /&gt;
Your repository contains the baseline version of the Nursery School site. Your assignment is to adapt that codebase to improve users' task performance. Within your top level repository directory you will find a subfolder called '''files''' that contains all of the HTML and CSS files you should need to edit for this project. If you would like to edit the JS of your site then do so in the '''scripts/ts/dynamic-dom''' folder.&lt;br /&gt;
&lt;br /&gt;
To run the site locally, do these steps:&lt;br /&gt;
# Open a terminal window or the terminal in your code editor.&lt;br /&gt;
# Navigate to your repository folder. This should be something like: information-foraging-&amp;lt;YOUR_GITHUB_ID&amp;gt;-wustl.&lt;br /&gt;
# Type in:&lt;br /&gt;
npm run dev&lt;br /&gt;
# This will open the Nursery School site running at http://localhost:3000/ in a web browser.&lt;br /&gt;
## You may notice a couple of alerts that pop up in your browser. This is because the URL is missing some information that the site expects to be there. If you would like these alerts not to show up, then use something like this URL in your browser instead: http://localhost:3000/?wustl_key=riley.mccuen.testing&amp;amp;sandbox=false&amp;amp;project=information-foraging&amp;amp;iteration=1&amp;amp;tag=books&lt;br /&gt;
## Feel free to configure the query string in in that url if you would like, but either way it should get rid of the alerts that show up on page reload.&lt;br /&gt;
# When you want to stop the web server you can press 'CTRL+C' and the server should shut down.&lt;br /&gt;
&lt;br /&gt;
=Introductory Studio=&lt;br /&gt;
The goal of this studio is to introduce you to the basic set of skills that you will need in order to begin modifying the nursery school site. While you won't emerge at the end of this knowing everything there is to know about HTML, CSS, and JavaScript, this should give you enough to be able to modify the starting code we've given you.&lt;br /&gt;
&lt;br /&gt;
[[Information Foraging Studio]]&lt;br /&gt;
&lt;br /&gt;
=Adding Javascript to Your Site=&lt;br /&gt;
When you find yourself wanting to add javascript there is one way we recommend doing it ('''NOTE''' if you do not do it this way it may not work as expected). &lt;br /&gt;
# Create a new file in the information-foraging/scripts/ts/dynamic-dom/ directory in your repository. If you are only using javascript then feel free to make a .js file, but it is recommended to use typescript which would be a .ts file. Both types of files will be included if used and imported properly. ('''NOTE''' regardless of whether or not you use TS you need to include it in the '''ts'''/dynamic-dom/ directory and import it into dynamic-dom.ts otherwise the build script will not bundle it.)&lt;br /&gt;
# Write your code in that new file.&lt;br /&gt;
# Import that file into dynamic-dom.ts and initialize it using a static initializer like you see is being done with the accordion and slideshow elements.&lt;br /&gt;
## Alternatively, if you only have a small amount of code and do not think that you need a whole new file then you can put your code directly in the information-foraging/scripts/ts/dynamic-dom/dynamic-dom.ts file.&lt;br /&gt;
# If your code is in script tags inlined into the html or not initialized through the dynamic-dom.ts file it will either not show up on your page or cause numerous runtime errors. Keep in mind, if you open your developer's console in your browser and there are red errors then that means your code is broken and needs to be fixed.&lt;br /&gt;
# Your code will need to be rebuilt in order to see these changes on your site.&lt;br /&gt;
Here is how you should write your code and import it, there is an example for both a .js file and .ts file but you only need to have one of them:&lt;br /&gt;
&lt;br /&gt;
This is for the javascript version in the file /information-foraging/scripts/ts/dynamic-dom/sticky.js&lt;br /&gt;
 export function setupSticky() {&lt;br /&gt;
    // TODO: Copy and paste your sticky code in here!!&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
This is for the typescript version in the file /information-foraging/scripts/ts/dynamic-dom/sticky.ts&lt;br /&gt;
 export function setupSticky() {&lt;br /&gt;
    // TODO: Copy and paste your sticky code in here!!&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
Now that you have your code in sticky.(j|t)s, put the bolded code below in the file /information-foraging/scripts/ts/dynamic-dom/dynamic-dom.ts:&lt;br /&gt;
 import { Accordion } from './accordion';&lt;br /&gt;
 import { Slideshow } from './slideshow';&lt;br /&gt;
 '''import { setupStickey } from './stickey';'''&lt;br /&gt;
 &lt;br /&gt;
 // Put all function calls that need to be made on every page load inside the setupAll function body.&lt;br /&gt;
 export function PutStudentPageLoadOperationsInsideThisStudentBody() {&lt;br /&gt;
     // TODO: Put all operations that you want to happen on ever page load in this function.&lt;br /&gt;
     // For example you could write: Sticky.setup()&lt;br /&gt;
     '''setupStickey();'''&lt;br /&gt;
 }&lt;br /&gt;
Like the comment says you can ''Put all function calls that need to be made on every page load inside the setupAll function body'' or you can put it into the PutStudentPageLoadOperationsInsideThisStudentBody function, either way it will work and is up to you.&lt;br /&gt;
&lt;br /&gt;
=Testing Your Site=&lt;br /&gt;
&lt;br /&gt;
To test your site, you need to do two things: &lt;br /&gt;
# Commit and push your code to Github. It may take a couple of minutes, but your changes will eventually be reflected in your Github pages site.&lt;br /&gt;
# Submit a sandbox hit that you can try out. ([[Submitting Sandbox HITs]])&lt;br /&gt;
# If you open your developer's console in your browser and see red errors, then something is broken and will be broken when you submit your hits. You must fix it.&lt;br /&gt;
&lt;br /&gt;
==Uploading to Github Pages==&lt;br /&gt;
To test or submit your project, you'll first need to upload your to Github.&lt;br /&gt;
&lt;br /&gt;
# If you've made changes to javascript and/or typescript code, please rebuild your code to get the new changes. (see [[Node Setup]] - step 6)&lt;br /&gt;
# Test your site locally via localhost (see [[Running Sites Locally]])&lt;br /&gt;
# Commit and push your changes (see [https://code.visualstudio.com/docs/editor/versioncontrol Version Control in VS Code])&lt;br /&gt;
# It will take a few minutes but your Github pages site will eventually reflect your changes.&lt;br /&gt;
&lt;br /&gt;
==Making a Sandbox HIT==&lt;br /&gt;
If you want to see what your MTurk workers will see, you can submit a sandbox hit. &lt;br /&gt;
&lt;br /&gt;
# This page offers a walkthrough on how to do that. ([[Submitting Sandbox HITs]])&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot (14).png|thumb|Worker Sandbox with relevant ui elements highlighted.]]&lt;br /&gt;
&lt;br /&gt;
=Submission=&lt;br /&gt;
For Iteration 0, you only need to upload your current site to Github and submit the canvas quiz stating that you've done so.&lt;br /&gt;
&lt;br /&gt;
For Iterations 1-3:&lt;br /&gt;
# Just as with testing, the first step in submitting your project is to upload your files to Github. &lt;br /&gt;
# Keep in mind that your project will be tested by actual users on Mechanical Turk. If it breaks and they can't get paid, they may well rate you poorly as a requestor which can create challenges for you to get good data going forward. Please test your submission on AWS and via a sandbox hit before you declare it ready to go.&lt;br /&gt;
# After you've tested your submission, please make sure that you have $10 in your Mechanical Turk account.&lt;br /&gt;
# Last, please fill out the canvas submission form for the current iteration. This serves as your declaration that we can safely submit real HITs for you. The submission will also ask you to specify the correct paths for each of your tasks. Note: you can only submit a single correct path for each task. We will randomly choose three of the tasks to test. For future iterations, we’ll keep two tasks the same and then choose a different third task. This is intended to keep disincentivize degenerate designs while also giving you an opportunity to iterate.&lt;br /&gt;
&lt;br /&gt;
=Top Solutions=&lt;br /&gt;
&lt;br /&gt;
You can see the top solutions for Spring 2021 [https://docs.google.com/spreadsheets/d/1S6Vmdt4RaIcrx8dod5IUhvycrtIGQmPLg8vhQKYdfIw/edit?usp=sharing here].&lt;br /&gt;
&lt;br /&gt;
=Best Practice Videos=&lt;br /&gt;
It seems pretty clear from looking at the sites you guys created that everyone has gotten the basic ideas around increasing the information density related to a given topic by grouping related information and increasing the information scent through the use of the right words and surrounding content. In going through the comments and the top solutions, I was looking to pull out some best practices that might not have been as obvious to give you one more set of tools that can help you think about information foraging into the future. These are a set of quick videos discussing some best practices in the context of the Nursery School Site.&lt;br /&gt;
&lt;br /&gt;
#[https://drive.google.com/file/d/1M7SRGYxawdlQrGtgNsKmC_MNmZzoifZV/view?usp=sharing Visible Exits]&lt;br /&gt;
#[https://drive.google.com/file/d/1HydDPrebZfj8d5yOHJiOl7IcSh4_VqB0/view?usp=sharing Intrapage Scent]&lt;br /&gt;
#[https://drive.google.com/file/d/1rpw0dRaADY7MzDwp6F6aIqNf_PxJyQFF/view?usp=sharing Promote High-Value Information]&lt;br /&gt;
#[https://drive.google.com/file/d/1FjGN5NNVvsW2fQTnR60a-zyh_tr2evZz/view?usp=sharing Overfitting]&lt;/div&gt;</summary>
		<author><name>Caitlin.Kelleher</name></author>
		
	</entry>
</feed>