GMN describe not returning DescribeResponse for IARC MN
The web tester is indicating that mn.describe is not returning a DescribeResponse for the new IARC member node that's in development phase.
Is this a code issue or config? Is IARC using the latest GMN?
the IARC MN baseurl: https://trusty.iarc.uaf.edu/mn/
#1 Updated by Mark Servilla about 8 years ago
- Status changed from New to In Progress
Mea culpa - the following is a response to an entirely different and not asked question; note to self - get more sleep.
-Regarding "Is this a code issue or config?", please explain further what the expected response should be when querying for the node capabilities.-
-According to the V1.2 specification (https://releases.dataone.org/online/api-documentation-v1.2.0/apis/MN_APIs.html#MNCore.getCapabilities) for MNCore.getCapabilities(), the method should return a Types.Node object (presumably in XML format) when using REST end points GET / and GET /node. When querying for IARC's node capabilities using either REST end point (https://trusty.iarc.uaf.edu/mn/v1/ or https://trusty.iarc.uaf.edu/mn/v1/node), the following is returned:-
IARC Data Archive
The International Arctic Research Center (IARC) Data Archive, a long term repository for Arctic data.
CN=James Long A16841,O=Google,C=US,DC=cilogon,DC=org
-Regarding "Is IARC using the latest GMN?", I believe so, but will confirm at a later date.-
#2 Updated by Mark Servilla about 8 years ago
Regarding "Is this a code issue or config?"
Based on the specification for v1.2 MNRead.describe (https://releases.dataone.org/online/api-documentation-v1.2.0/apis/MN_APIs.html#MNRead.describe) and the types.DescribeResponse (https://releases.dataone.org/online/api-documentation-v1.2.0/apis/Types.html#Types.DescribeResponse), the IARC MN is returning what appears to be the correct response:
curl -i -X HEAD https://trusty.iarc.uaf.edu/mn/v1/object/dcx_62a112d0-876d-41fd-b882-499a62210912_0
HTTP/1.1 200 OK
Date: Tue, 25 Nov 2014 18:37:45 GMT
Server: Apache/2.4.7 (Ubuntu)
Last-Modified: Thu, 01 Jan 1970 00:00:00 GMT
curl: (18) transfer closed with 2721 bytes remaining to read
I do note that the example provided in the MNRead.Describe document shows the object format header field as "DataONE-ObjectFormat", where as the Types.DescribeResponse shows the object format header field as "DataONE-formatId"; the later is how GMN responds.
Regarding "Is IARC using the latest GMN?" - yes, running on Ubuntu 14.04.
#3 Updated by Mark Servilla about 8 years ago
GMN does not respond correctly when reporting that an object not found exception occurred when using HEAD for MNRead.describe:
curl -i -X HEAD https://trusty.iarc.uaf.edu/mn/v1/object/blahblahblah
HTTP/1.1 404 NOT FOUND
Date: Tue, 25 Nov 2014 19:30:30 GMT
Server: Apache/2.4.7 (Ubuntu)
The appropriate response should apparently (it is not, however, clear in the v1.2 MN API documentation as to what the exception header field name should be) contain exception header fields:
DataONE-Exception-Description: The specified object does not exist on this node.