fix(db): ship missing helper views and bump current_version to 22.1
The shipped SQLite was missing
vw-mimat-mirna-uniqueandvw-mimat-mirna-swapped-mimat, which the companion miRNAmeConverter package queries directly fromcheckMiRNAName()andassessMiRNASwappingMIMAT(). Both methods failed with “no such table” against the shipped DB. Also setscurrent_versionmetadata to 22.1 (the latest exposed alias release).
- Add the two helper views to inst/extdata/miRBaseVersions.sqlite
- Make creating-views.R idempotent (CREATE VIEW IF NOT EXISTS) and skip 22.1 in the per-version loop so the alias view is not shadowed
- Persist the current_version metadata row from creating-views.R so future rebuilds keep it consistent
- Add integrity tests asserting helper views exist and current_version is “22.1”
Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com
miRBaseVersions.db
A Bioconductor-style annotation R package shipping mature miRNA names from 23 miRBase release versions (6.0 through 22.1). Exposed through the standard
AnnotationDbiselectinterface so it plugs in alongside any other annotation package.Use it to translate or reconcile mature miRNA accessions and names across miRBase versions — e.g. mapping a legacy
MIMATaccession to its current v22.1 name, or pulling the full per-version naming history of a miRNA.Installation
Runtime dependencies:
AnnotationDbi,DBI,RSQLite,methods,gtools.Quick start
The
MIMATkeytype searches across every version. EachVW-MIMAT-<X.Y>keytype is a per-release SQL view that filters down to one version.Versions covered
277 organisms in total.
Note on v22.1. miRBase 22.1 only updated the high-confidence subset (which this package does not model); sequences, accessions and names are unchanged from v22.0. The
VW-MIMAT-22.1keytype is therefore a relabelled alias view overVW-MIMAT-22.0rather than a separately ingested release. Querying it yields the same rows as v22.0 withVERSION = 22.1.Documentation
A worked-examples vignette is included with the package:
License
Artistic-2.0