Open ravila4 opened 1 year ago
The simplest implementation option might be to use Elasticsearch's index lifecycle management (ILM) to delete indices when they reach a certain size or age. We would need to create a separate index for anonymous genesets. Edit: or possibly two indices, and have them rotate.
https://www.elastic.co/guide/en/elasticsearch/reference/8.5/index-lifecycle-management.html
Let me know if you do this, because we'll want to have a big warning about this, and also list it as a "pro" for signing up.
I'd recommend being very lenient though. Maybe 3-6 months. Maybe someone wants to have a geneset ready for a conference they are attending later in the year, and creates one anonymously because they are too busy to create an account.
Yes, probably not soon, I think this would be considered an enhancement. If we get a lot of anonymous genesets being created, we can reconsider.
Anonymous genesets are intended to allow quick sharing or user testing of the application, but we want to encourage users to associate their genesets to an account for long-term storage. Therefore, we could set anonymous genesets to have a default expiration date of, say, 1 week or 1 month (but we could allow customization for shorter or slightly longer expiries).
This could also help us discourage abuse and creation of spam or low quality genesets.