-
Notifications
You must be signed in to change notification settings - Fork 15
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
What does -[XX] mean #28
Comments
It indicates some additional information to be provided in the shorthand. For example, The [XX] is meant to indicate the number of months, e.g., TS-[6]. This originates in the original Dyke et al paper That being said, I'm not sure this is helpful anymore. Firstly, there was no guideline on how to use them practically (eg for geo location, what should the possible values of XX be?) and even for time the group thought using ISO would be better (see here)Secondly, this is not documented as you pointed out. Thirdly, we are working on a schema representation based on DUO codes to capture those 'modifiers' - see here I'll flag this with group at our next call, thanks for the feedback! |
Thanks for looking into this Melanie. So I went to read the Dyke et al paper you linked, I guess the -[XX] here does not necessarily mean the number of months. From this table: It looks like, at least in the context of this article, I would be interested in learning more about how the modifiers are structured. Thanks again for looking into these. |
Hi @HaoYuanLi - you're totally right, maybe I wasn't very clear. The [XX] in the shorthand is meant to encode the 'modifier' - time in months for TS, geo location for GS etc. Also for Time, practically a duration in months is hard to maintain for resources - as it implies a 'start date' was also captured (one needs to know 6 months starting from when) - the proposal is therefore to instead indicate the end date directly (and this could be encoded in ISO 8601) Given those, I am thinking that it is not very helpful to keep the [XX] notation for the shorthand - I would instead expect resources to display the code + modifier based on schemablock format. For disease, we always intended to use a disease ontology from the start - being explicit about the modifier - so we didn't include it in the shorthand. IMO this adds to the confusion and streghten the position above that we should just remove them all together. Does that help? Happy to have a chat otherwise, it may be easier to have a quick call than using the GH comments :) |
Yeah, that clarifies a lot of things. Thanks a lot Melanie. I don't think I have more questions for now, but I will certainly let you know if I have more questions otherwise, and will be happy to chat more over the phone or any other means you think is more convenient. |
I notice that in some of the fields,
https://github.com/EBISPOT/DUO/blob/master/src/ontology/duo.csv
Its shorthand includes -[XX], what does it mean? Thanks
The text was updated successfully, but these errors were encountered: