metus_dataexchange

The Metus data exchange module provides bi-directional data exchange between Teamcenter and Metus.

The metus_import function will be used to read a mapping.xml file and a data.xml file, parse their content and perform the corresponding import in Teamcenter.

The metus_export function will be used to read a mapping.xml file and a objects.txt file, and each of the listed item will be exported as appropriate in the interchange format.

In addition, metus_dataexchange can be used as a command-line tool to perform the import (-m import mapping.xml data.xml) or the export (-m export mapping.xml data.xml objects.txt) from the shell.

Changelog

• 0.1 - proof-of-concept, doesn't yet import or export anything
• 0.2 - import from data.xml items and create links
• 0.3 - import from data.xml assemblies
• 0.4 - after import, update data.xml with generated item IDs
• 0.5 - attach created items in a folder
• 0.6 - export of items and properties in data.xml
• 0.7 - export of links in data.xml
• 0.8 - export of assemblies in data.xml
• 0.9 - import filtering of item types, link types and structure
• 1.0 - export filtering of item types, link types and structure
• 1.1 - upgrade to Ruby 2.2, last version working with itk 0.7.0
• 1.2 - upgrade to itk 1.1 (+ itk100001, itk110002)
• 2.0 - consider update key in the options
• 2.1 - upgrade to itk 1.4 (unlock, date_t)
• 2.2 - upgrade to itk 1.5.1 + checkpoint release
• 2.3 - upgrade to itk 1.7 (ItkUtils and AddOnsSyntax migrated there)
• 2.4 - upgrade to itk 1.8 (...EXT modules)
• 3.0 - use protodataplx gem (separate packaging of dataseq.rb)
• 3.1 - upgraded to Ruby 2.4

See also https://git.bct-technology.com/cboos/metus_dataexchange