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

normalize provenance name #185

Merged
merged 1 commit into from
Oct 11, 2024
Merged

Conversation

catkins-miso
Copy link
Contributor

closes #140

I elected to use "source" as the element name which was used for this schema in a few places already.

@catkins-miso catkins-miso marked this pull request as draft October 11, 2024 12:58
@catkins-miso catkins-miso force-pushed the 142-normalize-provenance-name branch 2 times, most recently from 0f2068b to f334973 Compare October 11, 2024 14:06
@catkins-miso catkins-miso marked this pull request as ready for review October 11, 2024 14:13
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please make special note of this file. I did some light refactoring to emphasize that temporary AAR exceptions and seasonal overrides have essentially the same information content.

@catkins-miso catkins-miso force-pushed the 142-normalize-provenance-name branch from f334973 to 2f39c42 Compare October 11, 2024 14:49
@getorymckeag getorymckeag merged commit 56c7958 into 1.0.0-wip Oct 11, 2024
3 checks passed
@getorymckeag getorymckeag deleted the 142-normalize-provenance-name branch October 11, 2024 17:19
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

Successfully merging this pull request may close these issues.

normalize element name for all uses of data-provenance.yaml
2 participants