IQSS / IQSS/dataverse-frontend
Hide RData download file option if R is not configured in Dataverse
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 26
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 4
Description
Overview of the Feature Request
The download option in R format should not be rendered if R is not configured in Dataverse.
Tabular files work well for both original and archival formats. But when selecting RData the following error appears:
{"status":"ERROR","code":404,"message":"datafile access error: requested optional service (image scaling, format conversion, etc.) could not be performed on this datafile."}
https://github.com/IQSS/dataverse-frontend/assets/17010447/1c780e11-c4d2-4741-9493-1194000dca72
This issue depends on backend changes to allow the SPA to know if R is configured in the Dataverse instance. There is already an issue created in the backend repository: https://github.com/IQSS/dataverse/issues/8711
This issue will potentially be divided into 2 spike issues for the frontend work: A UI issue and an integration issue.
What kind of user is the feature intended for?
All users
What inspired the request?
What existing behavior do you want changed?
None
Any brand new behavior do you want to add to Dataverse?
Hide RData download option if R not configured.
Any open or closed issues related to this feature request?
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
No frontend files or tests are named. Start by tracing where download options are rendered and review backend issue 8711 for the configuration data the SPA will receive. Done means the RData option is hidden when R is not configured while existing tabular downloads remain available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100