Score tags

[Macayla-weiner]

Description

Summarize the changes

Fixes: # Link to any relevant issues and/or discussions

Major Changes

• Every locus got a new tag: conflicting, limited, or supported depending on their score
• Added the above tags and hover-over blurbs

Checklist

• All changes are well summarized
• Check all tests pass
• Check that the website preview looks good
• Update the STRchive version in CITATION.cff, format X.Y.Z. If any major changes, increment Y. If only minor changes, increment Z. If the breaking change (rare), increment X.
• Ask someone to review this PR

[netlify]

✅ Deploy Preview for strchive ready!

Name	Link
🔨 Latest commit	4182cff
🔍 Latest deploy log	https://app.netlify.com/projects/strchive/deploys/6896018ea022d50008dccaa1
😎 Deploy Preview	https://deploy-preview-229--strchive.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[hdashnow]

@Macayla-weiner what do you think about having a category like "not yet assessed" or "not yet reviewed". I'm not sure quite what to call it. I can have it automatically added to any locus that doesn't yet have an evidence tag and then it can be manually removed once it has been scored.

[hdashnow]

There are two ways I think this could look. See examples. I've pushed option 2 below. To switch to option 1, simply change this value to true.

Option 1: Annotate all loci with the evidence tag - most will have the supported check mark

Option 2: Only annotate loci with evidence tag if they're not supported - most will have no tag