We have to work out how to do change notifications and usage tracking when data is requested via a redirect.

We could:

1. resolve redirects before recording usage. That makes puring easy, but when the redirect changes (or is undone), we'd need to find and update all tracking records that use the redirect. For this, we have to put the requested and the effective entity ID into the tracking table. Needs a schema change on all clients.
2. do a reverse lookup for redirects when processing change notifications. That adds some overhead, but should not be horrible.

We have the same problem again with managing subscriptions; we should probably resolve and subscribe to the redirect as well as the target. When the redirect is undone, the client would remain subscribed to the original target, but that should not cause any issues.

Version: master
Severity: normal
Whiteboard: u=dev c=backend p=0