You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have an increasingly large number of import scripts in the bin/ directory. @YaphetKG suggested in a comment that we should move them into a new repository. If we were to do that, we could consolidate the other repositories containing import code in that repository, which would include:
I like the idea of having some basic importers in this repository (like the dbGaP one), but certainly more sophisticated ones like the HEAL Platform MDS import or HEAL VLMD import don't need to be in this repository.
This issue covers deciding whether we should create a single dug-importers directory for all these scripts, or whether they should be organized by project (e.g. heal-importers, bdc-importers, etc.).
The text was updated successfully, but these errors were encountered:
We have an increasingly large number of import scripts in the
bin/
directory. @YaphetKG suggested in a comment that we should move them into a new repository. If we were to do that, we could consolidate the other repositories containing import code in that repository, which would include:I like the idea of having some basic importers in this repository (like the dbGaP one), but certainly more sophisticated ones like the HEAL Platform MDS import or HEAL VLMD import don't need to be in this repository.
This issue covers deciding whether we should create a single
dug-importers
directory for all these scripts, or whether they should be organized by project (e.g.heal-importers
,bdc-importers
, etc.).The text was updated successfully, but these errors were encountered: