You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A recent study which utilized AmpliconRepository somehow cited the dev server as the source of their calls (perhaps they found it on Github?) Regardless, this is definitely a mistake and we do not want people somehow ending up there because we don't guarantee the data hosted on dev is the 'correct' version of a project (CCLE, TCGA, etc.).
Proposed solution: when landing on dev.ampliconrepository.org, a pop-up or overlay (something much more obvious than a notification banner at the top of the page) appears to tell the that they are on the dev server and they can either "Redirect to AmpliconRepository.org" or "Continue using dev server".
Even better, users must log in to even see anything on dev (only specific people can access it), but I think this is more engineering.
A recent study which utilized AmpliconRepository somehow cited the dev server as the source of their calls (perhaps they found it on Github?) Regardless, this is definitely a mistake and we do not want people somehow ending up there because we don't guarantee the data hosted on dev is the 'correct' version of a project (CCLE, TCGA, etc.).
Proposed solution: when landing on dev.ampliconrepository.org, a pop-up or overlay (something much more obvious than a notification banner at the top of the page) appears to tell the that they are on the dev server and they can either "Redirect to AmpliconRepository.org" or "Continue using dev server".
Even better, users must log in to even see anything on dev (only specific people can access it), but I think this is more engineering.
https://www.sciencedirect.com/science/article/pii/S2001037024003829#sec0010
The text was updated successfully, but these errors were encountered: