Open davidfastovich opened 5 years ago
Oh right. This is an API issue. Unfortunately, the API that pulls in the chronology tables is coming from the postgres version of the Neotoma Database, while "fresh" information is still going into the SQL Server database.
The new sites will not be accessible to the curl
calls in the Bulk Baconizing script until we migrate another snapshot of the SQL Server database. I will put in a request on Slack.
Its only a handful of sites so I can wait however long until they're migrated over, otherwise I can just download the chron control from Neotoma Explorer and run Bacon myself.
Sites recently uploaded by PI: Oswald, W. Wyatt are not populating chronology tables despite each site having multiple radiocarbon dates. Datasets effected are 40791 ,40793, 40797 ,40799, 40803, 40844, 40854, 40861, 40875, 40914, 40988, 40992, 41001, 41018, 41025, 41027.