> ℹ️ You can use the "Add Field" button to define each field, set its name, interface, and whether it's required.
Similarly create all your required collections
Similarly to Kohainfo, TARA etc.
---
## 4. 🔽 For a Select Field add
1. Add a new field:
- Name: `töö_tüüp`
- Type: `String`
- Interface: `Select Dropdown`
2. In **Options**, define choices:
```json
[
{"text":"Magistritöö","value":"magistritoo"},
{"text":"Doktoritöö","value":"doktoritoo"}
]
```
3. Enable “Allow None” if the field can be empty.
---
## 5. 🗂 Create subfolder for the project
Similarly and drag your newly created collections under it. (See Kohainfo, TARA etc.)
Then navigate to data management->ARHUT settings->Databases (Andmebaasid)(https://db.arh.ut.ee/admin/content/databases) and add a record for the folder to recently added.
Then navigate to related Views (Vaated, https://db.arh.ut.ee/admin/content/views) and a record for each of your newly created records.
## Create collections
Can a project manager do it or should it be done by a dedicated person?
## Associate data with other tables
...
...
@@ -30,4 +97,14 @@ Create policies that allow required access to specific tables that are required
Webapp uses the same user policies as in Directus. Read more [how to make collection/view accessible via Arhut webapp](How-to-Make-Collection-Accessible-in-ARHUT-WebApp).