-
Notifications
You must be signed in to change notification settings - Fork 495
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
Fix Text Spacing in Astronomy Metadata Fields #2622
Comments
Still a bug as of 4.6.1. Here's the file: https://github.com/IQSS/dataverse/blob/v4.6.1/scripts/api/data/metadatablocks/astrophysics.tsv #2551 is related. |
Enquiring minds are curious about the source of the controlled vocabulary for astrotype. |
@johnhuck here you go: https://github.com/IQSS/dataverse/blob/v4.18/scripts/api/data/metadatablocks/astrophysics.tsv#L30 Pull requests welcome! 😄 |
thanks, @pdurbin - yes, but where did this list of type values originate? is it from a standard? was it created locally? |
@johnhuck oh! For that you'd go to http://guides.dataverse.org/en/4.18/user/appendix.html#metadata-references |
@pdurbin Of course! I'm sorry, I thought we'd already checked there. Looks like the terms are primarily from the VO schema, rather than the IVOA (there's some overlap between the VO and IVOA types, but not much, which is curious). I don't see the values |
To focus on the most important features and bugs, we are closing issues created before 2020 (version 5.0) that are not new feature requests with the label 'Type: Feature'. If you created this issue and you feel the team should revisit this decision, please reopen the issue and leave a comment. |
I was asked to propose next steps based on discussion in the related pull request that @sbondka created at #10206. I think that we should work with experts, like contacts at Harvard's CfA and folks who worked on that VO metadata standard, to figure out how the vocab terms should appear when researchers choose them, and to figure out how identifiers, a blockUri and/or termUris should be added to the metadata block. @scolapasta suggested closing the PR, and that we could reopen it if we decide to build on it. I agreed. We'll meet with @cmbz next week to review this. |
Field Display Name: RedshiftType -> Redshift Type (also fix in the field description as well)
Controlled Vocabulary for Type:
Also a good opportunity to add identifiers in the controlled vocabulary
The text was updated successfully, but these errors were encountered: