Open bilalshaikh42 opened 2 years ago
Looking at this more closely, I realized that a request to https://models.physiomeproject.org/exposure/e340f005288ec6bd49535cf792769dd0
redirects to https://models.physiomeproject.org/exposure/e340f005288ec6bd49535cf792769dd0/document_view
rather than https://models.physiomeproject.org/exposure/e340f005288ec6bd49535cf792769dd0/exposure_info
like the other exposures do.
That does explain the discrepancy in the response.
Is there a reason this exposure does not redirect to the expected exposure_info endpoint?
Yes, the reason being that the exposure was created with a textual document specified for the root exposure object, such that a view was generated for it, rather than triggering the redirection to the only model file being exposed as an exposure file for that exposure.
This tends to be an issue for earlier exposures as that was how exposures were created.
Hello,
I am experiencing a strange issue for the following exposure:
https://models.physiomeproject.org/exposure/e340f005288ec6bd49535cf792769dd0
When visiting the URL by browser (HTML) I see the navigation has a link called "Modeling Activation and Desensitisation of G-Protein Coupled Receptors Provides Insight into Ligand Efficacy" that points to a CellML file.
Usually, this is represented in the JSON as a link with the prompt "Modeling Activation and Desensitisation of G-Protein Coupled Receptors Provides Insight into Ligand Efficacy" and a HREF pointing to the view for the particular CellML file.
However, requesting this exposure with a JSON content type gives the following, which is unlike any other response that I have encountered:
Is this intended behavior?