Technical Industrial Volume Book Management System

Last updated: April 2026
A Fortune 500 publisher of internationally distributed technical and industrial reference books needed a single system to manage 5 separate multi-volume encyclopedias covering 100,000+ sources, tens of thousands of data investigation points, and millions of records across categories up to 50 levels deep. The project landed as a late-starting Y2K remediation with a hard publication deadline. PCG tripled its staff, analyzed multiple legacy database systems, and delivered a complete book management system in 8 months. Each set distributed over 1 million copies.
Project requirements

Gather and compile data from 100,000+ sources. Track all contact points, dates, recontact, and verification. Categorize up to 50 levels deep with branches of 1,000+ levels each. Error review process. Coordinate editors, writers, researchers, proofreaders, IT, and management. Manage 5 separate independent technical volumes. Database architecture. Dynamic data entry forms. User security. High-level reporting.

Languages and database

Visual Basic 6, SQL Server, Paradox, Oracle.

Company size

Fortune 500. Distribution of over 1 million copies per set.

Industry

Publishing / technical and industrial reference.

❓ What problem did this project solve?

The publisher was managing 5 separate technical encyclopedia projects from an old database and handwritten form tracking system. Each publication covered a distinct technical or industrial domain, with data gathered from more than 100,000 sources and organized into category structures up to 50 levels deep with over 1,000 branches at each level. Tracking that volume of data through its full research, verification, editing, and production cycle across hundreds of employees and contractors was not possible with the existing tools.

The project arrived as a Y2K remediation with a publication deadline already in jeopardy. The existing legacy systems spanned multiple database platforms including Paradox and Oracle, none of which were talking to each other. Getting the data consolidated, verified, and formatted for both CD-ROM and print publication required a unified system that could manage millions of records, track the research audit trail for each data point, and produce accurate production reports for a deadline-driven publishing operation.

🛠️ What PCG built

The scale of this project required PCG to triple its staff, bringing in developers, business and systems analysts, database administrators, and networking engineers. Within 8 months, the team gathered business specifications from the publisher's editors, writers, researchers, proofreaders, IT staff, and management, analyzed the multiple legacy database systems, and delivered a complete new book management platform.

The core of the system was a dynamic interface that generated data entry forms through SQL queries, allowing the platform to adapt to each publication's specific data structure without requiring custom-coded forms for every category. That architecture was what made it possible to manage 5 independent technical volumes, each with its own deep category hierarchy, from a single interface.

Every data point moved through a documented audit trail from initial research contact through verification, editorial review, and final production. The error review process flagged inconsistencies before they reached the production stage. Scheduling tracked the research verification status of millions of records against the publication deadlines for both the CD-ROM and print editions. The publisher met its deadlines, and each set reached distribution of over 1 million copies.

🔍 Technology used

Visual Basic 6 SQL Server Paradox Oracle Dynamic SQL-driven form generation Multi-platform legacy database consolidation Research audit trail management CD-ROM and print production output
Managing a large-scale content, research, or data publishing operation across systems that were not built to work together? PCG starts every project with a diagnostic that scopes the work before any development begins.
Talk to PCG

PCG founded 1995. All project details drawn from PCG's internal documentation. Client identity withheld at client request.

Frequently Asked Questions

The answer on this project was to build a dynamic interface where the forms themselves were generated from SQL queries rather than hard-coded. That meant the data entry structure could be modified as requirements evolved across five separate encyclopedia publications without rebuilding the underlying system each time. PCG tripled its staff for this engagement, bringing in developers, business and systems analysts, database administrators, and networking engineers. Within 8 months, the team gathered business specifications from multiple legacy database systems, completed analysis and design, and deployed an entirely new system. The publication deadlines for both electronic and print volumes were tracked directly in the system so that production status was always visible against the delivery schedule.
For a technical and industrial encyclopedia covering 100,000-plus source records, the taxonomy has to be deep enough to place every fact in a precise location within the reference structure while remaining navigable for researchers, editors, and writers who are not database administrators. PCG built the categorization architecture to support up to 50 levels of depth with branch structures exceeding 1,000 nodes per level. The interface surfaced only the relevant portion of that hierarchy at any given data entry point, so the depth of the underlying structure did not burden the people working in it daily. The security model also controlled which user types could access and modify which branches, since editors, writers, investigators, and IT staff had different permissions across the same data set.
Every source contact in this system had a timestamped record of initial contact, follow-up contacts, data received, verification status, and the data investigator responsible for each interaction. The scheduling module coordinated recontact dates so that sources requiring follow-up did not fall through the cracks when investigators were working across tens of thousands of records simultaneously. Error review criteria were built into the data entry workflow so that records flagged for verification could not move forward in the publication process until the flag was cleared. For a Fortune 500 publisher distributing more than one million copies per set internationally, a fact that traced back to an unverified source was a liability. The audit trail was not a reporting feature added at the end. It was woven into how data moved through the system from first contact to final publication.
This is exactly what PCG did on this project. The client was running multiple legacy systems including Visual Basic 6, SQL Server, Paradox, and Oracle, each managing a different part of the publication workflow. PCG analyzed each system's data structures, mapped the relationships between them, and designed a consolidated architecture that preserved the data relationships each legacy system depended on while unifying them under a single interface. The five publications that represented 85% of the client's total product base all ran through the new system. The consolidation was completed within an 8-month window that included a Y2K remediation component, which added its own deadline pressure to an already complex migration.
This project required PCG to triple its team for the duration of the engagement. The full roster included software developers, business and systems analysts, database administrators, and networking engineers working in parallel across analysis, design, development, and deployment phases. The 8-month timeline from business specification gathering to full deployment was tight given the scope: five publication systems, multiple legacy platforms to analyze, millions of records to migrate, and a staff of editors, writers, data investigators, proofreaders, and IT personnel who all needed training on a system that had to be intuitive enough to use without disrupting their actual research work. Projects of this complexity are scoped individually. Contact PCG to discuss what an engagement of this type would look like for your organization.

Related Projects

Health Care and Medical Scheduling Application
Residential Care Medical Scheduling Software for Senior Care Facilities

.NET/Health Care/

Small Business Projects - Constrution Estimator and Management System
Construction Estimator and Management System for Housing Subcontractors

.NET/Small Business/