Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retrieving Processed JSON Data from Input CSV After Validation #1713

Open
ratheesh-kr opened this issue Nov 29, 2024 · 2 comments
Open

Retrieving Processed JSON Data from Input CSV After Validation #1713

ratheesh-kr opened this issue Nov 29, 2024 · 2 comments

Comments

@ratheesh-kr
Copy link

We integrated Frictionless for validating CSV files, and we are receiving validation responses as expected. However, we need to retrieve the original processed data in JSON format, parsed directly from the input CSV, along with the validation response.

Could you kindly confirm if there is a built-in method or API endpoint within Frictionless that allows us to obtain the parsed JSON data along with or after the validation process? If so, any guidance or documentation would be greatly appreciated.

@pierrecamilleri
Copy link
Collaborator

the original processed data in JSON format

Sorry, I do not understand this. Can you please elaborate ? Do you mean the validation report in JSON format ?

If yes, then frictionless validate --json returns the report in JSON format.

@megin1989
Copy link

Here’s the refined reply for your query:


Thank you for your response!

To clarify, we are successfully receiving the validation report in JSON format using the validate method. However, along with the validation report, we also need the actual data from the CSV file in a JSON-like format (e.g., rows parsed into dictionaries or similar structures).

We are aware of the extract method, which allows parsing CSV data into JSON. However, we would like to know if this data extraction can be done directly within the validate process, avoiding the need to handle the file separately for validation and data extraction.

Could you please confirm:

  1. If there’s a built-in feature in validate that supports this functionality?
  2. If not, would you recommend combining validate and extract programmatically to achieve this?

Any guidance or suggestions would be highly appreciated. Thank you!


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants