MSK users sometimes put internal urls in their publications. e.g.
http://ascopubs.org/doi/full/10.1200/JCO.2017.75.3384

We need to be able to add a warning and ask them not to do that.
study_view_warningThis issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
this is still happening. But maybe the message I put above is a bit too long.
thoughts, @schultzn ?
How about just "Study URL is temporary - do NOT include in publications."
This applies to all studies in MSKCC/triage portals right? If so, maybe we can make it more general i.e. allow to add some blurb to the description of all studies in a portal. For example a skin.study_view.blurb. Similar to skin.blurb: https://docs.cbioportal.org/2.3-customization/portal.properties-reference#control-the-content-of-specific-sections.
@inodb sounds good. Yes, to all studies.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
we should do this

Thanks, @Leowisd. It looks good!
For the last one, could you add "transferred to the public cBioPortal"?
Is this message configurable? e.g. we should have a message in the private portal too.
@schultzn @n1zea144 comments?
Okay.

Reverse the order of items so the link warning is first, and the guidelines second.
When adding a link to a cBioPortal cohort in a manuscript, **I will not link to the internal MSK portal (cbioportal.mskcc.org)**, but will instead link to this study on the public cBioPortal (cbioportal.org). Contact [email protected] with any questions about getting the data transferred to the public cBioPortal.
Got it


@Leowisd we only want to do this when
["triage-portal","mskcc-portal"].includes(AppConfig.serverConfig.app_name)
you may have to import AppConfig if it's not already imported on your page