Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multiple audio audits #18

Open
rohan-econ opened this issue Apr 18, 2024 · 6 comments
Open

multiple audio audits #18

rohan-econ opened this issue Apr 18, 2024 · 6 comments
Assignees

Comments

@rohan-econ
Copy link

Hi,
I want to use sctomedia for multiple audio audits for each observation. How do I go about that?

@martacto
Copy link
Contributor

Hi,
Thank you for reaching out! If you would like to use sctomedia for multiple media variables, you will need to run the command twice - one for each audio audit variable. In case you want to use the by() option, i.e., create sub-folders and organize your audio audits based on specific variables, that's still possible. SurveyCTO won't create/duplicate sub-folders if they already exist. They will be created when you run the command the first time only. Does this make sense?

@martacto martacto self-assigned this Apr 18, 2024
@rohan-econ
Copy link
Author

rohan-econ commented Apr 18, 2024 via email

@martacto
Copy link
Contributor

Hi Rohan,
That's exactly why you need to run the command twice - so that you specify a different naming convention and allow for different files to have different names. A file name must be unique. Since any operating system won't allow you to have different files with the same name, what would be the best solution for you? You can use Stata to help you achieve what you are looking for. For example, let's imagine that you are using the variable "name" to name your audio audits. You can create a new variable named "name_2" and concatenate the suffix "_2" into all your names. This way, you can use this variable for your second audio audit variable.

@martacto
Copy link
Contributor

martacto commented May 2, 2024

Hi Rohan,

Were you able to overcome the problem? Do you have any follow up concerns/questions? Otherwise, I will close this issue.

Thank you,
Marta

@rohan-econ
Copy link
Author

rohan-econ commented May 2, 2024 via email

@martacto
Copy link
Contributor

martacto commented May 2, 2024

Hi Rohan,

Thank you for confirming! Would you mind sharing the approach that worked for you so that anyone looking for a similar solution can learn from you?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants