kandarpksk
commented
2 weeks ago FWIW, there is a better message we show when the dataset ID entered is numeric, but does not exist. For example, https://cryoetdataportal.czscience.com/datasets/10500 shows:
404 Dataset with ID 10500 not found
Maybe there's potential to keep them consistent for such cases.
Alongside design updates for prefixed IDs in the web GUI, let's also improve the error page that users might see if they use the prefixed ID in URLs. For example: https://cryoetdataportal.czscience.com/datasets/DS-10083 shows:
400 ID is not definedLet's use this issue to discuss the phrasing async. I'm thinking there could be dedicated messages when:
a user enters an ID that's invalid, and not a prefixed ID
There is no dataset with ID '20103'.a user enters an prefixed ID for a different entity, say /datasets/TS-10101
There is no dataset with ID 'TS-10101'. Enter just the numeric part of any dataset ID in the link, for example '.../datasets/10000'.a user enters a prefixed ID for the same entity, say /datasets/DS-10101
Enter just the numeric part of any dataset ID in the link, for example '.../datasets/10101'.(Idea: could we have the corrected link here to click?)(These are first drafts for the message part, I don't know how best to show the HTTP 400 error code)
cc: @junxini @kev-zunshiwang @dgmccart