Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: include meetings and unscheduled calls signals in flex_index() #183

Closed
Staceyun opened this issue Aug 27, 2021 · 1 comment · Fixed by #185
Closed

Feature request: include meetings and unscheduled calls signals in flex_index() #183

Staceyun opened this issue Aug 27, 2021 · 1 comment · Fixed by #185
Assignees
Labels
enhancement New feature or request

Comments

@Staceyun
Copy link

Is your feature request related to a problem? Please describe.
Meetings and unscheduled calls, apart from emails and IMs, are critical components to understand user collaboration behaviors and are suggested to be added to the flexibility index analysis.

Describe the solution you'd like
Have meetings and unscheduled calls included in the signal extraction. For example, enable users to write, signals = c("email", "IM", "Meetings", "Unscheduled_calls") and extract signals accordingly.

@martinctc
Copy link
Member

Thanks @Staceyun! Meetings and unscheduled calls were initially omitted because of the high likelihood of false positives (e.g. meetings accepted but not attended) compared to actual emails/IMs sent. However, we want to provide options for users so we will be implementing this - targeting for patch version v1.6.2.

@martinctc martinctc added the enhancement New feature or request label Sep 3, 2021
@martinctc martinctc self-assigned this Sep 3, 2021
@martinctc martinctc changed the title Include meetings and unscheduled calls in flex_index analysis Feature request: include meetings and unscheduled calls signals in flex_index() Sep 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants