You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A research team within the Purdue College of Agriculture has started to use Frictionless for its data pipelines, and we would like to write custom Steps that receive configuration options from the Pipeline YAML file. For example:
steps:
# Standard Step -- ensure ID is an integer
- type: field-updatename: iddescriptor:
name: farm_animal_idtype: integer# Custom Step -- normalize funky date formats# Currently, in our testing, values (below) such as field_name or descriptor.name# are not getting passed to the custom step, and it appears they are not kept by# the custom Step mechanism. We want to capture them and pass them into the# custom Step initialization.
- type: date-normalizefield_name: Datedescriptor:
name: Datetype: string
The text was updated successfully, but these errors were encountered:
Hi Frictionless! We want to develop and submit a solution, and also plan to attend the hangout tomorrow, to get connected to the Frictionless community.
Overview
A research team within the Purdue College of Agriculture has started to use Frictionless for its data pipelines, and we would like to write custom Steps that receive configuration options from the Pipeline YAML file. For example:
The text was updated successfully, but these errors were encountered: