search

International-Soil-Radiocarbon-Database / ISRaD

Repository for the development and release of ISRaD data and tools
https://international-soil-radiocarbon-database.github.io/ISRaD/
24 stars 15 forks source link

Temporary Home for Completed but Not-Yet-Ingested Templates #81

Closed coreylawrence closed 5 years ago

coreylawrence commented 6 years ago

In working through the google document for tracking entries, I was wondering how we are/should be handling entries that are either (1) new or (2) in progress and are otherwise passing QA/QC and ready for ingestion?

For example, lets say someone downloads a file from the ISRaD_data_in_progress folder and makes the necessary modifications so that it is complete and passing the QA/QC. When that file is emailed to info.israd@gmail.com and has been reviewed, where does that file go before it is officially added through a recompile?

Alternatively, if I (an expert reviewer) am satisfied that an entry I have working on is ready to be compiled, where should I put it (if I do not plan to recompile the database right away)?

coreylawrence commented 6 years ago

Or can these files just be added to the ISRaD_data int the Dev branch? @aahoyt @greymonroe @jb388

aahoyt commented 6 years ago

Adding to ISRaD_data in the Dev branch sounds good to me, if it is passing QAQC and has been through expert review. That is effectively what we've been doing I think, and avoids more folders.

jb388 commented 6 years ago

@coreylawrence @aahoyt Agreed!

greymonroe commented 5 years ago

yes, the workflow is that files are...

  1. emailed to info.israd@gmail.com
  2. sent out for expert review
  3. added to ISRaD_data_files
  4. the database is recompiled with ISRaD.build()
  5. changes are committed to github