Now that talk claims have changed, we need some new endpoints so we can see what they are and approve the claims from web2 via the API.
Two new endpoints are needed.
The first is for a user to see which talks someone else has linked them to as a speaker. These are rows in the pending_talk_claims table for this speaker_id with an empty user_approved_at field. We should return the talk name, speaker display name, hypermedia link to an individual URI for this claim (so that we can DELETE it), link to their user account and link to the endpoint for talk approval. This should be at /user/42/talk_claims.
Implement the GET endpoint for the individual URI for this claim.
We also need the equivalent for events where speakers have claimed their talks (the user_approved_at date is set in the pending_talk_claims table) and the organisers can choose to approve or deny the claims. This should be at event/12345/talk_claims and have the same fields as above.
Major
Now that talk claims have changed, we need some new endpoints so we can see what they are and approve the claims from web2 via the API.
Two new endpoints are needed.
The first is for a user to see which talks someone else has linked them to as a speaker. These are rows in the pending_talk_claims table for this speaker_id with an empty user_approved_at field. We should return the talk name, speaker display name, hypermedia link to an individual URI for this claim (so that we can DELETE it), link to their user account and link to the endpoint for talk approval. This should be at /user/42/talk_claims.
Implement the GET endpoint for the individual URI for this claim.
We also need the equivalent for events where speakers have claimed their talks (the user_approved_at date is set in the pending_talk_claims table) and the organisers can choose to approve or deny the claims. This should be at event/12345/talk_claims and have the same fields as above.