It would be cool to have multiple databases, all of which (except one) would not be modifiable using the UI.
This would be cool because it would enable database-generation. For example, let's suppose you have an ICS calendar on nextcloud, and you want to transform that calendar into a schedule.
You could create a very custom script that, given an ICS calendar, creates a file in the same format as db.json.
Being in a totally different file would allow for strong isolation and no conflicts whatsoever. ie: you are free to change this file however you want, without horrible consequences.
Challenges:
what eventID and audioID should those have? is adding a prefix fine?
can an "additional" time mention an audio from other DBs?
the UI should be aware of this. Events such as those should be displayed in calendar, maybe even with details, but should not be modifiable.
## Is it a bug or a feature request?
Feature request
## Describe what happens
Right now there is one, read-write, database
### what should happen, instead?
It would be cool to have multiple databases, all of which (except one) would not be modifiable using the UI.
This would be cool because it would enable database-generation. For example, let's suppose you have an ICS calendar on nextcloud, and you want to transform that calendar into a schedule.
You could create a very custom script that, given an ICS calendar, creates a file in the same format as `db.json`.
Being in a totally different file would allow for strong isolation and no conflicts whatsoever. ie: you are free to change this file however you want, without horrible consequences.
Challenges:
- what eventID and audioID should those have? is adding a prefix fine?
- can an "additional" time mention an audio from other DBs?
- the UI should be aware of this. Events such as those should be displayed in calendar, maybe even with details, but should not be modifiable.
Is it a bug or a feature request?
Feature request
Describe what happens
Right now there is one, read-write, database
what should happen, instead?
It would be cool to have multiple databases, all of which (except one) would not be modifiable using the UI.
This would be cool because it would enable database-generation. For example, let's suppose you have an ICS calendar on nextcloud, and you want to transform that calendar into a schedule.
You could create a very custom script that, given an ICS calendar, creates a file in the same format as
db.json.Being in a totally different file would allow for strong isolation and no conflicts whatsoever. ie: you are free to change this file however you want, without horrible consequences.
Challenges: