Closed laughedelic closed 9 years ago
I don't know... I don't think it'd make much sense to group all names from different sources such as BLAST, GenBank and so on. Besides, I don't think they would be useful since the only sort of standard that exist is that of the NCBI _(scientificname in this file) Let's see what @rtobes thinks... :wink:
Well, even if those other names are not so usefull, we should leave one property: name
or scientificName
, because we have only one value.
OK but in any case let's wait and see what @rtobes says about it, she knows better than any of us whether any of those names are useful or on the contrary we should run away from them! :smile:
any update here? @pablopareja @rtobes
It is true that the most important name is the scientific name but after doing many different project I think that it is better to store all the names with their type. You never knows the type of name that you will need for future projects. @marina-manrique what is your opinion?
I agree with @rtobes on storing all the names but I don't know how would be the better way to implement that: multivalues or different node attributes... for that you guys ( @pablopareja @eparejatobes @laughedelic ) know much more
Once we know that they are interested I think that names should be stored as different properties.according to their source, that's to say, we would have properties such as:
(I got these after having a quick look at the values included in the files) By the way, as far as I see there might be repetitions in all these categories always talking about the same taxonomic unit :wink:
up :point_up: let's decide something here for the upcoming release. I think, it's a small change, but it improves usability.
mmm It's extra work too... I think there're more important things to invest that time on but if you want to do it yourself that'd be nice! :stuck_out_tongue_winking_eye:
whatever, it's no work. I'm saying that we should first decide something here.
name
property, which is never filled (according to titandb importing), so it's not clear what is this "name"scientificName
which is actually filledSo I suggest to make this property multi-valued and write there all fine names that we get from
names.dmp