waldronlab / waldronlab/BugSigDB

Duplicated experiments become orphaned and do not appear on the main study page

Open
#348 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
9
Forks
9
Avg merge
1h 56m
Merged PRs (30d)
4

Description

Hi @tosfos,

I'd like to report an issue with duplicated experiments not appearing on the main study page.

Study URL

https://bugsigdb.org/Study_https:/doi.org/10.1038/s41522-026-01144-y

Description

While working on this study, I noticed that when an experiment is duplicated, the duplicated experiment does not appear on the main/parent study page.

I found the duplicated experiments under the Orphaned experiments category instead:

This suggests that the duplicated experiments are being created successfully, but are not being properly associated with the parent study.

Steps to Reproduce

  1. Go to the study page:
    https://bugsigdb.org/Study_https:/doi.org/10.1038/s41522-026-01144-y
  2. Open an experiment belonging to the study.
  3. Click Duplicate this Experiment.
  4. Complete/save the duplicated experiment.
  5. Return to the main/parent study page.
  6. Observe that the duplicated experiment does not appear on the study page.
  7. Check the Orphaned experiments category.
  8. The duplicated experiment can be found there instead.

Expected Behavior

After duplicating an experiment, the duplicated experiment should appear on the main/parent study page as another experiment belonging to that study.

Actual Behavior

The duplicated experiment does not appear on the main/parent study page.

Instead, the duplicated experiment becomes an orphaned experiment.

The orphaned duplicated experiments I found are:

Screenshots

I have attached screenshots showing:

  1. The normal behavior, where experiments are displayed on the main study page.
Image
  1. The orphaned duplicated experiments.
Image

Environment

  • Browser: Google Chrome
  • Device: Desktop
  • Operating System: Windows 11

Thank you.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Reproduce the issue from a study page by using “Duplicate this Experiment,” saving it, and checking both the parent study and Orphaned experiments category. Trace the duplication flow from that action and verify that the saved experiment is associated with the parent study and appears on its page rather than being orphaned.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
database
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.