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

Specifying target file name #171

Closed
dgutman opened this issue Nov 6, 2023 · 0 comments · Fixed by #175
Closed

Specifying target file name #171

dgutman opened this issue Nov 6, 2023 · 0 comments · Fixed by #175
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@dgutman
Copy link

dgutman commented Nov 6, 2023

It seems that the app currently uses the parameter study_slide to specify the output file name, but I can't see anywhere that can be specified.

I think currently just generating a study_slide and incrementing it based on the order an image happens to be in a folder should not be the default behavior. In most use cases, the user would either provide a very simple CSV file with. , or the app simply preserves the existing filename, but maybe adds. ".deid." which is what I have been doing internally during testing.

In most use cases, the user would not only hand over the raw images, but some basic manifest that maps the files to some basic metadata. With the current implementation, there doesn't seem to be a simple way to even figure out the map of OldFileName --> NewFileName without doing a lot of work.

At the very least, exporting a deidManifest file with the mapping would allow the user to then update/modify them during whatever QC process they are going to run to make sure all the files they wanted to be processed were actually processed.

@dgutman dgutman added documentation Improvements or additions to documentation enhancement New feature or request labels Nov 6, 2023
@naglepuff naglepuff self-assigned this Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants