[ckan-discuss] Deletion of packages
rufus.pollock at okfn.org
Wed Jun 15 09:43:13 BST 2011
On 14 June 2011 18:30, Anja Jentzsch <anja at anjeve.de> wrote:
> Hi Rufus,
> On Jun 14, 2011, at 6:21 PM, Rufus Pollock wrote:
>> On 14 June 2011 18:17, Anja Jentzsch <anja at anjeve.de> wrote:
>>> Hi all,
>>> I wonder why even an admin is not allowed to delete packages on CKAN? If there is no reason to prevent admins from doing that, can we have this feature?
>> Do you mean as an admin of the package or as a sysadmin? I'm certain
>> that as a sysadmin you can put a package in a deleted state (and more
>> significantly you can delete revisions and then purge then in
> a CKAN admin like me can delete every single revision and then purge them - which I did. This still leaves the package on CKAN in it's last stage (see bio2rdf).
> Friedrich then put the package in a deleted state which didn't change that either.
Answer to this is that there is a problem with the purge where the
package was added to a group (which this package unfortunately was).
Because of the FK from group the purge currently fails (you can see
this clearly from the error message in /ckan-admin/trash when you try
to purge it). We're working to fix this bug ...
>>> There are mainly three reasons a package might a deletion candidate:
>>> 1) mistyped package name
>>> 2) outdated and unavailable
>>> 3) misleading (as bio2rdf)
>> Agreed though think both (2) and (3) might better be addressed by some
>> special tagging system e.g. meta.obsolete meta.virtual (for virtual
>> packages that are "implemented" by other packages/datasets)
> Where is this documented?
What? The purging stuff or the approach to deletion candidates? On the
On the latter I think we should create a new wiki page, perhaps:
More information about the ckan-discuss