eduKate Singapore

VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Next useful routeCanonical hubHELP

Why English? | Reading Acrobat’s Full-Text Index Options Before Searching a PDF Collection

—

by

eduKate Asia
Three learners review open books together at a classroom table, with stacks of textbooks, stationery and a whiteboard in the bright room.
ACROBAT PRO · FULL-TEXT INDEX · PDF COLLECTION SEARCH

Make a PDF collection searchable without confusing indexed words, document metadata, included folders, relative paths and the evidence needed to keep search results current

Use a research-question–authority–collection-inventory–searchable-text–metadata-vocabulary–embedded-or-catalog-choice–PDX-definition–IDX-support-folder–include-and-exclude-paths–options–build–query-test–update-or-rebuild–ReadMe–distribution–release chain. Index only the collection you can explain and maintain.

ROUTE 1OrientDefine the retrieval questionsROUTE 2InterpretPrepare consistent metadataROUTE 3ControlRead included and nested foldersROUTE 4VerifyTest queries and zero results

Open the full chapter index ↓

Why this English matters now

Reading Acrobat’s full-text index options before searching a PDF collection is practical English for students, researchers, librarians and office teams searching how to create a PDF index, speed up Acrobat search or build a searchable collection of PDF documents.

Adobe’s current guidance, updated 26 February 2026, distinguishes an index embedded in one lengthy PDF from a catalog index for a collection in Acrobat Pro. A collection index uses a PDX definition file and supporting IDX files; people need those files available with the indexed PDFs to search the collection reliably.

An index can accelerate retrieval, but it cannot make poor scans legible, inconsistent metadata coherent or an outdated collection current. Strong users define scope, preserve access controls, prepare searchable text and consistent titles, record included and excluded folders, understand nested-folder and relative-path behaviour, test queries, choose Build, Rebuild or Purge deliberately, and verify the distributed collection.

Checked against the linked first-party sources on 2 November 2026. Interfaces, managed-device rules and school procedures can change, so reopen the current source before a live assessment, disclosure or account decision.

The practical reading method

Use a research-question–authority–collection-inventory–searchable-text–metadata-vocabulary–embedded-or-catalog-choice–PDX-definition–IDX-support-folder–include-and-exclude-paths–options–build–query-test–update-or-rebuild–ReadMe–distribution–release chain. Index only the collection you can explain and maintain.

  1. Adobe says an embedded word index can speed search in one lengthy PDF and travels with copies of that PDF.
  2. Adobe says Acrobat Pro’s full-text catalog index creates a PDX definition file and a support folder containing IDX files, all of which must be available to people searching the collection.
  3. Adobe says nested folders under an included directory are also included, and moving a collection can break the index when relative paths change.
  4. Adobe distinguishes Build, Rebuild and Purge: Build updates entries, Rebuild overwrites the index folder contents and Purge removes IDX contents without deleting the PDX definition file.

Official factual floor

  • Adobe’s 26 February 2026 page documents the route All tools > Add search index > Full text index with catalog for a collection in Acrobat Pro.
  • Adobe recommends consistent document properties such as titles, authors, subjects and keywords because these fields can support finding and categorising documents.
  • Adobe says Build can accumulate invalidated entries after repeated updates and increase search time, while Rebuild creates a fresh index from the definition.
Scope: This guide cannot grant permission to index confidential files; perform OCR on image-only scans automatically; guarantee that every PDF’s text, attachments or annotations are indexed as expected; turn inconsistent metadata into a taxonomy; preserve links when folders move; make an index current without maintenance; replace a records-management or discovery system; prove that an absent search result means an absent fact; or certify privacy, legal retention, accessibility or evidential completeness.

Did You Know?

A catalog index is not just one PDX file. Adobe says the supporting IDX files contain the index entries and must remain available to searchers. Moving or sharing only the definition file can leave a collection that looks indexed but cannot deliver the intended search.

Full chapter index

  1. 1. Define the retrieval questions
  2. 2. Obtain authority and classify the collection
  3. 3. Verify searchable text
  4. 4. Prepare consistent metadata
  5. 5. Choose embedded or catalog indexing
  6. 6. Understand PDX and IDX roles
  7. 7. Read included and nested folders
  8. 8. Set options and exclusions deliberately
  9. 9. Build and inspect the index
  10. 10. Test queries and zero results
  11. 11. Maintain with Build Rebuild and Purge
  12. 12. Preserve paths when moving
  13. 13. Publish a ReadMe and verify release
CHAPTER 1 OF 13

1. Define the retrieval questions

Back to contents

The mechanism

Index design should begin with what people need to find and which collection is authoritative.

Adobe says an embedded word index can speed search in one lengthy PDF and travels with copies of that PDF. In this chapter, the decisive phrase is define the retrieval questions. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: A department indexes every PDF on a drive but cannot answer which policy version is current.

A full-text index is a retrieval aid built from available PDF text and selected metadata. An embedded index belongs to one PDF; a catalog index describes a collection and depends on companion files and paths. Neither type interprets meaning, guarantees completeness or substitutes for reading the source document in context.

Decision sequence
  1. 1. list user questions
  2. 2. name the record owner
  3. 3. define authoritative versions
  4. 4. state exclusions

Define the research or retrieval questions; obtain authority for every file and location; freeze an inventory; classify confidential, signed, duplicate and obsolete material; verify that each PDF contains searchable text and run authorised OCR where needed; standardise titles, authors, subjects and keywords without rewriting historical facts; decide whether one PDF needs an embedded index or a collection needs a catalog index; open Acrobat Pro’s Add search index tool; create a descriptive PDX title and purpose; choose advanced options carefully; add explicit folders; remember that nested folders are included; set exclusions; record paths; build the index and retain the PDX with its IDX support folder; test common, rare, phrase, metadata and zero-result queries; open results and compare them with the source PDFs; create a ReadMe describing scope, exclusions, contacts and search conventions; update the collection through controlled intake; use Build, Rebuild or Purge according to the actual maintenance need; test after moving the collection; preserve relative paths; distribute the PDFs, PDX, IDX folder and ReadMe together; download the released package; and repeat the query suite. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record purpose, authority, collection owner, PDF inventory and hashes where required, confidentiality class, searchable-text and OCR status, duplicates, metadata fields, embedded or catalog choice, Acrobat version, PDX title, IDX folder, included and excluded directories, nested-folder decision, options, build date, query test set and results, false positives and missing results, ReadMe path, Build/Rebuild/Purge history, move test, reviewer and released package.

Important boundary: Faster search does not resolve version governance.

Transfer: Research language supports useful scope. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 2 OF 13

2. Obtain authority and classify the collection

Back to contents

The mechanism

Indexing can expose filenames, text and metadata across a wider group than intended.

Adobe says Acrobat Pro’s full-text catalog index creates a PDX definition file and a support folder containing IDX files, all of which must be available to people searching the collection. In this chapter, the decisive phrase is obtain authority and classify the collection. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: A shared index includes confidential student records stored in a nested folder.

A full-text index is a retrieval aid built from available PDF text and selected metadata. An embedded index belongs to one PDF; a catalog index describes a collection and depends on companion files and paths. Neither type interprets meaning, guarantees completeness or substitutes for reading the source document in context.

Decision sequence
  1. 1. confirm permission
  2. 2. classify sensitivity
  3. 3. separate signed records
  4. 4. freeze the inventory

Define the research or retrieval questions; obtain authority for every file and location; freeze an inventory; classify confidential, signed, duplicate and obsolete material; verify that each PDF contains searchable text and run authorised OCR where needed; standardise titles, authors, subjects and keywords without rewriting historical facts; decide whether one PDF needs an embedded index or a collection needs a catalog index; open Acrobat Pro’s Add search index tool; create a descriptive PDX title and purpose; choose advanced options carefully; add explicit folders; remember that nested folders are included; set exclusions; record paths; build the index and retain the PDX with its IDX support folder; test common, rare, phrase, metadata and zero-result queries; open results and compare them with the source PDFs; create a ReadMe describing scope, exclusions, contacts and search conventions; update the collection through controlled intake; use Build, Rebuild or Purge according to the actual maintenance need; test after moving the collection; preserve relative paths; distribute the PDFs, PDX, IDX folder and ReadMe together; download the released package; and repeat the query suite. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record purpose, authority, collection owner, PDF inventory and hashes where required, confidentiality class, searchable-text and OCR status, duplicates, metadata fields, embedded or catalog choice, Acrobat version, PDX title, IDX folder, included and excluded directories, nested-folder decision, options, build date, query test set and results, false positives and missing results, ReadMe path, Build/Rebuild/Purge history, move test, reviewer and released package.

Important boundary: Technical access is not permission to index or distribute.

Transfer: Authority language supports lawful retrieval. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 3 OF 13

3. Verify searchable text

Back to contents

The mechanism

An index can only represent text and fields that Acrobat can read from the PDFs.

Adobe says nested folders under an included directory are also included, and moving a collection can break the index when relative paths change. In this chapter, the decisive phrase is verify searchable text. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: Scanned pages look clear but produce no useful results because they contain images rather than recognised text.

A full-text index is a retrieval aid built from available PDF text and selected metadata. An embedded index belongs to one PDF; a catalog index describes a collection and depends on companion files and paths. Neither type interprets meaning, guarantees completeness or substitutes for reading the source document in context.

Decision sequence
  1. 1. test text selection
  2. 2. run authorised OCR
  3. 3. check language and accuracy
  4. 4. record exceptions

Define the research or retrieval questions; obtain authority for every file and location; freeze an inventory; classify confidential, signed, duplicate and obsolete material; verify that each PDF contains searchable text and run authorised OCR where needed; standardise titles, authors, subjects and keywords without rewriting historical facts; decide whether one PDF needs an embedded index or a collection needs a catalog index; open Acrobat Pro’s Add search index tool; create a descriptive PDX title and purpose; choose advanced options carefully; add explicit folders; remember that nested folders are included; set exclusions; record paths; build the index and retain the PDX with its IDX support folder; test common, rare, phrase, metadata and zero-result queries; open results and compare them with the source PDFs; create a ReadMe describing scope, exclusions, contacts and search conventions; update the collection through controlled intake; use Build, Rebuild or Purge according to the actual maintenance need; test after moving the collection; preserve relative paths; distribute the PDFs, PDX, IDX folder and ReadMe together; download the released package; and repeat the query suite. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record purpose, authority, collection owner, PDF inventory and hashes where required, confidentiality class, searchable-text and OCR status, duplicates, metadata fields, embedded or catalog choice, Acrobat version, PDX title, IDX folder, included and excluded directories, nested-folder decision, options, build date, query test set and results, false positives and missing results, ReadMe path, Build/Rebuild/Purge history, move test, reviewer and released package.

Important boundary: OCR errors can create false negatives and false positives.

Transfer: Text-state language supports honest search. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 4 OF 13

4. Prepare consistent metadata

Back to contents

The mechanism

Titles, authors, subjects and keywords help users distinguish similar results.

Adobe distinguishes Build, Rebuild and Purge: Build updates entries, Rebuild overwrites the index folder contents and Purge removes IDX contents without deleting the PDX definition file. In this chapter, the decisive phrase is prepare consistent metadata. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: Some files use Biology in Keywords while others use Life Sciences in Subject for the same category.

A full-text index is a retrieval aid built from available PDF text and selected metadata. An embedded index belongs to one PDF; a catalog index describes a collection and depends on companion files and paths. Neither type interprets meaning, guarantees completeness or substitutes for reading the source document in context.

Decision sequence
  1. 1. use descriptive titles
  2. 2. choose consistent fields
  3. 3. preserve provenance
  4. 4. document the vocabulary

Define the research or retrieval questions; obtain authority for every file and location; freeze an inventory; classify confidential, signed, duplicate and obsolete material; verify that each PDF contains searchable text and run authorised OCR where needed; standardise titles, authors, subjects and keywords without rewriting historical facts; decide whether one PDF needs an embedded index or a collection needs a catalog index; open Acrobat Pro’s Add search index tool; create a descriptive PDX title and purpose; choose advanced options carefully; add explicit folders; remember that nested folders are included; set exclusions; record paths; build the index and retain the PDX with its IDX support folder; test common, rare, phrase, metadata and zero-result queries; open results and compare them with the source PDFs; create a ReadMe describing scope, exclusions, contacts and search conventions; update the collection through controlled intake; use Build, Rebuild or Purge according to the actual maintenance need; test after moving the collection; preserve relative paths; distribute the PDFs, PDX, IDX folder and ReadMe together; download the released package; and repeat the query suite. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record purpose, authority, collection owner, PDF inventory and hashes where required, confidentiality class, searchable-text and OCR status, duplicates, metadata fields, embedded or catalog choice, Acrobat version, PDX title, IDX folder, included and excluded directories, nested-folder decision, options, build date, query test set and results, false positives and missing results, ReadMe path, Build/Rebuild/Purge history, move test, reviewer and released package.

Important boundary: Metadata should not overwrite original evidence or invent certainty.

Transfer: Metadata language supports discriminating results. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 5 OF 13

5. Choose embedded or catalog indexing

Back to contents

The mechanism

One lengthy PDF and a multi-file collection have different packaging and maintenance needs.

Adobe says an embedded word index can speed search in one lengthy PDF and travels with copies of that PDF. In this chapter, the decisive phrase is choose embedded or catalog indexing. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: A team builds a catalog when users only need one portable handbook, adding avoidable support files.

A full-text index is a retrieval aid built from available PDF text and selected metadata. An embedded index belongs to one PDF; a catalog index describes a collection and depends on companion files and paths. Neither type interprets meaning, guarantees completeness or substitutes for reading the source document in context.

Decision sequence
  1. 1. count source PDFs
  2. 2. assess portability
  3. 3. choose the index type
  4. 4. document the reason

Define the research or retrieval questions; obtain authority for every file and location; freeze an inventory; classify confidential, signed, duplicate and obsolete material; verify that each PDF contains searchable text and run authorised OCR where needed; standardise titles, authors, subjects and keywords without rewriting historical facts; decide whether one PDF needs an embedded index or a collection needs a catalog index; open Acrobat Pro’s Add search index tool; create a descriptive PDX title and purpose; choose advanced options carefully; add explicit folders; remember that nested folders are included; set exclusions; record paths; build the index and retain the PDX with its IDX support folder; test common, rare, phrase, metadata and zero-result queries; open results and compare them with the source PDFs; create a ReadMe describing scope, exclusions, contacts and search conventions; update the collection through controlled intake; use Build, Rebuild or Purge according to the actual maintenance need; test after moving the collection; preserve relative paths; distribute the PDFs, PDX, IDX folder and ReadMe together; download the released package; and repeat the query suite. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record purpose, authority, collection owner, PDF inventory and hashes where required, confidentiality class, searchable-text and OCR status, duplicates, metadata fields, embedded or catalog choice, Acrobat version, PDX title, IDX folder, included and excluded directories, nested-folder decision, options, build date, query test set and results, false positives and missing results, ReadMe path, Build/Rebuild/Purge history, move test, reviewer and released package.

Important boundary: Product and licence availability can constrain the choice.

Transfer: Architecture language supports proportionate solutions. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 6 OF 13

6. Understand PDX and IDX roles

Back to contents

The mechanism

The PDX defines the catalog while IDX files contain the index entries.

Adobe says Acrobat Pro’s full-text catalog index creates a PDX definition file and a support folder containing IDX files, all of which must be available to people searching the collection. In this chapter, the decisive phrase is understand pdx and idx roles. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: Only the PDX is emailed, so colleagues cannot search the intended collection.

A full-text index is a retrieval aid built from available PDF text and selected metadata. An embedded index belongs to one PDF; a catalog index describes a collection and depends on companion files and paths. Neither type interprets meaning, guarantees completeness or substitutes for reading the source document in context.

Decision sequence
  1. 1. name the definition file
  2. 2. identify the support folder
  3. 3. keep components together
  4. 4. test on another computer

Define the research or retrieval questions; obtain authority for every file and location; freeze an inventory; classify confidential, signed, duplicate and obsolete material; verify that each PDF contains searchable text and run authorised OCR where needed; standardise titles, authors, subjects and keywords without rewriting historical facts; decide whether one PDF needs an embedded index or a collection needs a catalog index; open Acrobat Pro’s Add search index tool; create a descriptive PDX title and purpose; choose advanced options carefully; add explicit folders; remember that nested folders are included; set exclusions; record paths; build the index and retain the PDX with its IDX support folder; test common, rare, phrase, metadata and zero-result queries; open results and compare them with the source PDFs; create a ReadMe describing scope, exclusions, contacts and search conventions; update the collection through controlled intake; use Build, Rebuild or Purge according to the actual maintenance need; test after moving the collection; preserve relative paths; distribute the PDFs, PDX, IDX folder and ReadMe together; download the released package; and repeat the query suite. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record purpose, authority, collection owner, PDF inventory and hashes where required, confidentiality class, searchable-text and OCR status, duplicates, metadata fields, embedded or catalog choice, Acrobat version, PDX title, IDX folder, included and excluded directories, nested-folder decision, options, build date, query test set and results, false positives and missing results, ReadMe path, Build/Rebuild/Purge history, move test, reviewer and released package.

Important boundary: A familiar filename does not prove that support files match its build.

Transfer: Component language supports reliable packaging. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 7 OF 13

7. Read included and nested folders

Back to contents

The mechanism

Adding a directory also includes folders nested beneath it unless exclusions are set.

Adobe says nested folders under an included directory are also included, and moving a collection can break the index when relative paths change. In this chapter, the decisive phrase is read included and nested folders. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: A temporary archive is indexed because it sits below an approved folder.

A full-text index is a retrieval aid built from available PDF text and selected metadata. An embedded index belongs to one PDF; a catalog index describes a collection and depends on companion files and paths. Neither type interprets meaning, guarantees completeness or substitutes for reading the source document in context.

Decision sequence
  1. 1. map the directory tree
  2. 2. list nested folders
  3. 3. set exclusions
  4. 4. reconcile file counts

Define the research or retrieval questions; obtain authority for every file and location; freeze an inventory; classify confidential, signed, duplicate and obsolete material; verify that each PDF contains searchable text and run authorised OCR where needed; standardise titles, authors, subjects and keywords without rewriting historical facts; decide whether one PDF needs an embedded index or a collection needs a catalog index; open Acrobat Pro’s Add search index tool; create a descriptive PDX title and purpose; choose advanced options carefully; add explicit folders; remember that nested folders are included; set exclusions; record paths; build the index and retain the PDX with its IDX support folder; test common, rare, phrase, metadata and zero-result queries; open results and compare them with the source PDFs; create a ReadMe describing scope, exclusions, contacts and search conventions; update the collection through controlled intake; use Build, Rebuild or Purge according to the actual maintenance need; test after moving the collection; preserve relative paths; distribute the PDFs, PDX, IDX folder and ReadMe together; download the released package; and repeat the query suite. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record purpose, authority, collection owner, PDF inventory and hashes where required, confidentiality class, searchable-text and OCR status, duplicates, metadata fields, embedded or catalog choice, Acrobat version, PDX title, IDX folder, included and excluded directories, nested-folder decision, options, build date, query test set and results, false positives and missing results, ReadMe path, Build/Rebuild/Purge history, move test, reviewer and released package.

Important boundary: Folder names can hide mixed sensitivity and ownership.

Transfer: Scope language supports complete control. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 8 OF 13

8. Set options and exclusions deliberately

Back to contents

The mechanism

Advanced choices can affect size, compatibility and what the index records.

Adobe distinguishes Build, Rebuild and Purge: Build updates entries, Rebuild overwrites the index folder contents and Purge removes IDX contents without deleting the PDX definition file. In this chapter, the decisive phrase is set options and exclusions deliberately. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: Common identifiers are excluded as stop words and can no longer be retrieved.

A full-text index is a retrieval aid built from available PDF text and selected metadata. An embedded index belongs to one PDF; a catalog index describes a collection and depends on companion files and paths. Neither type interprets meaning, guarantees completeness or substitutes for reading the source document in context.

Decision sequence
  1. 1. read every option
  2. 2. predict search effects
  3. 3. record exclusions
  4. 4. test representative terms

Define the research or retrieval questions; obtain authority for every file and location; freeze an inventory; classify confidential, signed, duplicate and obsolete material; verify that each PDF contains searchable text and run authorised OCR where needed; standardise titles, authors, subjects and keywords without rewriting historical facts; decide whether one PDF needs an embedded index or a collection needs a catalog index; open Acrobat Pro’s Add search index tool; create a descriptive PDX title and purpose; choose advanced options carefully; add explicit folders; remember that nested folders are included; set exclusions; record paths; build the index and retain the PDX with its IDX support folder; test common, rare, phrase, metadata and zero-result queries; open results and compare them with the source PDFs; create a ReadMe describing scope, exclusions, contacts and search conventions; update the collection through controlled intake; use Build, Rebuild or Purge according to the actual maintenance need; test after moving the collection; preserve relative paths; distribute the PDFs, PDX, IDX folder and ReadMe together; download the released package; and repeat the query suite. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record purpose, authority, collection owner, PDF inventory and hashes where required, confidentiality class, searchable-text and OCR status, duplicates, metadata fields, embedded or catalog choice, Acrobat version, PDX title, IDX folder, included and excluded directories, nested-folder decision, options, build date, query test set and results, false positives and missing results, ReadMe path, Build/Rebuild/Purge history, move test, reviewer and released package.

Important boundary: Smaller indexes are not automatically better indexes.

Transfer: Configuration language supports reproducible search. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 9 OF 13

9. Build and inspect the index

Back to contents

The mechanism

A successful build is operational evidence, not proof that the right material is searchable.

Adobe says an embedded word index can speed search in one lengthy PDF and travels with copies of that PDF. In this chapter, the decisive phrase is build and inspect the index. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: The catalog completes but several protected or damaged PDFs contribute no usable text.

A full-text index is a retrieval aid built from available PDF text and selected metadata. An embedded index belongs to one PDF; a catalog index describes a collection and depends on companion files and paths. Neither type interprets meaning, guarantees completeness or substitutes for reading the source document in context.

Decision sequence
  1. 1. save the build record
  2. 2. review warnings
  3. 3. compare inventory
  4. 4. inspect support files

Define the research or retrieval questions; obtain authority for every file and location; freeze an inventory; classify confidential, signed, duplicate and obsolete material; verify that each PDF contains searchable text and run authorised OCR where needed; standardise titles, authors, subjects and keywords without rewriting historical facts; decide whether one PDF needs an embedded index or a collection needs a catalog index; open Acrobat Pro’s Add search index tool; create a descriptive PDX title and purpose; choose advanced options carefully; add explicit folders; remember that nested folders are included; set exclusions; record paths; build the index and retain the PDX with its IDX support folder; test common, rare, phrase, metadata and zero-result queries; open results and compare them with the source PDFs; create a ReadMe describing scope, exclusions, contacts and search conventions; update the collection through controlled intake; use Build, Rebuild or Purge according to the actual maintenance need; test after moving the collection; preserve relative paths; distribute the PDFs, PDX, IDX folder and ReadMe together; download the released package; and repeat the query suite. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record purpose, authority, collection owner, PDF inventory and hashes where required, confidentiality class, searchable-text and OCR status, duplicates, metadata fields, embedded or catalog choice, Acrobat version, PDX title, IDX folder, included and excluded directories, nested-folder decision, options, build date, query test set and results, false positives and missing results, ReadMe path, Build/Rebuild/Purge history, move test, reviewer and released package.

Important boundary: Some documents may need separate remediation or exclusion.

Transfer: Build language supports auditable creation. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 10 OF 13

10. Test queries and zero results

Back to contents

The mechanism

A query suite should include common terms, rare identifiers, phrases, metadata and expected absence.

Adobe says Acrobat Pro’s full-text catalog index creates a PDX definition file and a support folder containing IDX files, all of which must be available to people searching the collection. In this chapter, the decisive phrase is test queries and zero results. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: One successful keyword is used to declare the whole collection complete.

A full-text index is a retrieval aid built from available PDF text and selected metadata. An embedded index belongs to one PDF; a catalog index describes a collection and depends on companion files and paths. Neither type interprets meaning, guarantees completeness or substitutes for reading the source document in context.

Decision sequence
  1. 1. write expected results
  2. 2. test exact and broad queries
  3. 3. open source hits
  4. 4. investigate zero results

Define the research or retrieval questions; obtain authority for every file and location; freeze an inventory; classify confidential, signed, duplicate and obsolete material; verify that each PDF contains searchable text and run authorised OCR where needed; standardise titles, authors, subjects and keywords without rewriting historical facts; decide whether one PDF needs an embedded index or a collection needs a catalog index; open Acrobat Pro’s Add search index tool; create a descriptive PDX title and purpose; choose advanced options carefully; add explicit folders; remember that nested folders are included; set exclusions; record paths; build the index and retain the PDX with its IDX support folder; test common, rare, phrase, metadata and zero-result queries; open results and compare them with the source PDFs; create a ReadMe describing scope, exclusions, contacts and search conventions; update the collection through controlled intake; use Build, Rebuild or Purge according to the actual maintenance need; test after moving the collection; preserve relative paths; distribute the PDFs, PDX, IDX folder and ReadMe together; download the released package; and repeat the query suite. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record purpose, authority, collection owner, PDF inventory and hashes where required, confidentiality class, searchable-text and OCR status, duplicates, metadata fields, embedded or catalog choice, Acrobat version, PDX title, IDX folder, included and excluded directories, nested-folder decision, options, build date, query test set and results, false positives and missing results, ReadMe path, Build/Rebuild/Purge history, move test, reviewer and released package.

Important boundary: An absent hit can reflect OCR, spelling, metadata, scope or index age.

Transfer: Evidence language supports trustworthy retrieval. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 11 OF 13

11. Maintain with Build Rebuild and Purge

Back to contents

The mechanism

These commands change index contents differently and should match the maintenance task.

Adobe says nested folders under an included directory are also included, and moving a collection can break the index when relative paths change. In this chapter, the decisive phrase is maintain with build rebuild and purge. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: Repeated Build operations accumulate invalid entries and slow searching, but nobody considers Rebuild.

A full-text index is a retrieval aid built from available PDF text and selected metadata. An embedded index belongs to one PDF; a catalog index describes a collection and depends on companion files and paths. Neither type interprets meaning, guarantees completeness or substitutes for reading the source document in context.

Decision sequence
  1. 1. record collection changes
  2. 2. choose update or fresh rebuild
  3. 3. protect the PDX definition
  4. 4. purge only with a recovery plan

Define the research or retrieval questions; obtain authority for every file and location; freeze an inventory; classify confidential, signed, duplicate and obsolete material; verify that each PDF contains searchable text and run authorised OCR where needed; standardise titles, authors, subjects and keywords without rewriting historical facts; decide whether one PDF needs an embedded index or a collection needs a catalog index; open Acrobat Pro’s Add search index tool; create a descriptive PDX title and purpose; choose advanced options carefully; add explicit folders; remember that nested folders are included; set exclusions; record paths; build the index and retain the PDX with its IDX support folder; test common, rare, phrase, metadata and zero-result queries; open results and compare them with the source PDFs; create a ReadMe describing scope, exclusions, contacts and search conventions; update the collection through controlled intake; use Build, Rebuild or Purge according to the actual maintenance need; test after moving the collection; preserve relative paths; distribute the PDFs, PDX, IDX folder and ReadMe together; download the released package; and repeat the query suite. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record purpose, authority, collection owner, PDF inventory and hashes where required, confidentiality class, searchable-text and OCR status, duplicates, metadata fields, embedded or catalog choice, Acrobat version, PDX title, IDX folder, included and excluded directories, nested-folder decision, options, build date, query test set and results, false positives and missing results, ReadMe path, Build/Rebuild/Purge history, move test, reviewer and released package.

Important boundary: Maintenance operations do not repair source PDFs.

Transfer: Lifecycle language supports current search. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 12 OF 13

12. Preserve paths when moving

Back to contents

The mechanism

Catalog definitions depend on paths between the PDX, support files and indexed folders.

Adobe distinguishes Build, Rebuild and Purge: Build updates entries, Rebuild overwrites the index folder contents and Purge removes IDX contents without deleting the PDX definition file. In this chapter, the decisive phrase is preserve paths when moving. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: The collection is moved to another server and every saved path breaks.

A full-text index is a retrieval aid built from available PDF text and selected metadata. An embedded index belongs to one PDF; a catalog index describes a collection and depends on companion files and paths. Neither type interprets meaning, guarantees completeness or substitutes for reading the source document in context.

Decision sequence
  1. 1. keep relative structure
  2. 2. move the whole package
  3. 3. edit include and exclude paths
  4. 4. rebuild when required

Define the research or retrieval questions; obtain authority for every file and location; freeze an inventory; classify confidential, signed, duplicate and obsolete material; verify that each PDF contains searchable text and run authorised OCR where needed; standardise titles, authors, subjects and keywords without rewriting historical facts; decide whether one PDF needs an embedded index or a collection needs a catalog index; open Acrobat Pro’s Add search index tool; create a descriptive PDX title and purpose; choose advanced options carefully; add explicit folders; remember that nested folders are included; set exclusions; record paths; build the index and retain the PDX with its IDX support folder; test common, rare, phrase, metadata and zero-result queries; open results and compare them with the source PDFs; create a ReadMe describing scope, exclusions, contacts and search conventions; update the collection through controlled intake; use Build, Rebuild or Purge according to the actual maintenance need; test after moving the collection; preserve relative paths; distribute the PDFs, PDX, IDX folder and ReadMe together; download the released package; and repeat the query suite. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record purpose, authority, collection owner, PDF inventory and hashes where required, confidentiality class, searchable-text and OCR status, duplicates, metadata fields, embedded or catalog choice, Acrobat version, PDX title, IDX folder, included and excluded directories, nested-folder decision, options, build date, query test set and results, false positives and missing results, ReadMe path, Build/Rebuild/Purge history, move test, reviewer and released package.

Important boundary: Cross-server permissions may change even when paths look similar.

Transfer: Path language supports portable collections. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 13 OF 13

13. Publish a ReadMe and verify release

Back to contents

The mechanism

Users need scope, exclusions, conventions and support information beside the index.

Adobe says an embedded word index can speed search in one lengthy PDF and travels with copies of that PDF. In this chapter, the decisive phrase is publish a readme and verify release. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: The index is distributed without explaining which years or document types it covers.

A full-text index is a retrieval aid built from available PDF text and selected metadata. An embedded index belongs to one PDF; a catalog index describes a collection and depends on companion files and paths. Neither type interprets meaning, guarantees completeness or substitutes for reading the source document in context.

Decision sequence
  1. 1. write the scope
  2. 2. list exclusions
  3. 3. name a contact
  4. 4. repeat the query suite after download

Define the research or retrieval questions; obtain authority for every file and location; freeze an inventory; classify confidential, signed, duplicate and obsolete material; verify that each PDF contains searchable text and run authorised OCR where needed; standardise titles, authors, subjects and keywords without rewriting historical facts; decide whether one PDF needs an embedded index or a collection needs a catalog index; open Acrobat Pro’s Add search index tool; create a descriptive PDX title and purpose; choose advanced options carefully; add explicit folders; remember that nested folders are included; set exclusions; record paths; build the index and retain the PDX with its IDX support folder; test common, rare, phrase, metadata and zero-result queries; open results and compare them with the source PDFs; create a ReadMe describing scope, exclusions, contacts and search conventions; update the collection through controlled intake; use Build, Rebuild or Purge according to the actual maintenance need; test after moving the collection; preserve relative paths; distribute the PDFs, PDX, IDX folder and ReadMe together; download the released package; and repeat the query suite. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record purpose, authority, collection owner, PDF inventory and hashes where required, confidentiality class, searchable-text and OCR status, duplicates, metadata fields, embedded or catalog choice, Acrobat version, PDX title, IDX folder, included and excluded directories, nested-folder decision, options, build date, query test set and results, false positives and missing results, ReadMe path, Build/Rebuild/Purge history, move test, reviewer and released package.

Important boundary: Documentation must be updated with every material rebuild.

Transfer: Release language supports responsible discovery. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

Four useful discoveries

Define the retrieval questions

Index design should begin with what people need to find and which collection is authoritative.

Boundary: Faster search does not resolve version governance.

Obtain authority and classify the collection

Indexing can expose filenames, text and metadata across a wider group than intended.

Boundary: Technical access is not permission to index or distribute.

Verify searchable text

An index can only represent text and fields that Acrobat can read from the PDFs.

Boundary: OCR errors can create false negatives and false positives.

Prepare consistent metadata

Titles, authors, subjects and keywords help users distinguish similar results.

Boundary: Metadata should not overwrite original evidence or invent certainty.

Practice with realistic decisions

Choose embedded or catalog indexing

A team builds a catalog when users only need one portable handbook, adding avoidable support files.

  • count source PDFs
  • assess portability
  • choose the index type
  • document the reason

Understand PDX and IDX roles

Only the PDX is emailed, so colleagues cannot search the intended collection.

  • name the definition file
  • identify the support folder
  • keep components together
  • test on another computer

Read included and nested folders

A temporary archive is indexed because it sits below an approved folder.

  • map the directory tree
  • list nested folders
  • set exclusions
  • reconcile file counts

Advice for students, families and educators

For students

  • Test whether scanned PDFs contain selectable text before assuming search will find them.
  • Keep a query log showing expected and actual results.

For families

  • Help the learner protect private files and keep the index package organised without reading confidential content unnecessarily.
  • Ask what a zero-result search actually proves.

For educators

  • Provide a safe public document set for indexing practice.
  • Assess scope, metadata, query testing and documentation as well as search speed.

Frequently asked questions

What is an embedded PDF index?

A word index included in one PDF so copies of that PDF carry the index.

What is a catalog index?

An Acrobat Pro index for a collection of PDFs, defined by a PDX file and supported by IDX files.

Where is the tool?

Adobe documents All tools > Add search index > Full text index with catalog.

Do users need the IDX files?

Yes; Adobe says the support files containing index entries must be available to searchers.

Are nested folders included?

Yes, folders below an included directory are included unless the definition excludes them.

What is Build?

An update that adds entries and marks changed or outdated entries invalid.

What is Rebuild?

A fresh creation that overwrites the existing index folder contents.

What is Purge?

Removal of IDX contents without deleting the PDX definition file.

What must I verify?

Authority, searchable text, metadata, scope, paths, support files, queries, maintenance and released package.

Why English?

Because index, embedded, catalog, include, exclude, build, rebuild, purge and zero result describe different retrieval states.

Useful next reading

Closing thought

Search becomes trustworthy when the collection, vocabulary and maintenance record are as clear as the search box. Build the index around an explicit scope, test the results against real questions and keep the definition, support files and documents together.