No way to assign representative contacts for external data in WALDO
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Some time ago, the "Collaborators" webpage was added to WALDO to support creating entries for new "representative contacts", particularly for external data where data intake largely all goes through WALDO.
However, there currently does not exist a way in WALDO to assign such collaborators to external samples. The current headers associated with the sample site updater in WALDO does not have any fields related to the collaborators.
Alternatively, one can edit the sample directly in WALDO starting from the sample lookup page, but the "Collaborator" field is always grayed out and cannot be modified. The "Secondary collaborators" field can be edited, however this method would be very inefficient when intaking hundreds of samples for a given publication.
I believe the original rationale for not having a way to modify the collaborators was because there is no reason for a bioinformatics person to change the collaborators associated with an internal sample. However, there should still be some way to set these fields for external samples.
Contributor guide
No contributing guide indexed for this repository
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 the sample site updater, the sample lookup page, and the Collaborators webpage linked in the issue. Trace how collaborator fields are displayed and updated for external samples, then define a bulk-intake path that can assign representative contacts without weakening the restriction for internal samples. Done means external samples can receive collaborator assignments efficiently while direct editing remains consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100