tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
gigs vs patentsview
A side-by-side editorial comparison of gigs and patentsview — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
gigs vs patentsview: at a glance
What is gigs?
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
gigs implements international newborn and infant growth standards — INTERGROWTH-21st, WHO — converting anthropometric measurements to z-scores and centiles and classifying growth outcomes. The 0.5.0 release rewrote the public API around rOpenSci review feedback; the two releases after it change no code at all, existing purely to get the documentation site building.
What is patentsview?
Dormant for years, then rewritten wholesale when the API underneath it broke.
patentsview is an R client for the USPTO PatentsView API, and version 1.0.0 is less a feature release than a forced reconstruction: the upstream API introduced mandatory keys, renamed and re-nested its endpoints, and the package had to follow. Between 2017 and 2021 the release cadence was roughly annual and almost entirely defensive — wrapping examples so CRAN would not fail during API outages, patching URL encoding, adding throttling retries. The 1.0.0 work restores the package to parity with an API that no longer resembles the one it was written against.
gigs vs patentsview: editorial side-by-side
gigs
0.0ANALYTICS
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
◆ Current state
gigs implements international newborn and infant growth standards — INTERGROWTH-21st, WHO — converting anthropometric measurements to z-scores and centiles and classifying growth outcomes. The 0.5.0 release rewrote the public API around rOpenSci review feedback; the two releases after it change no code at all, existing purely to get the documentation site building.
◆ Where it's heading
The package has moved from vector-in, vector-out conversion helpers to a data.frame-oriented interface with a single classify_growth() entry point that computes whatever outcomes the supplied columns allow. That is a shift from library to tool — the user describes their data rather than picking the right function. The trailing releases suggest the code is settled and the remaining work is packaging and discoverability.
◆ Prediction
With the API rewrite absorbed and hosting moved to rOpenSci, the next substantive release should add growth standards or outcomes rather than reshape the interface again.
patentsview
0.0ANALYTICS
Dormant for years, then rewritten wholesale when the API underneath it broke.
◆ Current state
patentsview is an R client for the USPTO PatentsView API, and version 1.0.0 is less a feature release than a forced reconstruction: the upstream API introduced mandatory keys, renamed and re-nested its endpoints, and the package had to follow. Between 2017 and 2021 the release cadence was roughly annual and almost entirely defensive — wrapping examples so CRAN would not fail during API outages, patching URL encoding, adding throttling retries. The 1.0.0 work restores the package to parity with an API that no longer resembles the one it was written against.
◆ Where it's heading
The arc here is a client package whose roadmap is entirely dictated by an upstream service it does not control. Every release since 0.2.0 has been reactive — HTTPS migration, throttling, encoding fixes, and now a full breaking rewrite. The one forward-looking piece is retrieve_linked_data(), which follows HATEOAS links the API now returns, meaning the package is starting to navigate the API rather than just query fixed endpoints.
◆ Prediction
Expect the next releases to be small follow-ups against the reworked API — field list refreshes and error handling for endpoints that behave differently in practice than in the documentation. The entries do not show any independent roadmap, so anything beyond that would depend on further upstream API changes.
Alternatives to gigs and patentsview
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either gigs or patentsview.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
datasetjson
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
See all gigs alternatives → · See all patentsview alternatives →
Recent activity from gigs and patentsview
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6mo agopatentsviewRebuilt for PatentsView's new API: keys, nested endpoints ⚡
- 1y agogigsDocs and Zenodo archiving
- 1y agogigsDocs-only release; nothing changed internally
- 1y agogigsConversion API rewritten around data frames and classify_growth() ⚡
- 2y agogigsDocumentation fixes for autotest compliance
- 2y agogigsINTERGROWTH-21st fetal standards and input validation
- 2y agogigsPatch release with documentation update
- 4y agopatentsviewMoves to HTTPS endpoints and handles API throttling
- 7y agopatentsviewVignettes dropped so CRAN builds survive API outages
- 8y agopatentsviewAPI examples wrapped in dontrun for CRAN stability
- 8y agopatentsviewcast_pv_data() converts returned columns to real types
- 9y agopatentsviewFirst release: query DSL for the PatentsView API
Frequently asked questions
What is the difference between gigs and patentsview?
Both compete on the same themes — r-package — within Analytics. gigs and patentsview are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is gigs better than patentsview?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gigs and patentsview are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to gigs?
Top gigs alternatives in Analytics are ranked by recent ship velocity. Browse the "gigs alternatives" section above for the current picks, or visit /alternatives/gigs for the full list with editorial commentary on each.
What are the best alternatives to patentsview?
Top patentsview alternatives in Analytics are ranked by recent ship velocity. Browse the "patentsview alternatives" section above for the current picks, or visit /alternatives/patentsview for the full list with editorial commentary on each.