Example analyses for PACA-CA are:
EGAZ00001258006
EGAZ00001258003
EGAZ00001258002
EGAR00001268085
The XMLs can be downloaded via the score client, which means their objectIds do exist, however the link points to an incorrect url. Since all links come from the ES index, this may be an issue in the dcc-repository and how it resolved the metaData (i.e the fileCopy object) when indexing.
Possible places to look are:
https://github.com/icgc-dcc/dcc-repository/blob/develop/dcc-repository-ega/src/main/java/org/icgc/dcc/repository/ega/core/EGAFileProcessor.java#L107
https://github.com/icgc-dcc/dcc-repository/blob/develop/dcc-repository-song/src/main/java/org/icgc/dcc/repository/song/core/SongProcessor.java#L290
Before attempting a deep debug, it may be worth while to just generate a new index and see if the issue irons out, since maybe there was updates after the dcc-repository indexing went offline
Example analyses for PACA-CA are:
EGAZ00001258006
EGAZ00001258003
EGAZ00001258002
EGAR00001268085
The XMLs can be downloaded via the score client, which means their objectIds do exist, however the link points to an incorrect url. Since all links come from the ES index, this may be an issue in the dcc-repository and how it resolved the metaData (i.e the fileCopy object) when indexing.
Possible places to look are:
https://github.com/icgc-dcc/dcc-repository/blob/develop/dcc-repository-ega/src/main/java/org/icgc/dcc/repository/ega/core/EGAFileProcessor.java#L107
https://github.com/icgc-dcc/dcc-repository/blob/develop/dcc-repository-song/src/main/java/org/icgc/dcc/repository/song/core/SongProcessor.java#L290
Before attempting a deep debug, it may be worth while to just generate a new index and see if the issue irons out, since maybe there was updates after the dcc-repository indexing went offline