<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type"/>
</head>
<body style="height: 100% !important; width: 100% !important; background-color: #F7F9FA; margin: 0; padding: 0;">
<!-- Preheader -->
<table border="0" cellpadding="0" cellspacing="0" align="center" style="font-family:Arial,Helvetica,sans-serif;font-size: 13px;color:#131619;background-color: #F7F9FA; width: 100%; height: 100%;padding-bottom: 10px;">
<tr>
<td style="vertical-align: top">
<table border="0" cellpadding="0" cellspacing="0" align="center" style="width:700px;">
<tr>
<td style="vertical-align: top;padding: 0px; background-color: #f4f5f9">
<table border="0" cellpadding="0" cellspacing="0" align="center"
style="margin-left: 0px;margin-right: 0px;width: 100%;background-color: #ffffff;padding-bottom: 37px;">
<!-- email header -->
<tr>
<td style="padding-top: 28px;padding-bottom: 28px;padding-left:32px;background-color:#0B5CFF;text-align: left;">
<a href= "https://zoom.com">
<img src="https://click.zoom.us/l/84442/2022-12-29/c4ns1t/84442/1672332921RKagdau8/Logo_white_2022.png" style="border-style: solid;" width="110" height="25" border="0"/>
</a>
</td>
</tr>
<!-- email body -->
<tr>
<td style="padding-left: 32px;padding-right: 32px;">
<table border="0" cellpadding="0" cellspacing="0" align="center"
style="width: 100%;font-size: 16px;color:#131619;">
</table>
<table border="0" cellpadding="0" cellspacing="0" style="width: 100%; height: 100%;">
<tbody>
<tr style="height: 24px;"></tr>
<tr>
<td colspan="2">
<table border="0" cellpadding="0" cellspacing="0" align="left" style="padding-top: 5px;padding-bottom: 5px;width: 100%;font-size: 13px;color: #39394d;font-family: Arial;background: #F2F2F4;">
<tr>
<td align="left" width="55" style="width: 55px;mso-line-height-rule: exactly; line-height: 30px;vertical-align:top;padding: 7px 12px 10px 12px">
<img width="55" height="25" src="https://st3.zoom.us/static/6.3.30118/image/summary/summary_new_logo_v2.png" style="width: 55px; height: 25px; border-width: 0; border-style: solid;vertical-align: bottom;" />
</td>
<td align="left" style="text-align: left; font-size: 13px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: middle;">
Meeting summary with AI Companion now supports additional languages in preview. </td>
<td align="left" width="80" style="width: 80px;text-align: left; font-size: 13px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: middle;">
<a style="display: inline-block;color: #0B5CFF;text-decoration: none;font-weight: 600" href="https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0058013#languages">Learn More</a>
</td>
</tr>
</table>
</td>
</tr>
<tr style="height: 24px;"></tr>
<tr>
<td colspan="2" style="font-size: 19px;color: #131619;font-family: Arial,Helvetica,sans-serif;line-height: 25px;font-weight: 700;">
<table border="0" cellpadding="0" cellspacing="0" align="center" style="width: 100%;font-size: 19px;color: #39394d;font-family: Arial;">
<tr>
<td align="left" style="padding-right: 24px;mso-line-height-rule: exactly; line-height: 25px;text-align:left;font-size:19px;color:#39394d;font-family:Arial,Helvetica,sans-serif;vertical-align:top">
<strong>Meeting summary for Data Curation & Publication Office Hours T/Th (01/15/2025)</strong>
</td>
</tr>
</table>
</td>
</tr>
<tr style="height: 32px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Quick recap</strong>
</td>
</tr>
<tr style="height: 6px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
The team discussed the limitations and potential improvements of their current data storage system, with a focus on the need for a more robust solution for large data sets. They explored the possibility of using a new backend, such as Versity, and considered breaking down large data sets into smaller, more manageable chunks for easier upload. The team also discussed the need for versioning in data sets and the importance of preserving access to original data.
</td>
</tr>
<tr style="height: 32px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Next steps</strong>
</td>
</tr>
<tr style="height: 6px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Maria to meet with the student (Sathannam) to discuss breaking up the problematic data set into manageable chunks.
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Maria to present the proposed data chunks to Nick for review before uploading.
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Maria and team to create a new data set and start uploading in smaller, manageable pieces.
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Nick to assist with testing and troubleshooting the new data set uploads as needed.
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Maria to add a clear message to the existing problematic data set indicating it contains stale data and should not be relied upon for scientific purposes.
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Chris to work on implementing the Versity S3 adapter as a replacement for MinIO.
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Kristi to follow up with Courtney regarding the upcoming meeting with the Dataverse developer about improving support for remote storage.
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
• Kristi to keep Chris, Maria, and Lydia informed about progress on the larger data working group and Dataverse development efforts.
</td>
</tr>
<tr>
<td colspan="2" style="font-size:14px;line-height:32px;color:#dedede;border-bottom: 1px solid #dedede;padding-top:22px;">
</td>
</tr>
<tr>
<td colspan="2" style="font-size:14px;line-height:32px;padding-top: 22px;">
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Summary</strong>
</td>
</tr>
<tr style="height: 6px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Addressing TDR Implementation Challenges</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
Maria expressed concerns about the current implementation of the Texas Data Repository (TDR) for large data sets, particularly for the robotics department at the University of Texas at Austin. She highlighted issues with the system, including roadblocks and the need for a more robust solution. Kristi, who was filling in for Courtney, agreed that a better solution was needed and mentioned a parallel project to develop a production service for larger data sets. Nicholas suggested that further testing with the current implementation might not be worth it, given that Minio is going out of support. Christopher was present but did not contribute to the discussion.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>System Fragility and Future Improvements</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
The team discussed the current state of their system, which is fragile and needs further testing. They agreed to continue supporting the current solution for now, but acknowledged that there is no viable future for it. They also discussed the need for versioning in data sets, which is crucial for researchers. The team expressed willingness to work on improving the system, despite it being an unfunded project. They agreed to test the system to determine its current quality and stability, which would provide Maria with a better understanding of its performance.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Exploring New Solutions and Testing</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
Nicholas and Christopher discussed the limitations of their current system and the potential for a new solution. They agreed that testing the current system might not be productive due to its lack of support and improvements. Christopher suggested moving quickly to test a new solution, but noted that this would require new QA and dev instances. Nicholas mentioned that they were planning an upgrade on their side and might be able to test a new solution on their training environment. Kristi confirmed that they could have an implementation of the new version within the next 2-3 weeks. Christopher also suggested that swapping out one S3 front end for another with the existing data structures could be a viable solution. Maria asked about the new technology they would like to implement and the next steps if the testing went well.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>DataVerse Backend Replacement Discussion</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
The team discussed the need for a new backend for their data storage system, DataVerse, due to the discontinuation of the current implementation, MinIO. They considered replacing it with Versity, which is supported by Los Alamos. However, they acknowledged that Versity is still relatively new and not fully mature. They also explored the possibility of using a different backend, such as a static HTTP server, but noted that they had not been able to get it to function properly. The team also discussed the limitations of their current business model, which does not allow for unlimited Amazon S3 storage for large data sets. They concluded that they need to find a solution that works with their current business model and that can handle large data sets. They also mentioned a future meeting with a DataVerse developer to explore improvements on the DataVerse side.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Proof of Concept and File Upload</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
Maria suggested that someone from their team could attend a meeting to listen and communicate if Chris couldn't. Kristi agreed to loop them in for future meetings and consultations. Maria and Kristi discussed a potential proof of concept and the possibility of uploading a file with versioning. Nicholas advised deleting the current file and doing a fresh upload due to previous interruptions and potential corruption.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Addressing Large File Upload Issues</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
Nicholas discussed the limitations of the current system, particularly the issues with uploading large numbers of files at once. He suggested breaking the data set into smaller chunks for easier upload and to minimize potential problems. Maria and Kristi agreed to this approach, with the understanding that it might not guarantee success. Nicholas also suggested leaving the existing problematic data set untouched, with clear markers indicating it should not be relied upon, while working on a fresh copy.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Dividing Large Dataset for Upload</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
Maria discusses dividing a large dataset into smaller, more manageable chunks for uploading to Dataverse. The dataset consists of video files, human interaction data, and sensor data from robots. Nicholas suggests creating separate datasets for each data type and isolating any problematic data. They plan to test different upload methods, starting with smaller chunks, and then scale up if successful. Maria will consult the students contributing the data to determine appropriate chunk sizes before attempting any uploads. Kristi suggests ways to preserve access to the original data if needed, and Nicholas emphasizes clearly marking any outdated data as stale.
</td>
</tr>
<tr style="height: 20px;"></tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
<strong>Ongoing Projects and Future Collaborations</strong>
</td>
</tr>
<tr>
<td colspan="2" style="font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
Maria, Kristi, Lydia, Christopher, and Nicholas discussed their ongoing projects and future plans. Kristi and Lydia agreed to follow up with Chris and Maria regarding the larger data subcommittee. Christopher emphasized the need for expanding resources and the intention to partner with the team to grow these resources in multiple dimensions. The team also reminisced about past collaborations, with Nicholas recalling a project with Maria from 10 years ago. The conversation ended with the team expressing their appreciation for each other's work and looking forward to future collaborations.
</td>
</tr>
<tr style="height: 32px;"></tr>
<tr>
<td colspan="2" style="font-style: italic;font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top;line-height: 20px;">
AI-generated content may be inaccurate or misleading. Always check for accuracy. </td>
</tr>
<tr style="height: 32px;"></tr>
<tr>
<td>
<a href="https://DesignSafe-ci.zoom.us/user/meeting/summary?meetingId=8%2FqRFjUhS2yzgW5WAx0wHA%3D%3D&summaryId=mss_bWn4jJHmT-OXzNbOFIbEtQ&fileId=ZTGNh67vQ4GTA7MTcg9Qrg" style="border: 1px solid #DFE3E8; padding: 6px 16px;border-radius:6px;color:#131619;text-decoration:none;font-weight: bold;">Edit</a>
</td>
<td style="text-align: right; font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: top">
<table border="0" cellpadding="0" cellspacing="0" align="center"
style="width: 100%;font-size: 13px;color: #39394d;font-family: Arial;">
<tr>
<td align="right"
style="mso-line-height-rule: exactly; line-height: 30px;text-align:right;font-size:16px;color:#39394d;font-family:Arial,Helvetica,sans-serif;vertical-align:top;">
Please rate the accuracy of this summary. </td>
<td align="left"
style="text-align: left; font-size: 16px;color: #39394d;font-family: Arial,Helvetica,sans-serif;vertical-align: middle;">
<a style="text-decoration:none;display: inline-block"
href="https://DesignSafe-ci.zoom.us/meeting/summary/feedback?meetingId=8%2FqRFjUhS2yzgW5WAx0wHA%3D%3D&email=aG9zdDA3QGRlc2lnbnNhZmUtY2kub3Jn&feedback=good"> <img height="30" width="30"
src="https://st2.zoom.us/static/6.3.30118/image/summary/feedback_good.png"
style="width: 30px; height: 30px; border-width: 0; border-style: solid;"/> </a>
<a style="text-decoration:none;display: inline-block" href="https://DesignSafe-ci.zoom.us/meeting/summary/feedback?meetingId=8%2FqRFjUhS2yzgW5WAx0wHA%3D%3D&email=aG9zdDA3QGRlc2lnbnNhZmUtY2kub3Jn&feedback=bad"> <img
height="30" width="30" src="https://st1.zoom.us/static/6.3.30118/image/summary/feedback_bad.png"
style="width: 30px; height: 30px; border-width: 0; border-style: solid;"/> </a>
</td>
</tr>
</table>
</td>
</tr>
</tbody>
</table>
<table>
<tr>
<td style="padding-top: 32px;font-size: 16px;line-height: 20px;">
Best,
</td>
</tr>
<tr>
<td style="font-size: 16px;line-height: 20px;padding-top: 10px;">
Zoom
</td>
</tr>
</table>
</td>
</tr>
<!-- email footer -->
<tr>
<td style="padding-top: 56px;background-color: #FFFFFF;">
<table align="center" border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td>
<a href="https://twitter.com/zoom" style="text-decoration: none;display: inline-block;">
<img alt="Twitter" border="0" height="32" src="https://click.zoom.us/l/84442/2019-12-26/bfs1bv/84442/140021/Social_Twitter_2020.png"
style="width: 32px; height: 32px; border-width: 0px; border-style: solid;"
/>
</a>
</td>
<td style="padding-left:16px; padding-right: 16px;">
<a href="https://www.linkedin.com/company/zoom-video-communications/"
style="text-decoration: none;display: inline-block;">
<img alt="LinkedIn" border="0" height="32" src="https://click.zoom.us/l/84442/2019-12-26/bfs1bs/84442/140023/Social_LinkedIn_2020.png"
style="width: 32px; height: 32px; border-width: 0px; border-style: solid;"
/>
</a>
</td>
<td>
<a href="https://blog.zoom.us/" style="text-decoration: none;display: inline-block;">
<img alt="Blog" border="0" height="32" src="https://click.zoom.us/l/84442/2019-12-26/bfs1bx/84442/140025/Social_Blog_2020.png"
style="width: 32px; height: 32px; border-width: 0px; border-style: solid;"
/>
</a>
</td>
</tr>
</tbody>
</table>
<table align="center" border="0" cellpadding="0" cellspacing="0" width="100%">
<tbody>
<tr>
<td style="font-size:12px; line-height:16px; color:#6E7680; text-align:center;padding-top: 16px;">+1.888.799.9666</td>
</tr>
<tr>
<td style="font-size:12px; line-height:16px; color:#6E7680; text-align:center;padding-top: 10px;">
©2025 Zoom Communications, Inc.
</td>
</tr>
<tr>
<td align="center" style="padding: 16px 0 0;font-size:12px;line-height:16px;color:#6E7680;" valign="top">
Visit <a href= "https://zoom.com" style="color:#6E7680" target="_blank">zoom.com</a>
</td>
</tr>
<tr>
<td align="center" style="padding: 4px 0 32px;font-size:12px;line-height:16px;color:#6E7680;" valign="top">
<a href="https://www.google.com/maps/place/55+Almaden+Blvd,+San+Jose,+CA+95113/@37.3328541,-121.897097,17z/data=!3m1!4b1!4m5!3m4!1s0x808fcca40adf3cb7:0x5a2d33d3593e0a33!8m2!3d37.3328541!4d-121.8949083" style="color:#969AA1; text-decoration: none;" target="_blank">
55 Almaden Blvd<br/>San Jose, CA 95113 </a>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</table>
</td>
</tr>
</table>
</td>
</tr>
</table>
</body>
</html>