Hearts Prison Essay Example For Students

Paper on Summation

Sowmya SUMMATION A Detailed audit of SUMMATION Introduction The CT Summation Blaze LG item family encourages you proficiently oversee case data, for example, transcripts and reports with the advantages of full-content imaging, PDF support, electronic proof help and complete creation apparatuses. Summation to load and check DII File DII File: A DII record is an uncommonly arranged ASCII content document that can be made inside any word processor. The DII record utilizes a non-delimited, different line position. Each record closes with the picture filenames themselves. The information from the record is stacked into Summation’s Core Database and sets up the connection between the database synopses and the related pictures and OCR archives. DII FILE COMPONENTS @T (Image Tag) Required for each DII record. Must be utilized before any @C tokens for each DII record. Each occasion of a line starting with the @T token makes Summation make another database record or overwrite a current one. On the off chance that the worth that follows the @T line doesn't coordinate a current record number in the dynamic table (ordinarily either the STDTABLE or the ETABLE) at that point another record with that number is made. On the off chance that a record with that number as of now exists, Summation prompts the client to either supplant that record’s existing picture data or leave its picture data unblemished. The field ordinarily used to decide a record’s one of a kind number is either the BEGDOC# field (for the STDTABLE) or the DOCID field (for the ETABLE). This field can be changed by means of OPTIONS>DEFAULTS>IMAGING>COLUMN TO HOLD IMAGE TAG however it isn't suggested. On the off chance that there is an information layout on the database’s record number field, at that point the @T esteem must comply with the layout group. Model: The case database has an information layout confining the BEGDOC# field to the arrangement â€Å"AA000000† (I. e. alpha, alpha, numeric, numeric, numeric, numeric, numeric, numeric). A DII document with the accompanying @T values is stacked: @T RT100556 @T 998113 The principal line coordinates the layout group and another database record with a BEGDOC# estimation of â€Å"RT100556† would be made. The subsequent line is off base, so no database record for this line would be made and a blunder message would show up on-screen and furthermore be kept in touch with the mistake log. D (Default Directory) Required for each DII record that has pictures or OCR to be stacked. The @D token assigns the area where the picture file(s) for a database record is put away. The information determined after the @D is stacked into the Default Directory (DEFDIR) field of the ImgInfo table. There are 3 distinct approaches to mean the DEFDIR. 1. @I, which alludes to the default IMAGES subfolder under the case catalog. For instance, for a portable establishment, if the case were SMITH V. JONES, â€Å"@I† would approach â€Å"C:PROGRAM FILESSUMMATIONCASEDATASMITH V. JONESIMAGES. † 2. The full way to the picture file(s) area. An UNC, neighborhood, or mapped drive letter way is adequate. For instance: @D SERVER1IMAGESSMITH V. JONESVOLUME1DISK1 @D C:IMAGESSMITH V. JONESVOLUME1DISK1 @D Z:IMAGESSMITH V. JONESVOLUME1DISK1 3. @V, which alludes to the particular volume name of removable media. NOTE: Users of Summation LG/iBlaze can utilize UNC ways after the @D to determine an envelope containing pictures. @L (Long Name Entry) Summation 5. 21 Legacy Field. @L means the long name or depiction of the picture file(s). The @L esteem is stacked into the LONGNAME field of the ImgInfo Table. This tag is out of date and superfluous on present day variants of Summation (1. 0 and higher) as they bolster long picture document names. @C (Column to Link) 3 Optional token. @C is utilized to stack information into determined fields in the user’s report database. This is a helpful method to diminish the measure of information section required for the database clients. It is intended for use when a similar worth is rehashed for a gathering of records, for example, reports that all have a similar box number or creator. It isn't intended to supplant customary information passage. Hence, there is a restriction of six (6) @C codes accessible for each DII record. The language structure for utilizing the @C token is: @C For instance, to fill in the ISSUES field of the database with the worth â€Å"Mental Health,† the line would peruse: @C ISSUES Mental Health The @C line(s) ought to show up underneath the @T line for every database record. For continuous DII records where these qualities are the equivalent, you don't have to rehash the @C line. Rather, embed the following @C line in the following DII record where the information changes. To quit entering information in a field, embed a @C line with the field name following by nothing. @I (Image Location as in Case Customize) Used with the @D token. The @I esteem alludes to the picture area determined in Case Customize. The @I esteem is stacked into the DEFDIR field of the ImgInfo table. This area must be a drive letter (or UNC way for LG/iBlaze clients) and way that focuses to the index where the pictures are put away. Summation clients can choose any legitimate area or use Summation’s default area, the IMAGES subdirectory under the case index. In either case, the picture records must be replicated to this area. @V (Volume Label of Removable Media and Any Subdirectories) Used with the @D code. The @V esteem alludes to the volume mark of the removable media holding picture documents. When utilizing a volume mark, the program will look through a scope of drive letters for the particular removable media volume. The scope of drive letters to be looked can be indicated in OPTIONS>DEFAULTS>IMAGING>DRIVES HOLDING IMAGES. The volume mark can be acquired from any drive by utilizing the DIR order at the order brief or by taking a gander at the drive properties in Windows Explorer/My Computer. When utilizing the order brief, the volume name will show up at the highest point of the catalog show posting. Since most report pictures are currently put away on either neighborhood or system hard drives Summation has given an alternative to change over volume marks to catalog names for existing database records with @V picture ways. By choosing the alternative box named â€Å"Map Volume to Directory† under OPTIONS>DEFAULTS>IMAGING the volume name is changed over to an i ndex name. A drive letter or letters coordinating the area where the pictures are put away should be included the OPTIONS>DEFAULTS>IMAGING>DRIVES HOLDING IMAGES segment. For instance: DEFDIR in ImgInfo Table: @VCD_00001:01 Drives Holding Images: DE Program glances in: D: or E: drive for media with a volume name of â€Å"CD_00001. † If it finds coordinating media, it searches for a catalog there named â€Å"001† for whichever picture record or documents were indicated. @Fulltext (Lets the Database Know There is an OCR Document Attached to the Record or Records) Tells Summation that there are OCR archives joined to the record. The filenames must match the names of the pictures (excluding the augmentation), and they should be situated in a similar spot. Varieties: @FULLTEXT DOC †One OCR content document exists for every database record. FULLTEXT PAGE †One fulltext record exists for each page of the report rundown. @FULLTEXT [PAGE or DOC] is set before the @T line. Like the @C token, this announcement stays in actuality until killed by utilizing the contrary assignment. At the end of the day, on the off chance that you are utilizi ng the â€Å"PAGE† technique, turn it off by utilizing @FULLTEXT in the record that doesn't contain a fulltext document. @O (Where OCR Documents Are in the event that They Are Not in the Image Location) Used when the OCR reports are found somewhere other than the picture area as determined by the @D line of the DII record. It is put quickly underneath the @D line. This token must be utilized related to the â€Å"@FULLTEXT DOC† tag. The full way to the OCR content archive must be incorporated. Model: 5 @FULLTEXT DOC @T AB100001 @D @I @O J:docsscanned 100001. TIF This reveals to Summation that the fulltext archive for record AB100001 isn't in the default Images catalog (@I) in any case, rather can be found in J:docsscanned. The document name should at present match the picture record name. For this situation the picture record name is 100001. TIF, in this manner the OCR content record name ought to be named 100001. TXT. ; (Comment Lines) Discretionary code for each DII record. You can offer remarks in the DII document for your reference. These lines don't influence the DII load. Model: ; After this Semi-colon I can make notes for my present record Image Files Required for each DII record. The last line(s) of each DII record is consistently the picture filename(s). Oblique punctuation lines before the filenames will guide Summation to search for the records at the base of the predetermined drive be that as it may, these can for the most part be discarded. Iterators are significant discretionary coding techniques. Iterators give an approach to utilize shorthand for picture record names. This takes into consideration less content per DII record, subsequently delivering a DII document that heaps more rapidly. On the off chance that your picture records utilize a number arrangement, you can utilize iterators to show a scope of numbers, as opposed to posting each picture document independently. Reaches are just substantial when the lower number and the higher number are a similar number of digits. Records Listed Separately Example: IM00001. TIF IM00002. TIF IM00003. TIF IM00004. TIF IM00005. TIF Files Iterated Example: 6 IM000{1-5}. TIF If emphasizing records with appended full content (OCR) reports in PAGE group, be mindful so as not to surpass forces of 10 in the emphasis. Model: IM0000{01-09}. TIF IM0000{10-99}. TIF IM000{100-999}. TIF The model above will appropriately stack each of the 999 pictures and their comparing OCR full-content archives. This standard applies to the @FULLTEXT PAGE design as it were. Tokens Used in Summation’s DII File Token @APPLICATION Field Populated APPLICAT @ATTACH ATTCHIDS (Field chose for related connection Doc IDs in Link Fields defaults) @ATTACHRANGE ATTRANGE Description The application used to see the electronic archive. For instance: @APPLICATION Word IDs of joined reports. Attaching t