0 Connect Google Drive

OAUTH CLIENT ID

API KEY

DRIVE FOLDER ID (your spec database)

◆ ACCESS LEVELS — assigned automatically from your Google email after sign-in

admin

Full access · manages the Users sheet · build & upload

editor

Connect · build spec books · save back to Drive

viewer

Read-only · browse matched specs, no build / upload

One-time setup (needed before first connect) — click to expand

Go to Google Cloud Console → create a project (free).
APIs & Services → Library → enable Google Drive API.
Credentials → Create credentials → API key. Copy it into the API KEY box above.
Create credentials → OAuth client ID → Web application. Under Authorized JavaScript origins add exactly where you open this file, e.g. http://localhost:8000. Copy the Client ID into the box above.
OAuth consent screen → add your own Google account under Test users.
Serve the file (don't double-click it). In its folder run python -m http.server 8000, then open http://localhost:8000/Spec_Book_Builder_Drive.html.

Keys are stored only in this browser (localStorage) and sent only to Google. Nothing goes anywhere else.

1 BOQ list — auto-loaded from Drive, or drop a file

Drop your BOQ list here

.xlsx · .xls · .csv — auto-detects header, description & reference columns

2 Specification PDFs — auto-loaded from Drive, or drop files

Drop all spec PDFs here

Each file named by its reference, e.g. MVS32H4MW6L.pdf

3 Options & build

Divider page before each spec Index / table of contents Title cover page (ATS logo) Page numbers Normalize page size (A4) Save result back to Drive folder

OUTPUT FILE NAME

AUTO MODE · “Connect & sign in”, then “Auto-build from Drive” reads every PDF and the component database (a spreadsheet named like Components_DB) directly from your folder, matches each BOQ row to a PDF by reference, merges in BOQ order, and (optionally) uploads the finished book back to Drive.
MANUAL MODE · Without keys it still works the old way — drop the BOQ and PDFs in yourself.