|
5 | 5 | - **Checkbox**: this property is represented by `true/false` in the underlying markdown ; |
6 | 6 | - **Date**: this property accepts dates. The default format is `yyyy-MM-dd`, but it can be changed in the plugin or database settings under `editing engine section > Date format` ; |
7 | 7 | - **Time**: this property accepts time. The default format is `yyyy-MM-dd HH:mm:ss`, but it can be changed in the plugin or database settings under `editing engine section > Datetime format` ; |
8 | | -- **Select**: this property accepts from a list of options you define. Colors are attributed automatically, though you can change them in the column settings. Furthermore, when removing the select option in the setting, it is also removed from the note's metadata ; |
| 8 | +- **Select**: this property accepts from a list of options you define. Colors are attributed automatically, though you can change them in the column settings. Furthermore, you can edit or remove the options from the column settings and the changes will be persisted on the notes' metadata ; |
9 | 9 | - **Tags**: similar to the previous property, but instead of only selecting one option, you can select multiples options per cell ; |
10 | 10 | - **Formulas**: property that accepts js code to return dynamic values in function of your code. See the [Formulas](/obsidian-db-folder/features/Formulas/) section for more details. |
11 | 11 | - **Image**: you can embed images in the `text` property in this format `![[image]]`. Make sure to enable `media links` in the column settings and adjust the dimensions too ; |
|
17 | 17 |
|
18 | 18 | > You can change from one property type to another, and if the format is right, it will be recognized by the plugin. |
19 | 19 |
|
| 20 | +## Column ID |
| 21 | + |
| 22 | +Where you create a column, the `column name` (name displayed in the database) is the same as the `column id` (the metadata persisted in your notes). You can change the column ID in the column settings. This ID is used by the **filters**, so keep that in mind when choosing what column to filter. |
| 23 | + |
| 24 | +<video width="670" controls> |
| 25 | + <source src="https://user-images.githubusercontent.com/38974541/197635378-256e2468-bb90-477f-8760-393f792777d6.mov" type="video/mp4"> |
| 26 | +</video> |
| 27 | + |
20 | 28 | ## YAML & Dataview Inline Fields |
21 | 29 |
|
22 | | -The plugin works with YAML and dataview inline fields, but by default, it looks for metadata in YAML. To make it work with inline fields, you have two options : |
| 30 | +The plugin works with YAML and dataview inline fields, but looks for metadata in YAML by default. To make it work with inline fields, you have two options : |
23 | 31 |
|
24 | | -- You can toggle `enable inline field as default` in database or plugin global settings, and you can choose between putting the inline fields at the top or at the bottom of the file ; |
25 | | -- Or you can change it in the column's settings to use it with one property only. Keep in mind that this change will not convert the underlying YAML to an inline format, it was meant to work with metadata already formatted as inline. |
| 32 | +- You can toggle `enable inline field as default` in database or plugin global settings, and you can choose between putting the inline fields at the top or the bottom of the file ; |
| 33 | +- Or you can change it in the column's settings to use it with one property only. This change will not convert the underlying YAML to an inline format until you edit one of the cells in the column. |
26 | 34 |
|
27 | 35 | If there is no metadata in your notes, it will be created when you fill the corresponding cell in the database. |
28 | 36 |
|
| 37 | +<video width="670" controls> |
| 38 | + <source src="https://user-images.githubusercontent.com/38974541/197635449-507ea33b-5213-4976-a7a2-bbb4e7b888b1.mov" type="video/mp4"> |
| 39 | +</video> |
| 40 | + |
| 41 | +## Nested Metadata |
| 42 | + |
| 43 | +You can add nested metadata by writing something like `metadata1.metadata2` in the column setting under `Behavior > column id`, which will render nested metadata separated by one space : |
| 44 | + |
| 45 | +``` |
| 46 | +--- |
| 47 | +metadata1: |
| 48 | + metadata2: something |
| 49 | +--- |
| 50 | +``` |
| 51 | + |
| 52 | +If you want to add existing nested metadata, you'll have to abide by the format described above. |
| 53 | + |
| 54 | +<video width="670" controls> |
| 55 | + <source src="https://user-images.githubusercontent.com/38974541/197635608-8c638ab0-1551-498f-b859-a9ab58eff34b.mov" type="video/mp4"> |
| 56 | +</video> |
| 57 | + |
29 | 58 | ## Appearance |
30 | 59 |
|
31 | | -You can enable text wrapping and you can change the text alignment between `right-aligned`, `centered`, `left-aligned`, and `justified` from the column settings of the **text**, **number**, and **formula** properties. |
| 60 | +You can enable text wrapping and you can change the text alignment between `right-aligned`, `centered`, `left-aligned`, and `justified` from the column settings of the **text**, **number**, and **formula** properties. |
| 61 | + |
| 62 | +<video width="670" controls> |
| 63 | + <source src="https://user-images.githubusercontent.com/38974541/197635327-31c273a1-6cb5-4283-a9a5-dddbdcc6b831.mov" type="video/mp4"> |
| 64 | +</video> |
0 commit comments