-
Notifications
You must be signed in to change notification settings - Fork 0
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
keywords stored on Zenodo as strings instead of an array #918
Comments
Two things: |
Email to Teodor about this is out now. |
this is a good point and I am supposed to ask you to get an (updated) https://drive.google.com/file/d/0B_yrQwn4yBySbk9KWkNDa0RZd0U/view?usp=sharing |
Being clueless myself, I asked @myrmoteras and he suggested I post the issue here. So, he is to blame 😉
Yea, that would be great. From my side, I thought that perhaps GGI is responsible for parsing the text into an array so it kinda made sense. Obviously I was wrong. Understanding the architecture (and the pipeline) would be tremendously helpful.
Well, that is way beyond my ken. I am glad you have bumped this to @teodorgeorgiev. Also, this kind of thing could be caught with some kind of automated QC, no? Thanks |
It has been fixed "keywords": [ |
Looking at https://zenodo.org/api/records/4067600 the keywords field is listed as
Perhaps that should be an array of those words but is being stored as a long string, no?
cc @gsautter @myrmoteras @tcatapano
The text was updated successfully, but these errors were encountered: