http://tsgdoc.socsci.ru.nl/api.php?action=feedcontributions&user=Wilbert.vanham&feedformat=atomTSG Doc - User contributions [en]2024-03-29T00:16:31ZUser contributionsMediaWiki 1.35.4http://tsgdoc.socsci.ru.nl/index.php?title=ButtonBoxes&diff=5726ButtonBoxes2023-08-29T11:21:09Z<p>Wilbert.vanham: /* Python/PsychoPy */</p>
<hr />
<div>{{Infobox tsg<br />
| name = Buttonbox (2018)<br />
| image = Buttonbox_2018_1.png<br />
| caption = 2018 Buttonbox<br />
| downloads = {{bulleted list<br />
| [https://surfdrive.surf.nl/files/index.php/s/PPTKCyrjLkN4XUO Buttonbox 2018]<br />
| [https://pypi.python.org/pypi/RuSocSci RuSocSci] (Python package)<br />
}}<br />
}}<br />
{{Infobox tsg<br />
| name = Buttonbox<br />
| image = Buttonbox 03s.png<br />
| caption = 2013 Buttonbox<br />
| downloads = {{bulleted list<br />
| [https://surfdrive.surf.nl/files/index.php/s/72XEcu2XKSgzxjp Buttonbox 2015]<br />
| [https://pypi.python.org/pypi/RuSocSci RuSocSci] (Python package)<br />
}}<br />
}}<br />
<br />
The buttonbox is used for time accurate(1ms) button press registration. We use it to register buttonpresses, soundkey, voicekey signals and to send tone onset, analog output, triggers with the BITSI protocol. It is suitable for Behavioral, EEG, MEG, and fMRI experiments. The buttonbox is connected to a computer with a usb connection.<br />
<br />
The output connector has two binary eight bit ports: input and output. The two ports can be used for responses (input) and stimulus triggers (output). Two 12 bits analog outputs and three 12 bits analog inputs. The output connector has a sound and voicekey which triggers when a amplitude reaches a threshold. By using the serial port, the BITSI can be used platform independently: it works on Windows, Linux and Mac OSX. Most programming environments and stimulus packages support serial communication.<br />
<br />
There is currently a [[Microsoft Windows driver issue]].<br />
<br />
== BITSI Protocol ==<br />
<br />
BITSI stands for Bits to Serial Interface. Because the BITSI is designed to interface both in- and output signals, the 'protocol' is asymmetric: the input and output protocols differ.<br />
<br />
===Input===<br />
<br />
The input port can be used to interface eight buttons maximally. Button presses are translated to serial output characters/bytes according to the following table:<br />
<br />
{| class="wikitable" <br />
|- <br />
! scope="row" colspan="3" | BITSI Simple<br />
|-<br />
! scope="row" width="120px" | Signal/Button<br />
! scope="row" width="120px" | ASCII (rise/fall)<br />
! scope="row" width="120px" | Code (rise/fall)<br />
|-<br />
| 1 || A / a || 65 / 97<br />
|-<br />
| 2 || B / b || 66 / 98<br />
|-<br />
| 3 || C / c || 67 / 99<br />
|-<br />
| 4 || D / d || 68 / 100<br />
|-<br />
| 5 || E / e || 69 / 101<br />
|-<br />
| 6 || F / f || 70 / 102<br />
|-<br />
| 7 || G / g || 71 / 103<br />
|-<br />
| 8 || H / h || 72 / 104<br />
|-<br />
|}<br />
<br />
This means that when signal 1 gets active(button press), a capital A will be sent to the serial port. A lowercase 'a' will be sent when the signal is deactivated(button release). Mechanical buttons can be connected directly.<br />
<br />
===Output===<br />
<br />
Output knows two protocols: '''BITSI simple''' or '''BITSI extended'''. To enter a certain protocol two buttons have to be pressed when the BITSIbox is powered or com port opens. '''[2015]Press button H and A for simple mode and H and B for extended mode. [2018]Press button E and A for simple mode and E and B for extended mode.'''<br />
<br />
If no button is pressed when powered it boots the last known protocol. In the simple protocol every byte sent to the BITSI over the serial port, is represented at the 8 bit output.<br />
<br />
The '''extended''' protocol uses two bytes(or two characters), this combination can access two analog outputs and a tone generator. The first byte selects the output. The second byte determines the value written to this output.<br />
<br />
{| class="wikitable" <br />
|- <br />
! scope="row" colspan="3" | BITSI Extended<br />
|-<br />
! scope="row" width="120px" | Function<br />
! scope="row" width="150px" | Byte 1 (ASCII/code)<br />
! scope="row" width="150px" | Byte 2<br />
|-<br />
| Marker Out || M / 77 || Marker Value<br />
|-<br />
| Pulse Out || P / 80 || Marker Value<br />
|-<br />
| Pulse Time || X / 88 || ms before pulse reset<br />
|-<br />
| Analog Out 1 || Y / 89 || Analog Output Value<br />
|-<br />
| Analog Out 2 || Z / 90 || Analog Output Value<br />
|-<br />
| Tone || T / 84 || Start Tone<br />
|-<br />
| Detect Sound || D / || S / 83<br />
|-<br />
| Detect Voice || D / || V / 83<br />
|-<br />
| Calibrate Sound || C / || S<br />
|-<br />
| Calibrate Voice || C / || V<br />
|-<br />
| Analog In 1 || A / || 1<br />
|-<br />
| Analog In 2 || A / || 2<br />
|-<br />
| Analog In 3 || A / || 3<br />
|-<br />
| Analog In 4 || A / || 4<br />
|-<br />
| LEDs Off || L / || X<br />
|-<br />
| LEDs Input || L / || I<br />
|-<br />
| LEDs Output || L / || O<br />
|-<br />
|}<br />
<br />
== Port Settings ==<br />
<br />
===Trigger port ===<br />
<br />
[[File:Connector.png|thumb|300x300px|Schematic view of the 25 pins connector]]<br />
<br />
The 25 pins female connector has 8 inputs and 8 outputs, respectively 1-8 are inputs and 9-16 are outputs. Three analog input with an analog to digital convertor of 12 bit, pins 17,18,20 and 21. Two analog outputs with an digital to analog convertor of 12 bits on pins 22 and 23.<br />
<br />
The inputs 1-8 will be pulled down from 5V to GND when the buttons are pressed. The outputs 9-16 will be pulled up from GND to 5V when the output is activated.<br />
<br />
===Serial port===<br />
<br />
Our hardware design allows to be connected to the computers USB and emulates a serial communication Port.<br />
<br />
{| class="wikitable"<br />
|-<br />
| Baudrate || 115200<br />
|-<br />
| Parity || None<br />
|-<br />
| Data bits || 8<br />
|-<br />
| Stop bits || 1<br />
|-<br />
| Flow control || None<br />
|-<br />
|}<br />
<br />
=== USB-Com port ===<br />
<br />
1.Connect the BITSIbox to your computer using the USB cable.<br />
<br />
2.When you connect the BITSIbox, Windows should initiate the driver installation process (if you haven't used the computer with an BITSIbox board before).<br />
<br />
3.On Windows Vista/7, the driver should be automatically downloaded and installed.<br />
<br />
4.On Windows XP, the Add New Hardware wizard will open:<br />
<br />
*When asked&nbsp;'''Can Windows connect to Windows Update to search for software?'''&nbsp;select&nbsp;'''No, not this time'''. Click next.<br />
*Select&nbsp;'''Install from a list or specified location (Advanced)'''&nbsp;and click next.<br />
*Make sure that&nbsp;'''Search for the best driver in these locations'''&nbsp;is checked; uncheck&nbsp;'''Search removable media'''; check&nbsp;'''Include this location in the search'''&nbsp;and browse to the&nbsp;'''c:/beheer/arduino/drivers '''directory.<br />
*The wizard will search for the driver and then tell you that a "USB Serial Converter" was found. Click finish.<br />
*The new hardware wizard will appear again. Go through the same steps and select the same options and location to search. This time, a "USB Serial Port" will be found.<br />
<br />
'''How to Check the Com Port settings(important!)'''<br />
<br />
*From the Start menu, open the '''Control Panel'''.<br />
<br />
*From the control panel, open the '''System window'''.<br />
<br />
*From the system properties window, go to the '''Hardware tab''' and click the '''Device Manager''' button.<br />
<br />
*From the Device Manager window, click '''Ports (Com&LPT).''' You should now be able to see which Com Port the USB adapter is assigned to.<br />
<br />
*If the Com Port is 10 or higher, you will have to change it to a lower port.<br />
<br />
*From the Device Manager window, click on '''USB Serial Port (Com#).''' Click the '''Port Settings tab''' of the USB Serial Port Properties window, and then click the '''Advanced''' button.<br />
<br />
*In the Advanced Settings window, use the scroll input to select a '''Com Port''' (select 10 or lower). Change '''Receive (bytes)''' and '''Transmit (bytes)''' to 64. Change the '''Latency Timer''' to 1.<br />
<br />
*Click the OK button.<br />
<br />
Always connect the usb device to the same port and your settings will be remembered.<br />
<br />
== Software Settings ==<br />
<br />
=== Neurobs Presentation ===<br />
<br />
The experiment files needs a few settings for the device to work:<br />
* In the settings tab: port -> input port -> 1 must be the device that identifies itself as "Arduino Uno" in the device manager. Note that the port must have a number not higher than 10 (COM1-COM10). Use re-enumerate if it is higher.<br />
* Rate must be set 115200, Parity to None, Data Bits to 8 and Stop Bits to 1, Uncheck FIFO Interrupt.<br />
<br />
[[File:Buttonbox2.png]]<br />
<br />
'''Testing Buttonbox'''<br />
<br />
When pressing on the A button within the input channel tester. You will see the following ASCII code.<br />
<br />
[[file:testbuttonbox.png]]<br />
<br />
'''Adding Marker'''<br />
<br />
[[file:output_buttonbox1.png | 800px]]<br />
<br />
'''Testing Markers (output)'''<br />
<br />
Send code 1 for Button A<br />
<br />
[[file:output_buttonbox2.png]]<br />
<br />
Button A will light up.<br />
<br />
[[file:buttonboxledA.png | 200px]]<br />
<br />
Send code 0 for clearing.<br />
<br />
[[file:output_buttonbox3.png]]<br />
<br />
'''Example PCL code you can program a handle to send a marker:'''<br />
<br />
#handle:<br />
output_port OutputPort = output_port_manager.get_port( 1 );<br />
<br />
'''Example to send a marker:'''<br />
OutputPort.send_code(100); #create a marker<br />
<br />
<br />
for more information see chapter 8 in the presentation course by clicking [http://tsgdoc.socsci.ru.nl/images/9/9e/Programming_with_Presentation_2013.pdf here]<br />
<br />
=== Python/PsychoPy ===<br />
<br />
Download this site-package to use the buttonbox: [https://pypi.python.org/pypi/RuSocSci rusocsci] <br />
<br />
or use in windows command 'pip install --upgrade rusocsci'<br />
<br />
'''Example using buttons from the buttonbox in Python:'''<br />
<br />
<syntaxhighlight lang="python" line><br />
#!/usr/bin/env python<br />
<br />
# import the rusocsci.buttonbox module<br />
from rusocsci import buttonbox <br />
<br />
# make a buttonbox<br />
bb = buttonbox.Buttonbox()<br />
<br />
# wait for a single button press<br />
b = bb.waitButtons()<br />
<br />
# print the button pressed<br />
print("b: {}".format(b)) <br />
</syntaxhighlight><br />
<br />
'''Example using markers with the buttonbox in Python:'''<br />
<br />
<syntaxhighlight lang="python" line><br />
#!/usr/bin/env python<br />
<br />
# import the rusocsci.buttonbox module<br />
from rusocsci import buttonbox <br />
<br />
# make a buttonbox<br />
bb = buttonbox.Buttonbox()<br />
<br />
# send a marker<br />
bb.sendMarker(val=100) #This is your marker code, range code 1-255 <br />
</syntaxhighlight><br />
<br />
'''Example using BITSI extended in Python:'''<br />
<br />
<syntaxhighlight lang="python" line><br />
#!/usr/bin/env python<br />
<br />
# import the rusocsci.buttonbox module<br />
from rusocsci import buttonbox <br />
<br />
# make a buttonbox<br />
bb = buttonbox.Buttonbox()<br />
<br />
# select a function<br />
bb.sendMarker(val=(ord('X'))) #select pulse time<br />
bb.sendMarker(val=2) #set time of dureation pulse to 2ms<br />
<br />
bb.sendMarker(val=(ord('M'))) #select marker out<br />
bb.sendMarker(val=115) #set marker value 115<br />
</syntaxhighlight><br />
<br />
'''Example using BITSI extended analog read in Python:'''<br />
<br />
<syntaxhighlight lang="python" line><br />
#!/usr/bin/env python<br />
<br />
# import the rusocsci.buttonbox module<br />
import serial<br />
<br />
# make a buttonbox<br />
ser = serial.Serial("COM2", 115200, timeout = 0.10 )<br />
ser = serial.Serial("/dev/ttyUSB0", 115200, timeout = 0.10 )<br />
<br />
while True:<br />
ser.write('A1')<br />
ser.flush()<br />
x = ser.readline()<br />
visual.TextStim(win, text=x).draw()<br />
<br />
# black screen for 1000 ms<br />
win.flip()<br />
<br />
key = event.getKeys()<br />
try:<br />
if key[0]=='escape':<br />
break<br />
except:<br />
continue<br />
</syntaxhighlight><br />
<br />
<br/>'''Example using the Buttonbox in PsychoPy:'''<br />
<br />
<syntaxhighlight lang="python" line><br />
#!/usr/bin/env python<br />
<br />
# import psychopy and rusocsci<br />
from psychopy import core, visual <br />
from rusocsci import buttonbox<br />
<br />
## Setup Section<br />
win = visual.Window(monitor="testMonitor")<br />
bb = buttonbox.Buttonbox()<br />
text = visual.TextStim(win, "Press a button on the buttonbox")<br />
<br />
## Experiment Section<br />
# show text<br />
text.draw()<br />
win.flip()<br />
# wait for response<br />
b = bb.waitButtons()<br />
# show response<br />
text.setText("you pressed: {}".format(b))<br />
text.draw()<br />
win.flip()<br />
core.wait(5)<br />
<br />
## Cleanup Section<br />
core.quit()<br />
</syntaxhighlight><br />
<br />
For more documentation click here: http://pythonhosted.org//RuSocSci/index.html<br />
<br><br />
<br><br />
<br />
=== Matlab ===<br />
'''Example using markers with the Buttonbox in Matlab:'''<br />
<br />
Download the file Bitsi.m from the DCCN website: https://intranet.donders.ru.nl/index.php?id=bitsim0<br />
<br> Make sure to have this file in your Matlab path.<br />
<syntaxhighlight lang="matlab" line style="overflow:auto;"><br />
% At the start of your script, create the buttonbox serial object<br />
bb = Bitsi("COM2");<br />
% other code<br />
:<br />
</syntaxhighlight><br />
<br />
BITSI simple mode:<br />
<syntaxhighlight lang="matlab" line style="overflow:auto;"><br />
% This example is for an EEG system sampling at 500Hz samplerate. <br />
% at the start of your script, reset marker<br />
samplerate = 500;<br />
pulseLen = 2000/samplerate;<br />
bb.sendTrigger(0);<br />
% send a marker<br />
val = 1; % val: this is your marker code, range code 1-255<br />
bb.sendTrigger(val);<br />
java.lang.Thread.sleep(pulseLen); % wait long enough for the EEG system to capture the trigger, i.e., 2000/samplerate ms<br />
% reset marker<br />
bb.sendTrigger(0) % Note: if resetting the marker is not possible at this moment in code, you can decide to do this later as long as it has taken place long enough before the next marker has to be sent. Another solution using a timer object instead of a simple delay is outlined below.<br />
</syntaxhighlight><br />
<br />
BITSI extended mode:<br />
<syntaxhighlight lang="matlab" line style="overflow:auto;"><br />
samplerate = 500;<br />
pulseLen = 2000/samplerate;<br />
% select a function<br />
bb.sendTrigger(uint8('X')); % select pulse time<br />
bb.sendTrigger(pulseLen); % set time of duration pulse to (2000/samplerate) ms<br />
<br />
val = 1; % val: this is your marker code, range code 1-255<br />
bb.sendTrigger(uint8('M')); % select marker out<br />
bb.sendTrigger(val); % val: this is your marker code, range code 1-255<br />
</syntaxhighlight><br />
<br />
<syntaxhighlight lang="matlab" line style="overflow:auto;"><br />
% At the end of your script, close the buttonbox serial object<br />
:<br />
bb.close();<br />
</syntaxhighlight><br />
<br />
Reset marker using a timer:<br />
<syntaxhighlight lang="matlab" line style="overflow:auto;"><br />
% At the start of your script, define timer object and callback function<br />
pulseTime = 0.004; % trigger pulse duration in s. NB: extra time will be added due to overhead in calling Matlab functions related to the timer event.<br />
resetMarker = timer('TimerFcn',@(x,y)bb.sendTrigger(0),'StartDelay',pulseTime);<br />
<br />
% replace the code to send a marker with:<br />
val = 1; % val: this is your marker code, range code 1-255<br />
bb.sendTrigger(val);<br />
resetMarker.start(); % this will call bb.sendTrigger(0) after pulseTime seconds (plus some additional overhead)<br />
<br />
</syntaxhighlight></div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Sequence_of_URLs&diff=5713Sequence of URLs2023-06-22T09:38:17Z<p>Wilbert.vanham: </p>
<hr />
<div>[https://www.socsci.ru.nl/tsg/sequence Sequence of URLs] allows you to send the same data as URL parameters to a numbers of URLs that together make up your experiment. Typically You will start from SONA or Prolific, then go to an informed consent form, then to an online experiment or survey and then back to Prolific for completion of the experiment.<br />
= Simple example =<br />
If you want to visit two URLs and let both know that your name is John, you can visit these pages like this:<br />
* https://www.ru.nl?name=John<br />
* https://www.nos.nl?name=John<br />
<br />
But you may want to prevent having to type the same information twice. That is where [https://www.socsci.ru.nl/tsg/sequence Sequence of URLs] can help. Put you two URLs in a sequence:<br />
[[File:Overview .png|border|A sequence of two URLs]]<br />
<br />
now you can visit the following two URLs:<br />
* https://www.socsci.ru.nl/tsg/sequence/123456/0?name=John<br />
* https://www.socsci.ru.nl/tsg/sequence/123456/1<br />
<br />
which will be automatically forwarded to the two URLs mentioned above. Note that the name is automatically send to both pages, while it was entered only for the first.<br />
<br />
= Prolific =<br />
Imagine you want to conduct an online experiment with Prolific and you want to your participants to visit the following three places:<br />
* Informed consent<br />
* Online Experiment<br />
* Prolific completion<br />
<br />
If the informed consent form is of the type that is most common in the Donders Center for Cognition, the experiment is on our exp server this will give you three URL's for these places like this:<br />
* https://questions.socsci.ru.nl/index.php/654321<br />
* https://exp.socsci.ru.nl/coolExperiment<br />
* https://app.prolific.co/submissions/complete?cc=FJ2UID24<br />
<br />
The last of the three comes from Prolific:<br />
<br />
[[File:Prolific completion.png|border|Form on the Prolific study page showing the completion URL.]]<br />
<br />
Since you programmed ''coolExperiment'' yourself you can make sure that the last page contains a link to the completion URL, but to let the informed consent survey know where the experiment is, you have to add it in the first URL like this:<br />
* https://questions.socsci.ru.nl/index.php/654321?url=https://exp.socsci.ru.nl/coolExperiment<br />
* https://exp.socsci.ru.nl/coolExperiment<br />
* https://app.prolific.co/submissions/complete?cc=FJ2UID24<br />
<br />
You may have never done this before by hand, since it is done for you by [[URL Composer]]. This works but typically we want to make it even more complicated. The experiment wants to keep track of the ''prolific pid'' the identify unique participants. In the past we could use [[URL Composer]] for an even more complicated URL, but that no longer works (2023-06-16) therefore we need [https://www.socsci.ru.nl/tsg/sequence Sequence of URLs], a small tool that makes aliases for the three URLs in your experiment and keeps track of the ''prolific pid'' for you. Just enter the three URLs there:<br />
<br />
* https://questions.socsci.ru.nl/index.php/654321?url=https://www.socsci.ru.nl/tsg/sequence/123456/1<br />
* https://exp.socsci.ru.nl/coolExperiment<br />
* https://app.prolific.co/submissions/complete?cc=FJ2UID24<br />
like this. <br />
<br />
[[File:Sequence of URLs.png|border|Three URLs that make up an experiment]]<br />
<br />
Instead of linking to the informed consent form directly, you link prolific to the first URL in the sequence:<br />
[[File:Prolific URL.png|border|form on the prolific study page showing the experiment url.]]<br />
<br />
Now all three URLs will receive the prolific PID, study id, etc.<br />
<br />
= Privacy =<br />
This method looks a bit like the way the worlds largest privacy breakers work. After all these web pages receive the name of the person visiting them without the participant sending it.<br />
This is precisely the intention, but from it is also very different. Rather than saving a persistent cookie and storing the participants information for later use, we save <br />
only the precise information entered by the participant, store it only on the participants computer and store it only during the session. Therefore no separate cookie notice is required.<br />
You only need to inform the participant that the information of the separate parts of the experiment is combined, like you would do anyway when using a method like [https://www.socsci.ru.nl/tsg/composer/ URL composer].</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Sequence_of_URLs&diff=5712Sequence of URLs2023-06-22T07:12:01Z<p>Wilbert.vanham: </p>
<hr />
<div>[Sequence of URLs] Allows you to send the same data as URL parameters to a numbers of URLs that together make up your experiment. Typically You will start from SONA or Prolific, then go to an informed consent form, then to an online experiment or survey and then back to Prolific for completion of the experiment.<br />
= Simple example =<br />
If you want to visit two URLs and let both know that your name is John, you can visit these pages like this:<br />
* https://www.ru.nl?name=John<br />
* https://www.nos.nl?name=John<br />
<br />
But you may want to prevent having to type the same information twice. That is where [https://www.socsci.ru.nl/tsg/sequence Sequence of URLs] can help. Put you two URLs in a sequence:<br />
[[File:Overview .png|border|A sequence of two URLs]]<br />
<br />
now you can visit the following two URLs:<br />
* https://www.socsci.ru.nl/tsg/sequence/123456/0?name=John<br />
* https://www.socsci.ru.nl/tsg/sequence/123456/1<br />
<br />
which will be automatically forwarded to the two URLs mentioned above. Note that the name is automatically send to both pages, while it was entered only for the first.<br />
<br />
= Prolific =<br />
Imagine you want to conduct an online experiment with Prolific and you want to your participants to visit the following three places:<br />
* Informed consent<br />
* Online Experiment<br />
* Prolific completion<br />
<br />
If the informed consent form is of the type that is most common in the Donders Center for Cognition, the experiment is on our exp server this will give you three URL's for these places like this:<br />
* https://questions.socsci.ru.nl/index.php/654321<br />
* https://exp.socsci.ru.nl/coolExperiment<br />
* https://app.prolific.co/submissions/complete?cc=FJ2UID24<br />
<br />
The last of the three comes from Prolific:<br />
<br />
[[File:Prolific completion.png|border|Form on the Prolific study page showing the completion URL.]]<br />
<br />
Since you programmed ''coolExperiment'' yourself you can make sure that the last page contains a link to the completion URL, but to let the informed consent survey know where the experiment is, you have to add it in the first URL like this:<br />
* https://questions.socsci.ru.nl/index.php/654321?url=https://exp.socsci.ru.nl/coolExperiment<br />
* https://exp.socsci.ru.nl/coolExperiment<br />
* https://app.prolific.co/submissions/complete?cc=FJ2UID24<br />
<br />
You may have never done this before by hand, since it is done for you by [[URL Composer]]. This works but typically we want to make it even more complicated. The experiment wants to keep track of the ''prolific pid'' the identify unique participants. In the past we could use [[URL Composer]] for an even more complicated URL, but that no longer works (2023-06-16) therefore we need [https://www.socsci.ru.nl/tsg/sequence Sequence of URLs], a small tool that makes aliases for the three URLs in your experiment and keeps track of the ''prolific pid'' for you. Just enter the three URLs there:<br />
<br />
* https://questions.socsci.ru.nl/index.php/654321?url=https://www.socsci.ru.nl/tsg/sequence/123456/1<br />
* https://exp.socsci.ru.nl/coolExperiment<br />
* https://app.prolific.co/submissions/complete?cc=FJ2UID24<br />
like this. <br />
<br />
[[File:Sequence of URLs.png|border|Three URLs that make up an experiment]]<br />
<br />
Instead of linking to the informed consent form directly, you link prolific to the first URL in the sequence:<br />
[[File:Prolific URL.png|border|form on the prolific study page showing the experiment url.]]<br />
<br />
Now all three URLs will receive the prolific PID, study id, etc.<br />
<br />
= Privacy =<br />
This method looks a bit like the way the worlds largest privacy breakers work. After all these web pages receive the name of the person visiting them without the participant sending it.<br />
This is precisely the intention, but from it is also very different. Rather than saving a persistent cookie and storing the participants information for later use, we save <br />
only the precise information entered by the participant, store it only on the participants computer and store it only during the session. Therefore no separate cookie notice is required.<br />
You only need to inform the participant that the information of the separate parts of the experiment is combined, like you would do anyway when using a method like [https://www.socsci.ru.nl/tsg/composer/ URL composer].</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=File:Overview_.png&diff=5711File:Overview .png2023-06-22T06:58:01Z<p>Wilbert.vanham: </p>
<hr />
<div>Overview page in Sequence of URLs</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=File:Sequence_of_URLs.png&diff=5708File:Sequence of URLs.png2023-06-20T14:48:13Z<p>Wilbert.vanham: Wilbert.vanham uploaded a new version of File:Sequence of URLs.png</p>
<hr />
<div>Three URL's that make up an experiment</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Sequence_of_URLs&diff=5707Sequence of URLs2023-06-16T07:34:36Z<p>Wilbert.vanham: </p>
<hr />
<div>[https://www.socsci.ru.nl/tsg/sequence Sequence of URLs] Allows you to send the same data as URL parameters to a numbers of URLs that together make up your experiment. Typically You will start from SONA or Prolific, then go to an informed consent form, then to an online experiment or survey and then back to Prolific for completion of the experiment.<br />
<br />
= Prolific =<br />
Imagine you want to conduct an online experiment with Prolific and you want to your participants to visit the following three places:<br />
* Informed consent<br />
* Online Experiment<br />
* Prolific completion<br />
<br />
If the informed consent form is of the type that is most common in the Donders Center for Cognition, the experiment is on our exp server this will give you three URL's for these places like this:<br />
* https://questions.socsci.ru.nl/index.php/654321<br />
* https://exp.socsci.ru.nl/coolExperiment<br />
* https://app.prolific.co/submissions/complete?cc=FJ2UID24<br />
<br />
The last of the three comes from Prolific:<br />
<br />
[[File:Prolific completion.png|border|Form on the Prolific study page showing the completion URL.]]<br />
<br />
Since you programmed ''coolExperiment'' yourself you can make sure that the last page contains a link to the completion URL, but to let the informed consent survey know where the experiment is, you have to add it in the first URL like this:<br />
* https://questions.socsci.ru.nl/index.php/654321?url=https://exp.socsci.ru.nl/coolExperiment<br />
* https://exp.socsci.ru.nl/coolExperiment<br />
* https://app.prolific.co/submissions/complete?cc=FJ2UID24<br />
<br />
You may have never done this before by hand, since it is done for you by [[URL Composer]]. This works but typically we want to make it even more complicated. The experiment wants to keep track of the ''prolific pid'' the identify unique participants. In the past we could use [[URL Composer]] for an even more complicated URL, but that no longer works (2023-06-16) therefore we need [https://www.socsci.ru.nl/tsg/sequence Sequence of URLs], a small tool that makes aliases for the three URLs in your experiment and keeps track of the ''prolific pid'' for you. Just enter the three URLs there:<br />
<br />
* https://questions.socsci.ru.nl/index.php/654321?url=https://www.socsci.ru.nl/tsg/sequence/123456/1<br />
* https://exp.socsci.ru.nl/coolExperiment<br />
* https://app.prolific.co/submissions/complete?cc=FJ2UID24<br />
like this. <br />
<br />
[[File:Sequence of URLs.png|border|Three URLs that make up an experiment]]<br />
<br />
Instead of linking to the informed consent form directly, you link prolific to the first URL in the sequence:<br />
[[File:Prolific URL.png|border|form on the prolific study page showing the experiment url.]]<br />
<br />
Now all three URLs will receive the prolific PID, study id, etc.</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Sequence_of_URLs&diff=5706Sequence of URLs2023-06-16T07:32:24Z<p>Wilbert.vanham: </p>
<hr />
<div>[https://www.socsci.ru.nl/tsg/sequence Sequence of URLs] Allows you to send the same data as URL parameters to a numbers of URLs that together make up your experiment. Typically You will start from SONA or Prolific, then go to an informed consent form, then to an online experiment or survey and then back to Prolific for completion of the experiment.<br />
<br />
= Prolific =<br />
Imagine you want to conduct an online experiment with Prolific and you want to your participants to visit the following three places:<br />
* Informed consent<br />
* Online Experiment<br />
* Prolific completion<br />
<br />
If the informed consent form is of the type that is most common in the Donders Center for Cognition, the experiment is on our exp server this will give you three URL's for these places like this:<br />
* https://questions.socsci.ru.nl/index.php/654321<br />
* https://exp.socsci.ru.nl/coolExperiment<br />
* https://app.prolific.co/submissions/complete?cc=FJ2UID24<br />
<br />
The last of the three comes from Prolific:<br />
<br />
[[File:Prolific completion.png|border|Form on the Prolific study page showing the completion URL.]]<br />
<br />
Since you programmed ''coolExperiment'' yourself you can make sure that the last page contains a link to the completion URL, but to let the informed consent survey know where the experiment is, you have to add it in the first URL like this:<br />
* https://questions.socsci.ru.nl/index.php/654321?url=https://exp.socsci.ru.nl/coolExperiment<br />
* https://exp.socsci.ru.nl/coolExperiment<br />
* https://app.prolific.co/submissions/complete?cc=FJ2UID24<br />
<br />
You may have never done this before by hand, since it is done for you by [[URL Composer]]. This works but typically we want to make it even more complicated. The experiment wants to keep track of the ''prolific pid'' the identify unique participants. In the past we could use [[URL Composer]] for an even more complicated URL, but that no longer works (2023-06-16) therefore we need [https://www.socsci.ru.nl/tsg/sequence Sequence of URLs], a small tool that makes aliases for the three URLs in your experiment and keeps track of the ''prolific pid'' for you. Just enter the three URLs there:<br />
<br />
* https://questions.socsci.ru.nl/index.php/654321?url=https://www.socsci.ru.nl/tsg/sequence/123456/1<br />
* https://exp.socsci.ru.nl/coolExperiment<br />
* https://app.prolific.co/submissions/complete?cc=FJ2UID24<br />
like this. <br />
[[File:Sequence of URLs.png|border|Three URLs that make up an experiment]]<br />
<br />
Instead of linking to the informed consent form directly, you link prolific to the first URL in the sequence:<br />
[[File:Prolific URL.png|border|form on the prolific study page showing the experiment url.]]<br />
<br />
Now all three URLs will receive the prolific PID, study id, etc.</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Sequence_of_URLs&diff=5705Sequence of URLs2023-06-16T07:30:25Z<p>Wilbert.vanham: </p>
<hr />
<div>[https://www.socsci.ru.nl/tsg/sequence Sequence of URLs] Allows you to send the same data as URL parameters to a numbers of URLs that together make up your experiment. Typically You will start from SONA or Prolific, then go to an informed consent form, then to an online experiment or survey and then back to Prolific for completion of the experiment.<br />
<br />
= Prolific =<br />
Imagine you want to conduct an online experiment with Prolific and you want to your participants to visit the following three places:<br />
* Informed consent<br />
* Online Experiment<br />
* Prolific completion<br />
<br />
If the informed consent form is of the type that is most common in the Donders Center for Cognition, the experiment is on our exp server this will give you three URL's for these places like this:<br />
* https://questions.socsci.ru.nl/index.php/654321<br />
* https://exp.socsci.ru.nl/coolExperiment<br />
* https://app.prolific.co/submissions/complete?cc=FJ2UID24<br />
<br />
The last of the three comes from Prolific:<br />
[[File:Prolific completion.png|border|left|Form on the Prolific study page showing the completion URL.]]<br />
<br />
Since you programmed ''coolExperiment'' yourself you can make sure that the last page contains a link to the completion URL, but to let the informed consent survey know where the experiment is, you have to add it in the first URL like this:<br />
* https://questions.socsci.ru.nl/index.php/654321?url=https://exp.socsci.ru.nl/coolExperiment<br />
* https://exp.socsci.ru.nl/coolExperiment<br />
* https://app.prolific.co/submissions/complete?cc=FJ2UID24<br />
<br />
You may have never done this before by hand, since it is done for you by [[URL Composer]]. This works but typically we want to make it even more complicated. The experiment wants to keep track of the ''prolific pid'' the identify unique participants. In the past we could use [[URL Composer]] for an even more complicated URL, but that no longer works (2023-06-16) therefore we need [https://www.socsci.ru.nl/tsg/sequence Sequence of URLs], a small tool that makes aliases for the three URLs in your experiment and keeps track of the ''prolific pid'' for you. Just enter the three URLs there:<br />
<br />
* https://questions.socsci.ru.nl/index.php/654321?url=https://www.socsci.ru.nl/tsg/sequence/123456/1<br />
* https://exp.socsci.ru.nl/coolExperiment<br />
* https://app.prolific.co/submissions/complete?cc=FJ2UID24<br />
like this. <br />
[[File:Sequence of URLs.png|border|left|Three URLs that make up an experiment]]<br />
<br />
Instead of linking to the informed consent form directly, you link prolific to the first URL in the sequence:<br />
[[File:Prolific URL.png|border|left|form on the prolific study page showing the experiment url.]]</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Sequence_of_URLs&diff=5704Sequence of URLs2023-06-16T07:28:18Z<p>Wilbert.vanham: </p>
<hr />
<div>[https://www.socsci.ru.nl/tsg/sequence Sequence of URLs] Allows you to send the same data as URL parameters to a numbers of URLs that together make up your experiment. Typically You will start from SONA or Prolific, then go to an informed consent form, then to an online experiment or survey and then back to Prolific for completion of the experiment.<br />
<br />
= Prolific =<br />
Imagine you want to conduct an online experiment with Prolific and you want to your participants to visit the following three places:<br />
* Informed consent<br />
* Online Experiment<br />
* Prolific completion<br />
<br />
If the informed consent form is of the type that is most common in the Donders Center for Cognition, the experiment is on our exp server this will give you three URL's for these places like this:<br />
* https://questions.socsci.ru.nl/index.php/654321<br />
* https://exp.socsci.ru.nl/coolExperiment<br />
* https://app.prolific.co/submissions/complete?cc=FJ2UID24<br />
<br />
The last of the three comes from Prolific:<br />
[[File:Prolific completion.png|frame|left|Form on the Prolific study page showing the completion URL.]]<br />
<br />
Since you programmed ''coolExperiment'' yourself you can make sure that the last page contains a link to the completion URL, but to let the informed consent survey know where the experiment is, you have to add it in the first URL like this:<br />
* https://questions.socsci.ru.nl/index.php/654321?url=https://exp.socsci.ru.nl/coolExperiment<br />
* https://exp.socsci.ru.nl/coolExperiment<br />
* https://app.prolific.co/submissions/complete?cc=FJ2UID24<br />
<br />
You may have never done this before by hand, since it is done for you by [[URL Composer]]. This works but typically we want to make it even more complicated. The experiment wants to keep track of the ''prolific pid'' the identify unique participants. In the past we could use [[URL Composer]] for an even more complicated URL, but that no longer works (2023-06-16) therefore we need [https://www.socsci.ru.nl/tsg/sequence Sequence of URLs], a small tool that makes aliases for the three URLs in your experiment and keeps track of the ''prolific pid'' for you. Just enter the three URLs there:<br />
<br />
* https://questions.socsci.ru.nl/index.php/654321?url=https://www.socsci.ru.nl/tsg/sequence/123456/1<br />
* https://exp.socsci.ru.nl/coolExperiment<br />
* https://app.prolific.co/submissions/complete?cc=FJ2UID24<br />
like this. <br />
[[File:Sequence of URLs.png|frame|left|Three URLs that make up an experiment]]<br />
<br />
Instead of linking to the informed consent form directly, you link prolific to the first URL in the sequence:<br />
[[File:Prolific URL.png|frame|left|form on the prolific study page showing the experiment url.]]</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=File:Sequence_of_URLs.png&diff=5703File:Sequence of URLs.png2023-06-16T07:25:44Z<p>Wilbert.vanham: </p>
<hr />
<div>Three URL's that make up an experiment</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Sequence_of_URLs&diff=5702Sequence of URLs2023-06-13T21:54:21Z<p>Wilbert.vanham: /* Sequence */</p>
<hr />
<div>= Sequence =<br />
[https://www.socsci.ru.nl/tsg/sequence Sequence] Allows you to send the same data as URL parameters to a num,bers of URLs that together make up your experiment. Typically You will start from SONA or Prolific, then go to an informed consent form, then to an online experiment or survey and then back to Prolific for completion of the experiment.<br />
<br />
== Prolific ==<br />
[[File:Prolific URL.png|frame|left|form on the prolific study page showing the experiment url.]]<br />
<br />
[[File:Prolific completion.png|frame|left|Form on the Prolific study page showing the completion URL.]]</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Sequence_of_URLs&diff=5701Sequence of URLs2023-06-13T21:53:48Z<p>Wilbert.vanham: /* Sequence */</p>
<hr />
<div>=== Sequence ===<br />
[https://www.socsci.ru.nl/tsg/sequence Sequence] Allows you to send the same data as URL parameters to a num,bers of URLs that together make up your experiment. Typically You will start from SONA or Prolific, then go to an informed consent form, then to an online experiment or survey and then back to Prolific for completion of the experiment.<br />
[[File:Prolific URL.png|frame|left|form on the prolific study page showing the experiment url.]]<br />
<br />
[[File:Prolific completion.png|frame|left|Form on the Prolific study page showing the completion URL.]]</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Sequence_of_URLs&diff=5700Sequence of URLs2023-06-13T21:53:21Z<p>Wilbert.vanham: /* Sequence */</p>
<hr />
<div>=== Sequence ===<br />
[https://www.socsci.ru.nl/tsg/sequence Sequence] Allows you to send the same data as URL parameters to a num,bers of URLs that together make up your experiment. Typically You will start from SONA or Prolific, then go to an informed consent form, then to an online experiment or survey and then back to Prolific for completion of the experiment.<br />
[[File:Prolific URL.png|frame|left|form on the prolific study page showing the experiment url.]]<br />
<br />
[[File:Prolific completion.png|frame|left|Form on the Prolific study page showing the experiment URL.]]</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Sequence_of_URLs&diff=5699Sequence of URLs2023-06-13T21:51:59Z<p>Wilbert.vanham: Created page with "=== Sequence === [https://www.socsci.ru.nl/tsg/sequence Sequence] Allows you to send the same data as URL parameters to a num,bers of URLs that together make up your experimen..."</p>
<hr />
<div>=== Sequence ===<br />
[https://www.socsci.ru.nl/tsg/sequence Sequence] Allows you to send the same data as URL parameters to a num,bers of URLs that together make up your experiment. Typically You will start from SONA or Prolific, then go to an informed consent form, then to an online experiment or survey and then back to Prolific for completion of the experiment.<br />
[[File:Prolific URL.png|thumb|Form on the Prolific study page showing the experiment URL.]]<br />
<br />
[[File:Prolific completion.png|thumb|Form on the Prolific study page showing the experiment URL.]]</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=File:Prolific_completion.png&diff=5698File:Prolific completion.png2023-06-13T21:51:31Z<p>Wilbert.vanham: </p>
<hr />
<div>Form on the Prolific study page showing the completion URL.</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=File:Prolific_URL.png&diff=5697File:Prolific URL.png2023-06-13T21:50:17Z<p>Wilbert.vanham: </p>
<hr />
<div>Form on the Prolific study page showing the experiment URL.</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Toolbox&diff=5696Toolbox2023-06-13T21:43:27Z<p>Wilbert.vanham: </p>
<hr />
<div>This page contains a number of tools for (online) experiments. The tool may only be some manual or description or it may be an app.<br />
<br />
* [[Participant Identification Code]]<br />
* [[Participant Counter]]<br />
* [[Mounting a Webdav File System]]<br />
* [[Sequence of URLs]]<br />
* [https://www.socsci.ru.nl/tsg/composer Composer of nested URLs for informed consent forms]</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Help:LimeSurvey/Collaboration&diff=5621Help:LimeSurvey/Collaboration2023-04-18T07:46:13Z<p>Wilbert.vanham: /* Collaborating with RU employees and students */</p>
<hr />
<div>== Collaborating with RU employees and students ==<br />
'''this is the preferred method'''<br />
<br />
If you wish to make a survey together with other RU employees, students or externals, you can add users and user groups in the ''Survey permissions'' section.<br />
<br />
[[File:Coadmins2.png]]<br />
<br />
== Collaborating with anyone in the world ==<br />
To allow people who do not have a university login to access a survey you can give them acces through your own account. '''Do not give them the password that comes with your university number!''' Rather click the ''Forgot your password?'' link in the main logon screen:<br />
<br />
[[File:Login2.png]]<br />
<br />
You will receive an additional password for your account by email. This additional password is stored in the ''Limesurvey internal database''. Select this database when logging on to Liemsurvey (see image above). This way people can edit surveys on your behalf. This additional password only works for Limesurvey.</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Help:LimeSurvey/Collaboration&diff=5620Help:LimeSurvey/Collaboration2023-04-18T07:45:59Z<p>Wilbert.vanham: /* Collaborating with RU employees and students */</p>
<hr />
<div>== Collaborating with RU employees and students ==<br />
'''this is the preferred method'''<br />
<br />
If you wish to make a survey together with other RU employees, students or externals, you can add users and user groups in the Survey permissions section.<br />
<br />
[[File:Coadmins2.png]]<br />
<br />
== Collaborating with anyone in the world ==<br />
To allow people who do not have a university login to access a survey you can give them acces through your own account. '''Do not give them the password that comes with your university number!''' Rather click the ''Forgot your password?'' link in the main logon screen:<br />
<br />
[[File:Login2.png]]<br />
<br />
You will receive an additional password for your account by email. This additional password is stored in the ''Limesurvey internal database''. Select this database when logging on to Liemsurvey (see image above). This way people can edit surveys on your behalf. This additional password only works for Limesurvey.</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=File:Coadmins2.png&diff=5619File:Coadmins2.png2023-04-18T07:45:29Z<p>Wilbert.vanham: </p>
<hr />
<div>add an admin</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Help:LimeSurvey/Collaboration&diff=5618Help:LimeSurvey/Collaboration2023-04-18T07:42:45Z<p>Wilbert.vanham: /* Collaborating with anyone in the world */</p>
<hr />
<div>== Collaborating with RU employees and students ==<br />
'''this is the preferred method'''<br />
<br />
If you wish to make a survey together with other RU employees, students or externals, you can add users and user groups in the Survey permissions section.<br />
<br />
[[File:Coadmins.png]]<br />
<br />
== Collaborating with anyone in the world ==<br />
To allow people who do not have a university login to access a survey you can give them acces through your own account. '''Do not give them the password that comes with your university number!''' Rather click the ''Forgot your password?'' link in the main logon screen:<br />
<br />
[[File:Login2.png]]<br />
<br />
You will receive an additional password for your account by email. This additional password is stored in the ''Limesurvey internal database''. Select this database when logging on to Liemsurvey (see image above). This way people can edit surveys on your behalf. This additional password only works for Limesurvey.</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=File:Login2.png&diff=5617File:Login2.png2023-04-18T07:42:23Z<p>Wilbert.vanham: </p>
<hr />
<div>Limesurvey 5 login page</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=LimeSurvey&diff=5616LimeSurvey2023-04-18T07:40:11Z<p>Wilbert.vanham: /* Template */</p>
<hr />
<div>{{Infobox software<br />
| name = LimeSurvey<br />
| logo = Limesurvey_logo.png<br />
| logo size = 200px<br />
| logo alt = Limesurvey<br />
| screenshot = Limesurvey_screenshot01.jpg<br />
| caption = A Limesurvey survey with the Radboud template<br />
| developer = <br />
| installed version = 5<br />
| installed version date = <!-- {{Start date and age|YYYY|MM|DD|df=yes}} --><br />
| platform = Web<br />
| language count = 84<br />
| website = [http://limesurvey.org limesurvey.org]<br />
| resources = <br />
{{Infobox tsg<br />
| child = yes<br />
| header2 = Radboud Survey 5<br />
| data2 = *[https://questions.socsci.ru.nl/admin Admin Login]<br />
| manuals = {{bulleted list<br />
| [http://manual.limesurvey.org/ Manual]<br />
}}<br />
}}<br />
}}<br />
== General ==<br />
LimeSurvey is a popular open source system for making and publishing surveys. All students and staff of the Faculty of Social Sciences can use it. <br />
<br />
Log on to [https://questions.socsci.ru.nl/index.php/admin questions.socsci.ru.nl/admin] with your university number and password to make a survey. Invitations to surveys can be send with a direct link to the survey (e.g. ''[https://questions.socsci.ru.nl/index.php/123456 https://questions.socsci.ru.nl/index.php/123456?lang=en]'') or by referring to the main survey page ''[http://survey.socsci.ru.nl questions.socsci.ru.nl]''. Note that in the latter case the participant has to find the survey in a list. By default surveys are not listed on the main page. Change this in the ''survey settings'' if you wish. The preferred way is using direct links. <br />
<br />
There is no limit on the number of surveys that you can make or the number of participants in a survey.<br />
<br />
== Tutorial ==<br />
There is a [https://www.socsci.ru.nl/wilberth/limesurvey/01intro.html Limesurvey beginner tutorial] for use of Limesurvey on the Radboud University Faculty of Social Sciences.<br />
<br />
== Callaboration ==<br />
To work with multiple people on the same survey, follow the instructions on our [[Help:LimeSurvey/Collaboration|Collaboration]] page.<br />
<br />
== Template ==<br />
[http://questions.socsci.ru.nl questions.socsci.ru.nl] uses an unobtrusive Radboud-branded template called ''radboud''. It is be applied by default. If you want to use a different template, go to:<br/><br />
Survey properties -> General settings -> Presentation & navigation -> Template -> Radboud -> Save <br/><br />
<br />
== Sona integration ==<br />
If you want to use Sona to invite people to take your survey, please follow the [http://www.sona-systems.com/help/limesurvey.aspx manual provided bij Sona]. Furthermore, if this participant ID should be stored in LimeSurvey such that it is possible to link a response to a participant ID, then you would also have to follow the instructions in the [https://manual.limesurvey.org/Panel_integration manual provided by LimeSurvery]. Please make sure to test whether it works with a [https://tsgdoc.socsci.ru.nl/index.php/Online_experiment_systems#Pilot_Run pilot run].<br />
<br />
== Data Storage ==<br />
Surveys and collected data are stored on campus. The server is not to be used for long term data storage. Surveys and data may be removed after a year without prior warning.<br />
<br />
== Support ==<br />
The TSG provides limited technical support for Limesurvey. Users themselves are responsible for the creation and design of their surveys, as well as the data analysis. For Help on designing your survey you can contact [mailto:p.vangroenestijn@maw.ru.nl Pieter van Groenestijn (RTOG)]. For questions about the use of Limesurvey, please consult the [http://manual.limesurvey.org/ manual] or the [https://www.limesurvey.org/community community support]. <br />
For technical support, contact our [[LimeSurvey/Administrators|administrator(s)]].<br />
<br />
<!-- == References ==<br />
<references /><br />
--><br />
<br />
==External Links== <!-- Optional --><br />
*{{Official website|http://limesurvey.org}}<br />
* [http://questions.socsci.ru.nl Radboud Survey]</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=LimeSurvey&diff=5615LimeSurvey2023-04-18T07:39:36Z<p>Wilbert.vanham: /* Template */</p>
<hr />
<div>{{Infobox software<br />
| name = LimeSurvey<br />
| logo = Limesurvey_logo.png<br />
| logo size = 200px<br />
| logo alt = Limesurvey<br />
| screenshot = Limesurvey_screenshot01.jpg<br />
| caption = A Limesurvey survey with the Radboud template<br />
| developer = <br />
| installed version = 5<br />
| installed version date = <!-- {{Start date and age|YYYY|MM|DD|df=yes}} --><br />
| platform = Web<br />
| language count = 84<br />
| website = [http://limesurvey.org limesurvey.org]<br />
| resources = <br />
{{Infobox tsg<br />
| child = yes<br />
| header2 = Radboud Survey 5<br />
| data2 = *[https://questions.socsci.ru.nl/admin Admin Login]<br />
| manuals = {{bulleted list<br />
| [http://manual.limesurvey.org/ Manual]<br />
}}<br />
}}<br />
}}<br />
== General ==<br />
LimeSurvey is a popular open source system for making and publishing surveys. All students and staff of the Faculty of Social Sciences can use it. <br />
<br />
Log on to [https://questions.socsci.ru.nl/index.php/admin questions.socsci.ru.nl/admin] with your university number and password to make a survey. Invitations to surveys can be send with a direct link to the survey (e.g. ''[https://questions.socsci.ru.nl/index.php/123456 https://questions.socsci.ru.nl/index.php/123456?lang=en]'') or by referring to the main survey page ''[http://survey.socsci.ru.nl questions.socsci.ru.nl]''. Note that in the latter case the participant has to find the survey in a list. By default surveys are not listed on the main page. Change this in the ''survey settings'' if you wish. The preferred way is using direct links. <br />
<br />
There is no limit on the number of surveys that you can make or the number of participants in a survey.<br />
<br />
== Tutorial ==<br />
There is a [https://www.socsci.ru.nl/wilberth/limesurvey/01intro.html Limesurvey beginner tutorial] for use of Limesurvey on the Radboud University Faculty of Social Sciences.<br />
<br />
== Callaboration ==<br />
To work with multiple people on the same survey, follow the instructions on our [[Help:LimeSurvey/Collaboration|Collaboration]] page.<br />
<br />
== Template ==<br />
questions.socsci.ru.nl uses a unobtrusive Radboud-branded template called ''radboud''. It is be applied by default. If you want to use a different template, go to:<br/><br />
Survey properties -> General settings -> Presentation & navigation -> Template -> Radboud -> Save <br/><br />
<br />
== Sona integration ==<br />
If you want to use Sona to invite people to take your survey, please follow the [http://www.sona-systems.com/help/limesurvey.aspx manual provided bij Sona]. Furthermore, if this participant ID should be stored in LimeSurvey such that it is possible to link a response to a participant ID, then you would also have to follow the instructions in the [https://manual.limesurvey.org/Panel_integration manual provided by LimeSurvery]. Please make sure to test whether it works with a [https://tsgdoc.socsci.ru.nl/index.php/Online_experiment_systems#Pilot_Run pilot run].<br />
<br />
== Data Storage ==<br />
Surveys and collected data are stored on campus. The server is not to be used for long term data storage. Surveys and data may be removed after a year without prior warning.<br />
<br />
== Support ==<br />
The TSG provides limited technical support for Limesurvey. Users themselves are responsible for the creation and design of their surveys, as well as the data analysis. For Help on designing your survey you can contact [mailto:p.vangroenestijn@maw.ru.nl Pieter van Groenestijn (RTOG)]. For questions about the use of Limesurvey, please consult the [http://manual.limesurvey.org/ manual] or the [https://www.limesurvey.org/community community support]. <br />
For technical support, contact our [[LimeSurvey/Administrators|administrator(s)]].<br />
<br />
<!-- == References ==<br />
<references /><br />
--><br />
<br />
==External Links== <!-- Optional --><br />
*{{Official website|http://limesurvey.org}}<br />
* [http://questions.socsci.ru.nl Radboud Survey]</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Presentation_modes&diff=5587Presentation modes2023-01-23T11:40:02Z<p>Wilbert.vanham: /* Detection */</p>
<hr />
<div>Presentation mode or present mode describes mainly the timing decisions involved in transferring an image from the computer to the monitor. In most situations you will not care about presentation mode, but if accuracy of timing is important, you should care about presention mode. This page uses terminology from the Vulkan API. It may be slightly different from terminology in other API's or commercials.<br />
== Modes ==<br />
There are four presentation modes:<br />
=== FIFO ===<br />
This is the most desired mode for experiments. Once an image is completed, it is scheduled for presentation. Typically there will be two images or buffers. One image is being prepared, one is being written to the screen. If no new image has been scheduled for presentation. The first image will be send again to the screen. If an image has been scheduled. The program will have to wait for the first image to be send completely before continuing. This waiting is desirable since it gives the program information about when the computer starts sending the image to the screen for the first time. This moment will typically be only a very short while before an optional [[Vertical_Sync_sensor|vertical sync sensor]] reports the image starting to appear on the screen.<br />
=== immediate ===<br />
This is usually not a desired mode. Once an image is completed, it is scheduled for presentation. The image being send the the screen is switched to the new image immediately. This may result in the lower part of the on screen image being part of the new image and the upper part begin part of the old image. The present function will return immediately and give no information about the monitor sync. Using the [[Vertical_Sync_sensor|vertical sync sensor]] is only useful if it is mounted on the monitor at the same height as the stimulus. If it is mounted on the top left and the stimulus is in the center, the sensor may send a signal one frame after showing the image on screen.<br />
=== FIFO relaxed ===<br />
This mode is like FIFO except when the image currently being send to the screen has been send before, then the image switch takes place immediately, like in immediate mode. When using FIFO relaxed mode, it is best to send images to the screen in quick succession to avoid the relaxed behavior. (option 1)<br />
<br />
If it is not possible to send images quickly, and synchronization is desired (the program must wait for the screen), make sure to send an image that is not a stimulus just before the stimulus with which the program must synchronize. If a [[Vertical_Sync_sensor|vertical sync sensor]] is used, make sure to send at least two blank images, or one blank image after a long wait (>0.1 s), before the stimulus image to make sure the sensor sees a blank screen before the stimulus. (option 2)<br />
<br />
If both is not possible you may want to take the precautions mentioned for immediate mode.<br />
<br />
This is the mode you will for now unfortunately have to work with when using Psychopy on our labcomputer.<br />
=== mailbox ===<br />
This mode typically uses more than two images. The program never waits for the monitor, like in immediate mode. If the image chain is full, the oldest image (that has not yet been written to screen) will be discarded. It is useful for reducing on high performance hardware latency since the most recently generated images are shown.<br />
<br />
<br />
== Detection ==<br />
You may not have control over the presentation mode, as is the case when using Psychopy on our labcomputer without discrete graphics hardware. You can however often detect it. Use this script ([[File:ModeTest.zip|thumb]]) the detect which mode your computer uses in Psychopy.</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=File:ModeTest.zip&diff=5586File:ModeTest.zip2023-01-23T11:38:42Z<p>Wilbert.vanham: </p>
<hr />
<div>Python script to test presentation mode</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Presentation_modes&diff=5584Presentation modes2023-01-23T11:33:55Z<p>Wilbert.vanham: initial</p>
<hr />
<div>Presentation mode or present mode describes mainly the timing decisions involved in transferring an image from the computer to the monitor. In most situations you will not care about presentation mode, but if accuracy of timing is important, you should care about presention mode. This page uses terminology from the Vulkan API. It may be slightly different from terminology in other API's or commercials.<br />
== Modes ==<br />
There are four presentation modes:<br />
=== FIFO ===<br />
This is the most desired mode for experiments. Once an image is completed, it is scheduled for presentation. Typically there will be two images or buffers. One image is being prepared, one is being written to the screen. If no new image has been scheduled for presentation. The first image will be send again to the screen. If an image has been scheduled. The program will have to wait for the first image to be send completely before continuing. This waiting is desirable since it gives the program information about when the computer starts sending the image to the screen for the first time. This moment will typically be only a very short while before an optional [[Vertical_Sync_sensor|vertical sync sensor]] reports the image starting to appear on the screen.<br />
=== immediate ===<br />
This is usually not a desired mode. Once an image is completed, it is scheduled for presentation. The image being send the the screen is switched to the new image immediately. This may result in the lower part of the on screen image being part of the new image and the upper part begin part of the old image. The present function will return immediately and give no information about the monitor sync. Using the [[Vertical_Sync_sensor|vertical sync sensor]] is only useful if it is mounted on the monitor at the same height as the stimulus. If it is mounted on the top left and the stimulus is in the center, the sensor may send a signal one frame after showing the image on screen.<br />
=== FIFO relaxed ===<br />
This mode is like FIFO except when the image currently being send to the screen has been send before, then the image switch takes place immediately, like in immediate mode. When using FIFO relaxed mode, it is best to send images to the screen in quick succession to avoid the relaxed behavior. (option 1)<br />
<br />
If it is not possible to send images quickly, and synchronization is desired (the program must wait for the screen), make sure to send an image that is not a stimulus just before the stimulus with which the program must synchronize. If a [[Vertical_Sync_sensor|vertical sync sensor]] is used, make sure to send at least two blank images, or one blank image after a long wait (>0.1 s), before the stimulus image to make sure the sensor sees a blank screen before the stimulus. (option 2)<br />
<br />
If both is not possible you may want to take the precautions mentioned for immediate mode.<br />
<br />
This is the mode you will for now unfortunately have to work with when using Psychopy on our labcomputer.<br />
=== mailbox ===<br />
This mode typically uses more than two images. The program never waits for the monitor, like in immediate mode. If the image chain is full, the oldest image (that has not yet been written to screen) will be discarded. It is useful for reducing on high performance hardware latency since the most recently generated images are shown.<br />
<br />
== Detection ==<br />
You may not have control over the presentation mode, as is the case when using Psychopy on our labcomputer without discrete graphics hardware. You can however often detect it. Use this script the detect which mode your computer uses in Psychopy.</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Vertical_Sync_sensor&diff=5583Vertical Sync sensor2023-01-23T10:42:59Z<p>Wilbert.vanham: </p>
<hr />
<div>{{Infobox tsg<br />
| name = Vertical Sync sensor<br />
| image = sensorPic.jpg<br />
| caption = Vertical Sync sensor<br />
}}<br />
{{Infobox tsg<br />
| name = Seeed Studio XIAO SAMD21<br />
| image = Seeeduino_XIAO.JPG<br />
| caption = Seeed Studio XIAO SAMD21<br />
| downloads = {{bulleted list<br />
| [https://wiki.seeedstudio.com/Seeeduino-XIAO/ product_page]<br />
}}<br />
}}<br />
{{Infobox tsg<br />
| name = TEMT6000 Licht Sensor Module<br />
| image = temt6000.jpg<br />
| caption = TEMT6000 Licht Sensor Module<br />
| downloads = {{bulleted list<br />
| [https://surfdrive.surf.nl/files/index.php/s/Mpdr2DGEFlwetag Datasheet]<br />
}}<br />
}}<br />
<br />
The Vertical Sync sensor is used on a computer/laptop monitor for time accurate visual presentation. The sensor measures screen brightness. It generates a BITSI trigger to the com-port("A" = ON/light, "a" = OFF/noLight) when the amount of light is higher than the (customizable) threshold. This means that the onset of visual stimulus on screen can be marked. It can easily be attached with a pincher to the screen. The Vertical Sync sensor is connected to a computer with a usb connection, a serial port is emulated. You may want to read about [[presentation modes]] in order to decide how to use the sync sensor.<br />
<br />
== BITSI Protocol ==<br />
<br />
BITSI stands for Bits to Serial Interface.<br />
{| class="wikitable" <br />
|- <br />
! scope="row" colspan="3" | Vertical Sync sensor<br />
|-<br />
! scope="row" width="120px" | ASCII (rise/fall)<br />
! scope="row" width="120px" | Code (rise/fall)<br />
! scope="row" width="120px" | Light<br />
|-<br />
| A / a || 65 / 97 || ON / OFF<br />
|-<br />
|}<br />
<br />
Meaning when light falls on the sensor, a capital A will be sent to the serial port. A lowercase 'a' will be sent when the signal is deactivated(no light).<br />
<br />
===Output===<br />
<br />
The treshold for monitor OFF is customizable and can be specified by sending a byte to specify the value for screen OFF. Any byte satisfies, see example code.<br />
<br />
== Port Settings ==<br />
<br />
===Serial port===<br />
<br />
Our hardware design allows to be connected to the computers USB and emulates a serial communication Port.<br />
<br />
{| class="wikitable"<br />
|-<br />
| Baudrate || 115200<br />
|-<br />
| Parity || None<br />
|-<br />
| Data bits || 8<br />
|-<br />
| Stop bits || 1<br />
|-<br />
| Flow control || None<br />
|-<br />
|}<br />
<br />
=== USB-Com port ===<br />
<br />
1.Connect the Vertical Sync sensor to your computer using the USB cable.<br />
<br />
2.When you connect the Vertical Sync sensor, Windows should initiate the driver installation process (if you haven't used the computer with an Vertical Sync sensor before).<br />
<br />
'''How to Check the Com Port settings(important!)'''<br />
<br />
*From the Start menu, open the '''Control Panel'''.<br />
<br />
*From the control panel, open the '''System window'''.<br />
<br />
*From the system properties window, go to the '''Hardware tab''' and click the '''Device Manager''' button.<br />
<br />
*From the Device Manager window, click '''Ports (Com&LPT).''' You should now be able to see which Com Port the USB adapter is assigned to.<br />
<br />
*If the Com Port is 10 or higher, you will have to change it to a lower port.<br />
<br />
*From the Device Manager window, click on '''USB Serial Port (Com#).''' Click the '''Port Settings tab''' of the USB Serial Port Properties window, and then click the '''Advanced''' button.<br />
<br />
*In the Advanced Settings window, use the scroll input to select a '''Com Port''' (select 10 or lower). Change '''Receive (bytes)''' and '''Transmit (bytes)''' to 64. Change the '''Latency Timer''' to 1.<br />
<br />
*Click the OK button.<br />
<br />
Always connect the usb device to the same port and your settings will be remembered.<br />
<br />
== Software Settings ==<br />
<br />
=== Python/PsychoPy ===<br />
<br />
<br/>'''The basics using the Vertical Sync sensor in PsychoPy:'''<br />
<br />
<syntaxhighlight lang="python" line><br />
# initialize treshold for OFF by sending a code<br />
ser.write(b'1')<br />
<br />
visual.Rect(win, .15, .25, pos=(-1, 1),fillColor="white", units="norm").draw()<br />
win.flip()<br />
# wait for a sync square<br />
b = ser.read()<br />
</syntaxhighlight><br />
<br />
<br/>'''Example script using the Vertical Sync sensor in PsychoPy:'''<br />
<br />
<syntaxhighlight lang="python" line><br />
#!/usr/bin/env python<br />
<br />
# import psychopy and rusocsci<br />
from psychopy import core, visual <br />
import serial<br />
import time<br />
<br />
## Setup Section<br />
win = visual.Window([400,400], fullscr=True, winType = "pyglet", monitor="testMonitor",color=(-1, -1, -1), waitBlanking=True)<br />
# connect to Vertical Sync sensor, find correct com port number<br />
ser = serial.Serial('com3', 115200, timeout=1.0)<br />
# create sync box left corner<br />
rect = visual.Rect(win, .15, .25, pos=(-1, 1),fillColor="white", units="norm")<br />
<br />
# wait 5 sec for python to become stabel<br />
core.wait(5)<br />
ser.flushInput()<br />
# define screen OFF by sending a code<br />
ser.write(b'1')<br />
<br />
## Experiment Section<br />
# show sync box left corner<br />
rect.draw()<br />
win.flip()<br />
tik = time.perf_counter()<br />
# wait for a sync square<br />
b = ser.read()<br />
tok = time.perf_counter()<br />
# show delay after a flip<br />
print("your timing after a flip: {}s".format(tok-tik))<br />
# as a remark 60Hz/~0.016s 120Hz/~0.008s<br />
<br />
## Cleanup Section<br />
core.quit()<br />
</syntaxhighlight><br />
<br />
=== Matlab ===<br />
'''Example using markers with the Buttonbox in Matlab:'''<br />
<br />
Download the file Bitsi.m from the DCCN website: https://intranet.donders.ru.nl/index.php?id=bitsim0<br />
<br> Make sure to have this file in your Matlab path.<br />
<syntaxhighlight lang="matlab" line style="overflow:auto;"><br />
% At the start of your script, create the buttonbox serial object<br />
bb = Bitsi("COM2");<br />
% other code<br />
:<br />
</syntaxhighlight><br />
<br />
BITSI simple mode:<br />
<syntaxhighlight lang="matlab" line style="overflow:auto;"><br />
% This example is for an EEG system sampling at 500Hz samplerate. <br />
% at the start of your script, reset marker<br />
samplerate = 500;<br />
pulseLen = 2000/samplerate;<br />
bb.sendTrigger(0);<br />
% send a marker<br />
val = 1; % val: this is your marker code, range code 1-255<br />
bb.sendTrigger(val);<br />
java.lang.Thread.sleep(pulseLen); % wait long enough for the EEG system to capture the trigger, i.e., 2000/samplerate ms<br />
% reset marker<br />
bb.sendTrigger(0) % Note: if resetting the marker is not possible at this moment in code, you can decide to do this later as long as it has taken place long enough before the next marker has to be sent.<br />
</syntaxhighlight></div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=LimeSurvey&diff=5523LimeSurvey2022-10-18T07:04:00Z<p>Wilbert.vanham: /* Template */ is suitable for small screens</p>
<hr />
<div>{{Infobox software<br />
| name = LimeSurvey<br />
| logo = Limesurvey_logo.png<br />
| logo size = 200px<br />
| logo alt = Limesurvey<br />
| screenshot = Limesurvey_screenshot01.jpg<br />
| caption = A Limesurvey survey with the Radboud template<br />
| developer = <br />
| installed version = 5<br />
| installed version date = <!-- {{Start date and age|YYYY|MM|DD|df=yes}} --><br />
| platform = Web<br />
| language count = 84<br />
| website = [http://limesurvey.org limesurvey.org]<br />
| resources = <br />
{{Infobox tsg<br />
| child = yes<br />
| header2 = Radboud Survey 5<br />
| data2 = *[https://questions.socsci.ru.nl/admin Admin Login]<br />
| manuals = {{bulleted list<br />
| [http://manual.limesurvey.org/ Manual]<br />
}}<br />
}}<br />
}}<br />
== General ==<br />
LimeSurvey is a popular open source system for making and publishing surveys. All students and staff of the Faculty of Social Sciences can use it. <br />
<br />
Log on to [https://questions.socsci.ru.nl/index.php/admin questions.socsci.ru.nl/admin] with your university number and password to make a survey. Invitations to surveys can be send with a direct link to the survey (e.g. ''[https://questions.socsci.ru.nl/index.php/123456 https://questions.socsci.ru.nl/index.php/123456?lang=en]'') or by referring to the main survey page ''[http://survey.socsci.ru.nl questions.socsci.ru.nl]''. Note that in the latter case the participant has to find the survey in a list. By default surveys are not listed on the main page. Change this in the ''survey settings'' if you wish. The preferred way is using direct links. <br />
<br />
There is no limit on the number of surveys that you can make or the number of participants in a survey.<br />
<br />
== Tutorial ==<br />
There is a [https://www.socsci.ru.nl/wilberth/limesurvey/01intro.html Limesurvey beginner tutorial] for use of Limesurvey on the Radboud University Faculty of Social Sciences.<br />
<br />
== Callaboration ==<br />
To work with multiple people on the same survey, follow the instructions on our [[Help:LimeSurvey/Collaboration|Collaboration]] page.<br />
<br />
== Template ==<br />
The TSG has helped to create a Radboud-branded template for Limesurvey. When creating a new survey, it should be applied by default. If not, go to:<br/><br />
Survey properties -> General settings -> Presentation & navigation -> Template -> Radboud -> Save <br/><br />
[[File:Limesurvey_theme.png|thumb|none|480px|Select Radboud Template]]<br />
<br />
== Sona integration ==<br />
If you want to use Sona to invite people to take your survey, please follow the [http://www.sona-systems.com/help/limesurvey.aspx manual provided bij Sona]. Furthermore, if this participant ID should be stored in LimeSurvey such that it is possible to link a response to a participant ID, then you would also have to follow the instructions in the [https://manual.limesurvey.org/Panel_integration manual provided by LimeSurvery]. Please make sure to test whether it works with a [https://tsgdoc.socsci.ru.nl/index.php/Online_experiment_systems#Pilot_Run pilot run].<br />
<br />
== Data Storage ==<br />
Surveys and collected data are stored on campus. The server is not to be used for long term data storage. Surveys and data may be removed after a year without prior warning.<br />
<br />
== Support ==<br />
The TSG provides limited technical support for Limesurvey. Users themselves are responsible for the creation and design of their surveys, as well as the data analysis. For Help on designing your survey you can contact [mailto:p.vangroenestijn@maw.ru.nl Pieter van Groenestijn (RTOG)]. For questions about the use of Limesurvey, please consult the [http://manual.limesurvey.org/ manual] or the [https://www.limesurvey.org/community community support]. <br />
For technical support, contact our [[LimeSurvey/Administrators|administrator(s)]].<br />
<br />
<!-- == References ==<br />
<references /><br />
--><br />
<br />
==External Links== <!-- Optional --><br />
*{{Official website|http://limesurvey.org}}<br />
* [http://questions.socsci.ru.nl Radboud Survey]</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=TemperatureHumidity&diff=5520TemperatureHumidity2022-10-11T07:50:53Z<p>Wilbert.vanham: /* Potential problems */</p>
<hr />
<div>{{Infobox tsg<br />
| name = TemperatureHumidity<br />
| image = <br />
| caption = TemperatureHumidity device<br />
| downloads = {{bulleted list<br />
| [[Media:temperaturehumidity.zip|Custom Module]]<br />
| [https://pypi.python.org/pypi/RuSocSci RuSocSci] (Python package)<br />
}}<br />
}}<br />
<br />
The TemperatureHumidity is a little (15 x 5 x 5 cm) black box with a black sphere on top. It is connected to your computer with the attached USB cable. When connected it will identify itself as a Virtual Serial port. <br />
<br />
== Installation ==<br />
Install the ''rusocsci'' package. On the lab computers it may already be installed for you. Also install ''pytz'', ''python-dateutil'' and ''pyqt4''. Download the [[Media:temperaturehumidity.zip|temperaturehumidity module]] and unzip it in the same directory as your experiment.<br />
<br />
== Testing ==<br />
Run the temperaturehumidity module and sensor by running the file 'temperaturehumidity.py'. Double click it in explorer or load in the Psychopy Coder and click 'run'.<br />
<br />
== Code example ==<br />
You can read temperature and humidity values with any software that connects to a serial port. Most conveniently you can use the [https://pypi.python.org/pypi/RuSocSci RuSocSci] library in python. Here is a little example how to write a script that reads the temperature and humidity and writes it to the standard output (console):<br />
<syntaxhighlight lang="python"><br />
#!/usr/bin/env python3<br />
import temperaturehumidity<br />
th = temperaturehumidity.TemperatureHumidity()<br />
print(th.waitString())<br />
</syntaxhighlight><br />
<br />
== Potential problems ==<br />
The temperaturehumidity device identifies as a buttonbox. Lab computer are set up in a way that makes the second buttonbox behave different from all other devices. If you are using both the buttonbox and the temperaturehumidity device, please look up the port name of the temperaturehumidity device in the windows device manager and if it is for instance 'COM3' then change the code above into:<br />
<syntaxhighlight lang="python"><br />
#!/usr/bin/env python3<br />
import temperaturehumidity<br />
th = temperaturehumidity.TemperatureHumidity(port='COM3')<br />
print(th.waitString())<br />
</syntaxhighlight></div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=TemperatureHumidity&diff=5519TemperatureHumidity2022-10-11T07:50:39Z<p>Wilbert.vanham: /* Code example */</p>
<hr />
<div>{{Infobox tsg<br />
| name = TemperatureHumidity<br />
| image = <br />
| caption = TemperatureHumidity device<br />
| downloads = {{bulleted list<br />
| [[Media:temperaturehumidity.zip|Custom Module]]<br />
| [https://pypi.python.org/pypi/RuSocSci RuSocSci] (Python package)<br />
}}<br />
}}<br />
<br />
The TemperatureHumidity is a little (15 x 5 x 5 cm) black box with a black sphere on top. It is connected to your computer with the attached USB cable. When connected it will identify itself as a Virtual Serial port. <br />
<br />
== Installation ==<br />
Install the ''rusocsci'' package. On the lab computers it may already be installed for you. Also install ''pytz'', ''python-dateutil'' and ''pyqt4''. Download the [[Media:temperaturehumidity.zip|temperaturehumidity module]] and unzip it in the same directory as your experiment.<br />
<br />
== Testing ==<br />
Run the temperaturehumidity module and sensor by running the file 'temperaturehumidity.py'. Double click it in explorer or load in the Psychopy Coder and click 'run'.<br />
<br />
== Code example ==<br />
You can read temperature and humidity values with any software that connects to a serial port. Most conveniently you can use the [https://pypi.python.org/pypi/RuSocSci RuSocSci] library in python. Here is a little example how to write a script that reads the temperature and humidity and writes it to the standard output (console):<br />
<syntaxhighlight lang="python"><br />
#!/usr/bin/env python3<br />
import temperaturehumidity<br />
th = temperaturehumidity.TemperatureHumidity()<br />
print(th.waitString())<br />
</syntaxhighlight><br />
<br />
== Potential problems ==<br />
The temperaturehumidity device identifies as a buttonbox. Lab computer are set up in a way that makes the second buttonbox behave different from all other devices. If you are using both the buttonbox and the temperaturehumidity device, please look up the port name of the temperaturehumidity device in the windows device manager and if it is for instance 'COM3' then change the code above into:<br />
<syntaxhighlight lang="python"><br />
#!/usr/bin/env python<br />
# -*- coding: utf-8 -*-<br />
import temperaturehumidity<br />
th = temperaturehumidity.TemperatureHumidity(port='COM3')<br />
print(th.waitString())<br />
</syntaxhighlight></div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=TemperatureHumidity&diff=5518TemperatureHumidity2022-10-11T07:49:25Z<p>Wilbert.vanham: /* Installation */</p>
<hr />
<div>{{Infobox tsg<br />
| name = TemperatureHumidity<br />
| image = <br />
| caption = TemperatureHumidity device<br />
| downloads = {{bulleted list<br />
| [[Media:temperaturehumidity.zip|Custom Module]]<br />
| [https://pypi.python.org/pypi/RuSocSci RuSocSci] (Python package)<br />
}}<br />
}}<br />
<br />
The TemperatureHumidity is a little (15 x 5 x 5 cm) black box with a black sphere on top. It is connected to your computer with the attached USB cable. When connected it will identify itself as a Virtual Serial port. <br />
<br />
== Installation ==<br />
Install the ''rusocsci'' package. On the lab computers it may already be installed for you. Also install ''pytz'', ''python-dateutil'' and ''pyqt4''. Download the [[Media:temperaturehumidity.zip|temperaturehumidity module]] and unzip it in the same directory as your experiment.<br />
<br />
== Testing ==<br />
Run the temperaturehumidity module and sensor by running the file 'temperaturehumidity.py'. Double click it in explorer or load in the Psychopy Coder and click 'run'.<br />
<br />
== Code example ==<br />
You can read temperature and humidity values with any software that connects to a serial port. Most conveniently you can use the [https://pypi.python.org/pypi/RuSocSci RuSocSci] library in python. Here is a little example how to write a script that reads the temperature and humidity and writes it to the standard output (console):<br />
<syntaxhighlight lang="python"><br />
#!/usr/bin/env python<br />
# -*- coding: utf-8 -*-<br />
import temperaturehumidity<br />
th = temperaturehumidity.TemperatureHumidity()<br />
print(th.waitString())<br />
</syntaxhighlight><br />
<br />
== Potential problems ==<br />
The temperaturehumidity device identifies as a buttonbox. Lab computer are set up in a way that makes the second buttonbox behave different from all other devices. If you are using both the buttonbox and the temperaturehumidity device, please look up the port name of the temperaturehumidity device in the windows device manager and if it is for instance 'COM3' then change the code above into:<br />
<syntaxhighlight lang="python"><br />
#!/usr/bin/env python<br />
# -*- coding: utf-8 -*-<br />
import temperaturehumidity<br />
th = temperaturehumidity.TemperatureHumidity(port='COM3')<br />
print(th.waitString())<br />
</syntaxhighlight></div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&diff=5459Psychopy2022-09-29T09:46:15Z<p>Wilbert.vanham: repair link</p>
<hr />
<div><br />
{{Infobox software<br />
| name = Psychopy<br />
| logo = Psychopy Logo.png<br />
| logo size = 250px<br />
| screenshot = <br />
| caption = <br />
| developer = <br />
| released = <!-- {{Start date and age|YYYY|MM|DD|df=yes}} --><br />
| discontinued = <br />
| latest release version = <br />
| latest release date = <!-- {{Start date and age|YYYY|MM|DD|df=yes}} --><br />
| latest preview version = <br />
| latest preview date = <!-- {{Start date and age|YYYY|MM|DD|df=yes}} --><br />
| installed version = <br />
| installed version date = <!-- {{Start date and age|YYYY|MM|DD|df=yes}} --><br />
| status = Active<br />
| programming language = Python<br />
| operating system = <br />
| platform = <br />
| size = <br />
| language = <br />
| genre = <br />
| license = <br />
| website = <br />
| resources = <br />
{{Infobox tsg<br />
| child = yes<br />
| downloads = {{bulleted list<br />
| [[Media:TemplatePsychopy2013.zip|Template]]<br />
}}<br />
| manuals = {{bulleted list<br />
| [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]<br />
}}<br />
}}<br />
}}<br />
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate.<br />
<br />
==Installation==<br />
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.7.6 64 bits installed. You can download it here: [https://www.python.org/ftp/python/3.7.6/python-3.7.6-amd64-webinstall.exe Python3.7.6 64 bits (Windows)] or choose here: [https://www.python.org/downloads/release/python-376/ Please choose a 64 bit version.]. Run the installer and make sure to add Python to the file path (it's an option in the installer).<br />
<br />
Download from here: [https://gitlab.socsci.ru.nl/h.voogd/psychopy-installation-on-python-3.7-64-bits PsychopyRequirements3.7.txt].Open a command prompt (with administrator rights), go to the folder where the downloaded file is and upgrade the pip installer by typing:<br/><br />
<code style="background-color:#000; color:#fff; padding:1px 3px;">python -m pip install --upgrade pip</code><br/><br />
Then:<br/><br />
<code style="background-color:#000; color:#fff; padding:1px 3px;">pip install -r PsychopyRequirements3.7.txt</code><br />
<br />
This should install everything you need for a basic Psychopy installation. Since packages are updated once in a while, this PsychoPyDependenciesPython3.7.txt might get outdated at some time. Please let us know.<br />
<br />
=== For Pavlovia users ===<br />
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in<br />
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.<br />
<br />
===Upgrade from Python 2.7===<br />
Since Python version 2.7 has reached end of life since January first 2020, this version is no longer installed on the PCs in the labs. Standard is now: Python 3.7 64-bits.<br />
If you still have scripts written in Python2, the scripts should be upgraded to Python 3. Most changes are probably the print statements. Print statements should always have parentheses: print('some text')<br />
Key differences between Python 2 and Python 3 are here: https://sebastianraschka.com/Articles/2014_python_2_3_key_diff.html<br />
<br />
Psychopy 2020.2.10 has been installed in the root of the Python3.7 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop.<br />
There is also a Psychopy 2020.2.10 installed on Python3.6 32-bits. This version has its own icon on the desktop and should be used when you are using a TOBII Eyetracker.<br />
<br />
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.<br />
<br />
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. <br />
<br />
=== For Tobii users ===<br />
Since Tobii does not support 64-bits and does not support Python higher than version 3.6.8, there is a 32 bits Python version 3.6.8 installed. If you want to use a Tobii Eyetracker and want to install Python and Psychopy yourself, download Python here: [https://www.python.org/ftp/python/3.6.8/python-3.6.8-webinstall.exe Python3.6.8 (Windows)] or here: [https://www.python.org/downloads/release/python-368/ List of downloads for Python3.6.8. Please choose a 32-bit version.] Run the installer, choose to add python to the file path (it's an option in the installer).<br />
<br />
Download from here: [https://gitlab.socsci.ru.nl/h.voogd/psychopy-installation-on-python-3.6.8 PsychoPyDependenciesPython3.6.8.txt]. Open a command prompt (with administrator rights), go to the folder where the downloaded file is and upgrade the pip installer by typing:<br/><br />
<code style="background-color:#000; color:#fff; padding:1px 4px;">python -m pip install --upgrade pip</code><br/><br />
Then:<br/><br />
<code style="background-color:#000; color:#fff; padding:1px 4px;">pip install -r PsychopyRequirements3.6.8.txt</code><br />
<br />
'''Note:''' in our labs, the 64-bits Python and 64-bits Psychopy are installed as default. The 32-bits Python 3.6.8 and 32-bits Psychopy are installed in a separate ''virtualenv''. If you want to use Python3.6.8 from the command prompt, you first have to type:<br/><br />
<code style="background-color:#000; color:#fff; padding:1px 4px;">workon Python36</code><br/><br />
After that, everything should work from Python3.6.8, including the 32-bits packages. <br />
<br />
=== For SR-Research Eyelink users ===<br />
Eyelink users should follow the regular instructions above. Additionally, download the SR-Research Python package from here: [https://gitlab.socsci.ru.nl/h.voogd/PyLink3.7-64bit pylinkForPython-3.7.5-x64-Win]. Unzip it, find the folder called: '''pylink''' and copy it to your Pythons '''lib/site-packages''' folder.<br />
<br />
=== For SMI RED 500 and SMI HiSpeed Tower users ===<br />
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.<br />
<br />
==Usage==<br />
===VirtualEnv===<br />
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.<br />
<br />
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.<br />
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.<br />
<br />
Open a command window with administrator rights and type:<br><br />
'''workon''' to see a list of existing virtualenvs.<br><br />
'''workon <virtualenvname>''', where <virtualenvname> is the name of the virtualenv you want to use.<br><br />
'''mkvirtualenv <virtualenvname>''' to create a new and empty virtualenv.<br><br />
'''mkvirtualenv -p=37 <virtualenvname>''' to create a new and empty virtualenv that uses the installed Python3.7.6.<br><br />
'''mkvirtualenv -p=36 <virtualenvname>''' to create a new and empty virtualenv that uses the installed Python3.6.8.<br><br />
'''mkvirtualenv -p=37 --system-site-packages <virtualenvname>''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.<br><br />
'''rmvirtualenv <virtualenvname>''' to remove the virtualenv with name <virtualenvname>.<br><br />
'''deactivate''' to return to the defaults.<br />
<br><br />
In our labs, we have th evirtualenvs:<br><br />
'''Python36''' that contains Python 3.6.8 32-bits, Psychopy and the tobii_research package.<br><br />
'''Python37''' that contains Python 3.7 64-bits, Psychopy and the pylink package (for use with the Eyelink eyetracker).<br><br />
and some more virtualenvs that contain packages that would otherwise interfere with Psychopy.<br />
<br />
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.<br />
<br />
=== Spyder ===<br />
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python 3.7.6 64-bits environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from the Python36 virtualenv, type '''workon python36''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.<br />
<br />
=== PyCharm ===<br />
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. <br><br><br />
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]<br />
<br />
=== Batch files ===<br />
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon <virtualenv>''' and type '''python <myscript.py>''' every time, you might want to make a batch file. Create a text file, type:<br><br />
'''call workon <virtualenv>'''<br><br />
'''python <myscript.py>'''<br><br><br />
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.<br />
<br />
=== 32-bits Psychopy (Tobii users) ===<br />
Our labcomputer has a special virtualenv that is called '''Python36'''. This virtualenv contains everything that Psychopy needs to install, and it contains the '''tobii-research''' package. It also contains the packages that are needed to use the '''cv.dll''' library. <br><br />
To start your script you can: <br><br />
- start Psychopy using the icon on the desktop that uses the 32-bit version. <br><br />
- from a command window, type '''workon Python36''', then type '''Psychopy''' to start the 32 bit Psychopy version.<br><br />
- from a command window, type '''workon Python36''', then type '''Spyder3''' to start the Spyder IDE.<br><br />
- choose the ''Python 3.6 (Python36)'' python interpreter in PyCharm. <br><br />
- from a command window type '''workon Python36''', then type '''python <myscript.py>''' to start your script. Or make a batch file that does this.</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=LimeSurvey&diff=5391LimeSurvey2022-03-23T10:29:11Z<p>Wilbert.vanham: updating to limesurvey 5</p>
<hr />
<div>{{Infobox software<br />
| name = LimeSurvey<br />
| logo = Limesurvey_logo.png<br />
| logo size = 200px<br />
| logo alt = Limesurvey<br />
| screenshot = Limesurvey_screenshot01.jpg<br />
| caption = A Limesurvey survey with the Radboud template<br />
| developer = <br />
| installed version = 5<br />
| installed version date = <!-- {{Start date and age|YYYY|MM|DD|df=yes}} --><br />
| platform = Web<br />
| language count = 84<br />
| website = [http://limesurvey.org limesurvey.org]<br />
| resources = <br />
{{Infobox tsg<br />
| child = yes<br />
| header2 = Radboud Survey 5<br />
| data2 = *[https://questions.socsci.ru.nl/admin Admin Login]<br />
| manuals = {{bulleted list<br />
| [http://manual.limesurvey.org/ Manual]<br />
}}<br />
}}<br />
}}<br />
== General ==<br />
LimeSurvey is a popular open source system for making and publishing surveys. All students and staff of the Faculty of Social Sciences can use it. <br />
<br />
Log on to [https://questions.socsci.ru.nl/index.php/admin questions.socsci.ru.nl/admin] with your university number and password to make a survey. Invitations to surveys can be send with a direct link to the survey (e.g. ''[https://questions.socsci.ru.nl/index.php/123456 https://questions.socsci.ru.nl/index.php/123456?lang=en]'') or by referring to the main survey page ''[http://survey.socsci.ru.nl questions.socsci.ru.nl]''. Note that in the latter case the participant has to find the survey in a list. By default surveys are not listed on the main page. Change this in the ''survey settings'' if you wish. The preferred way is using direct links. <br />
<br />
There is no limit on the number of surveys that you can make or the number of participants in a survey.<br />
<br />
== Tutorial ==<br />
There is a [https://www.socsci.ru.nl/wilberth/limesurvey/01intro.html Limesurvey beginner tutorial] for use of Limesurvey on the Radboud University Faculty of Social Sciences.<br />
<br />
== Callaboration ==<br />
To work with multiple people on the same survey, follow the instructions on our [[Help:LimeSurvey/Collaboration|Collaboration]] page.<br />
<br />
== Template ==<br />
The TSG has helped to create a Radboud-branded template for Limesurvey. When creating a new survey, it should be applied by default. If not, go to:<br/><br />
Survey properties -> General settings -> Presentation & navigation -> Template -> Radboud -> Save <br/><br />
[[File:Limesurvey_theme.png|thumb|none|480px|Select Radboud Template]]<br />
<br />
<br/><br />
'''Note:''' The Radboud template does not yet feature a fully responsive design and may therefore not be suitable for use on mobile devices or small screens.<br />
<br />
== Sona integration ==<br />
If you want to use Sona to invite people to take your survey, please follow the [http://www.sona-systems.com/help/limesurvey.aspx manual provided bij Sona]. Furthermore, if this participant ID should be stored in LimeSurvey such that it is possible to link a response to a participant ID, then you would also have to follow the instructions in the [https://manual.limesurvey.org/Panel_integration manual provided by LimeSurvery]. Please make sure to test whether it works with a [https://tsgdoc.socsci.ru.nl/index.php/Online_experiment_systems#Pilot_Run pilot run].<br />
<br />
== Data Storage ==<br />
Surveys and collected data are stored on campus. The server is not to be used for long term data storage. Surveys and data may be removed after a year without prior warning.<br />
<br />
== Support ==<br />
The TSG provides limited technical support for Limesurvey. Users themselves are responsible for the creation and design of their surveys, as well as the data analysis. For Help on designing your survey you can contact [mailto:p.vangroenestijn@maw.ru.nl Pieter van Groenestijn (RTOG)]. For questions about the use of Limesurvey, please consult the [http://manual.limesurvey.org/ manual] or the [https://www.limesurvey.org/community community support]. <br />
For technical support, contact our [[Administrator]] or [mailto:maarten.snellen@ru.nl Eric Lieffers] (server admin).<br />
<br />
<!-- == References ==<br />
<references /><br />
--><br />
<br />
==External Links== <!-- Optional --><br />
*{{Official website|http://limesurvey.org}}<br />
* [http://questions.socsci.ru.nl Radboud Survey]</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Mounting_a_Webdav_File_System&diff=5341Mounting a Webdav File System2022-01-21T15:36:12Z<p>Wilbert.vanham: /* Dolphin */ add screenshot</p>
<hr />
<div>Quite often we will give a researcher access to some resource by giving a webdav enabled url, a username and password. This page describes how to use this url. In the remainder of this page we will assume that you were given the url https://exp.socsci.ru.nl/experiment/webdav.php, the username u123456 and the password PASSWORD.<br />
<br />
The resource can be anything. It can be simply a folder for shared data, or it can be a web experiment accessible via another (non webdav) url.<br />
<br />
= Webbrowser =<br />
To use the url in a webbrowser, just open the url and type username and password in the popup dialog. <br />
<br />
The page show is a SabreDav web page that will give you a limited number of features (create new folder, upload file, ...).<br />
[[File:Browser sabre dav.png|thumb|Using Sabre Webdav in your browser.]]<br />
<br />
= Linux =<br />
In Linux (and other POSIX compliant operating systems) you can connect a local directory (~/experiment in this example) to the Webdav resource (replace USER with your username):<br />
<br />
sudo apt install davfs2 # no need to allow non root users (setuid root)<br />
mkdir ~/experiment<br />
sudo mount.davfs https://exp.socsci.ru.nl/experiment/webdav.php ~/experiment -o rw,uid=USER,gid=USER<br />
<br />
If you want to mount this resource each time you boot your computer, put the following in /etc/fstab (replacing USER with your username)<br />
<br />
https://exp.socsci.ru.nl/experiment/webdav.php /home/USER/experiment davfs _netdev,noauto,user,uid=USER,gid=USER 0 0<br />
<br />
and put the password in /etc/davfs2/secrets using:<br />
<br />
/home/USER/experiment u123456 PASSWORD<br />
<br />
== Nautilus ==<br />
Type ctrl-L to open the address bar. Type the address: davs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
== Dolphin ==<br />
[[File:Dolphinwebdav.png.png|thumb|none|Dolphin mounting a Webdav filesystem]]<br />
Click the address bar. Type the address: webdavs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
= Microsoft Windows =<br />
[[File:Map windows webdav.png|thumb|none|Mapping a network drive in Microsoft Windows]]<br />
One can use the Microsoft Windows '''Map Network Drive''' feature to assign a drive letter. No special Windows program is needed to do this. It is an operating system feature. Note that there are quite a few [https://sabre.io/dav/clients/windows/ issues]. If you use Microsoft Windows it is usually a better idea to use an external program for accessing a webdav drive. Among other things, if the mount is not in the root directory of the server (http://example.com/mydir) but at a deeper level (http://example.com/superdir/mydir) using the microsoft operating system feature will probably not work.<br />
<br />
== Cyberduck ==<br />
If you use Microsoft windows, Cyberduck is the most popular way to mount a webdav resource. See the image for how to enter information about the mount.<br />
[[File:Mount webdav cyberduck.png|thumb|none|Mounting a webdav filesystem in cyberduck]]<br />
<br />
== KS<sup>2</sup> drive ==<br />
If you want data to be synchronized automatically you can use <br />
[https://github.com/FrKaram/KS2.Drive KS<sup>2</sup> drive]. It is the same program that Utrecht university calls Yoda drive and for which the Donders Institute has an <br />
[https://data.donders.ru.nl/doc/help/user-manual/transfer-data/YodaDrive.html?3 intranet page]. It integrates nicely with the classical MS-DOS system with drive letters.<br />
[[File:Ks2.png|thumb|none|KS<sup>2</sup> configure]]<br />
<br />
If you do not have administrative privileges on your computer, please install the ''portable'' version of the software. Just unzip it somewhere convenient.<br />
<br />
After installing the software configure your webdav drive as shown in the image. After this you can use the taskbar icon for viewing the log and mounting the drive:<br />
[[File:Ks2 mount.png|frame|none|KS<sup>2</sup> taskbar menu]]<br />
<br />
= Mac OSX =<br />
Use the finder "Connect to Server" option (cmd-k) to mount to the webdav file folder. For the server address use: https://exp.socsci.ru.nl/experiment/webdav.php and replace "experiment" with the name of your experiment folder. Press the connect button and login as a registered user with your u-number or s-number. If you want to use OSX finder please ask TSG to enable file locking, otherwise resouces will be mounted read only.<br />
[[File:Finder connecttoserver login.jpg|thumb|none|Mapping a network drive in OSX using Finder]]<br />
<br />
Alternatively Cyberduck (see Windows) also works for OSX.<br />
<br />
== References ==<br />
https://en.wikipedia.org/wiki/SabreDAV</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=File:Dolphinwebdav.png.png&diff=5340File:Dolphinwebdav.png.png2022-01-21T15:35:23Z<p>Wilbert.vanham: </p>
<hr />
<div>Dolphin with webdav</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Mounting_a_Webdav_File_System&diff=5339Mounting a Webdav File System2022-01-21T15:32:06Z<p>Wilbert.vanham: /* Dolphin */ add screenshot</p>
<hr />
<div>Quite often we will give a researcher access to some resource by giving a webdav enabled url, a username and password. This page describes how to use this url. In the remainder of this page we will assume that you were given the url https://exp.socsci.ru.nl/experiment/webdav.php, the username u123456 and the password PASSWORD.<br />
<br />
The resource can be anything. It can be simply a folder for shared data, or it can be a web experiment accessible via another (non webdav) url.<br />
<br />
= Webbrowser =<br />
To use the url in a webbrowser, just open the url and type username and password in the popup dialog. <br />
<br />
The page show is a SabreDav web page that will give you a limited number of features (create new folder, upload file, ...).<br />
[[File:Browser sabre dav.png|thumb|Using Sabre Webdav in your browser.]]<br />
<br />
= Linux =<br />
In Linux (and other POSIX compliant operating systems) you can connect a local directory (~/experiment in this example) to the Webdav resource (replace USER with your username):<br />
<br />
sudo apt install davfs2 # no need to allow non root users (setuid root)<br />
mkdir ~/experiment<br />
sudo mount.davfs https://exp.socsci.ru.nl/experiment/webdav.php ~/experiment -o rw,uid=USER,gid=USER<br />
<br />
If you want to mount this resource each time you boot your computer, put the following in /etc/fstab (replacing USER with your username)<br />
<br />
https://exp.socsci.ru.nl/experiment/webdav.php /home/USER/experiment davfs _netdev,noauto,user,uid=USER,gid=USER 0 0<br />
<br />
and put the password in /etc/davfs2/secrets using:<br />
<br />
/home/USER/experiment u123456 PASSWORD<br />
<br />
== Nautilus ==<br />
Type ctrl-L to open the address bar. Type the address: davs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
== Dolphin ==<br />
[[File:Screenshot 20220121 162932|thumb|Dolphin with Webdav]]<br />
Click the address bar. Type the address: webdavs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
= Microsoft Windows =<br />
[[File:Map windows webdav.png|thumb|none|Mapping a network drive in Microsoft Windows]]<br />
One can use the Microsoft Windows '''Map Network Drive''' feature to assign a drive letter. No special Windows program is needed to do this. It is an operating system feature. Note that there are quite a few [https://sabre.io/dav/clients/windows/ issues]. If you use Microsoft Windows it is usually a better idea to use an external program for accessing a webdav drive. Among other things, if the mount is not in the root directory of the server (http://example.com/mydir) but at a deeper level (http://example.com/superdir/mydir) using the microsoft operating system feature will probably not work.<br />
<br />
== Cyberduck ==<br />
If you use Microsoft windows, Cyberduck is the most popular way to mount a webdav resource. See the image for how to enter information about the mount.<br />
[[File:Mount webdav cyberduck.png|thumb|none|Mounting a webdav filesystem in cyberduck]]<br />
<br />
== KS<sup>2</sup> drive ==<br />
If you want data to be synchronized automatically you can use <br />
[https://github.com/FrKaram/KS2.Drive KS<sup>2</sup> drive]. It is the same program that Utrecht university calls Yoda drive and for which the Donders Institute has an <br />
[https://data.donders.ru.nl/doc/help/user-manual/transfer-data/YodaDrive.html?3 intranet page]. It integrates nicely with the classical MS-DOS system with drive letters.<br />
[[File:Ks2.png|thumb|none|KS<sup>2</sup> configure]]<br />
<br />
If you do not have administrative privileges on your computer, please install the ''portable'' version of the software. Just unzip it somewhere convenient.<br />
<br />
After installing the software configure your webdav drive as shown in the image. After this you can use the taskbar icon for viewing the log and mounting the drive:<br />
[[File:Ks2 mount.png|frame|none|KS<sup>2</sup> taskbar menu]]<br />
<br />
= Mac OSX =<br />
Use the finder "Connect to Server" option (cmd-k) to mount to the webdav file folder. For the server address use: https://exp.socsci.ru.nl/experiment/webdav.php and replace "experiment" with the name of your experiment folder. Press the connect button and login as a registered user with your u-number or s-number. If you want to use OSX finder please ask TSG to enable file locking, otherwise resouces will be mounted read only.<br />
[[File:Finder connecttoserver login.jpg|thumb|none|Mapping a network drive in OSX using Finder]]<br />
<br />
Alternatively Cyberduck (see Windows) also works for OSX.<br />
<br />
== References ==<br />
https://en.wikipedia.org/wiki/SabreDAV</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=File:Screenshot_20220121_162932.png&diff=5338File:Screenshot 20220121 162932.png2022-01-21T15:30:11Z<p>Wilbert.vanham: </p>
<hr />
<div>Dolphin with webdav</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=File:Mount_webdav_cyberduck.png&diff=5325File:Mount webdav cyberduck.png2021-04-19T14:52:02Z<p>Wilbert.vanham: Wilbert.vanham uploaded a new version of File:Mount webdav cyberduck.png</p>
<hr />
<div></div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=File:Mount_webdav_cyberduck.png&diff=5324File:Mount webdav cyberduck.png2021-04-19T14:51:30Z<p>Wilbert.vanham: Wilbert.vanham uploaded a new version of File:Mount webdav cyberduck.png</p>
<hr />
<div></div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Mounting_a_Webdav_File_System&diff=5323Mounting a Webdav File System2021-04-19T14:11:17Z<p>Wilbert.vanham: /* KS2 drive */</p>
<hr />
<div>Quite often we will give a researcher access to some resource by giving a webdav enabled url, a username and password. This page describes how to use this url. In the remainder of this page we will assume that you were given the url https://exp.socsci.ru.nl/experiment/webdav.php, the username u123456 and the password PASSWORD.<br />
<br />
The resource can be anything. It can be simply a folder for shared data, or it can be a web experiment accessible via another (non webdav) url.<br />
<br />
= Webbrowser =<br />
To use the url in a webbrowser, just open the url and type username and password in the popup dialog. <br />
<br />
The page show is a SabreDav web page that will give you a limited number of features (create new folder, upload file, ...).<br />
[[File:Browser sabre dav.png|thumb|Using Sabre Webdav in your browser.]]<br />
<br />
= Linux =<br />
In Linux (and other POSIX compliant operating systems) you can connect a local directory (~/experiment in this example) to the Webdav resource (replace USER with your username):<br />
<br />
sudo apt install davfs2 # no need to allow non root users (setuid root)<br />
mkdir ~/experiment<br />
sudo mount.davfs https://exp.socsci.ru.nl/experiment/webdav.php ~/experiment -o rw,uid=USER,gid=USER<br />
<br />
If you want to mount this resource each time you boot your computer, put the following in /etc/fstab (replacing USER with your username)<br />
<br />
https://exp.socsci.ru.nl/experiment/webdav.php /home/USER/experiment davfs _netdev,noauto,user,uid=USER,gid=USER 0 0<br />
<br />
and put the password in /etc/davfs2/secrets using:<br />
<br />
/home/USER/experiment u123456 PASSWORD<br />
<br />
== Nautilus ==<br />
Type ctrl-L to open the address bar. Type the address: davs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
== Dolphin ==<br />
Click the address bar. Type the address: webdavs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
= Microsoft Windows =<br />
[[File:Map windows webdav.png|thumb|none|Mapping a network drive in Microsoft Windows]]<br />
One can use the Microsoft Windows '''Map Network Drive''' feature to assign a drive letter. No special Windows program is needed to do this. It is an operating system feature. Note that there are quite a few [https://sabre.io/dav/clients/windows/ issues]. If you use Microsoft Windows it is usually a better idea to use an external program for accessing a webdav drive. Among other things, if the mount is not in the root directory of the server (http://example.com/mydir) but at a deeper level (http://example.com/superdir/mydir) using the microsoft operating system feature will probably not work.<br />
<br />
== Cyberduck ==<br />
If you use Microsoft windows, Cyberduck is the most popular way to mount a webdav resource. See the image for how to enter information about the mount.<br />
[[File:Mount webdav cyberduck.png|thumb|none|Mounting a webdav filesystem in cyberduck]]<br />
<br />
== KS<sup>2</sup> drive ==<br />
If you want data to be synchronized automatically you can use <br />
[https://github.com/FrKaram/KS2.Drive KS<sup>2</sup> drive]. It is the same program that Utrecht university calls Yoda drive and for which the Donders Institute has an <br />
[https://data.donders.ru.nl/doc/help/user-manual/transfer-data/YodaDrive.html?3 intranet page]. It integrates nicely with the classical MS-DOS system with drive letters.<br />
[[File:Ks2.png|thumb|none|KS<sup>2</sup> configure]]<br />
<br />
If you do not have administrative privileges on your computer, please install the ''portable'' version of the software. Just unzip it somewhere convenient.<br />
<br />
After installing the software configure your webdav drive as shown in the image. After this you can use the taskbar icon for viewing the log and mounting the drive:<br />
[[File:Ks2 mount.png|frame|none|KS<sup>2</sup> taskbar menu]]<br />
<br />
= Mac OSX =<br />
Use the finder "Connect to Server" option (cmd-k) to mount to the webdav file folder. For the server address use: https://exp.socsci.ru.nl/experiment/webdav.php and replace "experiment" with the name of your experiment folder. Press the connect button and login as a registered user with your u-number or s-number. If you want to use OSX finder please ask TSG to enable file locking, otherwise resouces will be mounted read only.<br />
[[File:Finder connecttoserver login.jpg|thumb|none|Mapping a network drive in OSX using Finder]]<br />
<br />
Alternatively Cyberduck (see Windows) also works for OSX.<br />
<br />
== References ==<br />
https://en.wikipedia.org/wiki/SabreDAV</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Mounting_a_Webdav_File_System&diff=5322Mounting a Webdav File System2021-04-19T13:30:12Z<p>Wilbert.vanham: </p>
<hr />
<div>Quite often we will give a researcher access to some resource by giving a webdav enabled url, a username and password. This page describes how to use this url. In the remainder of this page we will assume that you were given the url https://exp.socsci.ru.nl/experiment/webdav.php, the username u123456 and the password PASSWORD.<br />
<br />
The resource can be anything. It can be simply a folder for shared data, or it can be a web experiment accessible via another (non webdav) url.<br />
<br />
= Webbrowser =<br />
To use the url in a webbrowser, just open the url and type username and password in the popup dialog. <br />
<br />
The page show is a SabreDav web page that will give you a limited number of features (create new folder, upload file, ...).<br />
[[File:Browser sabre dav.png|thumb|Using Sabre Webdav in your browser.]]<br />
<br />
= Linux =<br />
In Linux (and other POSIX compliant operating systems) you can connect a local directory (~/experiment in this example) to the Webdav resource (replace USER with your username):<br />
<br />
sudo apt install davfs2 # no need to allow non root users (setuid root)<br />
mkdir ~/experiment<br />
sudo mount.davfs https://exp.socsci.ru.nl/experiment/webdav.php ~/experiment -o rw,uid=USER,gid=USER<br />
<br />
If you want to mount this resource each time you boot your computer, put the following in /etc/fstab (replacing USER with your username)<br />
<br />
https://exp.socsci.ru.nl/experiment/webdav.php /home/USER/experiment davfs _netdev,noauto,user,uid=USER,gid=USER 0 0<br />
<br />
and put the password in /etc/davfs2/secrets using:<br />
<br />
/home/USER/experiment u123456 PASSWORD<br />
<br />
== Nautilus ==<br />
Type ctrl-L to open the address bar. Type the address: davs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
== Dolphin ==<br />
Click the address bar. Type the address: webdavs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
= Microsoft Windows =<br />
[[File:Map windows webdav.png|thumb|none|Mapping a network drive in Microsoft Windows]]<br />
One can use the Microsoft Windows '''Map Network Drive''' feature to assign a drive letter. No special Windows program is needed to do this. It is an operating system feature. Note that there are quite a few [https://sabre.io/dav/clients/windows/ issues]. If you use Microsoft Windows it is usually a better idea to use an external program for accessing a webdav drive. Among other things, if the mount is not in the root directory of the server (http://example.com/mydir) but at a deeper level (http://example.com/superdir/mydir) using the microsoft operating system feature will probably not work.<br />
<br />
== Cyberduck ==<br />
If you use Microsoft windows, Cyberduck is the most popular way to mount a webdav resource. See the image for how to enter information about the mount.<br />
[[File:Mount webdav cyberduck.png|thumb|none|Mounting a webdav filesystem in cyberduck]]<br />
<br />
== KS<sup>2</sup> drive ==<br />
If you want data to be synchronized automatically you can use <br />
[https://github.com/FrKaram/KS2.Drive KS<sup>2</sup> drive]. It is the same program that Utrecht university calls Yoda drive and for which the Donders Institute has an <br />
[https://data.donders.ru.nl/doc/help/user-manual/transfer-data/YodaDrive.html?3 intranet page]. It integrates nicely with the classical MS-DOS system with drive letters.<br />
[[File:Ks2.png|thumb|none|KS<sup>2</sup> configure]]<br />
<br />
If you do not have administrative privileges on your computer, please install the ''portable'' version of the software. Just unzip it somewhere convenient.<br />
<br />
After installing the software configure your webdav drive as shown in the image. After this you can use the taskbar icon for viewing the log and mounting the drive:<br />
[[File:Ks2 mount.png|frame|none|KS<sup>2</sup> configure]]<br />
<br />
= Mac OSX =<br />
Use the finder "Connect to Server" option (cmd-k) to mount to the webdav file folder. For the server address use: https://exp.socsci.ru.nl/experiment/webdav.php and replace "experiment" with the name of your experiment folder. Press the connect button and login as a registered user with your u-number or s-number. If you want to use OSX finder please ask TSG to enable file locking, otherwise resouces will be mounted read only.<br />
[[File:Finder connecttoserver login.jpg|thumb|none|Mapping a network drive in OSX using Finder]]<br />
<br />
Alternatively Cyberduck (see Windows) also works for OSX.<br />
<br />
== References ==<br />
https://en.wikipedia.org/wiki/SabreDAV</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Mounting_a_Webdav_File_System&diff=5321Mounting a Webdav File System2021-04-19T13:29:22Z<p>Wilbert.vanham: /* KS2 drive */</p>
<hr />
<div>Quite often we will give a researcher access to some resource by giving a webdav enabled url, a username and password. This page describes how to use this url. In the remainder of this page we will assume that you were given the url https://exp.socsci.ru.nl/experiment/webdav.php, the username u123456 and the password PASSWORD.<br />
<br />
The resource can be anything. It can be simply a folder for shared data, or it can be a web experiment accessible via another (non webdav) url.<br />
<br />
= Webbrowser =<br />
To use the url in a webbrowser, just open the url and type username and password in the popup dialog. <br />
<br />
The page show is a SabreDav web page that will give you a limited number of features (create new folder, upload file, ...).<br />
[[File:Browser sabre dav.png|thumb|Using Sabre Webdav in your browser.]]<br />
<br />
= Linux =<br />
In Linux (and other POSIX compliant operating systems) you can connect a local directory (~/experiment in this example) to the Webdav resource (replace USER with your username):<br />
<br />
sudo apt install davfs2 # no need to allow non root users (setuid root)<br />
mkdir ~/experiment<br />
sudo mount.davfs https://exp.socsci.ru.nl/experiment/webdav.php ~/experiment -o rw,uid=USER,gid=USER<br />
<br />
If you want to mount this resource each time you boot your computer, put the following in /etc/fstab (replacing USER with your username)<br />
<br />
https://exp.socsci.ru.nl/experiment/webdav.php /home/USER/experiment davfs _netdev,noauto,user,uid=USER,gid=USER 0 0<br />
<br />
and put the password in /etc/davfs2/secrets using:<br />
<br />
/home/USER/experiment u123456 PASSWORD<br />
<br />
== Nautilus ==<br />
Type ctrl-L to open the address bar. Type the address: davs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
== Dolphin ==<br />
Click the address bar. Type the address: webdavs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
= Microsoft Windows =<br />
[[File:Map windows webdav.png|thumb|none|Mapping a network drive in Microsoft Windows]]<br />
One can use the Microsoft Windows '''Map Network Drive''' feature to assign a drive letter. No special Windows program is needed to do this. It is an operating system feature. Note that there are quite a few [https://sabre.io/dav/clients/windows/ issues]. If you use Microsoft Windows it is usually a better idea to use an external program for accessing a webdav drive. Among other things, if the mount is not in the root directory of the server (http://example.com/mydir) but at a deeper level (http://example.com/superdir/mydir) using the microsoft operating system feature will probably not work.<br />
<br />
== Cyberduck ==<br />
If you use Microsoft windows, Cyberduck is the most popular way to mount a webdav resource. See the image for how to enter information about the mount.<br />
[[File:Mount webdav cyberduck.png|thumb|none|Mounting a webdav filesystem in cyberduck]]<br />
<br />
== KS<sup>2</sup> drive ==<br />
If you want data to be synchronized automatically you can use <br />
[https://github.com/FrKaram/KS2.Drive KS<sup>2</sup> drive]. It is the same program that Utrecht university calls Yoda drive and for which the Donders Institute has an <br />
[https://data.donders.ru.nl/doc/help/user-manual/transfer-data/YodaDrive.html?3 intranet page]. It integrates nicely with the classical MS-DOS system with drive letters.<br />
[[File:Ks2.png|thumb|none|KS<sup>2</sup> configure]]<br />
<br />
If you do not have administrative privileges on your computer, please install the ''portable'' version of the software. Just unzip it somewhere convenient.<br />
<br />
After installing the software configure your webdav drive as shown in the image. After this you can use the taskbar icon for viewing the log and mounting the drive:<br />
[[File:Ks2 mount.png|frame|none|KS<sup>2</sup> configure]]<br />
<br />
= Mac OSX =<br />
Use the finder "Connect to Server" option (cmd-k) to mount to the webdav file folder. For the server address use: https://exp.socsci.ru.nl/experiment/webdav.php and replace "experiment" with the name of your experiment folder. Press the connect button and login as a registered user with your u-number or s-number. If you want to use OSX finder please ask TSG to enable file locking, otherwise resouces will be mounted read only.<br />
[[File:Finder connecttoserver login.jpg|thumb|Mapping a network drive in OSX using Finder]]<br />
<br />
Alternatively Cyberduck (see Windows) also works for OSX.<br />
<br />
== References ==<br />
https://en.wikipedia.org/wiki/SabreDAV</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Mounting_a_Webdav_File_System&diff=5320Mounting a Webdav File System2021-04-19T13:22:42Z<p>Wilbert.vanham: </p>
<hr />
<div>Quite often we will give a researcher access to some resource by giving a webdav enabled url, a username and password. This page describes how to use this url. In the remainder of this page we will assume that you were given the url https://exp.socsci.ru.nl/experiment/webdav.php, the username u123456 and the password PASSWORD.<br />
<br />
The resource can be anything. It can be simply a folder for shared data, or it can be a web experiment accessible via another (non webdav) url.<br />
<br />
= Webbrowser =<br />
To use the url in a webbrowser, just open the url and type username and password in the popup dialog. <br />
<br />
The page show is a SabreDav web page that will give you a limited number of features (create new folder, upload file, ...).<br />
[[File:Browser sabre dav.png|thumb|Using Sabre Webdav in your browser.]]<br />
<br />
= Linux =<br />
In Linux (and other POSIX compliant operating systems) you can connect a local directory (~/experiment in this example) to the Webdav resource (replace USER with your username):<br />
<br />
sudo apt install davfs2 # no need to allow non root users (setuid root)<br />
mkdir ~/experiment<br />
sudo mount.davfs https://exp.socsci.ru.nl/experiment/webdav.php ~/experiment -o rw,uid=USER,gid=USER<br />
<br />
If you want to mount this resource each time you boot your computer, put the following in /etc/fstab (replacing USER with your username)<br />
<br />
https://exp.socsci.ru.nl/experiment/webdav.php /home/USER/experiment davfs _netdev,noauto,user,uid=USER,gid=USER 0 0<br />
<br />
and put the password in /etc/davfs2/secrets using:<br />
<br />
/home/USER/experiment u123456 PASSWORD<br />
<br />
== Nautilus ==<br />
Type ctrl-L to open the address bar. Type the address: davs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
== Dolphin ==<br />
Click the address bar. Type the address: webdavs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
= Microsoft Windows =<br />
[[File:Map windows webdav.png|thumb|none|Mapping a network drive in Microsoft Windows]]<br />
One can use the Microsoft Windows '''Map Network Drive''' feature to assign a drive letter. No special Windows program is needed to do this. It is an operating system feature. Note that there are quite a few [https://sabre.io/dav/clients/windows/ issues]. If you use Microsoft Windows it is usually a better idea to use an external program for accessing a webdav drive. Among other things, if the mount is not in the root directory of the server (http://example.com/mydir) but at a deeper level (http://example.com/superdir/mydir) using the microsoft operating system feature will probably not work.<br />
<br />
== Cyberduck ==<br />
If you use Microsoft windows, Cyberduck is the most popular way to mount a webdav resource. See the image for how to enter information about the mount.<br />
[[File:Mount webdav cyberduck.png|thumb|none|Mounting a webdav filesystem in cyberduck]]<br />
<br />
== KS<sup>2</sup> drive ==<br />
[[File:Ks2.png|thumb|none|KS<sup>2</sup> configure]]<br />
[[File:Ks2 mount.png|frame|right|KS<sup>2</sup> configure]]<br />
If you want data to be synchronized automatically you can use <br />
[https://github.com/FrKaram/KS2.Drive KS<sup>2</sup> drive]. It is the same program that Utrecht university calls Yoda drive and for which the Donders Institute has an <br />
[https://data.donders.ru.nl/doc/help/user-manual/transfer-data/YodaDrive.html?3 intranet page]. It integrates nicely with the classical Windows system with drive letters.<br />
<br />
If you do not have administrative privileges on your computer, please install the ''portable'' version of the software. Just unzip it somewhere convenient.<br />
<br />
After installing the software configure your webdav drive as shown in the image. Ather this you can use the taskbar icon for viewing the log and mounting the drive.<br />
<br />
= Mac OSX =<br />
Use the finder "Connect to Server" option (cmd-k) to mount to the webdav file folder. For the server address use: https://exp.socsci.ru.nl/experiment/webdav.php and replace "experiment" with the name of your experiment folder. Press the connect button and login as a registered user with your u-number or s-number. If you want to use OSX finder please ask TSG to enable file locking, otherwise resouces will be mounted read only.<br />
[[File:Finder connecttoserver login.jpg|thumb|Mapping a network drive in OSX using Finder]]<br />
<br />
Alternatively Cyberduck (see Windows) also works for OSX.<br />
<br />
== References ==<br />
https://en.wikipedia.org/wiki/SabreDAV</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Mounting_a_Webdav_File_System&diff=5319Mounting a Webdav File System2021-04-19T13:22:03Z<p>Wilbert.vanham: </p>
<hr />
<div>Quite often we will give a researcher access to some resource by giving a webdav enabled url, a username and password. This page describes how to use this url. In the remainder of this page we will assume that you were given the url https://exp.socsci.ru.nl/experiment/webdav.php, the username u123456 and the password PASSWORD.<br />
<br />
The resource can be anything. It can be simply a folder for shared data, or it can be a web experiment accessible via another (non webdav) url.<br />
<br />
= Webbrowser =<br />
To use the url in a webbrowser, just open the url and type username and password in the popup dialog. <br />
<br />
The page show is a SabreDav web page that will give you a limited number of features (create new folder, upload file, ...).<br />
[[File:Browser sabre dav.png|thumb|Using Sabre Webdav in your browser.]]<br />
<br />
= Linux =<br />
In Linux (and other POSIX compliant operating systems) you can connect a local directory (~/experiment in this example) to the Webdav resource (replace USER with your username):<br />
<br />
sudo apt install davfs2 # no need to allow non root users (setuid root)<br />
mkdir ~/experiment<br />
sudo mount.davfs https://exp.socsci.ru.nl/experiment/webdav.php ~/experiment -o rw,uid=USER,gid=USER<br />
<br />
If you want to mount this resource each time you boot your computer, put the following in /etc/fstab (replacing USER with your username)<br />
<br />
https://exp.socsci.ru.nl/experiment/webdav.php /home/USER/experiment davfs _netdev,noauto,user,uid=USER,gid=USER 0 0<br />
<br />
and put the password in /etc/davfs2/secrets using:<br />
<br />
/home/USER/experiment u123456 PASSWORD<br />
<br />
== Nautilus ==<br />
Type ctrl-L to open the address bar. Type the address: davs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
== Dolphin ==<br />
Click the address bar. Type the address: webdavs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
= Microsoft Windows =<br />
One can use the Microsoft Windows '''Map Network Drive''' feature to assign a drive letter. No special Windows program is needed to do this. It is an operating system feature. Note that there are quite a few [https://sabre.io/dav/clients/windows/ issues]. If you use Microsoft Windows it is usually a better idea to use an external program for accessing a webdav drive. Among other things, if the mount is not in the root directory of the server (http://example.com/mydir) but at a deeper level (http://example.com/superdir/mydir) using the microsoft operating system feature will probably not work.<br />
[[File:Map windows webdav.png|thumb|Mapping a network drive in Microsoft Windows]]<br />
<br />
== Cyberduck ==<br />
If you use Microsoft windows, Cyberduck is the most popular way to mount a webdav resource. See the image for how to enter information about the mount.<br />
[[File:Mount webdav cyberduck.png|thumb|none|Mounting a webdav filesystem in cyberduck]]<br />
<br />
== KS<sup>2</sup> drive ==<br />
[[File:Ks2.png|thumb|none|KS<sup>2</sup> configure]]<br />
[[File:Ks2 mount.png|frame|right|KS<sup>2</sup> configure]]<br />
If you want data to be synchronized automatically you can use <br />
[https://github.com/FrKaram/KS2.Drive KS<sup>2</sup> drive]. It is the same program that Utrecht university calls Yoda drive and for which the Donders Institute has an <br />
[https://data.donders.ru.nl/doc/help/user-manual/transfer-data/YodaDrive.html?3 intranet page]. It integrates nicely with the classical Windows system with drive letters.<br />
<br />
If you do not have administrative privileges on your computer, please install the ''portable'' version of the software. Just unzip it somewhere convenient.<br />
<br />
After installing the software configure your webdav drive as shown in the image. Ather this you can use the taskbar icon for viewing the log and mounting the drive.<br />
<br />
= Mac OSX =<br />
Use the finder "Connect to Server" option (cmd-k) to mount to the webdav file folder. For the server address use: https://exp.socsci.ru.nl/experiment/webdav.php and replace "experiment" with the name of your experiment folder. Press the connect button and login as a registered user with your u-number or s-number. If you want to use OSX finder please ask TSG to enable file locking, otherwise resouces will be mounted read only.<br />
[[File:Finder connecttoserver login.jpg|thumb|Mapping a network drive in OSX using Finder]]<br />
<br />
Alternatively Cyberduck (see Windows) also works for OSX.<br />
<br />
== References ==<br />
https://en.wikipedia.org/wiki/SabreDAV</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Mounting_a_Webdav_File_System&diff=5318Mounting a Webdav File System2021-04-19T13:21:00Z<p>Wilbert.vanham: </p>
<hr />
<div>Quite often we will give a researcher access to some resource by giving a webdav enabled url, a username and password. This page describes how to use this url. In the remainder of this page we will assume that you were given the url https://exp.socsci.ru.nl/experiment/webdav.php, the username u123456 and the password PASSWORD.<br />
<br />
The resource can be anything. It can be simply a folder for shared data, or it can be a web experiment accessible via another (non webdav) url.<br />
<br />
= Webbrowser =<br />
To use the url in a webbrowser, just open the url and type username and password in the popup dialog. <br />
<br />
The page show is a SabreDav web page that will give you a limited number of features (create new folder, upload file, ...).<br />
[[File:Browser sabre dav.png|thumb|Using Sabre Webdav in your browser.]]<br />
<br />
= Linux =<br />
In Linux (and other POSIX compliant operating systems) you can connect a local directory (~/experiment in this example) to the Webdav resource (replace USER with your username):<br />
<br />
sudo apt install davfs2 # no need to allow non root users (setuid root)<br />
mkdir ~/experiment<br />
sudo mount.davfs https://exp.socsci.ru.nl/experiment/webdav.php ~/experiment -o rw,uid=USER,gid=USER<br />
<br />
If you want to mount this resource each time you boot your computer, put the following in /etc/fstab (replacing USER with your username)<br />
<br />
https://exp.socsci.ru.nl/experiment/webdav.php /home/USER/experiment davfs _netdev,noauto,user,uid=USER,gid=USER 0 0<br />
<br />
and put the password in /etc/davfs2/secrets using:<br />
<br />
/home/USER/experiment u123456 PASSWORD<br />
<br />
== Nautilus ==<br />
Type ctrl-L to open the address bar. Type the address: davs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
== Dolphin ==<br />
Click the address bar. Type the address: webdavs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
= Microsoft Windows =<br />
One can use the Microsoft Windows '''Map Network Drive''' feature to assign a drive letter. No special Windows program is needed to do this. It is an operating system feature. Note that there are quite a few [https://sabre.io/dav/clients/windows/ issues]. If you use Microsoft Windows it is usually a better idea to use an external program for accessing a webdav drive. Among other things, if the mount is not in the root directory of the server (http://example.com/mydir) but at a deeper level (http://example.com/superdir/mydir) using the microsoft operating system feature will probably not work.<br />
[[File:Map windows webdav.png|thumb|Mapping a network drive in Microsoft Windows]]<br />
<br />
== Cyberduck ==<br />
If you use Microsoft windows, Cyberduck is the most popular way to mount a webdav resource. See the image for how to enter information about the mount.<br />
[[File:Mount webdav cyberduck.png|thumb|none|Mounting a webdav filesystem in cyberduck]]<br />
<br />
== KS<sup>2</sup> drive ==<br />
[[File:Ks2.png|807x628px|frameless|none|KS<sup>2</sup> configure]]<br />
If you want data to be synchronized automatically you can use <br />
[https://github.com/FrKaram/KS2.Drive KS<sup>2</sup> drive]. It is the same program that Utrecht university calls Yoda drive and for which the Donders Institute has an <br />
[https://data.donders.ru.nl/doc/help/user-manual/transfer-data/YodaDrive.html?3 intranet page]. It integrates nicely with the classical Windows system with drive letters.<br />
<br />
If you do not have administrative privileges on your computer, please install the ''portable'' version of the software. Just unzip it somewhere convenient.<br />
<br />
After installing the software configure your webdav drive as shown in the image. Ather this you can use the taskbar icon for viewing the log and mounting the drive.<br />
[[File:Ks2 mount.png|frame|none|KS<sup>2</sup> configure]]<br />
<br />
= Mac OSX =<br />
Use the finder "Connect to Server" option (cmd-k) to mount to the webdav file folder. For the server address use: https://exp.socsci.ru.nl/experiment/webdav.php and replace "experiment" with the name of your experiment folder. Press the connect button and login as a registered user with your u-number or s-number. If you want to use OSX finder please ask TSG to enable file locking, otherwise resouces will be mounted read only.<br />
[[File:Finder connecttoserver login.jpg|thumb|Mapping a network drive in OSX using Finder]]<br />
<br />
Alternatively Cyberduck (see Windows) also works for OSX.<br />
<br />
== References ==<br />
https://en.wikipedia.org/wiki/SabreDAV</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Mounting_a_Webdav_File_System&diff=5317Mounting a Webdav File System2021-04-19T13:19:35Z<p>Wilbert.vanham: /* KS2 drive */</p>
<hr />
<div>Quite often we will give a researcher access to some resource by giving a webdav enabled url, a username and password. This page describes how to use this url. In the remainder of this page we will assume that you were given the url https://exp.socsci.ru.nl/experiment/webdav.php, the username u123456 and the password PASSWORD.<br />
<br />
The resource can be anything. It can be simply a folder for shared data, or it can be a web experiment accessible via another (non webdav) url.<br />
<br />
= Webbrowser =<br />
To use the url in a webbrowser, just open the url and type username and password in the popup dialog. <br />
<br />
The page show is a SabreDav web page that will give you a limited number of features (create new folder, upload file, ...).<br />
[[File:Browser sabre dav.png|thumb|Using Sabre Webdav in your browser.]]<br />
<br />
= Linux =<br />
In Linux (and other POSIX compliant operating systems) you can connect a local directory (~/experiment in this example) to the Webdav resource (replace USER with your username):<br />
<br />
sudo apt install davfs2 # no need to allow non root users (setuid root)<br />
mkdir ~/experiment<br />
sudo mount.davfs https://exp.socsci.ru.nl/experiment/webdav.php ~/experiment -o rw,uid=USER,gid=USER<br />
<br />
If you want to mount this resource each time you boot your computer, put the following in /etc/fstab (replacing USER with your username)<br />
<br />
https://exp.socsci.ru.nl/experiment/webdav.php /home/USER/experiment davfs _netdev,noauto,user,uid=USER,gid=USER 0 0<br />
<br />
and put the password in /etc/davfs2/secrets using:<br />
<br />
/home/USER/experiment u123456 PASSWORD<br />
<br />
== Nautilus ==<br />
Type ctrl-L to open the address bar. Type the address: davs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
== Dolphin ==<br />
Click the address bar. Type the address: webdavs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
= Microsoft Windows =<br />
One can use the Microsoft Windows '''Map Network Drive''' feature to assign a drive letter. No special Windows program is needed to do this. It is an operating system feature. Note that there are quite a few [https://sabre.io/dav/clients/windows/ issues]. If you use Microsoft Windows it is usually a better idea to use an external program for accessing a webdav drive. Among other things, if the mount is not in the root directory of the server (http://example.com/mydir) but at a deeper level (http://example.com/superdir/mydir) using the microsoft operating system feature will probably not work.<br />
[[File:Map windows webdav.png|thumb|Mapping a network drive in Microsoft Windows]]<br />
<br />
== Cyberduck ==<br />
If you use Microsoft windows, Cyberduck is the most popular way to mount a webdav resource. See the image for how to enter information about the mount.<br />
[[File:Mount webdav cyberduck.png|thumb|Mounting a webdav filesystem in cyberduck]]<br />
<br />
== KS<sup>2</sup> drive ==<br />
[[File:Ks2.png|807x628px|frameless|none|KS<sup>2</sup> configure]]<br />
If you want data to be synchronized automatically you can use <br />
[https://github.com/FrKaram/KS2.Drive KS<sup>2</sup> drive]. It is the same program that Utrecht university calls Yoda drive and for which the Donders Institute has an <br />
[https://data.donders.ru.nl/doc/help/user-manual/transfer-data/YodaDrive.html?3 intranet page]. It integrates nicely with the classical Windows system with drive letters.<br />
<br />
If you do not have administrative privileges on your computer, please install the ''portable'' version of the software. Just unzip it somewhere convenient.<br />
<br />
After installing the software configure your webdav drive as shown in the image. Ather this you can use the taskbar icon for viewing the log and mounting the drive.<br />
[[File:Ks2 mount.png|frame|none|KS<sup>2</sup> configure]]<br />
<br />
= Mac OSX =<br />
Use the finder "Connect to Server" option (cmd-k) to mount to the webdav file folder. For the server address use: https://exp.socsci.ru.nl/experiment/webdav.php and replace "experiment" with the name of your experiment folder. Press the connect button and login as a registered user with your u-number or s-number. If you want to use OSX finder please ask TSG to enable file locking, otherwise resouces will be mounted read only.<br />
[[File:Finder connecttoserver login.jpg|thumb|Mapping a network drive in OSX using Finder]]<br />
<br />
Alternatively Cyberduck (see Windows) also works for OSX.<br />
<br />
== References ==<br />
https://en.wikipedia.org/wiki/SabreDAV</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Mounting_a_Webdav_File_System&diff=5316Mounting a Webdav File System2021-04-19T13:19:04Z<p>Wilbert.vanham: /* KS2 drive */</p>
<hr />
<div>Quite often we will give a researcher access to some resource by giving a webdav enabled url, a username and password. This page describes how to use this url. In the remainder of this page we will assume that you were given the url https://exp.socsci.ru.nl/experiment/webdav.php, the username u123456 and the password PASSWORD.<br />
<br />
The resource can be anything. It can be simply a folder for shared data, or it can be a web experiment accessible via another (non webdav) url.<br />
<br />
= Webbrowser =<br />
To use the url in a webbrowser, just open the url and type username and password in the popup dialog. <br />
<br />
The page show is a SabreDav web page that will give you a limited number of features (create new folder, upload file, ...).<br />
[[File:Browser sabre dav.png|thumb|Using Sabre Webdav in your browser.]]<br />
<br />
= Linux =<br />
In Linux (and other POSIX compliant operating systems) you can connect a local directory (~/experiment in this example) to the Webdav resource (replace USER with your username):<br />
<br />
sudo apt install davfs2 # no need to allow non root users (setuid root)<br />
mkdir ~/experiment<br />
sudo mount.davfs https://exp.socsci.ru.nl/experiment/webdav.php ~/experiment -o rw,uid=USER,gid=USER<br />
<br />
If you want to mount this resource each time you boot your computer, put the following in /etc/fstab (replacing USER with your username)<br />
<br />
https://exp.socsci.ru.nl/experiment/webdav.php /home/USER/experiment davfs _netdev,noauto,user,uid=USER,gid=USER 0 0<br />
<br />
and put the password in /etc/davfs2/secrets using:<br />
<br />
/home/USER/experiment u123456 PASSWORD<br />
<br />
== Nautilus ==<br />
Type ctrl-L to open the address bar. Type the address: davs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
== Dolphin ==<br />
Click the address bar. Type the address: webdavs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
= Microsoft Windows =<br />
One can use the Microsoft Windows '''Map Network Drive''' feature to assign a drive letter. No special Windows program is needed to do this. It is an operating system feature. Note that there are quite a few [https://sabre.io/dav/clients/windows/ issues]. If you use Microsoft Windows it is usually a better idea to use an external program for accessing a webdav drive. Among other things, if the mount is not in the root directory of the server (http://example.com/mydir) but at a deeper level (http://example.com/superdir/mydir) using the microsoft operating system feature will probably not work.<br />
[[File:Map windows webdav.png|thumb|Mapping a network drive in Microsoft Windows]]<br />
<br />
== Cyberduck ==<br />
If you use Microsoft windows, Cyberduck is the most popular way to mount a webdav resource. See the image for how to enter information about the mount.<br />
[[File:Mount webdav cyberduck.png|thumb|Mounting a webdav filesystem in cyberduck]]<br />
<br />
== KS<sup>2</sup> drive ==<br />
[[File:Ks2.png|807x628px|frameless|left|KS<sup>2</sup> configure]]<br />
If you want data to be synchronized automatically you can use <br />
[https://github.com/FrKaram/KS2.Drive KS<sup>2</sup> drive]. It is the same program that Utrecht university calls Yoda drive and for which the Donders Institute has an <br />
[https://data.donders.ru.nl/doc/help/user-manual/transfer-data/YodaDrive.html?3 intranet page]. It integrates nicely with the classical Windows system with drive letters.<br />
<br />
If you do not have administrative privileges on your computer, please install the ''portable'' version of the software. Just unzip it somewhere convenient.<br />
<br />
After installing the software configure your webdav drive as shown in the image. Ather this you can use the taskbar icon for viewing the log and mounting the drive.<br />
[[File:Ks2 mount.png|frame|none|KS<sup>2</sup> configure]]<br />
<br />
= Mac OSX =<br />
Use the finder "Connect to Server" option (cmd-k) to mount to the webdav file folder. For the server address use: https://exp.socsci.ru.nl/experiment/webdav.php and replace "experiment" with the name of your experiment folder. Press the connect button and login as a registered user with your u-number or s-number. If you want to use OSX finder please ask TSG to enable file locking, otherwise resouces will be mounted read only.<br />
[[File:Finder connecttoserver login.jpg|thumb|Mapping a network drive in OSX using Finder]]<br />
<br />
Alternatively Cyberduck (see Windows) also works for OSX.<br />
<br />
== References ==<br />
https://en.wikipedia.org/wiki/SabreDAV</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Mounting_a_Webdav_File_System&diff=5315Mounting a Webdav File System2021-04-19T13:17:11Z<p>Wilbert.vanham: </p>
<hr />
<div>Quite often we will give a researcher access to some resource by giving a webdav enabled url, a username and password. This page describes how to use this url. In the remainder of this page we will assume that you were given the url https://exp.socsci.ru.nl/experiment/webdav.php, the username u123456 and the password PASSWORD.<br />
<br />
The resource can be anything. It can be simply a folder for shared data, or it can be a web experiment accessible via another (non webdav) url.<br />
<br />
= Webbrowser =<br />
To use the url in a webbrowser, just open the url and type username and password in the popup dialog. <br />
<br />
The page show is a SabreDav web page that will give you a limited number of features (create new folder, upload file, ...).<br />
[[File:Browser sabre dav.png|thumb|Using Sabre Webdav in your browser.]]<br />
<br />
= Linux =<br />
In Linux (and other POSIX compliant operating systems) you can connect a local directory (~/experiment in this example) to the Webdav resource (replace USER with your username):<br />
<br />
sudo apt install davfs2 # no need to allow non root users (setuid root)<br />
mkdir ~/experiment<br />
sudo mount.davfs https://exp.socsci.ru.nl/experiment/webdav.php ~/experiment -o rw,uid=USER,gid=USER<br />
<br />
If you want to mount this resource each time you boot your computer, put the following in /etc/fstab (replacing USER with your username)<br />
<br />
https://exp.socsci.ru.nl/experiment/webdav.php /home/USER/experiment davfs _netdev,noauto,user,uid=USER,gid=USER 0 0<br />
<br />
and put the password in /etc/davfs2/secrets using:<br />
<br />
/home/USER/experiment u123456 PASSWORD<br />
<br />
== Nautilus ==<br />
Type ctrl-L to open the address bar. Type the address: davs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
== Dolphin ==<br />
Click the address bar. Type the address: webdavs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
= Microsoft Windows =<br />
One can use the Microsoft Windows '''Map Network Drive''' feature to assign a drive letter. No special Windows program is needed to do this. It is an operating system feature. Note that there are quite a few [https://sabre.io/dav/clients/windows/ issues]. If you use Microsoft Windows it is usually a better idea to use an external program for accessing a webdav drive. Among other things, if the mount is not in the root directory of the server (http://example.com/mydir) but at a deeper level (http://example.com/superdir/mydir) using the microsoft operating system feature will probably not work.<br />
[[File:Map windows webdav.png|thumb|Mapping a network drive in Microsoft Windows]]<br />
<br />
== Cyberduck ==<br />
If you use Microsoft windows, Cyberduck is the most popular way to mount a webdav resource. See the image for how to enter information about the mount.<br />
[[File:Mount webdav cyberduck.png|thumb|Mounting a webdav filesystem in cyberduck]]<br />
<br />
== KS<sup>2</sup> drive ==<br />
[[File:Ks2.png|frameless|left|KS<sup>2</sup> configure]]<br />
If you want data to be synchronized automatically you can use <br />
[https://github.com/FrKaram/KS2.Drive KS<sup>2</sup> drive]. It is the same program that Utrecht university calls Yoda drive and for which the Donders Institute has an <br />
[https://data.donders.ru.nl/doc/help/user-manual/transfer-data/YodaDrive.html?3 intranet page]. It integrates nicely with the classical Windows system with drive letters.<br />
<br />
If you do not have administrative privileges on your computer, please install the ''portable'' version of the software. Just unzip it somewhere convenient.<br />
<br />
After installing the software configure your webdav drive as shown in the image. Ather this you can use the taskbar icon for viewing the log and mounting the drive.<br />
[[File:Ks2 mount.png|frame|none|KS<sup>2</sup> configure]]<br />
<br />
= Mac OSX =<br />
Use the finder "Connect to Server" option (cmd-k) to mount to the webdav file folder. For the server address use: https://exp.socsci.ru.nl/experiment/webdav.php and replace "experiment" with the name of your experiment folder. Press the connect button and login as a registered user with your u-number or s-number. If you want to use OSX finder please ask TSG to enable file locking, otherwise resouces will be mounted read only.<br />
[[File:Finder connecttoserver login.jpg|thumb|Mapping a network drive in OSX using Finder]]<br />
<br />
Alternatively Cyberduck (see Windows) also works for OSX.<br />
<br />
== References ==<br />
https://en.wikipedia.org/wiki/SabreDAV</div>Wilbert.vanhamhttp://tsgdoc.socsci.ru.nl/index.php?title=Mounting_a_Webdav_File_System&diff=5314Mounting a Webdav File System2021-04-19T13:14:50Z<p>Wilbert.vanham: /* KS2 drive */</p>
<hr />
<div>Quite often we will give a researcher access to some resource by giving a webdav enabled url, a username and password. This page describes how to use this url. In the remainder of this page we will assume that you were given the url https://exp.socsci.ru.nl/experiment/webdav.php, the username u123456 and the password PASSWORD.<br />
<br />
The resource can be anything. It can be simply a folder for shared data, or it can be a web experiment accessible via another (non webdav) url.<br />
<br />
= Webbrowser =<br />
To use the url in a webbrowser, just open the url and type username and password in the popup dialog. <br />
<br />
The page show is a SabreDav web page that will give you a limited number of features (create new folder, upload file, ...).<br />
[[File:Browser sabre dav.png|thumb|Using Sabre Webdav in your browser.]]<br />
<br />
= Linux =<br />
In Linux (and other POSIX compliant operating systems) you can connect a local directory (~/experiment in this example) to the Webdav resource (replace USER with your username):<br />
<br />
sudo apt install davfs2 # no need to allow non root users (setuid root)<br />
mkdir ~/experiment<br />
sudo mount.davfs https://exp.socsci.ru.nl/experiment/webdav.php ~/experiment -o rw,uid=USER,gid=USER<br />
<br />
If you want to mount this resource each time you boot your computer, put the following in /etc/fstab (replacing USER with your username)<br />
<br />
https://exp.socsci.ru.nl/experiment/webdav.php /home/USER/experiment davfs _netdev,noauto,user,uid=USER,gid=USER 0 0<br />
<br />
and put the password in /etc/davfs2/secrets using:<br />
<br />
/home/USER/experiment u123456 PASSWORD<br />
<br />
== Nautilus ==<br />
Type ctrl-L to open the address bar. Type the address: davs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
== Dolphin ==<br />
Click the address bar. Type the address: webdavs://u123456@exp.socsci.ru.nl/experiment/webdav.php. A popup will appear for the password.<br />
<br />
= Microsoft Windows =<br />
One can use the Microsoft Windows '''Map Network Drive''' feature to assign a drive letter. No special Windows program is needed to do this. It is an operating system feature. Note that there are quite a few [https://sabre.io/dav/clients/windows/ issues]. If you use Microsoft Windows it is usually a better idea to use an external program for accessing a webdav drive. Among other things, if the mount is not in the root directory of the server (http://example.com/mydir) but at a deeper level (http://example.com/superdir/mydir) using the microsoft operating system feature will probably not work.<br />
[[File:Map windows webdav.png|thumb|Mapping a network drive in Microsoft Windows]]<br />
<br />
== Cyberduck ==<br />
If you use Microsoft windows, Cyberduck is the most popular way to mount a webdav resource. See the image for how to enter information about the mount.<br />
[[File:Mount webdav cyberduck.png|thumb|Mounting a webdav filesystem in cyberduck]]<br />
<br />
== KS<sup>2</sup> drive ==<br />
[[File:Ks2.png|frameless|left|KS<sup>2</sup> configure]]<br />
If you want data to be synchronized automatically you can use <br />
[https://github.com/FrKaram/KS2.Drive KS<sup>2</sup> drive]. It is the same program that Utrecht university calls Yoda drive and for which the Donders Institute has an <br />
[https://data.donders.ru.nl/doc/help/user-manual/transfer-data/YodaDrive.html?3 intranet page]. It integrates nicely with the classical Windows system with drive letters.<br />
<br />
If you do not have administrative privileges on your computer, please install the ''portable'' version of the software. Just unzip it somewhere convenient.<br />
<br />
After installing the software configure your webdav drive as shown in the image. Ather this you can use the taskbar icon for viewing the log and mounting the drive.<br />
[[File:Ks2 mount.png|frame|left|KS<sup>2</sup> configure]]<br />
<br />
= Mac OSX =<br />
Use the finder "Connect to Server" option (cmd-k) to mount to the webdav file folder. For the server address use: https://exp.socsci.ru.nl/experiment/webdav.php and replace "experiment" with the name of your experiment folder. Press the connect button and login as a registered user with your u-number or s-number. If you want to use OSX finder please ask TSG to enable file locking, otherwise resouces will be mounted read only.<br />
[[File:Finder connecttoserver login.jpg|thumb|Mapping a network drive in OSX using Finder]]<br />
<br />
Alternatively Cyberduck (see Windows) also works for OSX.<br />
<br />
== References ==<br />
https://en.wikipedia.org/wiki/SabreDAV</div>Wilbert.vanham