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

Where can I find instructions on how to use frictionless with custom specifications #1616

Open
areleu opened this issue Jan 8, 2024 · 0 comments

Comments

@areleu
Copy link
Contributor

areleu commented Jan 8, 2024

Overview

We have been working for a couple of years with the open energy metadata: https://github.com/OpenEnergyPlatform/oemetadata/ which itself is an extension of the frictionless tabular data resource tabular data package specification (although I am trying to push for them to support other types of resources).

In short the spec consists of the base frictionless one with the possibility of adding more context (like spatial and temporal scopes, or funding agencies) and semantic annotations using IRIs and ontologies.

Currently If I use a descriptor following the open energy metadata spec to open a dataset with frictionless it works wonders, allows me to load and validate structures relatilvely fast. However It would be nice to have a way for the user to be able to explore the rest of the metadata directly using the frictionless api. So if for example I want the IRI of a specific field, instead of looking back and forth on the file or having to load paralel the metadata using a json library I can just ask frictionless to give me the extra fields of an specific field.

In the past I was trying to implement a plugin and I was already getting how to develop using the frictionless API but then you changed it completely so I had to drop the project and find an oportunity to start from scratch. Now I do not have the time to look at every piece of code so it would be great from you if there were some resources availible on how to develop plugins or how to support custom specficications.

I am aware of this documentation piece and this one but I can't seem to grasp on how to do what I want, which is extending the metadata and not to parse new types of files.

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

1 participant