Page Comparison

Social Media

Andrew

n/a - Twitter audience is bouncing back

Cynthia asked about our having a LinkedIn; Dina and Andrew will start off a discussion and we can bring back to the group

Website

Cynthia/Meggie

Dina

Web stories update

• 1/24 TACC Science Story ( Moiré patterns) – Cynthia 

• 1/26 Enhanced security aspects of ACCESS – Hannah

• 2/1 PSC Science Story (Hurricane Ian) – Hannah

• 2/7 PSC Science Story (NC student project/materials Science) -- Meggie

• 2/9 (Tentative) STEP program story – Hannah

• Comprehensive Style Guide

  • Currently being built and should be iterative - we can share out pieces once they are available

  • in this way we can provide the tools to developers across all service areas so our sites look more cohesive

  • Should be completed by March

• Web Presence Working Groups

  • One group is working to unify headers and footers

  • Another group is working to determine what needs to go on a Resource Provider page, which we expect will be linked from the top, universal navigation

Newsletters

Hannah

Follow-up discussion from Constant Contact training

• we need to work with each service area to assess:

  • what types of emails they will be sending from CC

  • how frequently those emails will be sent

  • who those emails will go to

  • how those emails will be collected and maintained in appropriate lists

• we need to get ACCESS user emails into Constant Contact

Discuss/approve criteria for external content in quarterly ACCESS Advance newsletter

• Discussion on should we should include - internal v. external

  • Support feels like some of the external ones are essential

    • They’ve been getting a lot of requests to send out a lot of training notifications

    • They are really getting pressured to promote things to a fairly large number (thousands)

  • Dina said NCSA allows external opportunities in its newsletter as long as we feel it would be of interest to our readership

  • Meggie sharing that we need to be cautious about too many communications because we will be seen as being too spammy

  • Cynthia wanted to get a sense of how consistent this might be newsletter to newsletter

    • Questions about how well the XSEDE User News Board opt in worked

    • Can we measure what people are clicking on w/in our newsletters to see what

      • Hannah shared the XSEDE click-through grid

  • Dina suggested a more centralized events calendar; Alana says the Support calendar hasn’t been well populated (by the community)

  • Stephen said all points are accurate

    • It’s important for us to understand the “why” of people requesting these

    • Now with a privacy policy in place we can address this

• Group decided we should focus on this in a sprint

• Hannah says if people unsubscribe they unsubscribe to all of our emails

• We will send out an all-ACCESS email explaining how we are handling and working on this

Brand

Dina

ACCESS Writing Style Guide

Misc.

Dina/Stephen

Similar to Hannah’s criteria above, we need to prioritize email criteria. I put together a rough draft with what the various awardees need to discuss so we can open the email pipes.

Would each of you, representing the service areas/tracks, be open to 1:1 meetings with us once a month?

For 2/9 Meeting: Assignment: Develop elevator pitches (to be used by your leadership and other team members):

Example for RAMPS: 

"Allocation Services interfaces with the research community to facilitate requests looking to utilize advanced cyberinfrastructure provided by the NSF. RAMPS is an open, inviting, and democratized allocations marketplace for a range of novel resources to empower all research communities with a simplified request and review framework through a flexible software environment."

Dina

Terminology Task Force adoption