Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Current »

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants - Rollcall

Dina Meek Andrew Helregel Megan Johnson Megan Janeski Alana.Romanella Hannah Naughton Cynthia Dillon (Unlicensed) Stephen Deems Bob DeLeon

\uD83E\uDD45 Goals

Item

Presenter

Notes

Social Media

Andrew

n/a

Website

Cynthia/Meggie

Dina

Boilerplate review

Deferred until next meeting

Newsletters/ Emails

Hannah, group

Everyone please populate this document as you deploy any newsletters

Questions from a constituent:

  1. How is this newsletter (ACCESS User Community) different than the ACCESS Support newsletter?

    1. In terms content, audience and expected submissions?

    2. In terms of pulling from events and training lists to populate content? The Support newsletter automatically pulls from Events and training lists, if those are intended for the User Community (or other) newsletters, can they be pulled from the list as well vs. resubmitting each month?

      1. Support Digest will only go to affinity groups and active allocations.

      2. Digest will mostly be events

      3. We could provide a link to Support’s calendar/events/trainings page

      4. OR they could opt in to the Support Digest

      5. Alana thinks either/both would be ok

      6. We need submission deadlines posted All ACCESS shared calendar (Ron manages); Hannah will work with Ron (Support Digest just pulls from their calendar)

      7. Team will develop criteria for what events from Support calendar rise to the level of the ACCESS Advance for publication.

  1. What content is the monthly newsletter appropriate for?

    1. listing upcoming trainings or should another newsletter be utilized? 

      1. Support calendar for now

    2. Does it matter if the same information is posted to multiple newsletters?

      1. shouldn’t be an issue

    3. Is there any space in the monthly newsletter for user stories? If so, how does an ideal content look (length/details/other information)? Or is it recommended to post news to the news portion of the ACCESS site to be curated in the various newsletters or should we be submitting to individual newsletters?  (e.g. will the User Community and other newsletters pull from the news that is already submitted and posted to the ACCESS site?)

      1. We’re always looking for User Stories

      2. We need to incorporate the length/details/other information into the style guide; also what does constitute news (criteria)

      3. Perhaps we develop a form for people to submit news and publish it in the newsletter

      4. Possibly reach out to RPs with the form to tell stories of work coming off their machines - we want to hear from ALL levels of RP, not just Level 1s.

        1. Also, Cynthia is meeting with RPs in the Forum

    4. Anything else that the monthly newsletter is appropriate for that hasn’t been touched on above?

 

  1. What is the source for science stories at the bottom of (https://access-ci.org/)?

 

  1. Are there other newsletters we should be aware of that we may want to post content too? If so, can you please confirm the available newsletters (or posting locations) and the focus of the content we should consider for each of these options?

Brand

Dina

n/a

Misc.

Dina/Stephen

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

ACCESS Support provides cost-effective scaled support to the broad scientific community using national cyberinfrastructure. These democratized efforts comprises three major themes: (1) leverage modern information delivery systems to simplify user interfaces; (2) leverage experts from the community to develop training materials and instructions that can dramatically reduce the user learning curve for several increasingly important CI computational techniques; and (3) employ a matchmaking service that will maintain a database of specialist mentors and student mentees that can be matched with projects to provide the domain-specific expertise needed to leverage ACCESS resources.

ACCESS Allocation Services interfaces with the research community to facilitate requests to utilize advanced cyberinfrastructure provided by the NSF. Allocation Services provides an open, inviting, and democratized allocations marketplace to easily request a range of resources to empower all research communities.

ACCESS Operations supports the integration and operation of ACCESS cyberinfrastructure with operational support, networking and data services, and cybersecurity support. We also support the nation’s resource providers and strive to grow the national cyberinfrastructure ecosystem by integrating new kinds of resources into the community.

The ACCESS Coordination Office fosters an environment of shared governance and horizontal leadership within which program PIs work with a common purpose to create and support an inclusive and vibrant CI ecosystem focused on enabling science.

ACCESS Metrics:   The primary goal of Metrics is to monitor the usage and performance of NSF’s suite of supercomputers.  The primary web-based tool to do this is XDMoD which helps center staff run their resources more efficiently, users run their code more efficiently and allows NSF to make data-based decisions on what new systems need to be built and upgraded to support the national research requirements.

Events

Dina

  • Plans for PEARC

    • we might need some kind of communication - and mechanism - about ordering materials for conferences etc. 

Open Discussion

Dina

What other topics does the team want to talk about today?

  • MJ is working on materials request form

  • Cynthia: how would folks in our teams feel about being featured in profiles? Could be like what we did with Alana, but expanded (was in Inside ACCESS).

    • team seemed to feel positive about this.

✅ Action items

⤴ Decisions

  • No labels