ANSI AIIM TR40-1995 Suggested Index Fields for Documents in Electronic Image Management (EIM) Environments.pdf

1、- AIIM TR40 95 LOL2348 0500745 495 B FOR INFORMATION AND IMAGE Suite 11 O0 Silver Spring, Maryland 20910 AIIM MANAGEMENT 301 -587-8202 INTERNATIONAL AIIM TR40 95 EO12348 0500746 321 a ANSI/AIIM TR40-1995 O by Association for Information and Image Management International 1100 Wayne Avenue, Suite 1 1

2、00 Silver Spring, MD 20910-5603 Tel: 301/587-8202 Fax: 301/583-2711 ISBN 0-89258-304-5 Printed in the United States of America AIIM TR40 95 3032348 0500747 268 ANSVAIIM TR40-1995 Technical Report for Information and Image Management - Suggested Index Fields for Documents in Electronic Image Manageme

3、nt (EIM) Environments An ANSI Technical Report prepared by the Association for Information and Image Management International Abstract: This technical report provides sample index fields for the processing and retrieval of information captured for use with electronic image management (EIM) systems.

4、AIIM TR40 95 9 1012348 0500748 IT4 9 ANSIIAIIM TR40- 1995 - Suggested Index Fields for Documents in Electronic Image Management (EIM) Environments Contents Foreword . i 1 Audience, scope, purpose, and exclusions . 1 2 References 1 3 Definitions . 2 4 Suggested processing information field list . 2 5

5、 Suggested retrieval information field list . 2 6 Field attributes . 3 7 Processing field descriptions 3 8 Retrieval field descriptions 7 Foreword This technical report describes sample fields of attribute information to be captured for use with electronic imaging systems. The fields described do no

6、t make up an exhaustive list, but are a set of possible fields. Although information can be grouped in a variety of ways for different applications, in this technical report information is grouped into two categories: 1. Processing Information: that information necessary to operate the system from t

7、he system administrators point of view and to verify the documents operational integrity; 2. Retrieval Information: that information necessary for an end-user to retrieve the document image (after the document has been captured). Suggestions for improvement of this technical report are welcome. They

8、 should be sent to the Chair, AIIM Standards Board, Association for Information and Image Management, 1100 Wayne Avenue, Suite 1 100, Silver Spring, Maryland, 20910-5603. At the time it approved this technical report, the AIIM Standards Board had the following members: Name of Representative Comganv

9、 Represented Judy Kilpaiick, Chair John C. Gale Tom Heltzel Bruce A. Holroyd James Meyer Roy Pierce Charles A. Plesums Fernando L. Podio Shahzad S. Qazi Michael L. Thomas Stephen Urban Association for Information and Image Management Intemational Information Workstation Group Consultant Eastman Koda

10、k Company Interleaf Xerox Corporation USAA National Inst. of Standards and Technology Eastman Kodak Company MSTC, Inc. Delta Information Systems The Committee on Electronic Imaging Software and Systems, C15, had the following members at the time this document was approved: Name of Representative Bet

11、sy A. Fanning, Chair Don M. Avedon Brant Bady John Ballock Av Bender Pete Bennett Bob Blackwelder Robert Blatt John B. Breeden William C. Brown Lois R. Bruss Paul Conway Robert W. Cook William A. Cozzens Donald P. DAmato Jim Daly Richard Donaldson Eric Erickson Bruce Evans Tom Fine Bruno B. Glavich

12、Bill Golstein Larry Greenberg Berne Crush Dexter S. Holt Buck Horyn Clare F. Jehle Brian Johannesson Bohdan Kantor Paul Kennedy Felix Krayeski Richard J. Laxman Daniel Mailick Basil Manns Ron Maultsby Theresa Maultsby Vorliss McLean Donald S. Merz Noah Nason Michael ODonnell Comaanv Reoresented Data

13、 Management Design Avedon Associates, Incorporated B.C. Archives in particular, it is not specific to bitonal (one bit per pixel, binary) images. The fields described in this technical report are independent of other file management and file descriptor fields and records associated with electronic i

14、mage management. An example of field information excluded from, and independent of, the fields described in this technical report is the image header record or image file directory record(s) describing how an image file is internally structured (resolution, size, tiling, compression type, photometri

15、c interpretation, etc.). 2 References All standards reports and publications are subject to revision. When the following documents are superseded by an approved revision, that revision may apply. 2.1 Referenced international standards IS0 8601 -1988, Information interchange - Data elements and inter

16、change formats - Representation of dates and times. 2.2 Related American national standards ANSI/AIIM MS44-1988 (R1993), Recommended Practice of quality control for image scanners. ANSI/AIIM MS53-1993, Recommended Practice: File format for storage and exchange of images; Bi-level image$le format: Pa

17、rt 1. ANSUAIIM MS55-1994, Recommended Practice for the identi3cation and indexing of page components (zones) for automated processing in an Electronic Image Management (EM) environment. 2.3 Referenced publications AIIM TR2-1992, Technical Report for Information and Image Management - Glossary of ima

18、ging technology. 1 Association for Information and Image Management International - - AIIN TRY0 95 = 3032348 0500751 799 ANWAIIM TR40- 1995 - Suggested Index Fields for Documents in Electronic Image Management (EIM) Environments 2.4 Related publications AIIM TR25-199.5, Technical Report for Informat

19、ion und Image Management - The use of optical disks for public records. AIIM TR21-1991, Technical Report for Information and Image Management - Recommendation for identifying information to be placed on Write-Once-Read-Many (WORM) and rewritable optical disk cartridge label(s) and optical disk cartr

20、idge packaging (shipping containers). 3 Definitions The following definitions apply to terms that appear in this technical report. Other terms are defined in AIIM TR2, Technical Report for Information and Image Management - Glossary of imaging technology. 3.1 document: A document is a collection of

21、zero or more pages that are related (linkedhound) to each other in some way appropriate to the application. In an electronic image management system, the provision of a zero-page document allows the creation of a document entity prior to capturing and linking its page(s). 3.2 page: A page is equival

22、ent to one side of a 2- dimensional sheet (e.g., paper, microfilm, transparencies, etc.). In the case of input media other than paper, a page will be the data in a single image frame. Note: In the case of a single sheet of paper printed on both sides and folded to form a multi-page document, it shou

23、ld be treated as either two, four or six pages, as appropriate. No minimum or maximum size is implied. 4 Suggested processing information fields Processing fields, as stated in the Foreword, contain information necessary for the system administrator to operate the system and to verify the documents

24、operational integrity. The processing-related fields covered in this technical report include: 1 2 3 4 5 6 7 8 9 10 11 Batch sequence number Creation date and time Local filing date and time Expire date and time. Start date and time Document size (in bytes) Input media format Input media location In

25、dexing operator ID Image record migration date Image record destruction date 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 Release date and time Revision history Output media format Output media location Orientation of page Output volume label References to other documents Superseded docu

26、ments Local file references Source document scaling ratio Source document resolution Source document size (print dimensions) Security code Authorization Security classification Scan device ID Scanner operator ID Status Distribution list 5 Suggested retrieval information fields Retrieval fields, as d

27、escribed in the Foreword, contain information necessary for an end-user to retrieve the document image after the document has been captured. The retrieval-related fields covered in this technical report include: 1 Abstract 2 3 Comments 4 Document date and time 5 Document type 6 Document reference 7

28、Keywords or secondary keys 8 Number of pages 9 Languages 10 Organization name 11 Preparers 12 Owners 13 Page identifier 14 Primary key 15 Record series 16 Revision ID 17 Title 18 Subject 1 Y Copyright 20 User defined field Name(s) of author(s) or editor(s) 2 Association for Information and image Man

29、agement International - AIIM TR40 95 W 3032348 0500752 b25 W ANSIIAIIM TR40- 1995 - Suggested Index Fields for Documents in Electronic Image Management (EIM) Environments 6 Field attributes This technical report does not specify attributes of these data fields. In particular, the technical report do

30、es not specify the following data field attributes: - length - format - structure - level - encoding Data within these fields could be stored as ASCII strings or in any format appropriate to the application or specific operating environment. In many operational circumstances, the internal storage fo

31、rmats of dates, integers, and real numbers could be application or operating-environment dependent. Length is not specified in this technical report because some applications could require fields of greater or shorter length and many implementations could use variable-length fields. The level for ea

32、ch attribute is not specified in this technical report because these attributes can be application dependent. Although most of these attributes refer to the entire document, some might be more appropriately used at the page level. (If an attribute is associated with document level, there will be one

33、 instance of a value for that attribute for every document. If an attribute is associated with page level, there will be one instance of a value for that attribute for every page of every document.) Because the level of each attribute can be application dependent, the system designer should decide w

34、hen to repeat an attribute for each page. An example of an attribute that might be used either at the document or page level, depending on the application, is page size. When a document includes pages of only one size, this attribute would be associated with the document level. When a document inclu

35、des pages of variable sizes, this attribute would be associated with page level. 7 Processing field descriptions 7.1 Batch sequence number This field could be used as an application-dependent batch control number. The same number would be carried on each document within a batch. 7.2 Creation date an

36、d time This field could be used to specify the date and time when the document was initially scanned or imported into the system. The value of this field could consist of a date character string and a time of day character string in accordance with IS0 8601. It is good practice to use a complete cap

37、ture date and time string (yyyymmddhhmmss) where yyyymmdd is International Date Format and hhmmss is the time (hours, minutes, seconds) with system-time hours based on a 24- hour clock. 7.3 Local filing date and time This field could be used to specify the date and the time when the document was fil

38、ed. (Filing can refer to the time the document was committed to optical media.) If more than one entry is allowed, the last entry could indicate the most recent local filing date and time. The value of this field could consists of a sequence of parameters. Each parameter could consist of a date char

39、acter string and a time character string, in accordance with IS0 8601. An example of a situation in which a user would want the filing date would be an application where the filing time of a document carries a legal or procedural meaning. 7.4 Expire date and time This field could be used to specify

40、the date and time after which the document is considered to be invalid. The value of this field could consist of a date character string and a time character string, in accordance with IS0 8601. 7.5 Start date and time This field could be used to specify the date and time after which the document is

41、 considered to be valid. The value of this field could consist of a date character string and a time character string, in accordance with IS0 8601. 7.6 Document size (in bytes) This field could be used to represent the estimated size of the whole document, expressed as a number of %bit bytes, where

42、the estimate cannot be less than the actual size. The size could include that of the document attributes as well as that of the document body (if present). 3 Association for Information and Image Management International - AIIM TR4O 75 m LOL2348 0500753 561 m ANSIAIIM TR40- 1995 - Suggested Index Fi

43、elds for Documents in Electronic Image Management (EIM) Environments 7.7 Input media format This field could be used to record the media type on which the information resided prior to scanning or copying for entry into the EIM system. The ordinal values provided in the left column, below, may be use

44、d to encode this field if it is appropriate to do so. O000 O00 1 0002 0003 0004 0005 0006 0007 0008 0009 unknown Paper microfilm microfiche aperture card film jacket fax (compressed record, as received electronically) digital recording media slides film “Digital recording media” (0007 in the list ab

45、ove) refers to magnetic or optical tape and disk. All other input media formats can be assumed to require conversion to a digital electronic format in which digital sampling errors will be introduced. This conversion requirement is one reason for distinguishing among non-electronic input formats. 7.

46、8 Input media location This field could be used to record the long-term storage location of the input media. If the media has been destroyed (e.g., shredded), the string “DESTROYED” could be used in this field instead of a location. If the media is not available (e.g., it was borrowed and not return

47、ed to the original owner), the string “NOT AVAILABLE” could be used. 7.9 Indexing operator ID This field could be used to identify the operator responsible for indexing or codifying the imaged document. The contents of this field could be selected from a set of legal operator names or ID strings def

48、ined by the application or the administrator of the application. If it is possible to have multiple indexing operators, it may be reasonable to keep an audit trail for this activity. 7.10 Image record migration date This field could be used to indicate the date on which the related imagery is to be

49、moved to a subsequent storage stage. For example, the document staging cycle may be magnetic disk to WORM to destruction. When the document is first introduced to the magnetic disk, this field could be set to the date on which the document cardshould be migrated to WORM. When this second date is reached, and the data is migrated, this field could be reset to the date designated for destruction. When this last date is reached, the data could be destroyed or otherwise be made inaccessible. It is good practice to record a field like this in International Date