Open chung88 opened 7 years ago
@chung88 , what do you think should be a correct access url for this record? can you give more details about this issue?
LINCS Dataset ID LDS-1354, is from NeuroLINCS, as described in the BioCaddie landing page. On the accessURL: http://lincsportal.ccs.miami.edu/dcic/api/download?path=LINCS_Data/HMS_LINCS&file=LDS-1354.tar.gz (download 1)
I see HMS LINCS, which is Harvard.
The correct access URL to download the package should be http://lincsportal.ccs.miami.edu/dcic/api/download?path=LINCS_Data/NeuroLINCS&file=LDS-1354.tar.gz (download 2)
The file size difference between [download 1] 0 GB and [download 2] 138 MB. The first download puts an empty file in the user download directory.
Thank you for the information, i have updated the code for LINCS and the new index will be pushed to production before next week.
From: Caty Chung [notifications@github.com] Sent: Wednesday, August 02, 2017 10:15 AM To: biocaddie/prototype_issues Cc: Yueling Li; Comment Subject: Re: [biocaddie/prototype_issues] [LINCS] accessURL (#279)
LINCS Dataset ID LDS-1354, is from NeuroLINCS, as described in the BioCaddie landing page. On the accessURL: http://lincsportal.ccs.miami.edu/dcic/api/download?path=LINCS_Data/HMS_LINCS&file=LDS-1354.tar.gz (download 1)
I see HMS LINCS, which is Harvard.
The correct access URL to download the package should be http://lincsportal.ccs.miami.edu/dcic/api/download?path=LINCS_Data/NeuroLINCS&file=LDS-1354.tar.gz (download 2)
The file size difference between [download 1] 0 GB and [download 2] 138 MB. The first download puts an empty file in the user download directory.
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/biocaddie/prototype_issues/issues/279#issuecomment-319738454, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALPhs2mWRoesBFc9I2nh0Jk8ggb3IM2Nks5sUK7BgaJpZM4Oq-GS.
The wrong URL is still visible today. When do we expect the corrected version?
The transformation file has been updated to the new URL and re-indexed by Burak, not sure what next step will be.
From: Ian Fore [notifications@github.com] Sent: Friday, September 15, 2017 9:49 AM To: biocaddie/prototype_issues Cc: Yueling Li; Comment Subject: Re: [biocaddie/prototype_issues] [LINCS] accessURL (#279)
The wrong URL is still visible today. When do we expect the corrected version?
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/biocaddie/prototype_issues/issues/279#issuecomment-329837216, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALPhs6tDYIaD0kBv8zLjv5gNHMgXk9cCks5siqqRgaJpZM4Oq-GS.
Is this just deployed on development?
Ian, LINCS uses identifiers.orghttp://identifiers.org PURL, where did you get the URL? Caty
On Sep 18, 2017, at 10:44 AM, yul129 notifications@github.com<mailto:notifications@github.com> wrote:
The transformation file has been updated to the new URL and re-indexed by Burak, not sure what next step will be.
From: Ian Fore [notifications@github.commailto:notifications@github.com] Sent: Friday, September 15, 2017 9:49 AM To: biocaddie/prototype_issues Cc: Yueling Li; Comment Subject: Re: [biocaddie/prototype_issues] [LINCS] accessURL (#279)
The wrong URL is still visible today. When do we expect the corrected version?
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/biocaddie/prototype_issues/issues/279#issuecomment-329837216, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALPhs6tDYIaD0kBv8zLjv5gNHMgXk9cCks5siqqRgaJpZM4Oq-GS.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbiocaddie%2Fprototype_issues%2Fissues%2F279%23issuecomment-330299524&data=02%7C01%7Cc.chung%40med.miami.edu%7Cedff10d18da344c26cdb08d4febcedbc%7C2a144b72f23942d48c0e6f0f17c48e33%7C0%7C0%7C636413534782128980&sdata=umFzh2QC%2FUChOGmyz%2BaQxGASpKqF642u408Y5j1igP4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADa5NhcLh67pDxaSugkkXVSSw2EQ-Pf-ks5sjqvxgaJpZM4Oq-GS&data=02%7C01%7Cc.chung%40med.miami.edu%7Cedff10d18da344c26cdb08d4febcedbc%7C2a144b72f23942d48c0e6f0f17c48e33%7C0%7C0%7C636413534782128980&sdata=aBZD%2FJHPGf78f65%2FdURJmApMZWHoXL4xsVLSv8Fbw10%3D&reserved=0.
LINCS is reindexed and available at
http://biocaddie.scicrunch.io/lincs_20170918/dataset
Burak On 09/18/2017 10:44 AM, yul129 wrote:
The transformation file has been updated to the new URL and re-indexed by Burak, not sure what next step will be.
From: Ian Fore [notifications@github.com] Sent: Friday, September 15, 2017 9:49 AM To: biocaddie/prototype_issues Cc: Yueling Li; Comment Subject: Re: [biocaddie/prototype_issues] [LINCS] accessURL (#279)
The wrong URL is still visible today. When do we expect the corrected version?
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/biocaddie/prototype_issues/issues/279#issuecomment-329837216, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALPhs6tDYIaD0kBv8zLjv5gNHMgXk9cCks5siqqRgaJpZM4Oq-GS.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/biocaddie/prototype_issues/issues/279#issuecomment-330299524, or mute the thread https://github.com/notifications/unsubscribe-auth/AHLczDB35YIraeR1A9keynuwjTPZeB-Xks5sjqvwgaJpZM4Oq-GS.
-- I. Burak Ozyurt PhD Project Scientist University of California, San Diego 9500 Gilman Drive, M/C 0608 La Jolla, CA 92093-0608
Caty - I was referring to the URL shown on the page you referenced (https://datamed.org/display-item.php?repository=0004&id=5833650a5152c608d984a415&query= ) is still a HMS_LINCS url and not the NeuroLINCS link that you had indicated was the correct one. The file downloaded is still zero bytes.
Though the dialog in this thread suggest this has been fixed the original problem you mentioned is still there. I was just asking what remains to be done to propagate the correction all the way through.
On the pasted image, the highlight is the difference in the download path for the same dataset.
https://datamed.org/display-item.php?repository=0004&id=5833650a5152c608d984a3f2&query=LINCS
http://lincsportal.ccs.miami.edu/dcic/api/download?path=LINCS_Data/BroadT_LINCS&file=LDS-1293.tar.gz
The accessURL in here is not correct:
accessURL: http://lincsportal.ccs.miami.edu/dcic/api/download?path=LINCS_Data/HMS_LINCS&file=LDS-1354.tar.gz
https://datamed.org/display-item.php?repository=0004&id=5833650a5152c608d984a415&query=
How did you get this value field?