| 34 | | Benefits of using ISO 15926-4: |
| 35 | | |
| 36 | | * It's already there. (Creating a taxonomy of terms for something as complex as a petrochemical plant or refinery is not trivial.) |
| 37 | | * It's there next time too. (You don't have to keep reinvent it next time. Re-use is easier every time you use it.) |
| 38 | | * Other use it too. (When you share information with a partner that has used ISO 15926-4 before, the infrastructure is already in place. Both of you will have less adjusting to do.) |
| 39 | | |
| 40 | | |
| 41 | | === [wiki:ISO15926HowTo_Tutorial_Spreadsheet Creating a Mapping Spreadsheet] === |
| 42 | | |
| 43 | | The first step is to look at the three sets of data and create a cross-reference list for each table. We want to be able to show equivalent database rows in the same row of the list. A spreadsheet is an excellent medium. |
| 44 | | |
| 45 | | |
| 46 | | === [wiki:ISO15926HowTo_Tutorial_RDSWIP_01 Mapping With the RDS/WIP] === |
| 47 | | |
| 48 | | Basically, your task here is to search for ISO 15926-4 class that most closely matches the meaning of each of the column names in your three databases. The first thing you will notice is that the best choice is not immediately apparent. In the sample spreadsheet below, some of the data rows have more than one choice. Look at a few of them to see what the differences are. |
| 49 | | |
| 50 | | === [wiki:ISO15926HowTo_DiscoverTheRightClass Discovering the Right Class] === |
| 51 | | |
| 52 | | Here are some guidelines for selecting the best class: |
| 53 | | |
| 54 | | |
| 55 | | The sample spreadsheet below has had the duplicates removed, with the best choice left. |
| 56 | | |
| 57 | | Sample Spreadsheet |
| 58 | | * attachment:MappingSpreadsheet_Second.xls |
| 59 | | |
| 60 | | === [wiki:ISO15926HowTo_Tutorial_RDSWIP_02 Resolving Differences] === |
| 61 | | |
| 62 | | Some ideas for resolving differences. |
