Electronic Records Management

-

Some points I made while considering whether TIFF or PDF format is more appropriate for the above.

  • Need to differentiate the processing for:
    1. Records “born” electronic – use acrobat distiller to convert to PDF
    2. Scanned records – use acrobat capture to convert to PDF, use OCR to convert to text
    3. Paper-based records
  • Archival workflow
    1. Document creation
    2. Document editing and annotation
    3. Tagging and metadata capturing
    4. Store and retrieve
    5. Print and distribute
  • PDF/A is based on PDF Reference 1.4 (Acrobat 5) and has the following constraints
    1. Self-contained: All fonts used have to be embedded & external content references are disallowed
    2. Device-independent: Colour must be device-independent and transparency is disallowed
    3. Self-describing: XMP (eXtensible Metadata Platform) is required
    4. Unfettered: Encryption and LZW compression are disallowed
    5. Multimedia, forms, embedded files and JavaScript are disallowed
  • PDF over TIFF
    1. More compact. I.e. smaller file size
    2. Metadata can be stored in PDF
    3. More device-independent

Comments

Post a Comment

Popular posts from this blog

Understanding ITIL Service Management the UML way…

-
Image
I originally had a great deal of difficult reconciling the differences amongst ITIL Change Management, Incident Management, and Problem Management. Having researched on the subjects and understanding them better now, I’ve tried to put the concepts together using a UML class diagram to capture my understanding and to keep it imprinted. Similarly, I wanted to differentiate the various categories of changes (Standard, Emergency, Normal) using an easy to understand & self-explanatory manner – a UML Activity Diagram!
Read more

Apache Web Server Troubleshooting

-
How to troubleshoot Apache Web Server? A few standard commands to know by hard: To confirm the modules that are or will be loaded in Apache: apachectl –M [-f <conf filename>] To check the virtual host load pattern: apachectl –S [-f <conf filename>] To test a httpd.conf file: apachectl –t [-f <conf filename>] To maintain the http server: apachectl start|stop|restart To start with a specified configuration file: apachectl –f <conf filename> Create a minimalist httpd.conf. Something like: Listen 80 ServerName myserver.com:80 ServerAdmin admin@myserver.com #ServerRoot " . " ServerRoot " /usr/local/apache2 " User nobody Group nobody #DocumentRoot " ..\wwwroot " DocumentRoot " /home/data/html " ErrorLog " logs/basic_apache.log " LogLevel debug #LoadModule log_config_module modules/mod_log_config.dll LoadModule log_config_module modules/mod_log_config.so <IfModule log_config_module> LogFormat " %h %l
Read more