Indexing and Hierarchies
Document Actions
| Previous | Main | Next |
Setting up relationships between metadata (index) fields and hierarchy levels provides a powerful tool for organizing your content.
The most important idea here is that you can set up a link between a metadata field and a hierarchy level. Hierarchy levels can be used for various purposes, but most importantly the following two functions:
- Define the start of a new document
- Use the hierarchy level labels as PDF bookmarks
Further on, you can also define relationships between barcode values (that can be scanned and detected by ELAN Capture).
When setting up a process for capturing images and metadata, you should thing about the following aspects of the job:
- Do I have to scan several portions of a job that will be delivered as sperate PDF files? In this case you want to set up at least a H1 level (in addition to the default H0, root level)
- Will be PDF bookmarks needed or desirable? If yes, you should set up at least one more (H2) hierarchy.
Notes on job size:
A practical scanning job that can be effectively processed should contain a maximum of 2000 to 3000 images. However, one scanning job is able to create one or more or hundreds of PDF output files that all can have metadata and bookmarks.