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

Missing Past Webinar/Meeting Instances #5

Open
kekoav opened this issue Oct 7, 2020 · 0 comments
Open

Missing Past Webinar/Meeting Instances #5

kekoav opened this issue Oct 7, 2020 · 0 comments

Comments

@kekoav
Copy link
Contributor

kekoav commented Oct 7, 2020

The tap only pulls information on the latest webinar instance, excluding past instances of meetings/webinars.

A webinar, like a meeting can be reused. Each use creates an instance with a UUID. There are several Zoom API calls that take either an instance UUID, or a meeting/webinar ID. If a specific instance is not requested, the latest instance is returned.

Expected Zoom API Usage

The tap should query the pastwebinars and pastmeetings endpoints and wherever possible utilize the webinar/meeting UUID of the instance, instead of just the webinar ID when making other API calls. In some cases, there is a separate endpoint that should be used instead.

Meetings

Webinars

Risks

  1. It should be tested that the endpoints labeled "past_meetings" are suitable for active meetings, or we will need to add a caveat that a meeting must have ended in order for it to be reported. I suspect despite the naming of these endpoints, the current meeting UUID can be queried, but this should be verified.
  2. This will include a potentially large amount of historical data. For my purposes this is exactly what I want, though this may make it more important to add incremental key-based extraction and potentially a historical start date to restrict the a amount of history returned.
lfpll pushed a commit to lfpll/tap-zoom that referenced this issue Dec 13, 2022
* Build the merge-into-bq job with a dedicated GHA workflow

* Remove the merge-into-bq build from the Development workflow

* Add label to the merge-into-bq Docker image to cause a rebuild

* Hack GHA workflow to push the merge-into-bq job image tagged with `latest`

* Publish production docker images to the analytics-warehouse-production project

* Change production DWH project and dataset for the masterdata layer
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant