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

[Feature]: Save info about the conversion in the NWB files #939

Open
oruebel opened this issue Oct 17, 2024 · 3 comments
Open

[Feature]: Save info about the conversion in the NWB files #939

oruebel opened this issue Oct 17, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@oruebel
Copy link
Collaborator

oruebel commented Oct 17, 2024

What would you like to see added to the NWB GUIDE?

Problem
It would be useful to be able to:

  1. identify if a file was generated with GUIDE. This is useful for usage metrics (e.g., to count the number of files on DANDI that use GUIDE) as well as for degbugging
  2. provide information about the conversion process

Proposed Solution:

  • NWB has the field /general/source_script that we could be used to store metadata about the conversion. For the minimal solution, this can be very simple. Maybe a YAML or JSON document with name of the software (i.e. "NWB GUIDE") and version of GUIDE used. We could then build on this approach, to include more information, e.g., to include the full YAML configuration for the conversion that GUIDE used.
  • Alternatively (or in addition to) we you could append a standard string to the /general/notes text, e.g., This file was generated using NWB GUIDE 1.0
  • It would also be useful to do follow the same approach in NeuroConv (or maybe implement it there)

Do you have any interest in helping implement the feature?

Yes.

Code of Conduct

Yes

Did you confirm this feature was not already reported?

Yes

@oruebel oruebel added the enhancement New feature or request label Oct 17, 2024
@rly
Copy link
Collaborator

rly commented Oct 17, 2024

  • NWB has the field /general/source_script that we could be used to store metadata about the conversion. For the minimal solution, this can be very simple. Maybe a YAML or JSON document with name of the software (i.e. "NWB GUIDE") and version of GUIDE used. We could then build on this approach, to include more information, e.g., to include the full YAML configuration for the conversion that GUIDE used.

The minimal solution is already implemented. Adding information about the conversion process would be nice though.

@rly rly changed the title [Feature]: Safe info about the conversion in the NWB files [Feature]: Save info about the conversion in the NWB files Oct 17, 2024
@rly rly self-assigned this Oct 17, 2024
@oruebel
Copy link
Collaborator Author

oruebel commented Oct 17, 2024

The minimal solution is already implemented.

Great! Does NeuroConv also do this?

Adding information about the conversion process would be nice though.

That can probably done when support for exporting to YAML is possible, because then NeuroConv could just add the YAML script in.

@rly
Copy link
Collaborator

rly commented Nov 1, 2024

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

No branches or pull requests

2 participants