Changeset View
Changeset View
Standalone View
Standalone View
src/docs/user/userguide/calendar_imports.diviner
@title Calendar User Guide: Importing Events | @title Calendar User Guide: Importing Events | ||||
@group userguide | @group userguide | ||||
Importing events from other calendars. | Importing events from other calendars. | ||||
Overview | Overview | ||||
======== | ======== | ||||
IMPORTANT: Calendar is a prototype application. See | IMPORTANT: Calendar is a prototype application. See | ||||
@{article:User Guide: Prototype Applications}. | @{article:User Guide: Prototype Applications}. | ||||
You can import events into Phabricator to other calendar applications or from | You can import events into Phorge to other calendar applications or from | ||||
`.ics` files. This document will guide you through how to import event data | `.ics` files. This document will guide you through how to import event data | ||||
into Phabricator. | into Phorge. | ||||
When you import events from another application, they can not be edited in | When you import events from another application, they can not be edited in | ||||
Phabricator. Importing events allows you to share events or keep track of | Phorge. Importing events allows you to share events or keep track of | ||||
events from different sources, but does not let you edit events from other | events from different sources, but does not let you edit events from other | ||||
applications in Phabricator. | applications in Phorge. | ||||
Import Policies | Import Policies | ||||
=============== | =============== | ||||
When you import events, you select a visibility policy for the import. By | When you import events, you select a visibility policy for the import. By | ||||
default, imported events are only visible to you (the user importing them). | default, imported events are only visible to you (the user importing them). | ||||
To share imported events with other users, make the import **Visible To** | To share imported events with other users, make the import **Visible To** | ||||
a wider set of users, like "All Users". | a wider set of users, like "All Users". | ||||
Importing `.ics` Files | Importing `.ics` Files | ||||
====================== | ====================== | ||||
`.ics` files contain information about events, usually either about a single | `.ics` files contain information about events, usually either about a single | ||||
event or an entire event calendar. | event or an entire event calendar. | ||||
If you have an event or calendar in `.ics` format, you can import it into | If you have an event or calendar in `.ics` format, you can import it into | ||||
Phabricator in two ways: | Phorge in two ways: | ||||
- Navigate to {nav Calendar > Imports > Import Events > Import .ics File}. | - Navigate to {nav Calendar > Imports > Import Events > Import .ics File}. | ||||
- Drag and drop the file onto a Calendar. | - Drag and drop the file onto a Calendar. | ||||
This will create a copy of the event in Phabricator. | This will create a copy of the event in Phorge. | ||||
If you want to update an imported event later, just repeat this process. The | If you want to update an imported event later, just repeat this process. The | ||||
event will be updated with the latest information. | event will be updated with the latest information. | ||||
Many applications send `.ics` files as email attachments. You can import these | Many applications send `.ics` files as email attachments. You can import these | ||||
into Phabricator. | into Phorge. | ||||
.ics Files: Google Calendar | .ics Files: Google Calendar | ||||
=========================== | =========================== | ||||
In **Google Calendar**, you can generate a `.ics` file for a calendar by | In **Google Calendar**, you can generate a `.ics` file for a calendar by | ||||
clicking the dropdown menu next to the calendar and selecting | clicking the dropdown menu next to the calendar and selecting | ||||
{nav Calendar Settings > Export Calendar > Export this calendar}. | {nav Calendar Settings > Export Calendar > Export this calendar}. | ||||
.ics Files: Calendar.app | .ics Files: Calendar.app | ||||
======================== | ======================== | ||||
In **Calendar.app**, you can generate an `.ics` file for a calendar by | In **Calendar.app**, you can generate an `.ics` file for a calendar by | ||||
selecting the calendar, then selecting {nav File > Export > Export...} and | selecting the calendar, then selecting {nav File > Export > Export...} and | ||||
saving the calendar as a `.ics` file. | saving the calendar as a `.ics` file. | ||||
You can also convert an individual event into an `.ics` file by dragging it | You can also convert an individual event into an `.ics` file by dragging it | ||||
from the calendar to your desktop (or any other folder). | from the calendar to your desktop (or any other folder). | ||||
When you import an event using an `.ics` file, Phabricator can not | When you import an event using an `.ics` file, Phorge can not | ||||
automatically keep the event up to date. You'll need to repeat the process if | automatically keep the event up to date. You'll need to repeat the process if | ||||
there are changes to the event or calendar later, so Phabricator can learn | there are changes to the event or calendar later, so Phorge can learn | ||||
about the updates. | about the updates. | ||||
Importing .ics URIs | Importing .ics URIs | ||||
===================== | ===================== | ||||
If you have a calendar in another application that supports publishing a | If you have a calendar in another application that supports publishing a | ||||
`.ics` URI, you can subscribe to it in Phabricator. This will import the entire | `.ics` URI, you can subscribe to it in Phorge. This will import the entire | ||||
calendar, and can be configured to automatically keep it up to date and in sync | calendar, and can be configured to automatically keep it up to date and in sync | ||||
with the external calendar. | with the external calendar. | ||||
First, find the subscription URI for the calendar you want to import (see | First, find the subscription URI for the calendar you want to import (see | ||||
below for some guidance on popular calendar applications). Then, browse to | below for some guidance on popular calendar applications). Then, browse to | ||||
{nav Calendar > Imports > Import Events > Import .ics URI}. | {nav Calendar > Imports > Import Events > Import .ics URI}. | ||||
When you import a URI, you can choose to enable automatic updates. If you do, | When you import a URI, you can choose to enable automatic updates. If you do, | ||||
Phabricator will periodically update the events it imports from this source. | Phorge will periodically update the events it imports from this source. | ||||
You can stop this later by turning off the automatic updates or disabling | You can stop this later by turning off the automatic updates or disabling | ||||
the import. | the import. | ||||
{icon lock} **Privacy Note**: When you import via URI, the URI often contains | {icon lock} **Privacy Note**: When you import via URI, the URI often contains | ||||
sensitive information (like a username, password, or secret key) which allows | sensitive information (like a username, password, or secret key) which allows | ||||
anyone who knows it to access private details about events. Anyone who can edit | anyone who knows it to access private details about events. Anyone who can edit | ||||
the import will also be able to view and edit the URI, so make sure you don't | the import will also be able to view and edit the URI, so make sure you don't | ||||
grant edit access to users who should not have access to the event details. | grant edit access to users who should not have access to the event details. | ||||
Show All 17 Lines | |||||
.ics URIs: Calendar.app | .ics URIs: Calendar.app | ||||
======================= | ======================= | ||||
**Calendar.app** does not support subscriptions via `.ics` URIs. | **Calendar.app** does not support subscriptions via `.ics` URIs. | ||||
You can export a calendar as an `.ics` file by following the steps above, but | You can export a calendar as an `.ics` file by following the steps above, but | ||||
Phabricator can not automatically keep events imported in this way up to date. | Phorge can not automatically keep events imported in this way up to date. | ||||
Next Steps | Next Steps | ||||
========== | ========== | ||||
Continue by: | Continue by: | ||||
- returning to the @{article:Calendar User Guide}. | - returning to the @{article:Calendar User Guide}. |
Content licensed under Creative Commons Attribution-ShareAlike 4.0 (CC-BY-SA) unless otherwise noted; code licensed under Apache 2.0 or other open source licenses. · CC BY-SA 4.0 · Apache 2.0