gbif
Metadata failed to load error
This was originally reported by @sformel-usgs
This resource: https://ipt-obis.gbif.us/resource?r=atn_137491_spotted-seal_trajectory_20180418-20180526
Gives the following error: Metadata file version #1.0 for resource atn_137491_spotted-seal_trajectory_20180418-20180526 failed to load
I am not sure why and I don't know how to fix it.
Thank you, Marie.
The dataset has never been published, has it? https://ipt-obis.gbif.us/resource/preview?r=atn_137491_spotted-seal_trajectory_20180418-20180526
Yes. There's no resource view page - resource has yet to be published.
Correct. This dataset has been made public but not published.
Looping in the appropriate @sformel. Steve, does this make sense? Why would OBIS still harvest it?
See https://obis.org/dataset/f8f2481a-c3c8-41f3-bdaa-c52615980b5e
I'm not sure why or how, because it doesn't show up on the RSS feed as far as I can tell. @pieterprovoost returns from vacation next week and I will alert him of this.
However, looking at the IPT logs (https://ipt-obis.gbif.us/admin/logs.do) if seems like there might be a few different things happening here:
This dataset has not been touched recently to my knowledge:
ERROR 18-Aug-2025 09:17:37 [org.gbif.ipt.action.portal.ResourceAction] - Metadata file version #2.0 for resource tpwd_harc_texasmatagordabay_bagseine_20150130 failed to load
These don't seem good
ERROR 14-Aug-2025 13:06:33 [org.gbif.utils.file.CompressionUtil] - More than one root directory at /mnt/auto/iptdata/ipt-data-us-obis/tmp/dir-128973274452036271 WARN 18-Aug-2025 21:34:46 [org.gbif.ipt.action.portal.ResourceFileAction] - Data dir file not found
We were working to publish programmatically through the IPT using the method developed by OTN, which essentially emulates clicks. Is it possible we broke our IPT?
the code we are putting up just interfaces with the web forms automatically. This looks like a misconfiguration of the backend of the IPT - a missing or duplicated directory entry on the hosted IPT. not something you should be able to do with a script like mine. Hopeful it's a hiccup that's easily resolved.
Any other ideas why a dataset that has been made public but not published has made it over to OBIS??
I do see a bunch of java.io.FileNotFoundException in the ipt-obis logs. Also some [org.gbif.ipt.action.LoginAction] - CSRF login token wrong! A potential malicious attack.
@sformel Maybe a reset of the IPT is needed. There's another example of the IPT having a dataset registered, published, public, and connected to the OBIS network, but it's not making it over there. https://ipt-obis.gbif.us/resource?r=mlpa_kelp_forest_monitoring Maybe there is a connection?
@MathewBiddle If the dataset made it over to OBIS then it must have been visible in the RSS feed at some point. Regarding https://ipt-obis.gbif.us/resource?r=mlpa_kelp_forest_monitoring, that is an unrelated processing issue on our end.
