12 Communications and Outreach
12.1 Documents and Websites to Update regularly
12.2 Where to announce events:
Besides our email listserv, we have a spreadsheet of places to announce events Feel free to add to or update it.
12.3 Group Email 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.
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.
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
12.4 Group Emails
We have two shared emails, cct-datascience@arizona.edu and cct-datascience-admins@arizona.edu. 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.
cct-datascience@arizona.eduis the general ‘how to contact us’, for use in websites, business cards, posters, etc, in many cases alongside a personal email address.cct-datascience-admins@arizona.eduis for shared accounts, licenses, billing etc. Remember to add passwords to Stache and share with group members when creating new accounts.
12.5 Group Website UA quickstart (Drupal)
Website here
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
- Go to https://datascience.cct.arizona.edu/user/login
- Click on the “Log in using University of Arizona WebAuth” link, and then sign in with UA credentials
- You can add new content or edit existing content
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
12.7 Group Blog
12.7.1 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
12.7.2 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
12.8 Group 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.
12.8.1 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
12.8.2 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
pkgdownwebsites 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
12.8.3 Examples
An example of a footer that could go on a GitHub readme, or the bottom of a web app
markdown
------------------------------------------------------------------------
Developed in collaboration with the University of Arizona [CCT Data Science](https://datascience.cct.arizona.edu/) teamDeveloped in collaboration with the University of Arizona CCT Data Science team
Example markdown for a logo that links to our homepage (official logo TBD). Appropriate for acknowledgments section of webpage/web app.
markdown
[{width="126"}](https://datascience.cct.arizona.edu/)
Appropriate for use on posters or in acknowledgments section of slides, for example
markdown
{width="286" height="70"} {width="70"} 
Appropriate for print or slides as an alternative to a QR code
The University of Arizona, CCT Data Science (tinyurl.com/ua-cct-ds)
12.6.2.6 Comments on other posts