IMAmuseum / LinkedArt

Transforming IMA objects, creators, and exhibitions data to the Linked Art data model.
https://linked.art
8 stars 4 forks source link

Partitioning Medium and Support - data consistency #8

Open SamiNorling opened 5 years ago

SamiNorling commented 5 years ago

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>

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>

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 commented 5 years ago

Clean-up to date:

Current model:

Future: