[Ops] Policy for pruning non-responsive services from VO registries

[Tom McGlynn (NASA/GSFC Code 660.1)]

Renaud has put the latest draft of their proposal for cleaning registry 
entries for non responsive services at 
http://wiki.ivoa.net/internal/IVOA/IvoaOps/Proposal-Registry-QA-v0.4.pdf.

In the VAO/NAVO we have adopted a similar process but with smaller time 
scales and using a different mechanism for marking the services.

Our approach was:

Each month
    List services non-responsive for > 2 months
    Review list in our operations group
    Send email to responsible party[ies] indicating service[s] that will 
be deprecated in
      2 weeks
    After two weeks review list again including any responses.  No
      service deprecated if the responsible party expresses any 
objection.  We
      also confirm that the service is still unresponsive.
    Update the registry to change the validation level to 1 for 
remaining services.
      These services will not be returned in normal registry queries.

We've been doing this with some regularity for about 3 years.  My 
recollection is that we've virtually never had someone object to the 
proposed deprecation, nor have we had any complaints after doing so.  
We've gotten a lot of responses where the user said that the record 
should be deleted entirely (which we did when MAST was the responsible 
registry).  No records are deleted except on request and we continue to 
check deprecated services in case they come back up.


     Tom McGlynn


Tom McGlynn (NASA/GSFC Code 660.1) wrote:
> At the end of the second Ops session (Friday morning) we plan to 
> discuss the appropriate policy for ensuring that non-working services 
> are not being returned in our registry searches.  Renaud Savalle will 
> outline the process that VO-Paris has suggested to the Exec and I can 
> comment on the the policy we've used in the VAO and now NAVO to try to 
> clean up the registry hosted at MAST.    Overall its very similar but 
> we have used a different time frame.  Please feel free to comment in 
> advance on the list.  We will try to put out some additional 
> information in advance of the meeting.
>
>     Tom McGlynn
> _______________________________________________
> ops mailing list
> ops at ivoa.net
> http://mail.ivoa.net/mailman/listinfo/ops