Merge pull request #32 from cct-datascience/callouts

Minor changes
cct-datascience · Dec 15, 2023 · eb09d9a · eb09d9a
2 parents 0899bac + c87cc4f
commit eb09d9a
Show file tree

Hide file tree

Showing 2 changed files with 24 additions and 21 deletions.
diff --git a/hiring.qmd b/hiring.qmd
@@ -37,15 +37,15 @@ All members of the hiring committee should be involved in all steps of the hirin
 -   NAU ecoinformatics: email katharyn.duffy\@nau.edu
 -   [Other resources (places to advertise) from UA HR](https://hr.arizona.edu/supervisors/recruitment-hiring/guide-successful-searches/advertising-position)
 -   Mastodon
-    -   hastags: #rstats #python #jobs #GetHired
+    -   Hashtags: #rstats #python #jobs #getfedihired #DataScience #rseng
 -   Slack
-    -   ROpenSci
+    -   rOpenSci
     -   Carpentries
     -   R4DS Online Learning Community
     -   Ecological Forecasting Initiative
     -   US-RSE
     -   ESIP (Earth Science Information Partners)
-    -   Rez-Baz
+    -   ResBazAZ
     -   UA-Data Science
     -   EDSIN
 
@@ -168,7 +168,7 @@ Salaries in DIAG range from \$30k for a recent graduate to \$85k for developers
 *Note: 6 and 7 are specific to a pipeline job; other positions may have additional required/desired skills*
 
 | Category of interest               |                                                         Description                                                         |
-|------------------------------------|:---------------------------------------------------------------------------------------------------------------------------:|
+|------------------|:----------------------------------------------------:|
 | **1. Learning new skills**         | Demonstrates ability to acquire new skills, especially technical skills, through self-teaching or by reaching out to others |
 | **2. Collaborative**               |                              Works well with a group and are able to problem solve with others                              |
 | **3. Software development skills** |                                 Able to demonstrate using software tools to solve problems                                  |

diff --git a/incubator.qmd b/incubator.qmd
@@ -81,24 +81,27 @@ Before the final meeting:
     -   copyright can be listed as "The University of Arizona and Authors"
 
 Send an email to schedule a final wrap-up meeting and to mark the conclusion of the incubator phase of the collaboration.
-Here's an example email you can build on:
 
-> Hi Jeremy,
->
-> As we come to the end of the incubator phase of our collaboration with AZMET, I just want to take some time and reflect on all the great stuff we've accomplished together.
-> I looked over the goals we set out to accomplish in the original project plan, and I think we've done a good job meeting them.
->
-> 1)  Static QA/QC routines that check data prior to going into the database ✅
-> 2)  Static checks for whether data for a station was retrieved in the previous hour: I don't think we put this one into place yet, but this could be a pretty simple addition to the report that just checks for NAs. I opened an issue to remind me to look into this.
-> 3)  A simple R package to wrap the API ✅
-> 4)  A "dynamic" QA/QC procedure that compares recent data to historical ✅
-> 5)  A Cooperative Extension bulletin describing the new AZMet QA/QC procedures: I'd be happy to help spread the word and provide edits to a draft bulletin. I also need to write a blog-post for our website and promote the `azmet` R package.
-> 6)  Availability of code on GitHub with a permissive open source license ✅
->
-> At our meeting on Monday, we'll discuss any final steps to the incubator phase and next steps for continued collaboration (i.e. funding continued work on the QA/QC report).
-> We'll also have a conversation about the incubator process itself---what worked well, what didn't work, and what could be improved.
->
-> Looking forward to seeing you then!
+::: {.callout-tip collapse="true"}
+## Example email
+
+Hi Jeremy,
+
+As we come to the end of the incubator phase of our collaboration with AZMET, I just want to take some time and reflect on all the great stuff we've accomplished together.
+I looked over the goals we set out to accomplish in the original project plan, and I think we've done a good job meeting them.
+
+1)  Static QA/QC routines that check data prior to going into the database ✅
+2)  Static checks for whether data for a station was retrieved in the previous hour: I don't think we put this one into place yet, but this could be a pretty simple addition to the report that just checks for NAs. I opened an issue to remind me to look into this.
+3)  A simple R package to wrap the API ✅
+4)  A "dynamic" QA/QC procedure that compares recent data to historical ✅
+5)  A Cooperative Extension bulletin describing the new AZMet QA/QC procedures: I'd be happy to help spread the word and provide edits to a draft bulletin. I also need to write a blog-post for our website and promote the `azmet` R package.
+6)  Availability of code on GitHub with a permissive open source license ✅
+
+At our meeting on Monday, we'll discuss any final steps to the incubator phase and next steps for continued collaboration (i.e. funding continued work on the QA/QC report).
+We'll also have a conversation about the incubator process itself---what worked well, what didn't work, and what could be improved.
+
+Looking forward to seeing you then!
+:::
 
 ### Wrap-up Meeting