You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently zat relies on the meeting name as the file name but that's typically not always desirable since the meeting might be verbose, contain special chars (spaces, parenthesis, etc) while for storage, there's typically a well defined name pattern that aims to be consistent.
It would be great if the configuration would allow this per meeting declaration:
- name: This is a big meeting
google: abc
zoom: 123
file: wed-meeting.
Potentially the name itself can serve as the template since the zoom matching happens based on the meeting ID. Extra points for allowing some kind of (basic) templating in the option:
- name: {YYYY-mm-dd}_wed-meeting
google: ...
The text was updated successfully, but these errors were encountered:
Currently zat relies on the meeting name as the file name but that's typically not always desirable since the meeting might be verbose, contain special chars (spaces, parenthesis, etc) while for storage, there's typically a well defined name pattern that aims to be consistent.
It would be great if the configuration would allow this per meeting declaration:
Potentially the name itself can serve as the template since the zoom matching happens based on the meeting ID. Extra points for allowing some kind of (basic) templating in the option:
The text was updated successfully, but these errors were encountered: