2022-08-11 Meeting notes

On search - will launch with basic Google Search functionality. The team will upgrade is a later phase.

Dina Meek

• Track 2/Support has a functionality that can crawl all the sites
  - currently ACO site will be one
  - Support has a search that will crawl all sites

On Contact form, can they make multiple selections and how would that be handled (for ex. I need information about…Allocations and Operations)?

Dina Meek

• See below - discussion about doing away with?

How do we want to handle news? Should the main site jump off to the various track sites for specific news items? Or should those news items be fed to the main site and, if so, what’s the mechanism?

Dina Meek

• User news 

  • Will we have something like this on the portal?

  • Track 3 is building a function that will gather all ACCESS news streams via API; A news aggregator for XSEDE and ACCESS infrastructure. This could work, but they weren’t building it for this purpose.

• Top questions for visitors to http://access-ci.org seeking information about your service area/track

Allocations -
- pointing to getting started…need to rephrase “How do I get an allocation…?”

Support -
- What’s changed about support within ACCESS?

• Where do I find the ACCESS Knoweldge Base?

Operations -

• How does my gateway, compute, storage, cloud resource become part of the ACCESS ecosystem?Metrics -

• What metrics can I view about my jobs?

• Where can I view performance information about my jobs?
  
  
  

• consider what emails you want to use for the contact form or if it should go into the ticket queue.

Waiting on Google Workspace to allow for creating alias lists (info@…); but also considering ticketing. Team is discussing doing away with the Contact Form. Send them directly to the Support site where they can search the knowledge base.