On 6 July 2017 at 17:37, Doug Bell <d...@preaction.me> wrote: > To me, that makes it a non-solution: > Forcing everyone using the data to figure out which data is invalid is too > high a burden. If we simply hide the data from any and all APIs that CPAN > Testers has, that is, to me, worse than deleting it, since it requires > changing potentially every query in the CPAN Testers site and every index in > the database, which would be disruptive, and it ensures the data is actually > worthless, since there's no actual way to read it. So if we're going to make > it worthless, why not just delete it?
I think it would be more useful to do it the other way around. Add a mechanism for authors to flag individual reports, as either "invalid" (that is, was never relevant) or "archive" (was once relevant, but now just confuses people who see it) And then do nothing with that data other than make it accessible from some future API we add. Then, the default behaviour of retaining those reports forever is preserved, but any tools that want to hide/filter data can do so (and we'll encourage said tools to make it obvious they're hiding data when they're hiding data, how much data they're hiding, and providing mechanisms to disable data hiding ) This way the author isn't dictating what the user sees, only creating a suggestion for how they might view the data, and its up to the author/consumer as to if they trust those suggestions or not. And then for Test2's kind of usecase, perhaps a tool that can bulk flag reports would be useful. -- Kent KENTNL - https://metacpan.org/author/KENTNL
