How to remove a dataset?

Once a dataset has been added to data.gov.uk it seems that I cannot remove it? The contact page is also ineffective as I have been waiting for a response for a very long time now.

Does anyone know how to remove a dataset? 

Comments

Why do you want to remove a dataset?

I am probably coming at this from too restricted a background (statistical) but the practice there is not to withdraw out-of-date or even incorrect datasets but to mark them as obsolete or errorneous respectively. That enables users to determine what has been revised and also enables them to replicate or refine someone else's analysis without having to worry about whether the data have since changed.

I'm not sure whether that basis principel - once published, always available - is followed elsewhere. Instinctively I feel it should be but there may be good reasons not to. So I'm asking - what are the reasons for wanting to withdraw a dataset altogether?

 Flag as offensive 

Deleting datasets

Hi Kamrul,

Following is a link to the relevant page in the Data.gov.uk guidance for users, publishers and sysadmins:

http://guidance.data.gov.uk/deleting_datasets.html

This indicates that only a system administrator can delete a dataset (or more precisely the catalogue entry for a dataset).

If you cannot get a response via the contact form I suggest shouting at them on Twitter. That usually works.

-- Owen Boswarva, 15/03/2016

 Flag as offensive 

Hi Kamrul,

Hi Kamrul,

If you could point me at the dataset, and explain why you think it needs removing, I can certainly take a look at that for you.  If it is INSPIRE data you should be able to talk to the publisher admin to use the 'Withdrawn' link (your administrator is listed under the people icon at https://data.gov.uk/publisher/nottingham-city-council if you're not sure who it is). 

Ross.

 Flag as offensive 

You need to call

You need to call TableCollection.Remove

m_dsSet.Tables.Remove(TableName);

 Flag as offensive 

How to remove a dataset?

before you remove the table from the dataset try to clear all its constaints, something like this:

domain.Tables["TABLE_NAME"].Constraints.Clear();
should work and you should then be able to remove it from the dataset.

if you have the issue with PK Constraint which cannot be removed try this:

        var myTable = domain.Tables["TABLE_NAME"];

        for (int i = myTable.Constraints.Count - 1; i >= 0; --i)
        {
            if (myTable.Constraints[i] is System.Data.ForeignKeyConstraint)
            {
                myTable.Constraints.Remove(myTable.Constraints[i]);
            }
        }

 Flag as offensive 

Hello :)

I'm not certain whether that premise principel - once distributed, constantly accessible - is taken after somewhere else. Naturally I feel it ought to be however there might be great reasons not to. So I'm asking - what are the explanations behind needing to pull back a dataset through and through?

 Flag as offensive