Closed tfmorris closed 6 years ago
given that it's crawled on archive.org ( see #250 ), should it be struck?
it was fairly well-organized into
with tags for further breakdown.
so barring a wayback link, a diff against awesome-public-datasets to check for missing content would be nice if someone's up to it.
I'd argue that it definitely should be struck. Having to troll through random old issues, Wayback Machine listings, etc is a huge blow to awesomeness. If you'd like to contribute any listings that they had which aren't already on the awesome list (few, I suspect), that'd be doubly awesome, but I don't think it should hold up necessary housekeeping.
Having to troll through random old issues, Wayback Machine listings, etc is a huge blow to awesomeness.
No disagreement there.
but I don't think it should hold up necessary housekeeping.
Perhaps what we're actually talking around is a lack of explicit housekeeping rule (anywhere obvious, at least). Unavailables struck immediately, or sent to list purgatory (in case it's an intermittent issue or revival's possible etc), or something else entirely.
Actually we involved awesome_bot to validate the availability of data sources at the beginning. Finally gave up due to its frequent fake alerts.
@jcahill I am doing efforts towards a housekeeping service against data sources. An incubated project named prism (caesar0301/prism) is incubated, which aims to standardize, index, monitor, link awesome data around the world. I am still call for more contributors of this project (next generation of awesome-public-datasets), vvvvery welcome if you are interested in joining it.
@caesar0301 Thanks for merging.
@jcahill For the record, this isn't "struck immediately." The site was first reported dead in October, 2016.
understood @tfmorris. i meant in the sense of project-level logging. i think @caesar0301's reply clarified that this is a superseded side issue though.
Overview
Dataset Description <link to dataset>
_