<commit_before><html xmlns:th="http://www.thymeleaf.org">
<head>
    <link th:remove="all" rel="stylesheet" media="screen"
          href="//cdn.jsdelivr.net/bootswatch/3.3.7/flatly/bootstrap.min.css"/>
    <link rel="stylesheet" href="../static//css/chosen.css"/>
    <link rel="stylesheet" href="../static/css/customStyles.css"/>
    <title>PDX Finder</title>
    <!--/*/ <th:block th:include="fragments/head-includes :: head-includes"></th:block> /*/-->
</head>
<body>
<div class="page-header text-center">
    <h2 class="topSpace50"> <span >PDX Data Submission, Integration and Distribution
 </span> </h2>
</div>
<div class="container">
    <!--/*/ <th:block th:include="fragments/header :: header"></th:block> /*/-->
</div>

<!-- Page Content -->
<div class="container shiftUp100" >

    <div class="row">

        <h5>A summary of the PDX Finder data flow is represented in the figure below. </h5>
        <p class="fillUp">


            <div class="row pdxSummary">

                    <div class="col-md-6">
                        <img  style="border: 1px dashed #ccc; padding: 30px; margin-top: 25px;"  class="fullImg" th:src="@{/images/PDXDataFlow2.jpg}" src="../../static/images/PDXDataFlow2.jpg" >
                    </div>

                    <div class="col-md-6"  >
                        <h5> (1) Submission </h5><hr/>
                        <ul class="shiftUp20">
                            <li>PDX data is submitted by PDX producers via data access end-points (APIs) or direct upload of files collection.  </li>
                            <li>PDX producers can contact the PDX finder via email to submit data
                                <a href="mailto:<EMAIL>?cc=<EMAIL>&subject=PDX%20PRODUCER:%20DATA%20SUBMISSION%20REQUEST&body=Body-goes-here">(<EMAIL>)</a></li>
                        </ul>


                        <h5> (2) Neo4j database integration </h5><hr/>
                        <ul class="shiftUp20">
                            <li>	PDX data is stored in a secure Neo4j graph database.   </li>
                        </ul>


                        <h5> (3) Standardization and harmonization </h5><hr/>
                        <ul class="shiftUp20">
                            <li>	Automated integration processes periodically consume data sources and ensure standardization/adherence to
                                <a href="#" data-toggle="modal" data-target="#mi-modal" onclick="return false;">PDX-MI</a> and across center data harmonization. </li>
                        </ul>

                        <h5> (4) Data Distribution </h5><hr/>
                        <ul class="shiftUp20">
                            <li> PDX Finder supports multiple search attributes thereby allowing various points of entry into the data (e.g: tumor type, diagnosis, molecular markers). </li>
                            <li> Search results are displayed in a table to allow easy visualization, further filtering and selection. </li>
                            <li> Links allow users to drill down in selected PDX model data to discover additional patient, tumour, model attributes and associated studies (e.g dose response studies, 'OMIC' studies). </li>
                            <li> Links to the data sources the model originate from are provided (5). </li><commit_msg>PDXI-89 : Edited the method page for small website changes ticket<commit_after><html xmlns:th="http://www.thymeleaf.org">
<head>
    <link th:remove="all" rel="stylesheet" media="screen"
          href="//cdn.jsdelivr.net/bootswatch/3.3.7/flatly/bootstrap.min.css"/>
    <link rel="stylesheet" href="../static//css/chosen.css"/>
    <link rel="stylesheet" href="../static/css/customStyles.css"/>
    <title>PDX Finder</title>
    <!--/*/ <th:block th:include="fragments/head-includes :: head-includes"></th:block> /*/-->
</head>
<body>
<div class="page-header text-center">
    <h2 class="topSpace50"> <span >PDX Data Submission, Integration and Distribution
 </span> </h2>
</div>
<div class="container">
    <!--/*/ <th:block th:include="fragments/header :: header"></th:block> /*/-->
</div>

<!-- Page Content -->
<div class="container shiftUp100" >

    <div class="row">

        <h5>A summary of the PDX Finder data flow is represented in the figure below. </h5>
        <p class="fillUp">


            <div class="row pdxSummary">

                    <div class="col-md-6">
                        <img  style="padding: 30px; margin-top: 25px;"  class="fullImg" th:src="@{/images/PDXDataFlow2.jpg}" src="../../static/images/PDXDataFlow2.jpg" >
                    </div>

                    <div class="col-md-6"  >
                        <h5> (1) Submission </h5><hr/>
                        <ul class="shiftUp20">
                            <li>PDX data is submitted by PDX producers via data access end-points (APIs) or direct upload of files collection.  </li>
                            <li>PDX producers can contact the PDX finder via email to submit data
                                <a href="mailto:<EMAIL>?cc=<EMAIL>&subject=PDX%20PRODUCER:%20DATA%20SUBMISSION%20REQUEST&body=Body-goes-here">(<EMAIL>)</a></li>
                        </ul>


                        <h5> (2) Neo4j database integration </h5><hr/>
                        <ul class="shiftUp20">
                            <li>	PDX data is stored in a secure Neo4j graph database.   </li>
                        </ul>


                        <h5> (3) Standardization and harmonization </h5><hr/>
                        <ul class="shiftUp20">
                            <li>	Automated integration processes periodically consume data sources and ensure standardization/adherence to
                                <a href="#" data-toggle="modal" data-target="#mi-modal" onclick="return false;">PDX-MI</a> and across center data harmonization. </li>
                        </ul>

                        <h5> (4) Data Distribution </h5><hr/>
                        <ul class="shiftUp20">
                            <li> PDX Finder supports multiple search attributes thereby allowing various points of entry into the data (e.g: tumor type, diagnosis, molecular markers). </li>
                            <li> Search results are displayed in a table to allow easy visualization, further filtering and selection. </li>
                            <li> Links allow users to drill down in selected PDX model data to discover additional patient, tumour, model attributes and associated studies (e.g dose response studies, 'OMIC' studies). </li>
                            <li> Links to the data sources the model originate from are provided (5). </li>
{'fraction_non_alphanumeric': 0.135565230445879, 'fraction_numerical': 0.0157633988890557, 'mean_word_length': 1.939982347749338, 'pattern_counts': {'":': 0, '<': 155, '<?xml version=': 0, '>': 155, 'https://': 0, 'lorem ipsum': 0, 'www.': 2, 'xml': 2}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 4, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4930524', 'n_tokens_mistral': 1918, 'n_tokens_neox': 1794, 'n_words': 544}