Merge Split Branch

Author: actions-user

preview-account-request/assets/search/index.json

@@ -229,14 +229,14 @@ <h1 class="uw-mini-bar mb-4">
 
       <h2 id="featured-fellow">Featured Fellow</h2>
 
-      <div id="sandhya-nayar" class="bg-white team-card justify-content-center mb-3 flex-grow-1">
+      <div id="william-jiang" class="bg-white team-card justify-content-center mb-3 flex-grow-1">
     <div class="uw-card-content shadow">
         <div class="row">
             <div class="col-3">
                 <div class="overflow-hidden d-flex justify-content-center">
 
 
-                    <img src="/web-preview/preview-account-request/staff-list/images/sandhya_nayar.jpg" alt="Headshot for Sandhya Nayar" />
+                    <img src="/web-preview/preview-account-request/staff-list/images/william_jiang.png" alt="Headshot for William Jiang" />
 
                 </div>
             </div>
@@ -245,36 +245,32 @@ <h2 id="featured-fellow">Featured Fellow</h2>
                     <div>
                         <h2 class="uw-mini-bar mb-0 mt-3">
 
-                            Sandhya Nayar
+                            William Jiang
 
                         </h2>
-                        <div><h6 class="mt-2">Mentor(s):</h6> Cole Bollig and Todd Tannenbaum</div>
+                        <div><h6 class="mt-2">Mentor(s):</h6> Emma Turetsky and Justin Hiemstra</div>
                     </div>
                 </div>
             </div>
             <div class="col-12">
-                <h4 class="mt-3">Smart Aggregation and Indexing with the Archive Librarian</h4>
+                <h4 class="mt-3">Integrating Pelican and Globus</h4>
                 <div class="pt-2">
-                    <p>HTCondor saves large amounts of useful data about finished jobs
-that can help administrators, facilitators, and researchers
-who are trying to utilize historical job data. Currently,
-condor_history manually parses through flat files to get users
-their data; this makes it significantly harder to use, especially
-for older jobs, with no easy way to create useful aggregates.</p>
-
-<p>This project focused on the creation of the “Archive Librarian” service,
-to index job records from the HTCondor history archive and
-improve the usability of historical job data. Each job’s “address”,
-which is the combination of an offset and file metadata of a
-historical archive file, is stored in a database. This allows
-the librarian to directly locate job records and avoid using a
-sequential scan. The database also stores relevant job attributes
-that researchers commonly rely on, enabling future support for
-complicated queries and aggregate statistics.</p>
+                    <p>The Pelican Platform is an open-source software platform designed to create
+data federations by unifying diverse data repositories (e.g. POSIX
+filesystems, S3) under a single architecture. It differs from the Globus
+project, whose main goal is to facilitate peer-to-peer data transfer, and it
+thus lacks the means to plug into cluster scheduling frameworks like HTCondor.</p>
+
+<p>This project focused on bridging the gap between Pelican and Globus by
+integrating Globus transfer capabilities into Pelican. This will allow users
+to leverage Globus’s robust data transfer features while benefiting from
+Pelican’s unified data access model. The integration involved developing a
+Globus backend for Pelican and enabling seamless data transfers between
+Pelican-managed repositories and external systems via Globus.</p>
 
                 </div>
                 <div>
-                    <a class="btn btn-primary" href="./reports/2025/sandhya-nayar">Read Final Report</a>
+                    <a class="btn btn-primary" href="./reports/2025/william-jiang">Read Final Report</a>
                 </div>
             </div>
         </div>

preview-account-request/assets/search/metadata.json

@@ -259,7 +259,7 @@ <h3 id="how-to-request-a-chtc-account">How to request a CHTC account</h3>
 <ol>
 <li> <b>Fill out the account request form.</b> Tell us about the computing work you want to do to the best of your knowledge.</li>
 <li>You will receive an automated email from <a href="mailto:[email protected]">[email protected]</a> within a few hours of completing the form.</li>
-<li><b>Wait 2-3 business days</b> for a follow-up from CHTC Facailitation Staff. Contact us if you don't hear from us after 3 business days.
+<li><b>Wait 2-3 business days</b> for a follow-up from CHTC Facailitation Staff. Contact us at <a href="mailto:[email protected]">[email protected]</a> if you don't hear from us after 3 business days.
 	<ul>
 	<li><b>If you are part of a new research group</b>, we will first schedule a meeting with you to understand your computational needs before creating your account.</li>
 	<li><b>If you are part of an existing research group</b>, we will create a new account. We don't require a meeting, but highly recommend meeting with us, especially if you are new to research computing!</li>