---
description: >-
  There are a lot of other properties that can be assigned to events. These are
  not necessary. Instead, they are optional and increase the functionality of
  your calendar!
---

# Optional Event Info

![](https://1857871955-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MdYYYaX6u6mOCBpjLIC%2F-Mi2ABgcWLyNYWB_g4pO%2F-Mi2L-px7lIa0R0TlEU1%2FScreen%20Shot%202021-08-26%20at%2012.42.44%20PM.png?alt=media\&token=6dd70a4a-019c-4083-ad3f-99a0c161e43e)

## Event Color List

&#x20;Color List `(list of strings)`

It will be vital that you format this list. Unlike an event title's potentially containing error causing commas, color's almost always have a comma unless you force Hex colors. But why be fussy, simply `:format as text` this list and replace the comma delimiter with a tilde  `~`and problem solved!

**Please read the notes in the image above**

![](https://1857871955-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MdYYYaX6u6mOCBpjLIC%2F-Mi2MCDtKj3e6-d1DDlc%2F-Mi2MoC68_pKca_nkaqS%2FScreen%20Shot%202021-08-26%20at%2012.50.50%20PM.png?alt=media\&token=8a171530-81fa-425a-950f-f614fc2cfa67)

## Event Resource List

![](https://1857871955-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MdYYYaX6u6mOCBpjLIC%2F-Mdcj2H2DRyiKyjg3hI4%2F-Mddrpvp9m8xLGHjAsnM%2FScreen%20Shot%202021-07-02%20at%208.57.16%20PM.png?alt=media\&token=bdf7e655-acfb-4c6e-bb2a-bd9755aa90ff)

* You may want to start using the calendar for resources or scheduling purposes. Maybe you want to schedule a room or specific person or piece of equipment.&#x20;
* When you create an event, you will save a resource to that event similarly to how you would save a title or start/end time.&#x20;
* To use resources, you must include a list of resources and tell the calendar to use a resource view
* Using resources allows you to separate visible events by the assigned resource. In contrast, without using resources, all events are clumped together by day and separated by time. When you have the potential for several resources being scheduled or if resource event times would overlap without using a 'Resource View', you should assign a resource to the event an include the list here.
* You _**MUST**_ include a list of resources if you want to use resources.&#x20;
  * This **will** come from the event entry in the database
  * The list _**must not contain commas**_ in the Resource Names unless you use the different delimiter. IMPORTANT!

## Event Location List

## Event Summary List

## Event Property 1 List

## Event Property 2 List

* These 4 input fields all follow the same logic
  *   You typically include some piece of related info.

      * &#x20;this is most likely a value from the events entry in the database or some other entry related  to the event
      * note: location is great to save a location, but really can be used to hold any kind of info you want.&#x20;

      **How to use identifiers**

      Once you have figured out your identifiers, you'll use them in the set of inputs on the next page.&#x20;

## **Event Identifier `(list of strings)`**

* This would be a value saved to the event when the event is created/modified.&#x20;
  * _**This**_ _**is not a**_ _**simple list of the types of identifiers possible.**_&#x20;
* A use case may include scheduling and wanting the ability for the user to assign colors to event types on the fly.&#x20;
  *   following the example above perhaps there are these types of events:

      * scheduled to occur
      * occurred on time
      * occurred but began late
      * event cancelled
      * event no call no show


* To ensure your calendar uses this logic to color events and nothing else, be sure to check the box from the image below.&#x20;
* This list should not take any formatting. That means, _**do not**_ include commas in your identifiers.

{% content-ref url="broken-reference" %}
[Broken link](broken-reference)
{% endcontent-ref %}

{% content-ref url="broken-reference" %}
[Broken link](broken-reference)
{% endcontent-ref %}

{% content-ref url="broken-reference" %}
[Broken link](broken-reference)
{% endcontent-ref %}

{% content-ref url="broken-reference" %}
[Broken link](broken-reference)
{% endcontent-ref %}

{% content-ref url="broken-reference" %}
[Broken link](broken-reference)
{% endcontent-ref %}

