Hi folks I am the Analytics Engineer for CloudTrucks. We are looking at various data lineage/catalog/metrics definition tools and after a demo with @limited-solstice-12595 I am demoing the app with sample data. I'd love to hear your favorite tips and tricks and why you chose Secoda over other options. ☁️ 🚚

Welcome to Secoda. This platform has the fastest and most helpful support I've ever experienced. It's also pretty cool to see feature requests make it to the roadmap and then get included in their surprisingly frequent product releases. I'm pretty invested in streamlining the non-technical end user experience for understanding our company data. From an administrative time-cost standpoint, it's super nice to have features to document technical notes and non-technical enablement in one application. Even better that you can separate it out easily enough that you aren't overwhelming people who don't code with the same kind of notes you want to have on hand for working with engineering. I feel like a lot of documentation tools are either geared toward a technical or a non-technical end user, so I'm a big fan that Secoda lets me write for both audiences in one place. It's definitely made for data teams which live between worlds instead of just repurposing typical engineering documentation.

Hey @miniature-artist-10059 Theres a few things that we love about Secoda. Organization is done well here, I would look at the collections feature to be able to group things easily into how it works for your organization, then tag definition, resources, dashboards into that collection tag. This will help users that may not be data oriented to find what they need easily. With Secoda, you are getting some tier 1 support at all times. They are very focused on their users and want to solve problems. With other companies, we didn’t feel that we would get the attention a customer deserves. With Secoda, to this day, they are always helping us in timely manners, so we experience little down time. They are open to feedback and feature requests, so it makes it really accessible to get things you want added in given it adds value overall. Writing things in markdown / notion style is beautiful, and def caters towards curators of data. Finally, we are using this tool as a core aspect of our data governance plan and path to self serve analytics (you cant build self serve out if information isnt accessible to your stakeholders). Theres so much to say but I will say specifically you would be investing in a company that is invested in your growth as much as theres, and i have seen it first hand.

+1 to Wills point about collections. I've seen some really sweet setups that use collections nicely to organize all the different data knowledge in one place. My number one tip is to try to create a structure for collections based on 1) Teams 2) Data source 3) KPI's. @witty-monitor-28236 and @victorious-computer-74029 are the experts at this IMO

Hi Justin, On our side we followed exactly Etai advices. We have first big collections like Alma Key metrics, Alma key terms where we gather all information that should be shared with new comers. And then all definitions/dashboards/tables are grouped in "Team" collections (Operations, Marketing, Finance, Product Dev, ....). Finally I'm thinking about a third granularity that would be "Project" collection. All information related to one project are gathered in one collection. It will be a temporary tag until the project is completed 🙂