Hello! I've been looking at extending the built-in metadata using the [No Code Metadata](https://datahubproject.io/docs/advanced/no-code-modeling) instructions, but it seems the [MCP/MCL stuff](https://datahubproject.io/docs/advanced/mcp-mcl) might make some changes to that process. Do the steps remain the same? Also, are all the old topics (MCE, MAE, FCE) and new topics (MCP, FMCP, MCLV, MCLT) required for a new deployment? Thanks!

Hi @blue-megabyte-68048 , yes all the topics are required for the new deployment. In terms of steps to add a new entity, they remain the same for now. We have a simplification planned soon, but not ready right now.

So for now, no need to worry about the

entity-registry.yml

that I'm seeing mentioned?

Yes no need to worry about it yet :) in the future you will be able to skip adding the aspect to the snapshot Union and add it to the entity registry instead.

This feels like it might be a big ask, but is there any chance someone from the datahub team could create a branch with an entirely new example Entity? The docs example uses the Dashboard entity, so it's been very confusing trying to tease apart what is actually required to add an entirely new Entity. I only ask on the small chance that it isn't as big an effort as it sounds 🙂

That is a great suggestion!

Will it cause problems if custom entities have a different pdl package from

com.linkedin.*

?

There is a model scanner that looks for aspects and entities and I think by default it scans within the

com.linkedin.*

namespace

Okay thanks!

Hey Greyson! Glad that you're trying to add an Entity. Happy to find some time to guide you through it, but agree a dedicated PR / branch showcasing this would be ideal... The process should remain the same as before give the new topics

Thanks, I'll reach out if I get stuck!