This wiki has undergone a migration to Confluence found Here
Difference between revisions of "V3 PubProcess - Prepare Source Files"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| + | __NOTOC__ | ||
==02...Prepare Source Files For Publication== | ==02...Prepare Source Files For Publication== | ||
| − | The various content files repaired by the Work Groups must be preprocessed in order to make them useful in the publication. For example, the domain content must be extracted( as an XML file) from the publication database; the Visio " | + | The various content files repaired by the Work Groups must be preprocessed in order to make them useful in the publication. For example, the domain content must be extracted( as an XML file) from the publication database; the Visio "vsd" files from HL7's RMIM Designer must be processed to create appropriately sized graphics, and a hyper-linked HTML "map" to drive graphic navigation; etc. This section documents the processes used in preprocessing these files. |
===02.10...PubDb Extract=== | ===02.10...PubDb Extract=== | ||
| + | This is the process that exports "domain xml" from the HL7 Publication data base (PubDb). The process is a part of the RoseTree tools. | ||
===02.20...Extract Graphic(s)=== | ===02.20...Extract Graphic(s)=== | ||
| + | This process provides for the extraction of "png" files for the static model designs and for "thumb-nail" graphics of same. | ||
===02.30...HTML Overlay Maps=== | ===02.30...HTML Overlay Maps=== | ||
| + | This process builds an html "map" (overlay) that works with the extracted PNG files to provide clickable-graphics for navigating to details of the static model designs. | ||
===02.40...Position all files=== | ===02.40...Position all files=== | ||
| + | The final processes of this section take the variety of source files received from a Work Group (or created by preceding extraction steps) and places them in the directories in which the V3 Generator and Publishing processes expect to find them. | ||
| + | |||
| + | :'''Defined Processes''' (Eclipse '''''Target''''' or '''''BAT''''' file): | ||
| + | :*'''''02.10...PUBDB Extract'''''' Extracts the content from all PubDbs found in the databases subdirectory of '''all domains''' and places the result in generator/InputFiles/DynamicModelFiles. It also copies (and over-writes) the extracted content for the domains in '''''domains.active''''' and '''''domains.support''''' back to the input/domains/uvnn directories. | ||
| + | :*'''''02.20...EXTRACT Visio Graphics and Maps''''' Actually combines steps 02.20 and 02.30. It copies the RMIM Designer Visio (vsd) files to output/processable/hmdvsd/vsd directory and the corresponding Visio xml files to generator/InputFiles/VisioModelXmlFiles. Then it processes the vsd files to extract the graphics, thumbnails and an html overlay map. These outputs are stored in output/processable/hmdvsd/Editable and output/processable/hmdvsd/Editable/images. (The domain-build processes will move each domain's files to its output directories just before the domain is built.) | ||
| + | :*'''''02.40...POSITION Domain Source - XML and Visio''''' Copies PubXML from input to the V3 Generator/InputFiles/DynamicModelFiles and domain Visio files to output/processable/hmdvsd/vsd. This process is redundant if both steps 02.10 and 02.20 have just been run. It is used when the Generator source has been cleared, and needs to be re-freshed from input, even as the original extraction remains valid. | ||
| + | :**''''' 02.41...Position Domain XML Source''''' Is the subset of 02.40 that copies PubXML to generator/InputFiles/DynamicModelFiles (There is no bat file for this.) | ||
| + | :**''''' 02.42...Position Domain Visio''''' Is the subset of 02.40 that copies Visio vsd files to output/processable/hmdvsd/vsd and Visio xmlfiles to generator/InputFiles/DynamicModelFiles. (There is no bat file for this.) | ||
| + | |||
| + | |||
{{to-top}} | {{to-top}} | ||
Revision as of 19:29, 12 August 2010
02...Prepare Source Files For Publication
The various content files repaired by the Work Groups must be preprocessed in order to make them useful in the publication. For example, the domain content must be extracted( as an XML file) from the publication database; the Visio "vsd" files from HL7's RMIM Designer must be processed to create appropriately sized graphics, and a hyper-linked HTML "map" to drive graphic navigation; etc. This section documents the processes used in preprocessing these files.
02.10...PubDb Extract
This is the process that exports "domain xml" from the HL7 Publication data base (PubDb). The process is a part of the RoseTree tools.
02.20...Extract Graphic(s)
This process provides for the extraction of "png" files for the static model designs and for "thumb-nail" graphics of same.
02.30...HTML Overlay Maps
This process builds an html "map" (overlay) that works with the extracted PNG files to provide clickable-graphics for navigating to details of the static model designs.
02.40...Position all files
The final processes of this section take the variety of source files received from a Work Group (or created by preceding extraction steps) and places them in the directories in which the V3 Generator and Publishing processes expect to find them.
- Defined Processes (Eclipse Target or BAT file):
- 02.10...PUBDB Extract' Extracts the content from all PubDbs found in the databases subdirectory of all domains and places the result in generator/InputFiles/DynamicModelFiles. It also copies (and over-writes) the extracted content for the domains in domains.active and domains.support back to the input/domains/uvnn directories.
- 02.20...EXTRACT Visio Graphics and Maps Actually combines steps 02.20 and 02.30. It copies the RMIM Designer Visio (vsd) files to output/processable/hmdvsd/vsd directory and the corresponding Visio xml files to generator/InputFiles/VisioModelXmlFiles. Then it processes the vsd files to extract the graphics, thumbnails and an html overlay map. These outputs are stored in output/processable/hmdvsd/Editable and output/processable/hmdvsd/Editable/images. (The domain-build processes will move each domain's files to its output directories just before the domain is built.)
- 02.40...POSITION Domain Source - XML and Visio Copies PubXML from input to the V3 Generator/InputFiles/DynamicModelFiles and domain Visio files to output/processable/hmdvsd/vsd. This process is redundant if both steps 02.10 and 02.20 have just been run. It is used when the Generator source has been cleared, and needs to be re-freshed from input, even as the original extraction remains valid.
- 02.41...Position Domain XML Source Is the subset of 02.40 that copies PubXML to generator/InputFiles/DynamicModelFiles (There is no bat file for this.)
- 02.42...Position Domain Visio Is the subset of 02.40 that copies Visio vsd files to output/processable/hmdvsd/vsd and Visio xmlfiles to generator/InputFiles/DynamicModelFiles. (There is no bat file for this.)
