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.

Sign up for GitHub

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

adding apostrophe, tweet to Tweet #74

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

adding apostrophe, tweet to Tweet #74

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/data/time.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@

Every Event results from an action that was taken at some point in time. This is considered to be the time that the Event 'occurred'. Examples of the 'occurred' field:

- The time the tweet was published.
- The time the Tweet was published.
- The time the edit was made on Wikipedia.
- The time that the Reddit comment was made.
- The time that the blog post was published.
Expand All @@ -23,7 +23,7 @@ These three dates are represented as the `occurred_at`, `timestamp` and `updated

### Using the Query API over time

The Query API is updated continuously, usually within one hour of current activity. It has two views (as documented in the [Query API page](../service/query-api)): `collected` and `observed`. Once a days worth of data is collected and made available via its `collected` view, that selection of Events won't change (although Events themselves may be edited for compliance reasons).
The Query API is updated continuously, usually within one hour of current activity. It has two views (as documented in the [Query API page](../service/query-api)): `collected` and `observed`. Once a day's worth of data is collected and made available via its `collected` view, that selection of Events won't change (although Events themselves may be edited for compliance reasons).

The Query API also contains an `occurred` view. This returns Events based on the date they **occurred** on. Because Events can be collected some time after they occurred, the data in this view can change.

Expand Down