Вы находитесь на странице: 1из 4

------------Legal Notices ------------Copyright, 2001, Intergraph Corporation. All Rights Reserved.

Including software, file formats, and audio-visual displays; may only be used pursuant to applicable software license agreement; contains confidential and proprietary information of Intergraph and/or third parties which is protected by copyright and trade secret law and may not be provided or otherwise made available without proper authorization. RESTRICTED RIGHTS LEGENDS Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of The Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c) (1) and (2) of Commercial Computer Software--Restricted Rights at 48 CFR 52.227-19, as applicable. Unpublished--rights reserved under the copyright laws of the United States. Intergraph and SmartPlant are registered trademarks of Intergraph Corporation. Other brands and product names are trademarks of their respective owners. Intergraph Corporation Huntsville, Alabama 35894-0001 -------------------End of Legal Notices -------------------------------------Version Information ------------------Product: Tag Merge utility Version: 01.00.00.00 Date: 01-Feb-2001 Tag Merge is a utility to allow users to merge multiple tag files into a single tag file. This utility enables users to identify duplicate tags and handle the resolution of these duplicates in a variety of ways as defined below. This utility was created based upon functionality / workflows that were dictated by SmartPlant Review customers. --------------------------End of Version Information ---------------------------------------------------------Installing and Running Tag Merge -------------------------------The Tag Merge utility is made up of a single executable file accompanied by a readme.txt file which will help the user make use of the utility. The utility can simply be copied to any directory and run as any other executable.

--------------------------------------End of Installing and Running Tag Merge ---------------------------------------------------Helpful Hints -------------- To enter data into editable fields of the Input list, select a row, then single click the field to be changed. - The Tag Merge utility works on ranges of tags in files, but is not a normally used for individual tag manipulation. - It is useful to name the .tag files to be merged something meaningful. This h elps uniquely identify files in the input list which would otherwise be named the same. - The user should avoid editing .tag files by hand. - Range and Start With column data may be reset to their original values by set ting the Offset column value for that file to zero. --------------------End of Helpful Hints -------------------------------Limitations ------------ Any tags in a .tag file may be dependent upon another tag for view related da ta. Therefore, tags that are rearranged from their original order may display som e differences in their appearance. - The utility assumes there are no duplicates within a particular .tag file. Th e .tag file must be valid before merging. - Values allowed in the Offset column are limited to 100000. ------------------End of Limitations ----------------------------------Example Workflow ----------------Multiple tag files used with collaboration: This workflow is intended to show one method of allowing the tag merge utility to assist the user with sharing tag data in an environment using collaboration. ------------------------------------------------------------------------------Given Setting: 3 users creating SmartPlant Review Tags for the same project. Each in a different city... Houston, London, Tokyo. Each user creates tags 1 through 5, each tag having unique information. Users want to collaborate, so they must merge the tag data into one file. Since all tags in a given file must be unique in their tag number, the tag files are merged with the tag merge utility to be sure there are no duplicates. ------------------------------------------------------------------------------Rename the .tag files from each location to Houston.tag, London.tag, and

Tokyo.tag. Set the Duplicate handling mode to Abort Merge. Check the Designation box. Type a text string into the Designation column for each file, ie."H","L","T" to represent the locations. Leave the "Offset" value of the file received from Houston blank, set the "Offset" value of the file received from New Orleans to 100, set the "Offset" value of the file received from Tokyo to 200. The resulting .tag file will contain 15 tags numbered 1 through 5, 101 through 105, and 201 through 205. After the collaboration, each site is sent a copy of the tag file containing all 15 tags for further tag input. Each site user adds one unique tag to the tag file resulting from the collaboration. This creates 3 files with tags numbered exactly the same, but having unique data in the tag. Each will contain 16 tags numbered 1 through 5, 101 through 105, and 201 through 206. The intent of the workflow is to once again merge the 3 tag files to prepare for another collaboration session in such a way that there are no duplicates and none of the tags are lost. One solution to merge the files can be the following: Merge the 3 unique .tag files with a copy of the .tag file that resulted from th e first collaboration. This file does not contain any tags other than those from the first collaboration session. This will allow each of the new tags to be reordered into a range that is associated with a particular user or group of users. In this example, Houston is associated with the range 1 through 100, London is associated with the range 101 through 200 and Tokyo is associated with the range 201 through 300. To do this, change the "Start With" value for each of the tag files to 206 leaving the tag file created during the collaboration as it is. Change the "Offs et" values for each of the new tag files so the newly created tag(s) will fall on the next available number in the range associated with the particular location. For the file from Houston, use an offset of -200. For the file from London use and offset of -100. Leave the offset for the file from Tokyo blank. This should result in tags numbered 1 through 6 representing the tags created by the user in Houston, 101 through 106 representing the tags created by the user i n London and 201 through 206 representing the tags created by the user in Tokyo. -----------------------End of Example Workflow -------------------------------------------------User Interface Description --------------------------Text additions: Designation - If this box column will of each tag Filename - If this box

is be in is

checked, the text strings in the Designation appended to the beginning of the text section the particular file. checked, the text strings displayed in the File

name column will be appended to the beginning of the text section of each tag in the particular file. If a Designation string exists, the File name string will appear just after the Designation string. Duplicate handling: Abort merge - If duplicate tag numbers are found, the conflicting files will be indicated in the "Results:" section on the dialog. The user will then have a chance to make changes to the input data and try again to successfully merge files. - If duplicate tag numbers are found, tag renumbering will be do automatically. Tag ranges will be changed by first sorting the files by tag minimum range values. Entire ranges are separated by finding the next minimum range value which falls on a boundary that keys on the 100's digit. Ranges with lower minim um Remove d. Tag duplicates will be removed from the merge. Files appearing nearest to the top of the list will have presidence, causing files listed after it to have their duplicate tags removed. Input Tag(.tag) Files: Add button - Displays a file open dialog to allow users to select multiple files for adding to the file input list. Delete button - Removes the selected file or files from the input list. Offset - (editable) Affects the beginning of the numeric sequence of tags in the file to be adjusted. The offset will be added to each tag number in the file. Range - (non editable) Displays the numeric range of tags in a file. Start With - (editable) Allows a starting point to be created for each file. Any tag in a file with a number lower than the this starting point will be removed from the merge. Designation - (editable) Accepts a text string to be appended to each tag found in the associated input file. File Name - (non editable) The filename of a particular input file. Output Tag(.tag) Files: Standard filename browse for the name of the resulting merge of input files. Results: Displays useful information regarding the status of the merge process. Merge button ring Close button - Will cause an attempt to merge the list of input files conside the associated data. - Closes the dialog. range values will have precedence. - If duplicate tag numbers are found, tags will not be renumbere

Renumber ne

---------------------------------End of User Interface Description ----------------------------------

Вам также может понравиться