Data modeling Issue for Moqui custom application -

we working on 1 custom project management application on top of moqui framework. our requirement is, need inform changes in ticket developers associated project through email.

currently using workeffortparty entity store parties associated project , partycontactmech entity store email addresses. here need iterate through workeffortparty , partycontactmech everytime fetch email address need send emails changes in tickets every time.

to avoid these iterations, thinking of giving feature add comma separated email addresses @ project level. project admin can add email addresses of associated parties or mailing list address needs send email notification ticket change.

for requirement, studied around data model didn't got right place store information. need extend entity or there best practice this? requirement useful in project management application. appreciate on data modeling problem.

the best practice use existing data model elements available. having normalized data model involves more work in querying data, more flexibility in addressing wide variety of requirements without changes data structures.

in case joined query can list of email addresses in single query based on project's workeffortid. if dealing massive data , message volumes there better solutions denormalizing source data, doubt that's case... unless you're dealing more thousands of projects , millions of messages per day basic query , iterate approach work fine.

if need go beyond easiest approach moqui use datadocument , datafeed send updates on fly elasticsearch, , use high volume queries , filtering (with arbitrarily complex filtering, etc requirements).

your question way open answer directly, data modeling complex topic , without understanding of context , intended usage there no answers. in general it's best start data model based on decades of experience , used in large number of production systems. mantle udm 1 such model.