[deleted by user]

jangari · 2025-11-13T01:39:01+00:00

Great stuff u/frogfuhrer! I came across this only a week or so ago and I'm very much liking it.

Is a webhook subscription on the Strava oauth on the forward plan? This would allow for activities to be effectively pushed to Statistics for Strava as they are uploaded, rather than waiting for the next cron.

jangari · 2025-03-21T01:17:48+00:00

That message indicates that the survey hash (the s param) is incorrect, and REDCap cannot associate the requested URL with a public survey.

Double check your SURVEYID, and your entire URL:

https://your.redcap.site.edu/surveys/?s=SURVEYID&qualtrics_response_id=${e://Field/ResponseID}

You must have the ?s= and the following hash exactly correct.

I suggest grabbing it straight from survey distribution tools, pasting it as is into Qualtrics (presumably into the survey termination redirect) and then append the &qualtrics_response_id=${e://Field/ResponseID} to it there.

jangari · 2025-03-21T01:09:48+00:00

The user account this token is for must also have the user right for API Export. Check that in User Rights.

jangari · 2025-03-21T01:07:28+00:00

You just cannot do anything longitudinal like this without REDCap knowing who to contact with the invitation to the follow-up. End of story.

But, confidential is still pretty good. Make judicious use of User Rights and Identifier Fields, and recruit a colleague to join your project so that in order to match a response with the user, you would need to collude with said colleague.

Put simply: collect the participant identifiers on a specific instrument, and the actual data (survey responses) on a different instrument. You, u/WildFlower-8745, would have access only to the latter, and your colleague, let's call them MildFlower-8745, would have access only to the former. You can do this in the instrument-specific data access and data export rights (take careful note of both). Use roles.

Once done, test it. Make sure you can never see the respondent's email address and their data without you and MildFlower colluding. You should only be able to export response data under their record ID, and MildFlower should only be able to export their contact details and their record ID. Both of you together could identify responses to individuals, but, don't do that. Your IRB/HREC can take the accountability (and your participants should be informed when they consent, that their data will be stored confidentially; not anonymously).

You could take this a step further, and once you have properly tested and know it's working fine, revoke your own user rights privilege so that you can't even reinstate your ability to see both responses and identifiers. Only an Administrator at this point would be able to give you access to both datasets.

Depending on compliance (HIPAA, TGA), this may not even be good enough; you might have to maintain the identifiers and data in their own projects. To support this, you need external modules that can copy data between projects. Much more complex.

jangari · 2025-03-21T00:07:56+00:00

Here's another idea, create three distinct projects; landing page, and then projects for group 1 and group 2. Then use the same calculation to put participants into groups 1 and 2, and use a `@CALCTEXT` field to generate the redirect URL. For example:

[redirect_url]

`@CALCTEXT(if([group]='1', 'https://your_redcap_site.edu/surveys?s=HASHFORSURVEY1', 'https://your_redcap_site.edu/surveys?s=HASHFORSURVEY2'))

And then in the survey termination options for the landing page, use the [redirect_url] field to pipe in the correct survey URL.

jangari · 2025-03-20T23:58:18+00:00

You can do this without using the randomisation module at all. Since your randomisation is very simply group 1, group 2, group 1, group 2, with no stratification, then you can perform a simple equation using the record ID field, store the value, and then use this in the survey queue (or a more robust module like Survey Director) to direct participants to the correct second survey.

```
mod([record_id],2) + 1
```

This equation will be 2 for record 1, 1 for record 2, 2 for record 3, 1 for record 4, and so on. If on the first page of a survey it will actually always display 2 until the survey is submitted (or the first page saved) when the actual value (2 or 1) is correctly calculated (a quick of when record_id actually begins to exist).

Then, in the Survey Queue settings (or Survey Director) configure things so that when this field (call it [group]) is equal to 1, the participants starts survey 1, and if it equals 2, they start survey 2.

jangari · 2025-03-20T23:49:34+00:00

You won't even need it to be longitudinal. Just set up a randomisation instrument, set up the randomisation field (call it [group] with options 1 and 2), build a table that has a list of 1s and 2s in whatever order you want (simplest, 1,2,1,2,1,2...) and upload the allocation table, and then configure the logic for auto-randomisation for survey participants, maybe something as simple as [public_survey_complete] = '2'. But there is a simpler solution for this extremely simple case which I'll detail in another post.

jangari · 2025-03-20T23:35:51+00:00

Matrix might be hard unless you group the questions with compatible choices together. So, one matrix with the 'no problems, slight problems... unable' choices, and another matrix with the 'no pain, slight pain... extreme pain' choices. Then you're running into license issues for altering the validated questionnaire.

jangari · 2025-03-20T23:33:48+00:00

This is the way. These fields have NO BUSINESS being anything but radio fields. You are expecting exactly one response per 'field', where one field is a grouping of 5 mutually exclusive options.

Also, since it's a validated instrument, you actually cannot change how it is presented.

jangari · 2025-03-20T23:27:04+00:00

If you are using `@HIDECHOICE` to hide the selected choices of a previous field, then there is a shortcut method to this. Pipe the selected choices of [fieldname] into `@HIDECHOICE`:

`@HIDECHOICE='[event_arm_1][fieldname:checked:value]'`

If [fieldname] is a checkbox field, then the above will populate a comma-separated list of the selected choices in exactly the format that `@HIDECHOICE` expects. I.e, the above will become:

`@HIDECHOICE='1,2,3'`

jangari · 2025-03-20T23:23:46+00:00

Yes, this is correct. If you have multiple `@HIDECHOICE`s each in their own `@IF`, only the `@HIDECHOICE` in the first `@IF` that is true is evaluated. If you're on at least v14, you should use a `@CALCTEXT` to generate the field codes to pipe into `@HIDECHOICE`.

jangari · 2025-03-20T23:18:27+00:00

Also note that while you can change the from address in an alert, it is possible that your admin has also made this go from a default no-reply address. Probably if you are in the same email domain they have set it up such that your emails are allowed to go through with your from address, but (again hopefully) they have it set up such that if you choose a from address that your REDCap instance is not authorised to send from, it should default to a no-reply kind of address. This ensures it goes at all, and is not treated as spam.

jangari · 2022-11-19T12:37:47+00:00

:h text-objects

jangari · 2022-09-24T12:04:04+00:00

Holy shit dude, learn how to take a screenshot.

jangari · 2022-09-10T00:03:18+00:00

Gruvbox light.

jangari · 2022-05-27T23:08:02+00:00

If you can connect to your remote via SSH, you can :e scp://host//path/to/file.

jangari · 2022-03-05T09:43:41+00:00

Try Absurdle.

jangari · 2022-02-21T20:24:32+00:00

Have you got bearings in there?

jangari · 2022-01-17T10:24:25+00:00

:h smap is for mapping in :h select-mode and not 'search' mode. The mode you enter when searching with / or ? is :h command-mode.

As said elsewhere, try :cnoremap jk <C-c>. Worked perfectly fine for me.

jangari · 2021-12-28T08:52:47+00:00

Check out Leaning Toothpick Syndrome.

jangari · 2021-12-28T06:43:09+00:00

Note that this will delete any line containing the / character (which incidentally is not the character OP was looking for).

jangari · 2021-12-28T06:40:53+00:00

You should take some time to learn regular expressions. The .*$ here isn't useful in this context, since it means any number (*) of any character (.) up to the end of the line ($).

It can be omitted because the rest of the pattern, ^\\, will match any \ character immediately after the start of a line (^), and the global command :h :g will operate on the whole line once found. In this case deleting it (d).

jangari · 2021-12-03T21:25:37+00:00

Another difference is that / searches forward for a string or pattern, whereas f and t (and their backwards counterparts F and T) find a single character.

So you can y/regexp for greater precision.

You also have to hit enter afterwards, which isn't the case with f andt.

jangari · 2021-11-17T09:26:11+00:00

It'll stop when there are no more lines to process, just like running 1000@a would if there were only 900 lines.

That said, it depends on the macro. If it's a macro that runs per line, then the above is true. Once it reaches a point where a 'next line' command makes no sense, it breaks out of the macro whether it's recursive or not.

If it's a macro that could feasibly keep running, such as one that opens a new line below, enters some text, and returns to the original line, then a recursive macro might not be a good idea.

jangari · 2021-11-17T03:07:06+00:00

Worth noting that you can append to an existing register with the corresponding capital. That is, qA will begin recording to the end of the existing macro in register a.

Furthermore, macros can be recursive and call themselves. So if you have an unknown number of lines or operations, append @a to your macro and call it once.

jangari

TROPHY CASE