269 | | of the hospital as the location name. |
| 269 | of the hospital as the location name. It will be helpful for this if our schema |
| 270 | uses standardized field names, like "name". Then, for instance, if we receive a |
| 271 | primary table with a name column, and linked tables without a name column, but where |
| 272 | we have a name field, we could have a general rule to use the primary's name. We |
| 273 | should also support mappings that call for the same input value to be inserted in |
| 274 | multiple destinations. (For a UI where a user is constructing a schema mapping, |
| 275 | we should remember to allow the user to map one input field to multiple destinations. |