-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Arctos Down - Planned Outage for updates #6518
Comments
BannerArctos will be offline on Friday, July 21st as we implement the new data entry and bulkloader formats. Data in the bulkloader at the time will be migrated to the new bulkloader format. If you have data in process in Excel or some other file format, please note that the bulkloader after July 21st will require a new set of column headers. Mapping from the old to the new column headers can be found here. If you need help transitioning to the new headers, please let us know by filing an issue. |
Sent out tweet with all information. |
Email sent out to AWG and another scheduled for Friday morning right before the outage so people know why we are down. |
In looking over the new BL column names, they all make sense and I like how their sort order will make fields of interest easier to find in a list (eg if filtering by them in the SQL editor); however - what's up with All the other georeference fields are getting rennamed with 'coordinate', eg georeference_protocol -> coordinate_georeference_protocol I would think georeference_source would become coordinate_georeference_source ???? |
@DerekSikes georeference_source will be moved to a locality attribute. This was the best way I could think to demonstrate that in the mapping. |
Arctos is now tentatively available, but many services have been disabled to prioritize cache rebuild, which should take around 48 hours. I can turn access restrictions back on if this is problematic. Please let me know if you encounter any problems. |
Please complete to the best of your ability.
Planned Outage
Communication before/during outage
Communication after outage
The text was updated successfully, but these errors were encountered: