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]: Config Future Development Ideas #1042

Closed
2 of 3 tasks
mavaylon1 opened this issue Jan 26, 2024 · 1 comment
Closed
2 of 3 tasks

[Feature]: Config Future Development Ideas #1042

mavaylon1 opened this issue Jan 26, 2024 · 1 comment
Assignees

Comments

@mavaylon1
Copy link
Contributor

mavaylon1 commented Jan 26, 2024

What would you like to see added to HDMF?

This is to keep track of ideas for the TermSetConfigurator:

  • Currently if the config comes upon a TermSetWrapper, it will not perform any validation as the wrapper would have already done it. Now we could check to see that the validation from the config and the wrapper match, but I am not sold on this being needed completely.
  • The config file needs to support compound data.
  • Add method to check and prevent duplications in the config for a datatype under the same namespace.

Notes:

  • We need to support the add_row and TermSet after the instance has already been created.
  • Talk about both replacing data after the instance has been created (big change) and/or follow the DataIO hack of replacing data with a termset wrapped version of the data.
  • dtype and shape validation and user created validator

What solution would you like?

Above

Do you have any interest in helping implement the feature?

Yes.

@mavaylon1 mavaylon1 self-assigned this Jan 26, 2024
@mavaylon1
Copy link
Contributor Author

Note: I decided matching validations is not needed till an issue raises.

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

1 participant