<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Preserving Dynamic Geospatial Data and Interactive Web Scholarship in Discussions</title>
    <link>https://www.googleforeducommunity.com/t5/Discussions/Preserving-Dynamic-Geospatial-Data-and-Interactive-Web/m-p/294221#M173</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Academic libraries excel at cataloging and preserving static digital outputs such as PDFs, dataset spreadsheets, and open-access monographs. However, an increasing volume of modern digital scholarship is published as complex, interactive web projects—such as interactive StoryMaps, multi-layered ArcGIS dashboards, and dynamically rendered 3D spatial models. When hosting servers sunset, software dependencies change, or proprietary APIs deprecate, these rich scholarly works often break down, creating severe digital preservation vulnerabilities for institutions and early-career researchers alike.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;When consulting with faculty on multi-layered digital scholarship or spatial humanities projects, what workflows, emulation platforms, or repository containerization practices (such as Docker or Webrecorder) have your teams implemented to guarantee that interactive web projects remain accessible and functional for decades to come?&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 23 Sep 2026 13:09:22 GMT</pubDate>
    <dc:creator>TracyAntonioli</dc:creator>
    <dc:date>2026-09-23T13:09:22Z</dc:date>
    <item>
      <title>Preserving Dynamic Geospatial Data and Interactive Web Scholarship</title>
      <link>https://www.googleforeducommunity.com/t5/Discussions/Preserving-Dynamic-Geospatial-Data-and-Interactive-Web/m-p/294221#M173</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Academic libraries excel at cataloging and preserving static digital outputs such as PDFs, dataset spreadsheets, and open-access monographs. However, an increasing volume of modern digital scholarship is published as complex, interactive web projects—such as interactive StoryMaps, multi-layered ArcGIS dashboards, and dynamically rendered 3D spatial models. When hosting servers sunset, software dependencies change, or proprietary APIs deprecate, these rich scholarly works often break down, creating severe digital preservation vulnerabilities for institutions and early-career researchers alike.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;When consulting with faculty on multi-layered digital scholarship or spatial humanities projects, what workflows, emulation platforms, or repository containerization practices (such as Docker or Webrecorder) have your teams implemented to guarantee that interactive web projects remain accessible and functional for decades to come?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Sep 2026 13:09:22 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Discussions/Preserving-Dynamic-Geospatial-Data-and-Interactive-Web/m-p/294221#M173</guid>
      <dc:creator>TracyAntonioli</dc:creator>
      <dc:date>2026-09-23T13:09:22Z</dc:date>
    </item>
  </channel>
</rss>

