{"id":300,"date":"2021-06-02T16:16:07","date_gmt":"2021-06-02T16:16:07","guid":{"rendered":"https:\/\/blog.mozilla.org\/data\/?p=300"},"modified":"2021-06-02T16:16:07","modified_gmt":"2021-06-02T16:16:07","slug":"this-week-in-glean-glean-dictionary-updates","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/data\/2021\/06\/02\/this-week-in-glean-glean-dictionary-updates\/","title":{"rendered":"This week in Glean: Glean Dictionary updates"},"content":{"rendered":"

(\u201cThis Week in Glean\u201d is a series of blog posts that the Glean Team at Mozilla is using to try to communicate better about our work. They could be release notes, documentation, hopes, dreams, or whatever: so long as it is inspired by Glean.) All \u201cThis Week in Glean\u201d blog posts are listed in the TWiG index<\/a> (and on the Mozilla Data blog<\/a>).<\/p>\n

Lots of progress on the Glean Dictionary since I made the initial release announcement<\/a> a couple of months ago. For those coming in late, the Glean Dictionary is intended to be a <\/span>data dictionary<\/span><\/a> for applications built using the <\/span>Glean SDK<\/span><\/a> and <\/span>Glean.js<\/span><\/a>. This currently includes Firefox for Android and Firefox iOS, as well as newer initiatives like <\/span>Rally<\/span><\/a>. Desktop Firefox <\/span>will<\/span><\/em> use Glean in the future, see <\/span>Firefox on Glean (FoG)<\/span><\/a>.<\/span><\/p>\n

Production URL<\/span><\/h2>\n

We\u2019re in production! You can now access the Glean Dictionary at <\/span>dictionary.telemetry.mozilla.org<\/span><\/a>. The old protosaur-based URL will redirect.<\/span><\/p>\n

Glean Dictionary + Looker = \u2764\ufe0f<\/span><\/h2>\n

At the end of last year, Mozilla chose <\/span>Looker<\/span><\/a> as our internal business intelligence tool. Frank Bertsch, Daniel Thorn, Anthony Miyaguchi and others have been building out first class support for Glean applications inside this platform, and we\u2019re starting to see these efforts bear fruit. Looker\u2019s explores are far easier to use for basic data questions, opening up data based inquiry to a much larger cross section of Mozilla.<\/span><\/p>\n

I recorded a quick example of this integration here:<\/span><\/p>\n