Replies: 5 comments 1 reply
-
@dafeder great question and this fits perfectly with current mapping efforts in frictionlessdata/forum#53 The starting point would be to extract the json schema fields and put in the spreadsheet here: https://docs.google.com/spreadsheets/d/1XdqGTFni5Jfs8AMbcbfsP7m11h9mOHS0eDtUZtqGVSg/edit#gid=774748003 Great if this is something you can help with o/w my colleagues @sglavoie may be able to help with it. Once that is done we can do a mapping which is generally pretty easy ~10m or so. Basically, most stuff just transfers across. |
Beta Was this translation helpful? Give feedback.
-
As a quick update, we have now described the Project Open Data schema in the spreadsheet (in this sheet). 🎉 |
Beta Was this translation helpful? Give feedback.
-
Thanks @rufuspollock and @sglavoie, coming back to this after a bit of time way. I'm going to go through but it looks pretty complete. One thing that's nice -- the move to calling this standard "DCAT-US" instead of the clunky "Project Open Data Schema" seems to be official, so that can make these docs a little more manageable. I'll try to create a mapping table as an additional sheet. |
Beta Was this translation helpful? Give feedback.
-
@dafeder that's great 👏 - let us know when you have gone through the mapping setup. |
Beta Was this translation helpful? Give feedback.
-
Hi all. Currently is there some way to convert (sort of) from DCAT to frictionless and viceversa? Thank you |
Beta Was this translation helpful? Give feedback.
-
I'm working on a data catalog that primarily stores and displays metadata using the Project Open Data metadata schema. What is the easiest way for me to present these datasets as data packages that will integrate with other frictionless data tools?
For instance, here is a one-dataset catalog example: https://gist.github.com/philipashlock/21ff607527863fba200b
Beta Was this translation helpful? Give feedback.
All reactions