Update Astronomy metadatablock's .tsv file to match updates to its .properties file, so that updates are applied to English-only installations
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
In the PR at https://github.com/IQSS/dataverse/pull/9367, changes were made in the astrophysics.properties file in order to fix typos in the tooltip text of several fields in the Astronomy and Astrophysics Metadata block.
Here's the diff showing changes made to the tooltip text of three fields:

The tooltip text of those fields is also in the metadata block's TSV file. Multilingual Dataverse installations (whose “lang” directory is configured) use the text in the metadatablock's .properties files, while "English-only" installations use what's in the database, which is controlled by what's in the metadatablock's TSV files. So the Astronomy and Astrophysics Metadata block's TSV file also needs to be updated to fix the tooltips in English-only installations.
I think it's also best to keep the information in each metadata block's .properties file and .tsv file the same so that people referring to the .tsv files (and the more readable copy in a Google Sheet) see the most up to date versions.
If/when this gets prioritized, I can open a PR to update the astrophysics.tsv file and update the text in the copy of the .tsv file kept in the Google Sheet.
Kind of related I think, is it possible to have both types of installations - multilingual and English-only - use the metadata field names and tooltip text in the .properties files? Then that information could be removed from the .tsv files? Would this simplify updates to metadatablocks in both types of installations?
Alternatively, when this came up in another context, @scolapasta wondered if instead, a script could automate the creation and updating of each metadata block's .properties file, so that what we change is the .tsv file, and then the corresponding .properties file gets updated. Would that help streamline things in the future?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with scripts/api/data/metadatablocks/astrophysics.tsv and compare its three affected tooltip texts with astrophysics.properties and the changes in pull request 9367. Update the TSV values so English-only installations match the corrected properties text, then update the corresponding Google Sheet copy; done means all versions contain the same corrected tooltips.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100