frictionless-r
frictionless-r copied to clipboard
R package to read and write Frictionless Data Packages
Data Package is now versioned, something that can be indicated at the `$schema` property. Ideally, frictionless-r supports (the properties that makes sense) for all versions (currently v1 and v2) and...
Just put together a quick sketch of what interlacer support might look like for frictionless-r Key features that interlacer brings: - interlaced columns (so missing reasons are easily accessible) -...
I wanted to assess the complexity of converting a v1 to a v2 Data Package. Below are the steps that need to be taken. For version detection, see #262. @khusmann...
With #262 we plan to introduce a `version()`, a function that doesn't start with a verb. This is similar to some [camtrapdp functions](https://inbo.github.io/camtrapdp/reference/index.html) (`version()`, `deployments()`, etc.). The functions have the...
To support Data Package v2 we need to be able to detect the version used by a package. - [ ] `$schema` is undefined - `version` = `1.0` - We...
This [vignette](https://docs.ropensci.org/frictionless/articles/data-package.html#manipulate) has a chunk to show that `check_package()` will return an (informative) error. The [code chuck](https://github.com/frictionlessdata/frictionless-r/blob/bb052ed50771bc1b00551381da137faca157e9b9/vignettes/data-package.Rmd#L62-L66) has the option `error = TRUE` allowing the vignette to ignore it and...
Hi, Is this desired? I would expect that `replace=TRUE` should not prevent the addition of a new (non-yet-exisiting) resource. ```r library(frictionless) package • deployments #> • observations #> • media...
It should cover: - [ ] `field.categoriesOrdered: true` - [ ] `field.categories` with labels - [ ] Integer field with categories - [ ] `field.missingValues` as array of strings -...
I'm starting this thread to brainstorm some of the ideas I mention in #198 and #251. It leans into the idea of data packages and table resources being their own...
The following helper functions have `package` and `resource_name` as arguments: - `locale()` - `read_from_path()` - `write_resource()` But they are called from functions that already have the `resource`. That means that...