>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3572540. --> Reported by: [danchamp](https://www.drupal.org/user/1366502) Related to !45 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>The module currently generates a .ics file for one-time download, and includes an event as a reminder to the user to refresh the download some weeks before the last collection date. This puts the onus on refresh on the user, and also won't pick up any changes to the collection data in the interim.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Use a webcal:// URI for the .ics output, and relabel the link as "Subscribe". Set default refresh period to bi-weekly with configurable override. This will effectively provide a perpetual calendar as long as the user retains the calendar in their client.</p> <p>Maintain the download route to support users who may already have downloaded calendars.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>Explore implications for calendars without direct webcal support, incluidng Google Calendar.</p> <h3 id="summary-ui-changes">User interface changes</h3> <p>Change the download calendar option to "Subscribe".</p>