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
The idea is to use the existing metadata we have, enrich it and then export to other metadata schemas. An example comes from the dataspice R package to prepare data publications.
I am thinking particularly of the write_spice() function, which writes metadata from a set of CSVs into the JSON-LD:
Take-away from 24/01 discussion:
Nic has a proof-of-concept python pkg on wasteskipsblantyre
current design is inside an owd R data package
pro: less redundant
con: can be confusing for most users and complica
This can be part of openwashdata phase 2 WP4: Increase FAIRness: https://openwashdata.org/pages/gallery/proposal-02/#wp4-increase-fairness
The idea is to use the existing metadata we have, enrich it and then export to other metadata schemas. An example comes from the
dataspice
R package to prepare data publications.I am thinking particularly of the
write_spice()
function, which writes metadata from a set of CSVs into the JSON-LD:https://docs.ropensci.org/dataspice/reference/write_spice.html
Package: https://docs.ropensci.org/dataspice/
We should review this workflow and adapt some of it to our own needs.
Another one is the Frictionless Data Table Schema: https://specs.frictionlessdata.io//table-schema/
Lastly, I think we should consider building a proper data catalogue using a data management system like CKAN: https://ckan.org/
@bonschorno @yashdubey132: we can split these up into different issues, but I would like you two to work on this.
The text was updated successfully, but these errors were encountered: