Open mwalzer opened 2 years ago
Since the URL link is formed such: https://www.proteomicsdb.org/use/?usi=mzspec:PXD015890:18May18_Olson_WT2.raw%20(F001551).mzid_18May18_Olson_WT2.raw_(F001551).MGF:index:6913:AEAEAQAEELSFPR/2&usi_origin=pride my suspicion is that either the white-space character or the brackets in the filename break it - is there any mitigation strategies outlined in the USI docs for such scenarios? Might be worth highlighting.
This may be due to some troubles at the PRIDE USI server. Separate from the above problem, and perhaps related to the above problem, I notice that PRIDE behaves weirdly on this example that we published in the USI paper itself:
http://wwwdev.ebi.ac.uk/pride/proxi/archive/v0.1/spectra?resultType=full&usi=mzspec%3APXD000966%3ACPTAC_CompRef_00_iTRAQ_05_2Feb12_Cougar_11-10-09.mzML%3Ascan%3A12298%3A[iTRAQ4plex]-LHFFM[Oxidation]PGFAPLTSR%2F3
yields:
Whitelabel Error Page
This application has no explicit mapping for /error, so you are seeing this as a fallback.
Mon Mar 21 04:55:23 GMT 2022
There was an unexpected error (type=Internal Server Error, status=500).
Unable to execute HTTP request: Connect to s3.embassy.ebi.ac.uk:443 [s3.embassy.ebi.ac.uk/193.62.54.252] failed: Connection refused (Connection refused)
This is our example 2 here:
http://proteomecentral.proteomexchange.org/usi/
This did work when we published the paper. Maybe this is an issue for @ypriverol ?
At least the proteomicsdb.org example in the Methods section of https://doi.org/10.1038/s41592-021-01184-6 is not working (both PDF and online version). See the screenshot below.