A Claim is a concept which contain an array of messages in addition to other attributes.  This array of messages is a subset of the `/messages` endpoint response based on how many were claimed.  The Messages collection only cares about `/messages` and not the Claim endpoint.  However, deleting a message in a claim still utilizes calls like `DELETE /messages/<message id>`, which is why the messages need the Messages collection.

The alternative would be some logic in the Messages collection that either queries `/messages` or /claim/<claim_id> to reload the messages.  This seemed like it would complicate the Messages collection when it could be isolated in the Claim.  I guess another alternative would be having a different Collection/Model for this case.

Open to ideas if this isn't kosher.