help please

courses/14530/assignments/196270 A real data store requires real data. And the acquisition of real data can expose (still morel) design refinements for a physical design. 5o: Research data sources for your focus of interest, and collect (or compose from your own experience) multiple records of data for your entities. You may use EARe Studio, a text editor, or a productivity app such as a spreadsheet app, to compose your data. The resulting CSV file must open for properly in a common spreadsheet app, with attribute values in their associated columns. For the validated physical design+sample data from Project 2 : - Add several records (rows) of realistic data under each entity Tips (general): - Refer to EARe Depths for notational conventions for entity data - To set up the CSV data structure each record requires, you may compose value lists within EARe Studio of course, or you may copy your entire EARe design to a text editor or spreadsheet application; commaseparated attribute names form the "headers" for the field columns! - Remember to put a blank fine between your entity data lines and the next entity definition line, for readability Tips (data values): - Study the generated data tables to ensure each data value makes sense for its attribute and has no !!tagged data warnings. As needed, refine data values to include proper values or the markers or - For 1:1 relationships the designer's intent may be inferred: either side with cardinality "required" or with a relationship description (suggesting a meaningful "ownership") should have a value, the other side's value is (or else it's redundant: why?)