Main content

Files | Discussion Wiki | Discussion | Discussion
default Loading...

Public Communications

Menu

Loading wiki pages...

View
Wiki Version:
## Communications and Outreach ## 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: - Our email list (try to consolidate events to quarterly emails) - Log into CCT Data Science myemma account - Select campaigns and create new campaign - Choose "Data Science" template and add text box with event info - Hit "Review & Send" - [UA Master Calendar](https://news.arizona.edu/calendar) - [Data Science Institute events page](https://datascience.arizona.edu/events) - Experiment Station Tues morning notes: send announcement to tmn@cals.arizona.edu - [CALS Bulletin](https://compass.arizona.edu/bulletin) - CALS Grad Student List Serv: send announcement to Dr. Jia Hu jiahu@arizona.edu - Individual CALS departments listservs as appropriate: - ruthholladay@arizona.edu Ruth Holladay for SNRE weekly digest - jbee@arizona.edu Jessica Bee for FCSC/Human Ecology grad student listserv - ___ for Plant sciences grad student listserv - jabrilithomas@arizona.edu Jabril Thomas for ACBS - davaj@arizona.edu Dava Jondall for Biosystems Engineering - danielleb@arizona.edu Danielle Pilar Buhrow for AREC - nmcisaac@arizona.edu Naomi McIsaac for Environmental Science - prupert@arizona.edu Peggy Rupert for Nutritional Sciences and Wellness - pnielsen322@arizona.edu Paula Nielsen for Entomology - thodges@arizona.edu Tanya Hodges for AETI (Yuma) - Data Science Institute ["Data Drip"](https://bcf.arl.arizona.edu/news) at Rii-datascienceinstitute@arizona.edu - R-Users AZ listserv, send announcement to Jeff Oliver jcoliver@email.arizona.edu - CALS Data Science Ambassadors - EEB grad student coordinator: send announcement to Pennie Rabago-Liebig pliebig@arizona.edu - [Form for Bio5 mailing list](https://docs.google.com/forms/d/e/1FAIpQLSfi1LZ53wHt74rcVt68TwNOatsntBtFM-u5Ag9N0ZPzCQ7IzA/viewform) - Slack - CyVerse, UA Data Science, RezBaz - UA Listservs (as appropriate) - Drones, GIS - See also ["ALVSCE Brand Guidelines and Tools to Promote Your Programs"](https://compass.arizona.edu/marketing/brand) ## Group Email Listserv We maintain our email list on the Emma platform. 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, `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.edu` is 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.edu` is for shared accounts, licenses, billing etc. ## 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](https://uasites.arizona.edu/home) * **Sign In** 1. Go to [https://datascience.cals.arizona.edu/user/](https://datascience.cals.arizona.edu/user/) 2. Click on the "Log in using UA WebAuth" button, click on "LOG IN", and then sign in with UA credentials 3. You can [add new content](https://uasites.arizona.edu/node/11_) or [edit existing content](https://uasites.arizona.edu/node/3) * **People** * **Move people around** https://datascience.cals.arizona.edu/admin/uaqs-person/reorder-people * **Add / edit people** https://quickstart.arizona.edu/people-directories * **Add blogpost** (this is added as a 'news' type) https://quickstart.arizona.edu/news-content-type * **Update Menu** https://quickstart.arizona.edu/setting-main-menu * **Preview page without publishing** * Save the page unpublished so that you can see how it will display without the public seeing it. * **Clear cache** so it appears to public immediately * [Configuration --> Development --> Performance](https://datascience.cals.arizona.edu/admin/config/development/performance) --> Clear all caches * Projects * Card summary - 1-2 sentences, only appears on the card ## Group Twitter **Twitter handle: [@cct_datascience](https://twitter.com/cct_datascience)** - Kristina has control over the password. She can give you access to the account, as a contributor or admin, via [Tweetdeck](https://tweetdeck.twitter.com/), a Twitter-owned app. You need your own Twitter account to use TweetDeck. - Group member Twitter handles: - @KristinaRiemer - @JessicaSGuo - @LeafyEricScott ### Twitter Curator - One person volunteers to be the Twitter Curator (TC) for two Sprints. - The TC will post, comment, or retweet at *least* once a week. - For the **future** - start utilizing Analytics to see what is and isn't working for improving engagement - consider an introduction tweet from the curator, like in this [tweet](https://twitter.com/WeAreRLadies/status/1289920134480568321?s=20) from R-Ladies Global. ### Posts #### Guidelines - Please review the [group code of conduct](https://osf.io/tzmhp/wiki/Code%20of%20Conduct/) 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.** - Cite sources and mention them (@journal or @author) if possible - If anyone comments on a post, make sure to respond to them, especially if it's a question. - All tweets, responses, and retweets 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. #### Tweets - Feel free to get creative! This is just a limited list of possible selections. - Content should be directly in line with our mission statement - **The mission of the UA ag data group is to provide scientists and engineers with open software, data, and computing that will allow more efficient discovery and invention so that we can engineer crops and manage sustainable agricultural landscapes that produce food, energy, and ecosystem services.** - 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.cals.arizona.edu/all-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 - Livetweet an event like a conference talk - this can be a difficult thing to do #### Retweets/Favorites - Content related to UA data science and/or ALVSCE related - All retweets **must** include a comment and **should** include a mention or hashtag #### 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 apprroval before posting. #### Link Roundups - TBD ### Analytics - TBD if all team members can access this, or only the owner. ### Resources - [Benefits and how to for scientists using Twitter](https://www.labsexplorer.com/c/twitter-and-scientists-a-love-story_185) - [UA Brand Resources](https://brand.arizona.edu/) - [Requesting an official UA Tweet](https://uarizona.co1.qualtrics.com/jfe/form/SV_1Nh6GSKXPDQlsKF) - [Advanced TweetDeck features](https://help.twitter.com/en/using-twitter/advanced-tweetdeck-features) - [Getting More out of TweetDeck](https://www.socialmediatoday.com/social-networks/10-ways-get-more-out-tweetdeck-explained-twitter) ## 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 Newsletter - TBD, will use Mailchimp
OSF does not support the use of Internet Explorer. For optimal performance, please switch to another browser.
Accept
This website relies on cookies to help provide a better user experience. By clicking Accept or continuing to use the site, you agree. For more information, see our Privacy Policy and information on cookie use.
Accept
×

Start managing your projects on the OSF today.

Free and easy to use, the Open Science Framework supports the entire research lifecycle: planning, execution, reporting, archiving, and discovery.