Use the database

How to use the lab's database

Prerequisites

  • None

Access database

Open experiments.childlanglab.com and enter the password found in the Lab HQ.

Participants

How to add participants to Salesforce

  1. Choose "New" under the participant tab.

How to add participants to the database

  1. Go to the "Participants" tab.

  2. Locate "Add a new participant" window on the left side of the screen.

  3. Fill out the requested information.

  4. Hit "Submit".

How to search participants

  1. Go to the "Participants" tab.

  2. Locate the search bar in the upper right hand corner.

  3. Type in part or all of the participant ID you are searching for.

  4. Choose the participant from the "Find a participant" box to see their runs listed in the "____'s runs" box.

Run experiments

Go to the "Run Experiment" tab.

Under Conditions to run (1) you will find a link to a google spread sheet. Here you can find which conditions you should run. Once you finish a trial, be sure to return to this spreadsheet and fill out which trial you just ran. Once you have found which trial you should be running move onto (2) (see image above).

Experiment: Pick the experiment that you will be running. Each experiment is associated with a unique number.

Condition: Pick the condition. If you are running a test run pick which ever condition you want to try out. For test runs you also have the option of running a demo, which is a shorter version of the experiment (so that you can try it out without wasting time clicking through the repetitive parts). If you are running an official run pick the next condition that you should run in the google spread sheet. Please note that running participants in the order given in the spread sheet is important!

Participant: Type in the participant ID number. These are the ID numbers that were generated by salesforce and are unique to each participant. However, unless you added the participant to the database (see above), this data won't be linked to a participant—so be sure to add the participant before you even begin with this section! Be sure that you put in the right participant ID, otherwise the data can be lost because it's not linked to any real participant. If you are running a test run be sure to put participant ID as 0, otherwise your test run might be counted as real data and could mess up statistics in an experiment.

Source: If you are doing a test run select labtest. If you are doing an official run with a participant select salesforce.

Experimenter: Select your name from the drop down menu.

Location: Select where you are conducting the experiment. Select childlanglab if you are running the experiment in the lab. Otherwise offsite locations should be listed in the dropdown menu.

Checked: Before continue double check that you entered everything correctly! Ask yourself:

  • Are you running the correct condition?

  • Did you type in the participant ID correctly?

  • If you are running a test run, did you select the right right participant (0) and source (labtest)?

You are now ready to run the experiment!

Starting the Audio

After you press the "start experiment" you will see the following screen. In case your particular experiment does not record audio then you can skip this section.

This screen is to remind you to start the audio recording. Do not press begin experiment until you do so. Find the app with the icon depicted in the image above (it is usually found in the dock, i.e bottom row of app icons on your screen). If you don't find it there find it in the applications folder. If the app is already running, pressing the app icon will start the recording. If not, press the black button on the top right of your screen (usually next to the battery/wifi symbols) and press record. You can see whether the app is recording if, instead of a black button, there is a red button with a timer that is counting up.

Once you have started the audio recording, press begin experiment and run through the experiment!

Once you've finished

You will see the screen below. Press end experiment.

Congrats you just finished the experiment! However, there are a few more things that you have to do before you are done.

  1. Stop and save the audio recording

    Press the red circle at the top of the screen (next to the batter/wifi icons) to stop the audio recording. This will automatically prompt you to save the audio file. Save it to the desktop under any name.

  2. Debrief the participant

    It is important that the participant knows what they just did and why it's important, and now that the experiment is over we can tell them about it! Explain what this experiment was looking at exactly and how that ties into the big picture of how people acquire/learn languages. Be sure to put the debriefing into terms that the participant understands—not everyone knows psychology/linguistics terminology and often times our participants are kids (they too have a right to know what the experiment was about!). You should also debrief their parent, so that the parent knows exactly what their child was doing and so that they know that bringing their child in was worth the while! If your participant was from SONA and is doing this for credit, be sure to explain how and when credit will be assigned.

  3. Show the participant out

    If you have an adult participant, you can show them out to the elevators (you need a key card to get into the compsci part of the wing). If you have a child participant, take them back to their parent. Talk to the parent a bit and if need be play with the child a bit more!

  4. Fill out the How did it go? screen

    You will see the screen below:

    Under the drop down menu you have the following options:

    • completed: if the study was completed

    • voluntary withdrawal: if the participant decided to end the study half way through

    • experiment malfunction: if the experiment ended prematurely for whatever reason, and you weren't able to finish. This could be a mistake on your part or a glitch in the computer. Both happen, don't worry about it.

    • test run (not real participant): if this run was for a test run

    Leave notes: never leave this section blank! If you have no notes to write, then write something like "successful run". It is helpful to always see comments while coding the data, so that the coder knows what is going on. This is usually the first thing that the coder looks at, before they even start to code the data. So write anything that you think might be helpful. This could be things like "participant pronounced geed as feed consistently", "participant was not paying attention in the exposure phase", "I (the experimenter" forgot to read the instructions out loud", etc. The coding can be done well after the experiment has been run, and well after you remember what happened during this particular trial. So it is helpful to have these notes so that everyone knows what happened. You should also write if you forgot to start the audio (so that the coder doesn't waste time looking for audio that doesn't exist) or if the audio won't upload in the next part (further instructions on what you should write in this case found there). Use your judgement on what should go in this section!

  5. upload the audio

    Click the blue upload audio button and attach the audio file that you saved. The audio files uploaded should be in .mp3 format (the audio recording app should automatically save them as such). The name of this file does not matter as the database will automatically rename it. Once you've uploaded it, you will see the following image at the top of the page (pay attention whether it pops up or not because it does disappear after a few seconds):

    If this does not pop up, you did not upload the audio file. If anything else pops up (such as a "query error" message), that means that something went wrong. Make a note in the notes box that this happened and that the audio file can be found in the google drive (part 7).

  6. press submit

    Once everything has been filled out, and the audio has been submitted, press submit. You should see the following change:

    That is how you know that everything was submitted correctly.

  7. upload the audio to google drive

    Finally you need to upload the audio to the lab's google drive. It should be saved under ChildLangLab-Data --> [study specific folder] --> data. Within this folder, create a folder labeled "[experiment number]-[trial number]-[experiment run id]". For example this could look like "7-13-5ydqex3667" for experiment 7, trial 13. The experiment run id can be found on the screen in step 6. Upload the audio file (in .mp3 format) into that folder under the name "[experiment number]-[trial number]-[experiment run id]-audio". For example this could look like: "7-13-5ydqex3667-audio.mp3".

  8. Update the conditions to run spread sheet

    Be sure to update the conditions to run spread sheet to keep track of which conditions you have already ran.

Yay!!! You are now finished with running this participant!

View Runs

  • how to view runs by experiment

  • how to view a particular run

  • how to update a run

Code data

If you haven't done so already, do the training under Code Data > Code Training. You should complete this training before you code data.

To start coding open the code data tab in the database and select the experiment that you will be coding.

You will be instructed to type in an experiment specific coding password. You are now ready to start coding! You will see the following screen:

  1. Select yourself as the coder

  2. This is the list of all participants ran

    Here you see a participant ID and the associated Random ID of that run. Select one of these rows to code data for that run. Once you are finished coding, you can mark the run as "complete" or "missing data". Note that you cannot undo once you've clicked one of these, so be sure to not click them by accident. Mark that trial complete once you've coded all of the data. Mark the trial as having missing data if the audio file is missing. The audio file should appear in 3. If it doesn't, check the google drive (sometimes audio files aren't automatically uploaded). If the audio file isn't in the google drive either, then it is possible that the data is missing. If the experimenter forgot to record the audio, that should be commented under Experimenter notes in 3.

  3. This is the raw data

    First check whether Withdrawn is 0 or 1. If it is 1, then the paritipant withdrew from participation during the study, and you can mark the data as missing. Next you should read the experimenter notes. This is where the experimenter leaves notes about how the study went and any thing you might need to know before you code (stuff like whether the experimenter forgot to turn on the audio recording, whether the participant pronounced a word weirdly but clearly meant this, or other things). The audio file that you will be extracting data from is found here. In case that the audio is not there, check the google drive and it should be there.

  4. This is where you will be coding. See the image below for more details

  1. Noun Correct

    This field takes in a boolean value which can be typed in as T for true and F for false. If the participant said a noun on that trial that matches the noun listed under the Noun column, then type in T. If the participant said another noun, or did not say a noun at all type in F. If multiple nouns were said, use your judgement to determine which noun the participant meant (this is often clear when the participant says things like "daffin ... no wait spad").

  2. Transcription

    This field takes in a string value: type in exactly what the participant said. If the participant goes on an unrelated tangent (as child participants often do) you do not need to type that and can just write [...].

  3. Marker Used

    Type the marker that the child used. This can be ka, po, nothing, or something that the child made up or applied from another language. Examples of this last case in the image above are "lu", "gee", and "goo"—since the participant only heard "ka" and "po" as plural markers within the experiment all of those previous markers are novel. If the child didn't use a plural marker, leave the space blank. The algorithm automatically marks empty boxes as null. Saying the noun twice, like daffin daffin, does not count as a marker.

  4. Marker Type

    You can type in the following: ka, po, null, otherX (whereby x is a number). Type "ka" if the participant says ka. Type "po" if the child says po. If the child did not produce a plural marker you can leave the space empty. That is exactly the same as in 3. If the child produces a form other than ka, po, or null, mark that as otherX. For each novel plural marker that the child uses (be it a plural marker from a real language or something that the child made up on its own) mark each novel marker with a number. For example "daffin lu" would be marked as other1. If the participant then later said "spad lu", you would mark this as other1 too, since "lu" was repeated. If the child produces yet another novel plural marker, such as "daffin gee", mark that as other2. Theoretically if the participant thought of a different plural marker for each trial, and you would have to enter {other1, other2, ..., other23}, but that has not yet happened.

  5. Gave Feedback?

    This field takes a boolean value: type T for true and F for false. Mark this field as true if the experimenter gives feedback, this includes things like "good job" and "great".

  6. Prompted Marker?

    This field takes a boolean value: type T for true and F for false. Mark this field as true if the experimenter prompted the marker. This is usual in the form of statements such as "does anything come after [noun]?".

  7. Notes

    You can type anything you deem relevant here. This usually includes what the experimenter said in terms of feedback/prompting the marker. Use your judgement to determine what should go here.

As you can see in the picture above, all the True/False values will automatically turn into checks or X's. Sometimes the program is coded so that instead of typing "T" or "F" you click on the field and it automatically changes to a check/X.

Also note that for each participant there can be multiple pages that have to be coded: be sure that you check at the bottom of this window to see how many pages there are as per the image below.

Once you are finished coding your data, double check that you wrote everything correctly, and press Mark Complete to submit it. Once you press mark complete, you can't get back to this participant, so make sure that you double check that everything is filled out!

Get data

  • How to get data for your experiment