-
Notifications
You must be signed in to change notification settings - Fork 0
/
outreach-communication.qmd
228 lines (152 loc) · 10.7 KB
/
outreach-communication.qmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
---
title: "Communications and Outreach"
editor:
markdown:
wrap: sentence
---
## Documents and Websites to Update regularly
- [CCT Data Science website](https://datascience.cct.arizona.edu/)
- [CCT Service Catalog](https://docs.google.com/document/d/1LIxkktiP219_Xd24vXpgA1Qz7j7WcuRORtN26p2Qujw/edit)
## Where to announce events:
Besides our email listserv, we have a [spreadsheet of places to announce events](https://docs.google.com/spreadsheets/d/155tcna1dMWwsZymdKFZPCrnZf3xocw4hPv1JKwOu9MQ/edit?gid=0#gid=0) Feel free to add to or update it.
## Group Email Listserv {#listserv}
We currently maintain our email list on the Emma platform.
We send out \~quarterly emails, and people can sign up for our listserv using the link on our [contact page](https://datascience.cct.arizona.edu/contact).
We also add people manually to this mailing list, for example, after registering for a workshop and opting in to the mailing list as one of the registration questions.
<!--# unclear if this is technically possible with Trellis lol -->
How to send out emails:
- Ask Matt Rahr to enable your account on Emma
- Sign in using your UA email address
- Select "Campaigns" tab and click "Create New Campaign" button
- Add relevant campaign name, including year and quarter, and keep default "Regular email" option
- Select most recent template
- Update email text
- Click "Preview" button to see what it will look like to recipients
- Click "Review & send" button to finalize
- Under "Choose recipients", add group called "Group announcements: workshop & other"
- Add subject line and (optional) preheader text
- Leave Sender name and Sender email as is
- Hit "Send now" button to send email
## Group Emails
We have two shared emails, `[email protected]` and `[email protected]`.
These should go to all people in the group.
When you respond, it will be from your address but please keep the original group email address in cc as long as is useful.
- `[email protected]` is the general 'how to contact us', for use in websites, business cards, posters, etc, in many cases alongside a personal email address.
- `[email protected]` is for shared accounts, licenses, billing etc.
Remember to add passwords to [Stache](https://stache.arizona.edu/) and share with group members when creating new accounts.
## Group Website UA quickstart (Drupal)
Website [here](https://datascience.cals.arizona.edu/)
Links to documentation:
- **Complete Quickstart Docs** instructions for how to change content or appearance of a UA website: <https://uasites.arizona.edu/home>
- **Sign In**
1. Go to <https://datascience.cct.arizona.edu/user/login>
2. Click on the "Log in using University of Arizona WebAuth" link, and then sign in with UA credentials
3. You can [add new content](https://quickstart.arizona.edu/get-started/adding-content) or [edit existing content](https://quickstart.arizona.edu/create-content/editor-toolbar)
- **People**
- **Add / edit people** <https://quickstart.arizona.edu/people-directories>
- **Add blogpost** (this is added as a 'news' type) <https://quickstart.arizona.edu/create-content/adding-news-pages>
- **Update Menu**
- **Preview page without publishing**
- Save the page unpublished so that you can see how it will display without the public seeing it.
- Projects
- Card summary - 1-2 sentences, only appears on the card
## Social Media
### Twitter
We no longer post to our Twitter/X account [\@cct_datascience](https://twitter.com/cct_datascience)
### Mastodon / fediverse
We have a mastodon account [\@cct_datascience\@fosstodon.org](https://fosstodon.org/@cct_datascience).
To log in, you'll find the password on [stache](https://stache.arizona.edu/) (you may need to ask for it to be shared with you if you don't see it)
#### Guidelines
- Please review the group [code of conduct](code-of-conduct.qmd) before posting to ensure you adhere to these guidelines
- Including relevant pictures in posts are encouraged. **Please get explicit verbal/written consent from everyone in the picture before posting.** Tag people in the pictures who are on Mastodon **with their permission**
- Cite sources and mention users (\@journal or \@author) in posts when applicable
- If anyone comments on a post, make sure to respond to them, especially if it's a question.
- All posts and replies should include at least one mention of a user or organization, or a relevant hashtag. These elements can bring others into a conversation, make our content more visible to a wider audience, and generate more engagement and followers.
- Example hashtags: #UArizona, #UniversityOfArizona, #Rstats, #DataScience, #DigitalAg, #DataViz, #AcademicChatter, #RSEng
#### Ideas for posts
- Feel free to get creative! This is just a limited list of possible selections.
- Content should be directly in line with our [mission statement](https://datascience.cct.arizona.edu/about)
- Announcements of recent group activities, e.g., quarterly review meeting
- Short summary & link to a recent publication from the group or collaborators
- Notification of recent release of group's software or documentation
- Relevant upcoming events, e.g., conferences or hackathons that group members are attending
- Link to recently posted news article on [group website](https://datascience.cct.arizona.edu/news) (new and improved website coming soon!)
- Link to good resources for the type of work we do, e.g., blog post for how to use an R package
- Live coverage of an event like a conference talk—this can be a difficult thing to do
#### Boosts/Favorites
- Content related to UA data science and/or ALVSCE related
#### Following
- University of Arizona, agriculture, ecology, open science, computational, scientific software, data science
#### Follow Backs
- When a new user or group follows us, we should follow back if they're a collaborator, well-known organization, associated with the University, or meet the guidelines above for Following in general. When in doubt, check with another team member.
#### Comments on other posts
- Follow guidelines for other types of posts, including seeking approval before posting.
#### Link Roundups
- TBD
### Resources
- [Benefits and how to for scientists using Twitter](https://app.scientist.com/blog/2019/01/31/twitter-and-scientists-a-love-story)
- [UA Brand Resources](https://brand.arizona.edu/)
- [Requesting an official UA Tweet](https://uarizona.co1.qualtrics.com/jfe/form/SV_1Nh6GSKXPDQlsKF)
## Group Blog
### Suggestions
- Feel free to collaborate with others inside or outside of the team for relevant blog posts
- Write your name next to an idea if you'd like to claim it
### Ideas
- Real-world examples of how open data / open science / cross-disciplinary collaboration has advanced data-driven discovery
- Tools to enable researchers to provision their own computing infrastructure
- Culture of collaboration and user-focused development for scientific / research software - Agile / Lean / Pair Programming / Mob Programming
- Power of DAG (directed acyclic graphs) workflows with applications for large-scale agricultural data pipelines
- Mini hackathons for collaborative idea generation and team-building
- Using modern IDE's like PyCharm effectively for scientific software development (NumPy, Jupyter, Docker, profiling, debugging, and automatic style / code smell detection)
- Github for project management
- Personal experiences of how ResBaz, R-Ladies, Python / GIS / UAV MeetUps, etc. have advanced your own professional development through knowledge-sharing, networking, and cross-disciplinary collaboration
- Going beyond the metadata buzzword with explanations using agricultural data science / data pipeline examples
## Group Branding {#branding}
Projects that we work on such as websites/web apps, or presentations given by us or our collaborators should include some recognition of our group's contribution.
For guidelines on receiving recognition for our work on publications, software, and datasets see [authorship and licensing guidelines](getting-credit.qmd).
### Guidelines
- Include "The University of Arizona" as part of our group name, especially if project is externally facing
- Always use official group logo (TBD)
- Always include a link, QR code, or tinyurl that leads to our group website
- Abbreviating CCT is fine for most cases
### Where to include
- Footer of GitHub README.md for all projects
- Web apps (e.g. Shiny apps) built for incubators (on landing page or footer)
- Contributors or acknowledgement page if a project has one
- `pkgdown` websites for R packages (can put in "getting started" vignette to be on home page)
- Project websites
- Posters and slides presented by collaborators at conferences
- Other printed materials presented by collaborators (banners, handouts, signs, etc.) when appropriate
### Examples
::: callout-note
## Footer text
An example of a footer that could go on a GitHub readme, or the bottom of a web app
``` {.markdown .code-overflow-wrap filename="markdown"}
------------------------------------------------------------------------
Developed in collaboration with the University of Arizona [CCT Data Science](https://datascience.cct.arizona.edu/) team
```
------------------------------------------------------------------------
Developed in collaboration with the University of Arizona [CCT Data Science](https://datascience.cct.arizona.edu/) team
:::
::: callout-note
## Logo with link
Example markdown for a logo that links to our homepage (official logo TBD).
Appropriate for acknowledgments section of webpage/web app.
``` {.markdown .code-overflow-wrap filename="markdown"}
[{width="126"}](https://datascience.cct.arizona.edu/)
```
[{width="168" height="31"}](https://datascience.cct.arizona.edu/)
:::
::: callout-note
## Logo with QR code
Appropriate for use on posters or in acknowledgments section of slides, for example
``` {.markdown .code-overflow-wrap filename="markdown"}
{width="286" height="70"} {width="70"}
```
{width="379" height="70"} {width="70"}
:::
::: callout-note
## Text with tinyurl
Appropriate for print or slides as an alternative to a QR code
> The University of Arizona, CCT Data Science (tinyurl.com/ua-cct-ds)
:::