Forum: What's the correct way to withdraw a published database/server ?
gravatar for Pierre Lindenbaum
6.9 years ago by
France/Nantes/Institut du Thorax - INSERM UMR1087
Pierre Lindenbaum134k wrote:

(forum ? question ?)

Some years ago, one of our public database/server has been published. But now the underlying data are obsolete, the main developers are gone, the PHP code looks like a bowl of spaghetti(*), only a few random users access our data worldwide, nobody wants to work on this....

What would be the correct to withdraw our service ?

My ideas:

Furtheremore, when starting a new service, what would be the correct way to prepare it's unavoidable future retirement ?

  • create a mailing list to alert the users later ?
  • ?


(*) that's not my code! that's not my code ! :-)

forum database practices • 1.8k views
ADD COMMENTlink written 6.9 years ago by Pierre Lindenbaum134k

I would definitely turn to PubMedCommons now to see if there's any notice. I really liked that feature of the way that was being used.

ADD REPLYlink written 6.9 years ago by Mary11k
gravatar for Damian Kao
6.9 years ago by
Damian Kao15k
Damian Kao15k wrote:

I think adding a message on the website stating why it is being phased out and what are the plans for phasing it out would be sufficient.

I hate it when I find a great database only to find that the data is 5 years old and most of the functionalities are broken. A simple message on the front page would have saved me the time I spent trying to figure out if the database is any good or not.

ADD COMMENTlink modified 14 months ago by Ram32k • written 6.9 years ago by Damian Kao15k

I agree that a message is sufficient. If you want to go one step further, how about supplying the dataset or a subset of the data for download to any users who still may want to access it? There are times when 5 year old data are better than no data.

ADD REPLYlink modified 14 months ago by Ram32k • written 6.9 years ago by Katie D'Aco1.0k

good point, a simple text dump of the database gzipped up

ADD REPLYlink written 6.9 years ago by Istvan Albert ♦♦ 86k

My guess is every Biostar user would agree that transparant life cycle managment (birth > death > archive the data) and release update information should be essential prerequisites for setting up a server or db in the fist place. AWAK this is exasperatingly rare. Sure, if folk are feeling down because funding is pulled/runs out we can understand them not bothering, but there has to be a better way. The PubMed commons announcment as a suplement to the web page announcment is a good idea.

ADD REPLYlink modified 14 months ago by Ram32k • written 6.9 years ago by cdsouthan1.8k

Moved your comment to an answer ... because now moderation includes this option :-)

I agree with everything and would have only made it a "me too" post.

Sunsetting services is unavoidable, and the only thing that is really irritating with obsolete services is not realizing that they are not maintained anymore and thus waste valuable time on them.

ADD REPLYlink written 6.9 years ago by Istvan Albert ♦♦ 86k
Please log in to add an answer.


Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 2.3.0
Traffic: 1667 users visited in the last hour