<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://wiki.bric.msu.edu/lib/exe/css.php?s=feed" type="text/css"?>
<rss version="2.0">
    <channel xmlns:g="http://base.google.com/ns/1.0">
        <title>BRIC Documentation - userdocs:redcap_usage:base</title>
        <description></description>
        <link>https://wiki.bric.msu.edu/</link>
        <lastBuildDate>Mon, 20 Apr 2026 00:38:40 +0000</lastBuildDate>
        <generator>FeedCreator 1.8</generator>
        <image>
            <url>https://wiki.bric.msu.edu/lib/exe/fetch.php/wiki:logo.png</url>
            <title>BRIC Documentation</title>
            <link>https://wiki.bric.msu.edu/</link>
        </image>
        <item>
            <title>Check if response is unique</title>
            <link>https://wiki.bric.msu.edu/doku.php/userdocs:redcap_usage:base:check_if_value_exists?rev=1774649193&amp;do=diff</link>
            <description>Check if response is unique

You can determine whether a response is unique within a project by using an SQL field type and then altering workflow behavior based on the result.

This approach is especially useful for public surveys, such as registration forms, where you may want to prevent multiple submissions using the same email address (or any other unique identifier).</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Fri, 27 Mar 2026 22:06:33 +0000</pubDate>
        </item>
        <item>
            <title>Save datetime of randomization</title>
            <link>https://wiki.bric.msu.edu/doku.php/userdocs:redcap_usage:base:save_datetime_of_randomization?rev=1713357853&amp;do=diff</link>
            <description>Save datetime of randomization

You can automatically save the time of randomization, or any other  status change, using the @CALCDATE action tag.  This tag lets you calculate a new date that is offset from an existing date.  In this case, the existing date is</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Wed, 17 Apr 2024 12:44:13 +0000</pubDate>
        </item>
        <item>
            <title>Save time on form</title>
            <link>https://wiki.bric.msu.edu/doku.php/userdocs:redcap_usage:base:save_time_on_form?rev=1774641210&amp;do=diff</link>
            <description>Save time on form

You can automatically capture how long a user spends on a form by using two timestamp variables along with built‑in REDCap action tags. This approach works for both instruments and surveys.
If you want to track time on multiple forms, each form must have its</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Fri, 27 Mar 2026 19:53:30 +0000</pubDate>
        </item>
        <item>
            <title>Unique media per subject</title>
            <link>https://wiki.bric.msu.edu/doku.php/userdocs:redcap_usage:base:unique_media_per_subject?rev=1712937005&amp;do=diff</link>
            <description>Unique media per subject

REDCap allowed for the embedding of media into a data collection form.  This is often a audio of video clip.  This is done by specifying the url of the media that should be embedded.  It is possible to use the piping feature of REDCap to make these links custom for each subject or event.  To do this, create a new variable to hold the location of the subject specific media.  For this example,</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Fri, 12 Apr 2024 15:50:05 +0000</pubDate>
        </item>
    </channel>
</rss>
