-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some images are displayed in PLANTDataHub as links which link to nowhere #12
Comments
Hi thanks for your feedback, I have implemented a new way to handle the different urls created by elabftw. Please try again and give more feedback. Thanks in advance |
@ArmandoTeixeira I would like to invite you to test the tool again when you have time. In addition, it will be great if you can give me some feedback on the new version of elab2arc, so I can further improve it 😄 |
Thank you for your quick response! The issue was raised by a coworker, since my pictures were all fine until now, but I will check with them to see if the issue has been solved. Regarding my feedback, when the conversion works, it is well formated in the ARC it goes to. However, I am coming across a problem of, while the eLab2ARC converter successfully adds an Experiment to an ARC for the first time, it cannot add a second Experiment, rasing the error of "could not find main". Sabrina is already aware of this, but maybe I should raise another Issue here. |
Hi @ArmandoTeixeira , glad to know that the tool worked (at least for the first experiment 😄 ). |
Hi @xiaoranzhou, unfortunately, when I try to convert another experiment, even if it is adding only one more to the arc and not several in a batch, it still yields me the error of "main not found". Please see the attached screenshot with the error. Apparently, it seems to be having problems finding the main branch of my ARC. |
Hi @ArmandoTeixeira, thanks for the feedback again. Does the ARC have a main branch? At the moment, I can not reproduce the error on other repos. |
Dear @xiaoranzhou, yes, the ARC has a main branch, which is accompanied by the tags "default" and "protected" (see picture). The access token is most likely not the problem, since it expires in 1 year, has Maintainer role and has the necessary permissions. I even tried generating a token with all possible permissions but it still yielded me an error. I am also a bit lost on what the problem might be, maybe I need to delete the ARC and create it again, but still I don't know what would make it act like this. |
Hi @ArmandoTeixeira, have you tried to restart conversion from eLabFTW to a new ARC? Is there anything I can help now? 😄 |
Describe the bug
When using the tool, some of the images are shown in the PLANTDataHub online viewer as only "broken" links. When you try to click them, they yield a 404 error. However, the image files are uploaded in the dataset folder. It does not happen because of a specific file type (e.g. png also yielded this problem), name (e.g. unusual characters), nor because of some text formating (e.g. indentation, inclusion in a bullet list, etc.). Until now, it's unclear why some pictures show up good and others have this bug.
When inspecting the webpage code, the src of the images that are correctly showing look like this:
"https ://git.nfdi4plants.org/ag_zurbriggen_hhu/*folder name*/*ARC name*/-/raw/main/assays/*assay name*/dataset/2_image.png"
while the src link of the "broken" images look like this:
"/ag_zurbriggen_hhu/*folder name*/*ARC name*/main/app/download.php?name=image.png&f=94/94eb2d0b570663f22de8959d2542cf7af8a1058d6be94da95924a44279d86c523e673b068d97ef42f8fa2ce5582db986ddb0265d9047c33da55b1d944e63bb43.png&storage=2"
To Reproduce
Steps to reproduce the behavior:
Note: I am not sure of exactly how to reproduce it because some images work and some don't, and I haven't find a common denominator regarding the file type/name/size
Expected behavior
Images show up in the web viewer of PLANTDataHub as "broken" links.
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: