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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Out-of-office: Expose data via OCP/OCS APIs #40650

Closed
Tracked by #40397
ChristophWurst opened this issue Sep 27, 2023 · 2 comments 路 Fixed by #40653
Closed
Tracked by #40397

Out-of-office: Expose data via OCP/OCS APIs #40650

ChristophWurst opened this issue Sep 27, 2023 · 2 comments 路 Fixed by #40653

Comments

@ChristophWurst
Copy link
Member

How to use GitHub

  • Please use the 馃憤 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.

Users can enter OOO info via #40616. Apps want access to this data and react when a users goes to or returns from OOO.

Describe the solution you'd like

Add an OCP API that exposes the OOO information. Add events for the start and end of OOO.

Describe alternatives you've considered

N/a

Additional context

N/a

@ChristophWurst ChristophWurst added this to the Nextcloud 28 milestone Sep 27, 2023
@ChristophWurst ChristophWurst self-assigned this Sep 27, 2023
@ChristophWurst ChristophWurst changed the title Out-of-office: Expose data via OCP API Out-of-office: Expose data via OCP API Sep 27, 2023
@ChristophWurst
Copy link
Member Author

ChristophWurst commented Sep 27, 2023

Brainstorming the requirements

DAV

  • Get called when OOO is scheduled -> OCP event
  • Get called when OOO is changed -> OCP event

Mail

  • Get called when the OOO starts -> OCP event
  • Get called when the OOO ends -> OCP event
  • Get OOO message of a user -> OCP API or OCS endpoint

Talk

  • Get OOO message of a user -> OCP API or OCS endpoint

@ChristophWurst ChristophWurst changed the title Out-of-office: Expose data via OCP API Out-of-office: Expose data via OCP/OCS APIs Sep 27, 2023
@nickvergessen
Copy link
Member

For Talk an OCS endpoint would be preferred. This way also mobile clients can show the information.

If the user status is uniquely identifyable (hardcoded message_id like the in_call), we can use that as an indicator to see if we should contact the OOO endpoint to load more info. The user status is returned on the conversation list, but I guess we wouldn't want to load even more data for all users every 30 seconds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging a pull request may close this issue.

3 participants