JASPAR
Update the following URL to point to the GitHub repository of the package you wish to submit to Bioconductor
- Repository: https://github.com/da-bar/JASPAR
Confirm the following by editing each check box to '[x]'
-
[x] I understand that by submitting my package to Bioconductor, the package source and all review commentary are visible to the general public.
-
[x] I have read the Bioconductor Package Submission instructions. My package is consistent with the Bioconductor Package Guidelines.
-
[x] I understand Bioconductor Package Naming Policy and acknowledge Bioconductor may retain use of package name.
-
[x] I understand that a minimum requirement for package acceptance is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. Passing these checks does not result in automatic acceptance. The package will then undergo a formal review and recommendations for acceptance regarding other Bioconductor standards will be addressed.
-
[x] My package addresses statistical or bioinformatic issues related to the analysis and comprehension of high-throughput genomic data.
-
[x] I am committed to the long-term maintenance of my package. This includes monitoring the support site for issues that users may have, subscribing to the bioc-devel mailing list to stay aware of developments in the Bioconductor community, responding promptly to requests for updates from the Core team in response to changes in R or underlying software.
-
[x] I understand it is my responsibility to maintain a valid, active maintainer email in the DESCRIPTION of my package. This email should allow emails from [email protected] and [email protected] to allow automatic notifications from the Bioconductor team concerning my package.
-
[x] I am familiar with the Bioconductor code of conduct and agree to abide by it.
I am familiar with the essential aspects of Bioconductor software management, including:
- [x] The 'devel' branch for new packages and features.
- [x] The stable 'release' branch, made available every six months, for bug fixes.
- [x] Bioconductor version control using Git (optionally via GitHub).
For questions/help about the submission process, including questions about the output of the automatic reports generated by the SPB (Single Package Builder), please use the #package-submission channel of our Community Slack. Follow the link on the home page of the Bioconductor website to sign up.
Hi @da-bar
Thanks for submitting your package. We are taking a quick look at it and you will hear back from us soon.
The DESCRIPTION file for this package is:
Package: JASPAR
Type: Package
Title: Data package for JASPAR databases
Version: 0.99.1
Authors@R: person(given = "Damir", family = "Baranasic",
role = c("aut", "cre"),
email = "[email protected]",
comment = c(ORCID = "0000-0001-5948-0932"))
Description: JASPAR (https://jaspar.elixir.no/) is an open-access database that
has provided high-quality, manually curated, and non-redundant DNA
binding profiles for transcription factors (TFs) as position
frequency matrices (PFMs) for over 20 years. For this 11th release
of the database, we expanded our CORE and UNVALIDATED collections
with new PFMs and updated existing profiles. Specifically, we
added 306 and 433 new binding profiles to the CORE (a 12%
increase) and UNVALIDATED (a 60% increase) collections,
respectively, and updated 13 profiles from the CORE collection.
With the new collections of PFMs, we updated the TF binding site
predictions in eight species and provided the corresponding
genomic tracks. Moreover, we updated the profile clusters and
familial TF binding sites accordingly. This release introduces a
regulatory sequence simulation tool, inMOTIFin, enabling users to
simulate regulatory sequences using JASPAR PFMs. To enrich the
annotations linked to the TFs, JASPAR now provides scientific
literature-based human TF target information derived from a large
language model. Notably, this release features the addition of a
new collection of deep learning BPnet models, providing a paradigm
shift in modeling and characterizing TF-DNA interactions, driven
by advances in artificial intelligence. JASPAR 2026 provides 1304
BPNet models trained on Homo sapiens ENCODE ChIP-seq datasets from
264 TFs. Interpretation of the BPnet revealed critical binding
profiles that were curated and matched to JASPAR CORE PFMs for an
easy overview of the binding patterns. Profiles from BPnet models
associated with the same TF were clustered to provide a
non-redundant summary of the binding properties of the TF,
resulting in 266 primary motifs in the new Deep Learning
collection. The 2026 release of JASPAR now offers the classical
manually curated collections of TF binding profiles and
state-of-the-art deep learning models. These collections lay a
foundation for future endeavors in genomic research, serving the
scientific community in uncovering the mechanisms of gene
regulation.
Depends: R (>= 4.5.0), methods, BiocFileCache, utils
License: GPL-2
URL: https://jaspar.elixir.no/
NeedsCompilation: no
biocViews: AnnotationData, FunctionalAnnotation, AnnotationHub
LazyData: no
RoxygenNote: 7.3.3
Suggests:
knitr,
rmarkdown,
BiocStyle,
RSQLite,
TFBSTools
VignetteBuilder: knitr
BugReports: https://github.com/da-bar/JASPAR
Will this package supersede current Annotation packages JASPAR2018, JASPAR2020, JASPAR2022, and JASPAR2024 where these older packages could potentially be deprecated?
I see you mention AnnotationHub as biocView? should the entries in metadata.csv be officially added to the AnnotationHub resource for access through that interface?
Your package has been added to git.bioconductor.org to continue the pre-review process. A build report will be posted shortly. Please fix any ERROR and WARNING in the build report before a reviewer is assigned or provide a justification on why you feel the ERROR or WARNING should be granted an exception.
IMPORTANT: Please read this documentation for setting up remotes to push to git.bioconductor.org. All changes should be pushed to git.bioconductor.org moving forward. It is required to push a version bump to git.bioconductor.org to trigger a new build report.
Bioconductor utilized your github ssh-keys for git.bioconductor.org access. To manage keys and future access you may want to active your Bioconductor Git Credentials Account
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on the Bioconductor Single Package Builder.
On one or more platforms, the build results were: "ERROR". This may mean there is a problem with the package that you need to fix. Or it may mean that there is a problem with the build system itself.
Please see the build report for more details.
The following are build products from R CMD build on the Single Package Builder: Linux (Ubuntu 24.04.3 LTS): JASPAR_0.99.1.tar.gz
Links above active for 21 days.
Remember: if you submitted your package after July 7th, 2020,
when making changes to your repository push to
[email protected]:packages/JASPAR to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.
Will this package supersede current Annotation packages JASPAR2018, JASPAR2020, JASPAR2022, and JASPAR2024 where these older packages could potentially be deprecated?
I see you mention AnnotationHub as biocView? should the entries in metadata.csv be officially added to the AnnotationHub resource for access through that interface?
Hi Lori,
I'm sorry for not getting back to you sooner. Yes, the current package will supersede the mentioned older packages, and those can be deprecated. Currently, the last three versions of JASPAR are supported and actively maintained and will be included in this package.
We would also like to add the entries in metadata officially.csv to the AnnotationHub resources; however, we would wait for the peer review of the JASPAR2026 version and the paper acceptance before we change the current version of JASPAR to JASPAR2026 and change to the release URL.
Received a valid push on git.bioconductor.org; starting a build for commit id: 55c321dbd7f7318ce40f34650f64a0938740be29
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on the Bioconductor Single Package Builder.
On one or more platforms, the build results were: "ERROR". This may mean there is a problem with the package that you need to fix. Or it may mean that there is a problem with the build system itself.
Please see the build report for more details.
The following are build products from R CMD build on the Single Package Builder: Linux (Ubuntu 24.04.3 LTS): JASPAR_0.99.3.tar.gz
Links above active for 21 days.
Remember: if you submitted your package after July 7th, 2020,
when making changes to your repository push to
[email protected]:packages/JASPAR to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.
Received a valid push on git.bioconductor.org; starting a build for commit id: fc9ce6046b9fe137637b6db8997fdd2e83680cbb
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on the Bioconductor Single Package Builder.
Congratulations! The package built without errors or warnings on all platforms.
Please see the build report for more details.
The following are build products from R CMD build on the Single Package Builder: Linux (Ubuntu 24.04.3 LTS): JASPAR_0.99.4.tar.gz
Links above active for 21 days.
Remember: if you submitted your package after July 7th, 2020,
when making changes to your repository push to
[email protected]:packages/JASPAR to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.
So is this package going to change its name? If that is the case we should not proceed until you are ready for that to happen as it is very very difficult and time consuming to change a package name once a package is accepted into Bioconductor.
Would you like me to proceed with adding the data into AnnotationHub awhile?
@da-bar response ?
Hi @lshep Sorry for my late reply. No, the package will not change its name, and the future releases of JASPAR will be added to this package. However, the metadata.csv file will change, since the links to the stable release will be refreshed. Will this be a problem for adding it to the AnnotationHub? Will be able to change the metadata.csv in the AnnotationHub when we update the links in it?
Will it only be the links to the downloadable data that changes or the entire metadata? And will this just be a one time change or every release (not including adding new -- just mean making changes to existing entries)
Hi @lshep
It will be only the links in the metadata.csv We will need to change the link every release (on top of adding the new version, every two years) since jaspar.elixir.no will be pointing to the newest release.
lets move forward with it and we can worry about the updating later on .... I'll go ahead and start adding these to the hub officially so we can proceed.
Data added
> query(ah, "JASPAR")
AnnotationHub with 16 records
# snapshotDate(): 2025-10-10
# $dataprovider: JASPAR 2022, JASPAR is brought to you by a collaborative ef...
# $species: Homo sapiens, Mus musculus, NA
# $rdataclass: GRanges, JASPAR
# additional mcols(): taxonomyid, genome, description,
# coordinate_1_based, maintainer, rdatadateadded, preparerclass, tags,
# rdatapath, sourceurl, sourcetype
# retrieve records with, e.g., 'object[["AH104719"]]'
title
AH104719 | T2T.JASPAR2022_CORE_vertebrates_non_redundant_v2.RData
AH104721 | T2T.MA0139.1.RData
AH104727 | hg38.JASPAR2022_CORE_vertebrates_non_redundant_v2.RData
AH104729 | hg38.MA0139.1.RData
AH104736 | hg19.JASPAR2022_CORE_vertebrates_non_redundant_v2.RData
... ...
AH104762 | mm9.JASPAR2022_CORE_vertebrates_non_redundant_v2.RData
AH104764 | mm9.MA0139.1.RData
AH121719 | JASPAR2026
AH121720 | JASPAR2024
AH121721 | JASPAR2022
Awsome, thank you. I will add the accession in the vignette.
A reviewer has been assigned to your package for an indepth review. Please respond accordingly to any further comments from the reviewer.
Hi @da-bar ,
Just a quick note: the vignette still follows the old workflow, so it needs an update to reflect the current AnnotationHub setup. No rush, but once that’s updated I can continue with the review. Thank you!