Lock Location Level URL reference links

[zack-rma]

I'm currently implementing support for locks in the API. As discussed at the last developer meeting, location levels associated with locks will not be returned in their entirety, rather, as a reference. It has been suggested to include a link containing the API path to access the associated location level data. This could make it much easier for the client to retrieve the location level data referenced by a lock without manually building the request.

For the location endpoint, all information needed to identify a record is included in the GET URL, including the identifying information tied to locks. As a result, it may be possible to provide the link URL as the only reference to the location level and parse the link for the identifying data we need. Alternatively, the link can be provided as a supplement to location name, office id, and any other necessary identifying information.

I am unsure if there are existing implementations or standards for this sort of use case, but I thought I'd get feedback to clarify the best way to move forward.

[zack-rma]

@MikeNeilson