Open rufuspollock opened 3 months ago
This is happening because there was no changes made to the corresponding README.md and so the sync workflow skipped it and its datapackage file wasn't processed. It will also happen if you make some changes to the datapackage that was previously correctly parsed if you don't make any changes to the README.md file (= datapackage changes won't go live). It's a bug of course.
@olayway great analysis.
IMO it's low priority as quite a rare bug so changing status.
Bug description
i've just published https://datahub.io/@rufuspollock/jaan-tallinn-donations-broken from https://github.com/rufuspollock/jaan-tallinn-donations - it should show up as a dataset project given i have a
datapackage.yaml
but that is not happening. Here's the result.I've now just created the site again new and it works 🎉 https://datahub.io/@rufuspollock/jaan-tallinn-donations
Debugging
OK, so i think the source here are the steps by which i created the repo. Steps were something like:
datapackage.yaml
So my guess here is that when it got initially published with just README and frontmatter it wasn't "seen" as a dataset project. And then even when the
datapackage.yaml
were added it didn't change the "type" of the project in the database (which is a 🐛)Thoughts
type
frontmatter field in the main README. Can still have the magic inference too.type
may be a bit too generic (it gets used for everything). MaybeprojectType
ordatahubType
. That saidtype
is simple and memorable!type
setting