The point isn’t necessarily to create the task, “enter the expected content values into the metadata repository” (although that would be a good one), but rather to ensure that expected content is at minimum part of the test case definition. extracted and stored in the metadata repository later. Eventually it will become easier to just put the details into the repository in the first place, but you need to make the barrier to adoption super-low.
I always make the following offer whenever I talk with a india whatsapp number data project team: if you want to write the data element definitions in crayon on a napkin or whatever, I’ll type them into the repository. That’s the least you should be willing to do to facilitate the work of your customer.
Process integration completes your bridge across the data chasm. Maybe it’s just a rickety swinging rope bridge, but it’s a start.
And now may be the most precarious point of the whole journey.
You can begin taking advantage of some of the great resources that live on this side of the data chasm, but please, please, please don’t rush headlong into new processes, deliverables, requirements, governance councils, and tools. Don’t neglect the connections that you worked so hard to establish. Continue to find and nurture new allies. Continue to focus on your customer. Success begets success.