ODDS Cave (One-Stop Data Depot for SOG)

Page tree

Versions Compared

Old Version 18

changes.mady.by.user Jessica Schultz

Saved on

compared with

New Version 19

changes.mady.by.user Jessica Schultz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Scroll ImageMap
viewSize8481.0
makeResponsivetrue
imgWidth2000.0
areasData{"areas":[{"shapeType":"rect","coords":"0.47,0.94,211.911,62.83","title":"","pageRefIndex":0,"linkTarget":"_self"},{"shapeType":"rect","coords":"542.2774,0.7,223222.7126,63.3","title":"","pageRefIndex":1,"linkTarget":"_self"},{"shapeType":"rect","coords":"767.01,0.47,373.71,62.36","title":"","pageRefIndex":2,"linkTarget":"_self"},{"shapeType":"rect","coords":"1140.72,1.17,478.35,62.83","title":"","pageRefIndex":3,"linkTarget":"_self"},{"shapeType":"rect","coords":"1618.04,0.23,381.96,63.77","title":"","pageRefIndex":4,"linkTarget":"_self"},{"shapeType":"rect","coords":"215211.9811,1.0385,324331.7462,61.86","title":"","pageRefIndex":5,"linkTarget":"_blank"}]}
imgRelativeODDStopnav.png
pageReferencesOneStop Data Depot for SOG (ODDS)-!!!!!-ASPEN-!!!!!-SOG Data Source-!!!!!-SOG Data Source Guides-!!!!!-Connect With Us-!!!!!-Acronym List
imgHeight64.0
alwaysHighlightfalse
dataModelVersion3

Button Hyperlink
custom-iconundo
iconcustom
titleBack to Home
typestandard
urlhttps://qnetconfluence.cms.gov/pages/viewpage.action?pageId=441160191



We have created a Slack channel for our internal ‘SOG Data Source’ communications (https://hcqis.slack.com/archives/C034TKY7ESJ ). Slack is a messaging app where we can have discussions, answer questions, share announcements and respond to ‘SOG Data Source’ requests

We want to use the best communication tools to make our lives easier and be more productive. Having everything in one place will help us work together better and faster. This also helps eliminate redundancies and reduce time spent in meetings. Everything you share in Slack is automatically indexed, creating a searchable archive of all our work.

All SOG staff members (200+ individuals) have access to this channel (NOTE:  If not done so already, please request access to CCSQ QualityNet Slack.  Here’s a video walking you through the steps to request access: https://youtu.be/8i0QzzkBoIl). Therefore, below please find a few helpful tips to help us all navigate this process smoothly:

Slack Channel Etiquette

Search before posting.

  • Slack is intended to be our community’s knowledge Try to searchSlack first before asking someone to find answers.

Socialize your availability for other users.

  • Use Do Not Disturb mode and turn on snooze notifications if you’re Your colleagues will receive a notification that you are busy.

  • Edit your profile status to indicate if you’re away and for how long (e.g. Joe Smith > 12/01).

Best Practices for Using ‘SOG Data Source’ Slack Channel

Please use the following emoji guide:

Please begin your post with the following emoji for SOG Data Source requests:

1

Begin your post with this if you have a question you would like to post to the SOG Data Source Slack channel
2

Begin your post with this for SOG Data Source requests
3

The SOG Data Source Slack Team will post this emoji to indicate that we’ve seen your inquiry/request and will respond ASAP.
4

The SOG Data Source Slack Team will post this emoji after the final response is provided to your inquiry/request. 
5

The SOG Data Source Slack Team will post this emoji for announcements.

We encourage you to spend some time exploring Slack on your own (Please feel free to check out the getting started guide and learn how to use Slack). If you have questions about our workspace, please post in the SOG Data Source channel in Slack (Remember to use the question mark emoji at the beginning of your question). If you have general questions about Slack, their Help Center is a great resource.

Thank you,

SOG Data Source Team


HTML
<style>#title-text { display:none !important; }

.wiki-content h1 {
color:#0a173a;
font-size: 16px;}

.wiki-content h2 {
color:#435947;
font-size: 17px;}
</style>



...