RDocumentation.org website - packages not linked to author papge

Open
#69 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
r, typescript
Domain
web-dev

Research direction

Reproduce the missing links from the Hakan Demirtas collaborator page and the four package URLs listed in the issue, then check the Ran Gao collaborator URL. Trace the collaborator/package association entry point; done means all four packages appear for Hakan Demirtas and the Ran Gao page resolves correctly.

Written by the indexing model from the issue text.

Description

Hello,

I am a Ph.D. student, and I have been working with my advisor on developing and maintaining 17 R packages on CRAN.
By looking at the 17 packages on the RDocumentation.org website, we find out there are four packages missing from the author page (see below link):
https://www.rdocumentation.org/collaborators/name/Hakan%20Demirtas

However, these 4 packages can be found in the RDocumentation.org directly but they are not linked to the author page like the other 13 packages:
(1) https://www.rdocumentation.org/packages/UnivRNG/versions/1.2.3
(2) https://www.rdocumentation.org/packages/MultiRNG/versions/1.2.4
(3) https://www.rdocumentation.org/packages/MultiVarMI/versions/1.0
(4) https://www.rdocumentation.org/packages/RNGforGPD/versions/1.1.0

Can someone help me with a solution?

In addition, I do see myself as a maintainer, but when I click the link (https://www.rdocumentation.org/collaborators/name/Ran%20Gao), it says the page doesn't exist.

Many thanks!!

Dominant language
TypeScript
Stars
301
Forks
54
Avg merge
16h 19m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from datacamp/rdocumentation-2.0

All issues in datacamp/rdocumentation-2.0

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.