The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

likingInitiative 0.2.2

• Release files are cached in the session’s temporary directory by default. use_persistent_cache() opts in to a cache that survives the session, and options(likingInitiative.cache_dir = ) or LIKING_INITIATIVE_CACHE_DIR still name a directory directly. The package now writes nothing outside the temporary directory unless asked.
• The database’s DOI is cited in the package description.

likingInitiative 0.2.1

• Examples that download are guarded with @examplesIf interactive() rather than \donttest{}, so R CMD check runs none of them and leaves the cache untouched.
• A pinned version = now downloads that version’s files. Previously the version label was honoured in the cache path but the newest release’s files were fetched, which would have silently drifted once a newer release existed.
• Unknown versions fail with the list of published versions.
• citation("likingInitiative") returns the database citation with its DOI.
• Package metadata points at the liking-initiative organization; the test suite honours LIKING_INITIATIVE_RELEASE_DIR outside the monorepo and skips cleanly when no release is available.

likingInitiative 0.2.0

• Assets are fetched from Zenodo, so the package works without credentials. latest follows the concept DOI (10.5281/zenodo.22216442) and needs no package update when a new version is published.
• Transient Zenodo statuses (429, 500, 502, 503, 504) are retried with backoff.
• cite() returns the database citation with its DOI.
• Six datasets carry repeated rating phases as timepoint; get_item() uses each dataset’s first phase.

likingInitiative 0.1.0

• First release: catalogue listings, get_dataset(), get_item(), load_database(), citations, and a local asset cache, all backed by versioned release files rather than the live API.

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.