Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance Reversals output with replication database details #197

Open
LukasWallrich opened this issue Nov 14, 2024 · 1 comment
Open

Enhance Reversals output with replication database details #197

LukasWallrich opened this issue Nov 14, 2024 · 1 comment
Labels
stale Marked by labeler

Comments

@LukasWallrich
Copy link
Contributor

LukasWallrich commented Nov 14, 2024

Currently, the Reversals output is frozen, but much of the content is already in the Replication Database. From there, we can generate additional valuable information. In the long term, the aim is to create Reversals-style entries from database sources that also include critiques and meta-analyses. Yet first, we should implement the following enhancement as soon as Reversals replication data is properly merged into FReD (@LukasRoeseler - let's focus on getting that done in the first coding phase).

  • Generate Replication Status field from FReD (criteria TBD)
  • Generate replication effect size from FReD (maybe with simple chart, showing original and replication effect size and CI)
  • Link to data in FReD database? E.g., annotator filtered to that specific effect via URL parameters?
  • Keep all other information as is

This requires two steps likely to be achieved by separate scripts:

  1. generate the FReD output, including figures
  2. embed that into the Reversals output - a key step here will be to simply identify the location where each effect is described

No 1 should be done by the FReD team (@LukasRoeseler or @LukasWallrich). No 2 could be done by anyone in #team-website

@flavioazevedo could you confirm that this is also your understanding of next steps?

Copy link

This issue has been inactive for more than 90 days. If there is no further activity, it will be automatically closed in seven days time. You can reopen the issue if it is still relevant.

@github-actions github-actions bot added the stale Marked by labeler label Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Marked by labeler
Projects
None yet
Development

No branches or pull requests

1 participant