Bug #8740
CN resolve service returning 404 for some pids
0%
Description
A user has reported that certain pids (all for metadata objects) return an http 404 status for the resolve service. Here is the complete list that the user tried that didn't resolve:
https://cn.dataone.org/cn/v2/resolve/knb-lter-arc.1343.2
https://cn.dataone.org/cn/v2/resolve/knb-lter-arc.1212.2
https://cn.dataone.org/cn/v2/resolve/knb-lter-arc.1477.2
https://cn.dataone.org/cn/v2/resolve/knb-lter-bnz.442.8
https://cn.dataone.org/cn/v2/resolve/knb-lter-pie.15.5
https://cn.dataone.org/cn/v2/resolve/knb-lter-pie.248.1
https://cn.dataone.org/cn/v2/resolve/knb-lter-sbc.6.13
https://cn.dataone.org/cn/v2/resolve/knb-lter-sbc.15.23
The CNRead.getSystemMetadata() service returns metadata for each of these pids.
History
#1 Updated by Rob Nahf almost 6 years ago
at least for the first one, the object is only accessible from one CN instance: cn-unm-1
compare the three:
* https://cn-unm-1.dataone.org/cn/v2/object/knb-lter-arc.1343.2
* https://cn-orc-1.dataone.org/cn/v2/object/knb-lter-arc.1343.2
* https://cn-ucsb-1.dataone.org/cn/v2/object/knb-lter-arc.1343.2
only the first returns the object
this seems likely to be a Metacat replication issue
#2 Updated by Rob Nahf almost 6 years ago
- Category changed from d1_cn_rest to cn_metacat
