search

SpeciesFileGroup / taxonworks

Workbench for biodiversity informatics.
http://taxonworks.org
Other
85 stars 25 forks source link

Feature Request - COL+ import #1695

Open tmcelrath opened 4 years ago

tmcelrath commented 4 years ago

Not sure if duplicate. Please merge if so.

As a user, I want to import COL+ or another TW project taxon hierarchy for use in my project. Basically this is the opposite of COLDP. I want COLIP. This would give at least skeletal records, but could include more information if requested.

Maybe @gdower is already working on this?

tmcelrath commented 4 years ago

From Kojun Kanda: "Would be great to just append someone's taxonomy to an existing parent node, and if there are downstream conflicts (like I think I might have a few cucujoids already in my taxonomy from things initially described in cucujoidea), they just get flagged for manual curation. I think for most users, that'll still save a boatload of time."

mjy commented 4 years ago

Which of the two is more useful?

  1. Insert a "pointer", a virtual node, that you can not change, but that is synced with the node it is pointed to.
  2. Clone, and change the clone
tmcelrath commented 4 years ago

I think 2. I can't see to tag Kojun for some reason. But I would want to tag him to get his opinion too.

tmcelrath commented 4 years ago

Although I can definitely see the appeal of 1. 1 would be useful for groups you don't work on, e.g. mammals for me - that I just want someone else to maintain and I can use for biological relationships or something. 2 would be more useful for starting a project.

gdower commented 4 years ago

It sounds like this is moving more in the direction of importing from another project within TaxonWorks, but at some point if a TaxonWorks CoLDP importer is implemented, probably it should use the same parent-child schema that we use for CoLDP exports from TaxonWorks. I imagine that the CoL Clearinghouse will export CoLDP in the parent-child schema as well, which would allow getting data from the CoL Clearinghouse into TaxonWorks. However, I'll check with Markus on our next stand-up if that's the case.

I could also potentially create a CoLDP to DarwinCore converter.