ACTIVE Network API Forums
[ Page 1 of 1 ]
ACTIVE Network API
Other Resources
- Terms of Use
- Copyright Policy
- Your Privacy Rights
- Cookie Policy
- Security
- Advertising
- Careers
- © 2017 Active Network, LLC and/or its affiliates and licensors. All rights reserved.
ACTIVE Network, LLC
717 North Harwood Street
Suite 2500
Dallas, TX 75201
717 North Harwood Street
Suite 2500
Dallas, TX 75201
Does AssetId or eventID stay the same if an event repeats? Would the Boston Marathon have the same ID this year as it would next year? Would there be anything different from year to year other than eventDate?
Message edited by ExposedAthlete 3 years ago
active Admin – 14 years ago
Unfortunately the Boston Marathon gets a new assetId and eventId each year. We're working on technology behind the scenes that will merge instances of an event into a single event record so that the assetId persists year over year. But we're a few quarters away from releasing that technology.
ExposedAthlete – 14 years ago
Good to know. Since events are typically yearly, I think I can make do for a while.
RunnersWithWheels – 13 years ago
It's been a year now, what's the status on the merging of recurring events? I'm very interested in such a feature. I noticed that the example asset in the asset details documentation has a collection of "metaEvents" which appear to be previous instances of the event. Does this mean that the parent assetId persists across all instances now?
active Admin – 13 years ago
Yes, it has been a year :) We have an engineering team working on solving this problem right now. It's called clustering, and it creates one uber-record for all event occurrences. Clustering won't be made available until Q2 2012 unfortunately.
The meta-events you noticed are related to an earlier attempt at clustering (using human-beings mechanical turk-style) and have since been abandoned.
RunnersWithWheels – 13 years ago
Understood. Could you suggest any ways to simulate clustering of repeat running events through the API? For instance, removing the date from the event's url and using that as the key for a repeating event? I realize such a hack probably won't work for all running events, but there must be a way of normalizing one more fields from the API that would work for the majority. Thoughts?
Looptivity – 10 years ago
In your API documentation (for both searching v2 and details) - the data format for recurring events are not defined. Can anyone please help us out in this?