• DATA AVAILABILITY - Results and datasets have to be provided as full datasets or as datasets pared based on statistical results. Studies that performed full analysis but only offer data for a subset of genes of interest are excluded.
• HUMAN - The database is for studies that involve human tissue or human-derived iPSCs and organoids.
• ORIGINAL RESEARCH - Original research and computational studies are considered. This excludes: reviews, database releases, commentaries.
• PUBLISHED - Preprint studies are not included in PARK-seq but are logged for follow-up.
• PUBMED - Only studies included in pubmed are considered.

• Can I add my own study? You cannot directly add a study, but you can contact us for review of the publication.
• What analysis did PARK-seq do? None. This is a curated database for published findings.
• How is data logged? Extraction is manual followed by gene standardization, and other editing in Python.
• Why is extraction not automated? The main problem with automated extraction is finding to what cohort, comparison, analysis, and author-specified cut-offs datasets refer. This is rarely straightforward. Extraction of other information can be automated.
• Why aren't there more studies? It will grow.
• Can I see FC, p-values and other metrics? At this time this information is not included. It is logged in a larger database; however, as data reported are not standard, PARK-seq does not offer a viewing option at this time. FC, r, and other measures should always be accompanied by an expression metric. baseMean, logCPM, FPKM, TPM, raw counts, and other values are not consistently provided.
• Can I download results? Not right now.  PARK-seq.release.2.May2026 is a beta release. Future versions will have download, report, and snapshot options. You can probably scrape, but we don't recommend that for the beta release as we are actively adding and amending.  PARK-seq.release.2.May2026 should not be considered a stable release. If you decide to scrape anyway, please be considerate and use random wait times where appropriate.
    def randomwait(numb1=1,numb2=1):
    waittime = numb1 + random.random()*numb2
    waittime = round(waittime,1)
    print("waittime:\t\t" + str(waittime))
    driver.implicitly_wait(waittime)
    time.sleep(waittime)
    return
  # USAGE THROUGHOUT CODE WHEN HUMAN WOULD DO A BUTTON CLICK
    randomwait(0,1)
  # USAGE AT END OF EACH QUERY
  if waitcanary % (1 + round(random.random()*100)) == 0:
    print("__longwait")
    randomwait(1,5)
  else:
    randomwait(0,1)
or something. Just be considerate of our resources. It's a small operation.
  
• Why are there different arrow types? Please refer to the Key on the site for the table:
  
  
  As a general rule,
  
  • ↑ or ↓ mean the adjusted p-value is less than 0.05 and both PARK-seq and the authors agree the results are significant. (If an adjusted p-value is not relevant then the rule holds for p-value).
  • (↑) or (↓) mean the authors consider the results significant but PARK-seq does not.
    This may be because the adjusted p-value used was 0.10 or a non-adjusted p-value was used (regardless of cut-off), or no p-value or adjusted p-value is provided. The former are both common for proteomics.
  • [↑] or [↓] mean PARK-seq considers the results significant, but the authors do not.
    This is most commonly when authors have a criterion for FC or expression levels.
  () and [] are also used for non-arrow results such as (eQTL), the same rules apply.
• Why is it PARK-seq so small on mobile? That is a setting design chosen to mimic a desktop display. We prefer it but realize it may not work for everyone. If you would like a more user-friendly mobile optimization, let us know so we can prioritize that in a future release.
• Where did you get this data? The data comes from published studies, associated supplemental data, and associated repositories.
  
  
• Is this only RNA-seq data? Proteomic, microarray, and long-read sequencing data are provided in addition to short-read data
• Are you associated with the PARKSEQ project 101107368? No. I apparently did not search thoroughly enough before buying the domains, and belatedly found out about the project. The name is a case of convergent evolution, if you will. But they certainly had it first.
• Why do I see spelling errors? Sorry.

If you would like to suggest a study, functionality, or if you have clarity on or suspect an error in the data, please contact us.

Conceptualization, design, lead curator, management

• Christy M. Kelley, Ph.D. 

Financial support

• Fredric P. Manfredsson, Ph.D.

Research associates and student volunteers

• Yash Sharma, B.S 
• Leena Abu-Rashid