<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://vistapedia.com/index.php?action=history&amp;feed=atom&amp;title=FILE_8925.1</id>
	<title>FILE 8925.1 - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://vistapedia.com/index.php?action=history&amp;feed=atom&amp;title=FILE_8925.1"/>
	<link rel="alternate" type="text/html" href="https://vistapedia.com/index.php?title=FILE_8925.1&amp;action=history"/>
	<updated>2026-05-02T14:18:26Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.0</generator>
	<entry>
		<id>https://vistapedia.com/index.php?title=FILE_8925.1&amp;diff=16158&amp;oldid=prev</id>
		<title>DavidWhitten: Created page with &quot;== File of Files entry == &lt;pre&gt; NUMBER: 8925.1                          NAME: TIU DOCUMENT DEFINITION APPLICATION GROUP: GMTS  DESCRIPTION:   This file stores Document Definit...&quot;</title>
		<link rel="alternate" type="text/html" href="https://vistapedia.com/index.php?title=FILE_8925.1&amp;diff=16158&amp;oldid=prev"/>
		<updated>2015-05-07T16:22:20Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;== File of Files entry == &amp;lt;pre&amp;gt; NUMBER: 8925.1                          NAME: TIU DOCUMENT DEFINITION APPLICATION GROUP: GMTS  DESCRIPTION:   This file stores Document Definit...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== File of Files entry ==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
NUMBER: 8925.1                          NAME: TIU DOCUMENT DEFINITION&lt;br /&gt;
APPLICATION GROUP: GMTS&lt;br /&gt;
 DESCRIPTION:   This file stores Document Definitions, which identify and&lt;br /&gt;
 define behavior for documents stored in the TIU DOCUMENTS FILE (#8925).  For&lt;br /&gt;
 consistency with the V-file schema, it may be viewed as the &amp;quot;Attribute&lt;br /&gt;
 Dictionary&amp;quot; for the Text Integration Utilities.&lt;br /&gt;
&lt;br /&gt;
 It also stores Objects, which can be embedded in a Document Definition&amp;#039;s&lt;br /&gt;
 Boilerplate Text (Overprint). Objects contain M code which gets a piece of&lt;br /&gt;
 data and inserts it in the document&amp;#039;s Boilerplate Text when a document is&lt;br /&gt;
 entered.&lt;br /&gt;
&lt;br /&gt;
 Warning: objects embedded in boilerplate text are looked up by multiple index&lt;br /&gt;
 (i.e. DIC(0) contains &amp;#039;M&amp;#039;). Current code (see routine CHECK^TIUFLF3) checks&lt;br /&gt;
 all present indexes to make sure object names, abbreviations and print names&lt;br /&gt;
 are not ambiguous for this lookup. If new indexes are added, this code MUST BE&lt;br /&gt;
 UPDATED to check the new index as well.&lt;br /&gt;
&lt;br /&gt;
 Some entries in this file are developed Nationally and exported across the&lt;br /&gt;
 country.  Others are created by local sites.  Entries in the first category&lt;br /&gt;
 are marked National Standard and are not editable by sites.&lt;br /&gt;
&lt;br /&gt;
 This file does NOT allow multiple entries OF THE SAME TYPE with the same name.&lt;br /&gt;
 That is, within a given Type, there are no duplicate names. (This refers to&lt;br /&gt;
 the .01 field, the Technical name of the entry.)&lt;br /&gt;
&lt;br /&gt;
 This file does not allow a parent to have items with the same name, even if&lt;br /&gt;
 the items have different internal file numbers (i.e. are different file&lt;br /&gt;
 entries).  Again, this refers to the .01 Technical name of the entry.&lt;br /&gt;
&lt;br /&gt;
 Because of ownership considerations, the file does NOT allow an entry to be an&lt;br /&gt;
 item under more than 1 parent.  If the same item is desired under more than 1&lt;br /&gt;
 parent, the item must be copied into a new entry.  There is one exception:&lt;br /&gt;
 Document Definitions of Type Component which have been marked Shared may have&lt;br /&gt;
 more than one parent.&lt;br /&gt;
&lt;br /&gt;
 The Document Definition Utility TIUF categorizes certain fields as Basic,&lt;br /&gt;
 Technical, or Upload, and displays these fields together as a group when user&lt;br /&gt;
 edits or views a Document Definition. BASIC fields include Name, Abbreviation,&lt;br /&gt;
 Print Name, Type, Personal Owner, Class Owner, Status, In Use, Shared, Orphan,&lt;br /&gt;
 Has Boiltxt, National Standard, OK to Distribute, and Suppress Visit&lt;br /&gt;
 Selection. TECHNICAL fields include Entry Action, Exit Action, Edit Template,&lt;br /&gt;
 Print Method, Print Form Header, Print Form Number, Print Group, Allow Custom&lt;br /&gt;
 Form Headers, Visit Linkage Method, Validation Method, and Object Method.&lt;br /&gt;
 UPLOAD fields include Upload Target File, Laygo Allowed, Target Text Field&lt;br /&gt;
 Subscript, Upload Look-up Method, Upload Post-Filing Code, Upload Filing Error&lt;br /&gt;
 Code, and multiples Upload Captioned ASCII Header and Upload Delimited ASCII&lt;br /&gt;
 Header.&lt;br /&gt;
&lt;br /&gt;
 The Document Definition file contains extensive, detailed field descriptions.&lt;br /&gt;
 Likewise, some protocols (File 101) used in TIU have extensive and careful&lt;br /&gt;
 descriptions in the Protocol file. Many of these descriptions are used in TIU&lt;br /&gt;
 for online help. If it becomes necessary for a national programmer to edit&lt;br /&gt;
 these descriptions, the programmer should check to make sure all online help&lt;br /&gt;
 is still displayed properly.&lt;br /&gt;
&lt;br /&gt;
 Users are expected to use the Document Definition Utility TIUF to enter, edit,&lt;br /&gt;
 and delete file entries.  In fact, the file prohibits the deletion of entries&lt;br /&gt;
 through generic Fileman Options.  It also prohibits the edit through generic&lt;br /&gt;
 Fileman of a few critical fields: Type, Status, Shared, and National Standard.&lt;br /&gt;
 Adding and Deleting (but not editing) Items is also prohibited through generic&lt;br /&gt;
 Fileman options.  Abbreviation and Print Name of OBJECTS cannot be edited&lt;br /&gt;
 through generic Fileman Options.&lt;br /&gt;
&lt;br /&gt;
 This does NOT imply that it is SAFE to use generic Fileman to edit other&lt;br /&gt;
 fields.  Users are cautioned that edit through generic Fileman bypasses many&lt;br /&gt;
 safeguards built in to the Document Definition Utility and can create havoc&lt;br /&gt;
 unless the user THOROUGHLY UNDERSTANDS the File and its uses.&lt;br /&gt;
&lt;br /&gt;
 If users find needs which are not met through TIUF, please communicate them to&lt;br /&gt;
 the TIU development team.&lt;br /&gt;
&lt;br /&gt;
                                *****************&lt;br /&gt;
&lt;br /&gt;
 WARNING: Using generic Fileman options to edit entries can cause SERIOUS&lt;br /&gt;
 database problems.&lt;br /&gt;
&lt;br /&gt;
                                ****************&lt;br /&gt;
  GLOBAL NAME (c): ^TIU(8925.1,         ENTRIES (c): 861&lt;br /&gt;
  DD ACCESS (c): @                      RD ACCESS (c): @&lt;br /&gt;
  WR ACCESS (c): @                      DEL ACCESS (c): @&lt;br /&gt;
  AUDIT ACCESS (c): @                   VERSION (c): 1.1&lt;br /&gt;
  DISTRIBUTION PACKAGE (c): C9CTIU CONTINUITY OBJECTS&lt;br /&gt;
  COMPILED CROSS-REFERENCES (c): NO&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[category:FILE]]&lt;/div&gt;</summary>
		<author><name>DavidWhitten</name></author>
	</entry>
</feed>