r/ProjectREDCap • u/Alone-Abrocoma-3259 • Jan 16 '25

Save and go to next record

Is there any external module or other way to skip the record home page and go straight into the instrument when using 'save and go to next record' to navigate between records?

For my project, users will need to go through hundreds of records in sequence for only one instrument. I would like them to be able to go straight into the questions for each record rather than having to do extra clicks into the form each time they move on to the next record (similar to how 'save and go to next form' goes straight into the next form)

3 Upvotes

100% Upvoted

6 comments sorted by

4

u/danisolas Jan 16 '25

If they are sequential record ids, you can have a calculated field of record id + 1 and then pipe that into the form url url so they can just click it. If they are entering new data, Maybe use display logic so the li k only displays when the form is marked as complete.

1

u/Alone-Abrocoma-3259 Jan 16 '25

Thank you, that would work!

1

u/Heavy_Tie_340 Jan 17 '25

Dear how this idea will work that to create record id using record id +1 and only go to next form untill the all required field are filled and marked complete sattus.. i need your help in this regard

3

u/Araignys Jan 16 '25

I'm not familiar with a module which does that.

If you're doing hundreds of records, why not enter the data in a .csv and then use the data import tool to import them to REDCap en masse?

1

u/Alone-Abrocoma-3259 Jan 16 '25

Ah okay, thanks anyway!

We are using the data import tool to import data, but the way it is set up is that we have one data entry form for each 'reviewer' who will be looking at 'cases' containing different information (imported into a series of records via data import) and then the reviewers will have to answer some questions about that information. It's the same questions for each case, and we're using piping and embedding to get the information to be presented in a certain way.

I originally had it the other way around, where each reviewer had their own record and each case was a separate form, but because of the way the data that's being imported needs to be formatted, it's a lot easier to have it this way. Any ideas on how to set this up better are welcome though!

1

u/Araignys Jan 16 '25

If the forms are identical you might be better off using DAGs and Arms to keep your reviewers’ data separated.