IQSS / IQSS/dataverse-frontend
Remove the hard-coded permissions from JSDatasetMapper
Open
Nobody has claimed this yet.
FY25 Sprint 9
GREI Re-arch
Original size: 3
Size: 3
SPA
SPA.Q4.10
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 26
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 4
Description
Overview of the Feature Request
From the JSDatasetMapper.ts, we could revise to replace certain hard-coded permissions with dynamic values once it is supported by js-dataverse APIs.
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 in src/dataset/infrastructure/mappers/JSDatasetMapper.ts around line 236 and inspect the hard-coded permissions and the related js-dataverse API support. Confirm which dynamic permission values are available before changing the mapper; done means the supported API values replace the hard-coded permissions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100