Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Partitioning Medium and Support - data consistency #8

Open
SamiNorling opened this issue Apr 19, 2019 · 1 comment
Open

Partitioning Medium and Support - data consistency #8

SamiNorling opened this issue Apr 19, 2019 · 1 comment
Assignees
Labels
EMu Need to adjust/clean source data. simple solution Data is modeled, but could possibly benefit from more complexity.

Comments

@SamiNorling
Copy link
Contributor

In EMu, Medium and Support are catalogued in two tables, and outputs in XML as:

<table name="Medium">
  <tuple>
    <atom name="PhyMedium">fabric</atom>
  </tuple>
  <tuple>
    <atom name="PhyMedium">plastic</atom>
  </tuple>
</table>
<table name="Support">
  <tuple>
    <atom name="PhySupport">structural foam</atom>
  </tuple>
</table>

Unfortunately, data is inconsistent. For example:

<table name="Medium">
  <tuple>
    <atom name="PhyMedium">paper</atom>
  </tuple>
</table>
  • Paper should be listed as a Support, not Medium

or

<table name="Medium">
  <tuple>
    <atom name="PhyMedium">plastic</atom>
  </tuple>
  <tuple>
    <atom name="PhyMedium">paint</atom>
  </tuple>
</table>
<table name="Support">
  <tuple>
    <atom name="PhySupport">steel</atom>
  </tuple>
  <tuple>
    <atom name="PhySupport">plastic</atom>
  </tuple>
  <tuple>
    <atom name="PhySupport">paint</atom>
  </tuple>
</table>
  • plastic and paint are repeated under Support, also listed in Medium

How will incorrect data affect partitioning of Support and Medium?

If too complicated, can simplify represent Medium(s) and Support(s) with made-of syntax. If we go this route though, will need to avoid duplication of made-of statements when values are repeated either within a single table or across both tables (e.g., XML example directly above).

@SamiNorling SamiNorling added the EMu Need to adjust/clean source data. label Apr 19, 2019
@SamiNorling SamiNorling self-assigned this Apr 19, 2019
@SamiNorling
Copy link
Contributor Author

Clean-up to date:

  • de-duped repeating values in Medium and Support (only repeating within table, not across tables)

Current model:

  • simple made_of array pulling distinct values between Medium and Support

Future:

  • Will possibly re-work the model to partition the support as a part, but current data would output some odd statements.

@SamiNorling SamiNorling added the simple solution Data is modeled, but could possibly benefit from more complexity. label Apr 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EMu Need to adjust/clean source data. simple solution Data is modeled, but could possibly benefit from more complexity.
Projects
None yet
Development

No branches or pull requests

1 participant