Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Welcome to
rfishbase 5
! This is the fourth rewrite of the originalrfishbase
package described in Boettiger et al. (2012).Another streamlined re-design following new abilities for data hosting and access.
This release relies on a HuggingFace datasets hosting for data and metadata hosting
in parquet and schema.org.
Data access is simplified to use the simple HuggingFace datasets API instead
of the previous contentid-based resolution. This allows metadata to be defined
with directly alongside the data platform independent of the R package.
A simplified access protocol relies on
duckdbfs
for direct reads of tables.Several functions previously used only to manage connections are now deprecated
or removed, along with a significant number of dependencies.
Core use still centers around the same package API using the
fb_tbl()
function,with legacy helper functions for common tables like
species()
are still accessible andcan still optionally filter by species name where appropriate. As before, loading the
full tables and sub-setting manually is still recommended.
Historic helper functions like
load_taxa()
(combining the taxonomic classification from Species,Genus, Family and Order tables),
validate_names()
, andcommon_to_sci()
andsci_to_common()
should be in working order, all using table-based outputs.