Update Unique Community Contributors per Month yml file to Tableau

Why is this change being made?

The central data team is helping with the migration of Unique Wider Community Contributors per Month (see issue). In order to do that we need to update this data file to point the .yml to the Tableau visual, instead of the Sisense visual. This changes the code for just this visual to point to Tableau. See here where we will make any needed updates to the handbook page itself, but this should remain the same because it stays in the same file with the same name. It will update this handbook page.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Updated using this handbook page.

Workflow

1. Go to the handbook page you want to update the PI's for, and edit the page. There you will find the name of the file that you are looking to update. It will look something like this: {{% performance-indicators "developer_relations_department" %}}

2. Go to the Gitlab.com repository and search "find file" for that file name, it should be a yml

3. Update the yml file according to these guidelines. Remember anything that is completely "public" needs to follow steps 4-5 below!

4. For public views in the public handbook (no sign in needed), make sure that you follow these steps to tag the workbook as public, get it moved over to the public Tableau site, and get the URL from the list of publicly embeddable workbooks. Our license and viewer agreement requires that those public views are coming from the "public" version of our Tableau cloud. Note the process takes about 24hr

   1. To do this, go to the workbook, select the "..." for more settings, and select "Tag". Then add "Public". Here is an example of a workbook that has the Public tag and is available for embedding.
      • You will also need to make the data source an "extract" instead of "live" connection because otherwise you would need to use different credentials for it to work on the different site, and those credentials are not self-serve. Here are guidelines for extracts.

5. It will show up in this list once it is migrated and ready. Use the share URL from here in your embedding information. Here is where to find the URL's that are available to embed from the public site.

   

6. Workflows:

   1. For private charts that require sign-in: From the handbook page, find the file name -> Search the repository for the yml file -> update the yml file to point to the Tableau workbook. Watch out for your tabs and spaces, they need to match the formatting exactly!
   2. For public charts in the public handbook: Find the file name -> search the repository for the yml file -> Tag the affected workbooks as "Public" -> Get their URL from the list of publicly embeddable views -> update the YML file

7. Feel free to reach out to me @annie-analyst if you need help with this

---