---
# System prepended metadata

title: OpenTEK future features

---

# OpenTEK future features


### Notifications
schould come in early cuz many other features work only or better with notifications. 
How: A little icon on the application bar (the top bar) /maybe a bell, which is highlighted (color, or other) which contains a list of notifications. Can also be an extra page, which lists all notifications, till a certain point in time (e.g. last 30 days) or a maximum numbers of notifications. e.g. last 50.

### Groups

Group page: List of admins and members, 
   
2 levels of complexity

1. Group as another user. Role in entries makes accessibility management easier. A group is a set of users, so sharing with the group shares it with the set of users (whatever sharing means: e.g. add as collaborator, make visible), ...

 2. More fancy group page with more features: name, descr, avatar, join settings (open, request(includes invitation), invitation only)

More group settings: member visibilty, ...

### Projects
A page that allows to contribute entries to it

How do they fit in between domains and templates. Would greatly benefit from template and code creation, cuz then projects could have custom templates

### Template and code creation

allowing users to create their own observation types and codes...

### Translations 

2 parts
#### UI
- translating the UI and allowing the user to select a ui language
#### Entries
- allowing the translation of entries. They would be separate entries but linked, so one can jump between translations of one entry. Filter and user settings allow users to show only entries in languages relevant for them.
- Translation of entries is crucial in order to have something like the local observation template in different languages, without loosing their relationship 

**More on Translation**
- Allow a felxible translation system. e.g. offer a endpoint (webaddress) to directly create an entry in a given language. If the required template (e.g. local observation, licci tree)  exists they can just go ahead. If not they are promted to a page, where they can help translating that part

- Allow to print forms of templates, which can be distributed and scanned into to a differnt entrytype, which can then be transcribed by other.
- Similar thing for audio files


### Entry comments
Entry comments, requires notifications 
should allow creator some settings if they want comments or not

### A more sophisticated review system
Reviews as comments (maybe not even on the whole entry but on particular aspects), allows the original creator to make the right corrections instead of getting it fixed by a reviewer (which might actually not be able to fix it)

### Entry download
#### Entry download, on each entry as button
Formats:
 1. Txt file
 2. Option:  text, json, csv
#### bulk download
Put it straight next to the search results?

### TK and BC notices and labels
Notices available for visitors
Labels available for actors (users and group)

... Label texts can be made by templates. users creating codes, so they basically just like the cc-licenses that are added to bottom of an entry. 
Data federation with their Hub through APIs would be good.

### Following
follow users or tags

A user setting might define that following must be granted.
eg. 
user setting: followers: open(default) | needs permission
user A sets setting followers to needs permission
user B wants to follow A, sends request
user A sees request and grants
user B gets notification about permission granted / otherwise no notification

### Additional privacy option: followers-only
Only followers of the actor can see the information. 
could also be added to the grant *Collaborators and entry access* section of an entry to finegrain, who can edit (or add) or see the entry.

### Collections 
 1.  Just another entry which allows adding entries, good as access for bulk download. Later interesting, when entries could be live documents, mixing data and analisys.

### Hot link entries (bad name)
Provide links straight to observation creation page. Basically use entry creation pages like google forms, which can be directly access with one link.
More sophisticated: Allow customizable or individual links, for a list of users, with specific settings per user depending on some csv data. e.g. different aspects depening on their gender

### Chat
Chatting with users


### Chatbot
Entry input with a conversational user interface, which can be integrated into telegram, whatsapp. 

### Flexible entries
E.g. collection. With a nicer ui, a mix of text and entrylist aspects can be added in edit mode. Would be great in combination with statistical or visual output view aspects
