forrtproject / forrtproject/fred-data
Review likely erroneous insula-review target for personality connectomics replication
- Dominant language
- HTML
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
The 14 September 2026 explorer snapshot contains a failed pair from original `10.3389/fnhum.2013.00014` (*Error awareness and the insula: links to neurological and psychiatric diseases*) to replication `10.64898/2026.01.19.700331` (*Replication Challenges in Linking Personality to Resting-State Functional Connectomics*).
The original is a review. The replication abstract identifies Gao et al.’s personality/network findings as its target. That empirical original, `10.3389/fnhum.2013.00257`, already has a separate pair to the same replication. This looks like an erroneous extra target relation, not evidence that the insula review failed to replicate.
Sources: [insula review](https://www.frontiersin.org/journals/human-neuroscience/articles/10.3389/fnhum.2013.00014/full), [published replication](https://www.frontiersin.org/journals/computational-neuroscience/articles/10.3389/fncom.2026.1796308/full).
Please inspect the extraction/source record; remove or reclassify the review relation if confirmed, retain the legitimate Gao relation, reconcile preprint and publication DOI `10.3389/fncom.2026.1796308`, and regenerate affected aggregates. Do not treat the publication as another independent replication. No data recoding has been made in the explorer UI fix.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by inspecting the extraction/source record for the relation between the insula review and the replication DOI. Confirm whether the review relation should be removed or reclassified, preserve the legitimate Gao relation, reconcile the preprint and publication DOI, and regenerate the affected aggregates without counting the publication as a separate replication.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100