http://localhost/ticket/283 <h2 id="Usecase">Use case</h2> <p> As a user I want to notify the CKAN admins of a spammed or unsuitable package for deletion. </p> <h2 id="Suggestedsolution">Suggested solution</h2> <p> In the package view side-bar, there is a note: "To have this package completely removed, contact the [ca.ckan.net administrators admin@…]." </p> <h2 id="Othersolutions">Other solutions</h2> <p> A more complicated solution would be to allow packages to be tagged for deletion, which would auto-alert administrators, and allow easier administration of this. But this might be overkill. </p> <p> c.f. <a class="ext-link" href="http://en.wikipedia.org/wiki/Deleting_an_article"><span class="icon">​</span>http://en.wikipedia.org/wiki/Deleting_an_article</a> </p> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/283 Trac 0.12.3 rgrp Thu, 08 Apr 2010 08:36:57 GMT http://localhost/ticket/283#comment:1 http://localhost/ticket/283#comment:1 <ul> <li><strong>description</strong> modified (<a href="/ticket/283?action=diff&amp;version=1">diff</a>) </li> </ul> <p> Can I *strongly* suggest we just use the existing perfectly-good-system for flagging stuff called "tags" :) </p> <p> I suggest we have agree in the community a standard set of "meta" tags for this kind of stuff. E.g. i'm already using the "duplicate" tag for marking duplicates (I also add in notes the link to duplicate package but that's optional). So I suggest we: </p> <ol><li>Create "reserved" tag prefix "meta" </li><li>Create following specific tags (suggestions/comments welcome): </li></ol><ul><li>meta.duplicate - duplicate of another package. If possible </li></ul><p> indicate in notes or an extras field (to be decided) what it is duplicate of </p> <ul><li>meta.spam </li></ul><p> Editors can then just visit <a class="ext-link" href="http://ckan.net/tag/read/meta.spam"><span class="icon">​</span>http://ckan.net/tag/read/meta.spam</a> and work through list of packages there. </p> <p> If "push" notifications are required as well as "pull" then I suggest this be put in an external service (e.g. rss2email) rather than integrated into CKAN core. </p> Ticket dread Fri, 22 Jul 2011 09:05:26 GMT http://localhost/ticket/283#comment:2 http://localhost/ticket/283#comment:2 <ul> <li><strong>repo</strong> set to <em>ckan</em> </li> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>theme</strong> set to <em>none</em> </li> <li><strong>resolution</strong> set to <em>wontfix</em> </li> </ul> Ticket