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

More informative output data dictionary file names #49

Open
alyssadai opened this issue Feb 19, 2025 · 2 comments · May be fixed by #61
Open

More informative output data dictionary file names #49

alyssadai opened this issue Feb 19, 2025 · 2 comments · May be fixed by #61
Assignees
Labels
usability Issue affecting user or developer experience.

Comments

@alyssadai
Copy link

Especially useful if you are annotating more than one dataset.

@alyssadai alyssadai added the usability Issue affecting user or developer experience. label Feb 19, 2025
@rmanaem
Copy link
Contributor

rmanaem commented Feb 28, 2025

@neurobagel/dev Any thoughts on how to name these files? Perhaps let the user choose a name?
I'd like to address this as part of the #61

@rmanaem rmanaem added the flag:check Issue needs attention before further action label Feb 28, 2025
@alyssadai
Copy link
Author

I'd recommend having the default be the filename of the input TSV, plus maybe _annotated.json. If the user then additionally has the option to change the default name if desired, that would be nice too!

@rmanaem rmanaem self-assigned this Feb 28, 2025
@rmanaem rmanaem removed the flag:check Issue needs attention before further action label Feb 28, 2025
@rmanaem rmanaem moved this to Implement - Active in Neurobagel Feb 28, 2025
@rmanaem rmanaem moved this from Implement - Active to Implement - Done in Neurobagel Feb 28, 2025
@rmanaem rmanaem linked a pull request Feb 28, 2025 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
usability Issue affecting user or developer experience.
Projects
Status: Implement - Done
Development

Successfully merging a pull request may close this issue.

2 participants