Changes between Initial Version and Version 1 of Ticket #283


Ignore:
Timestamp:
04/08/10 08:36:57 (4 years ago)
Author:
rgrp
Comment:

Can I *strongly* suggest we just use the existing perfectly-good-system for flagging stuff called "tags" :)

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:

  1. Create "reserved" tag prefix "meta"
  2. Create following specific tags (suggestions/comments welcome):
  • meta.duplicate - duplicate of another package. If possible

indicate in notes or an extras field (to be decided) what it is duplicate of

  • meta.spam

Editors can then just visit ​http://ckan.net/tag/read/meta.spam and work through list of packages there.

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.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #283 – Description

    initial v1  
    1 Use case 
    2 ======== 
     1== Use case == 
    32 
    43As a user I want to notify the CKAN admins of a spammed or unsuitable package for deletion. 
    54 
    6 Suggested solution 
    7 ================== 
     5== Suggested solution == 
    86 
    97In the package view side-bar, there is a note: "To have this package completely removed, contact the [ca.ckan.net administrators [email protected]]." 
    108 
    11 Other solutions 
    12 =============== 
     9== Other solutions == 
    1310 
    1411A 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.