IQSS / dataverse

Open source research data repository software
http://dataverse.org
Other
878 stars 486 forks source link

Fix Text Spacing in Astronomy Metadata Fields #2622

Closed posixeleni closed 1 month ago

posixeleni commented 9 years ago

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

pdurbin commented 7 years ago

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.

johnhuck commented 4 years ago

Enquiring minds are curious about the source of the controlled vocabulary for astrotype.

pdurbin commented 4 years ago

@johnhuck here you go:

https://github.com/IQSS/dataverse/blob/v4.18/scripts/api/data/metadatablocks/astrophysics.tsv#L30

Pull requests welcome! 😄

johnhuck commented 4 years ago

thanks, @pdurbin - yes, but where did this list of type values originate? is it from a standard? was it created locally?

pdurbin commented 4 years ago

@johnhuck oh! For that you'd go to http://guides.dataverse.org/en/4.18/user/appendix.html#metadata-references

Screen Shot 2019-11-14 at 8 13 31 PM
johnhuck commented 4 years ago

@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 Figure, PrettyPicture, Documentation, and Press Release in the VO list (although IVOA has Press), but the VO document says the list is extensible, so I guess we can assume they were introduced somewhere along the way. Perhaps not important at this point. Thanks for the assist!

cmbz commented 1 month ago

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.