Adding metadata from BEP document to specification glossary#19
Merged
m-miedema merged 4 commits intophysiopy:masterfrom Oct 24, 2025
Merged
Adding metadata from BEP document to specification glossary#19m-miedema merged 4 commits intophysiopy:masterfrom
m-miedema merged 4 commits intophysiopy:masterfrom
Conversation
Some checks on formatting (particularly for how I entered the allowable values) might be necessary here, I also added some comments on the BEP document to flag potential issues or changes we could make going forward.
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Some checks on formatting (particularly for how I entered the allowable values) might be necessary here, I also added some new comments on the BEP document to flag potential issues or changes we could make going forward.
This should allow our metadata fields to be referenced when creating the appropriate macro templates!
After much discussion in our monthly meetings, I believe this closes #21 and also resolves #4.