This message was deleted.

What do you think @high-family-51768 + @rapid-yak-26508?

Also adding @fancy-megabyte-9510 @miniature-bird-71534 @billions-fish-10893 @plain-balloon-39336 and @chilly-pillow-52933

Hi @bright-magazine-87007, in my opinion, It depends on the size of your company and your data team organization. If data people are decentralized (data engineers and data analysts in every team) then the secoda management is decentralized among all these people (Or one dedicated people per team). On the other hand, if there is a unique data team, then the content creation is centralized in this team. On our side, we are only two people on Data team. Only the two of us create content (table docs, dictionnary entry ..). Secoda documentation is the last step of our implementation flow, either it's about a looker dashboard, dbt model, ... All of our colleagues can then access the content we created and search for documentation. Hope it helps 🙂

Hi @bright-magazine-87007 Ours leans towards the first option, the responsibility is shared across the different teams within our data team. For example - if an analyst creates a dashboard/table, they ensure its documented, same with if an analytics engineer creates a table…It is only the engineers that are excluded from the primary task of maintaining metadata in Secoda and this has worked well for us so far