Page Comparison

...

...

• object components are included as first-class objects if and only if there are multiple components for parent object
• object components should have componentID (objectID) that does not conflict with any parent objectID: we can prepend "c" to the componentID to ensure this, per Michael (1/12/12)
• many object components have a non-unique componentNumber (objectNumber), duplicated by other components and/or parent object; these values are OK to import as-is, per Michael (1/12/12)
• "componentType" field does not need to be imported, per Michael (1/12/12)
• "inscribed" field has only a few entries, which can be updated manually after data migration, per Michael (12/15/11)
• "dimensions" field will be handled by a separate extract (John Lowe is working on this as of 1/9/12)
• DONE: add 6 new custom fields: pahmaCollection, objectStatus, pahmaTms2003DataSource, pahmaTmsLegacyDepartment, inventoryCount, portfolioSeries
• DONE: add controlled list options for 5 of these new fields (all except inventoryCount)
• DONE: nagpraInventoryName field values need to be transformed to match option ID values in existing controlled list
• DONE: add isComponent field for indicating components
• June 12, 2012: Inventory Count now coming from two fields.
• June 12, 2012: Object Status now a repeating field so not using pahmaObjectStatus in this view

Object-Object Relationships extract

...

SELECT
 CAST(o.objectID AS VARCHAR) objectID,
 t.TextEntry notes
FROM
 TextEntries t
 JOIN Objects o ON t.ID = o.objectID
 JOIN TextTypes tt ON t.TextTypeID = tt.TextTypeID
WHERE
 t.tableID = 108
 AND o.IsVirtual = 0 AND o.IsTemplate = 0
 AND t.TextTypeID = 96
;

notes

Object Status

field mapping

sql query

notes