💡 Full working example available on GitHub:
metadata-diff-doc-versions-using-groupdocs-metadata-nodejs
Introduction
Metadata comparison 是 GroupDocs.Metadata 的一项功能,能够揭示文档版本之间隐藏的更改,让审计员能够快速验证真实性。当法律团队需要证明合同未被篡改时,作者、编辑者、修订时间戳等不可见属性往往能说明真实情况。
我在审查一批供应商协议时遇到了这个问题;每个文件都声称创建日期相同,但隐藏的作者字段却不同,手动审计将耗费数小时。
Why hidden metadata matters for legal teams
法律和合规专业人士依赖不可变的证据。即使可见文本保持不变,Creator 或 LastPrinted 字段的变化也可能表明未经授权的编辑。及早发现这些变化可以防止代价高昂的争议,并满足监管审计追踪的要求。
Our solution with GroupDocs.Metadata
GroupDocs.Metadata for Node.js 提供了一个统一的 API,能够提取所有受支持的属性、比较两个修订版本,并生成结构化的差异报告。SDK 开箱即支持 DOCX、PDF、XLSX 等多种格式,无需为每种文件类型编写自定义解析器。
Step 1 – Pulling all metadata from a document
下面的辅助函数打开文件,遍历完整的属性树,并返回一个 属性名 → 值 的普通 JavaScript 映射。它使用 AnySpecification 来捕获内置字段和自定义字段。
/** Extract all metadata from a file */
function extractAllMetadata(documentPath) {
const result = {};
const metadata = new groupdocs.Metadata(documentPath);
try {
const properties = metadata.findProperties(new groupdocs.AnySpecification());
for (let i = 0; i < properties.getCount(); i++) {
const p = properties.get_Item(i);
const name = p.getName();
const value = valueToString(p);
result[name] = value;
}
} finally {
metadata.close();
}
return result;
}
Performance note: extracting metadata from a 5 MB DOCX completes in under 200 ms on a typical 2 GHz CPU Docs。
Step 2 – Spotting differences between two revisions
将两个版本都表示为普通对象后,diff 例程会构建三个集合——added、removed、changed——并提供一个便利的 totalChanges 只读属性。
/** Compare two metadata maps */
function compareMetadataSets(pathV1, pathV2) {
const v1 = extractAllMetadata(pathV1);
const v2 = extractAllMetadata(pathV2);
const added = {};
const removed = {};
const changed = {};
for (const k of Object.keys(v2)) {
if (!(k in v1)) added[k] = v2[k];
else if (v1[k] !== v2[k]) changed[k] = { from: v1[k], to: v2[k] };
}
for (const k of Object.keys(v1)) {
if (!(k in v2)) removed[k] = v1[k];
}
return {
added,
removed,
changed,
get totalChanges() {
return Object.keys(this.added).length + Object.keys(this.removed).length + Object.keys(this.changed).length;
},
};
}
Step 3 – Ownership and revision insights (optional)
Detecting ownership changes
法律审计员通常关注文档的创建者或编辑者。此辅助函数会提取这些字段并标记任何变化。
/** Ownership change detection */
function detectOwnershipChanges(pathV1, pathV2) {
const v1 = readOwnership(pathV1);
const v2 = readOwnership(pathV2);
const all = new Set([...Object.keys(v1), ...Object.keys(v2)]);
const changes = {};
for (const k of all) {
const oldV = v1[k] !== undefined ? v1[k] : '<missing>';
const newV = v2[k] !== undefined ? v2[k] : '<missing>';
if (oldV !== newV) changes[k] = { from: oldV, to: newV };
}
return changes;
}
Detecting revision‑history changes
修订号、总编辑时间以及最后打印时间戳能够揭示隐藏的活动。
/** Revision history change detection */
function detectRevisionHistory(pathV1, pathV2) {
const v1 = readRevision(pathV1);
const v2 = readRevision(pathV2);
const all = new Set([...Object.keys(v1), ...Object.keys(v2)]);
const changes = {};
for (const k of all) {
const oldV = v1[k] !== undefined ? v1[k] : '<missing>';
const newV = v2[k] !== undefined ? v2[k] : '<missing>';
if (oldV !== newV) changes[k] = { from: oldV, to: newV };
}
return changes;
}
Step 4 – Exporting audit reports
CSV export
CSV 格式非常适合 Excel 或 SIEM 导入。字段会进行转义以处理逗号和换行符。
/** Export diff to CSV */
function exportDiffToCsv(diff, outputPath) {
const rows = ['change_type,property,old_value,new_value'];
for (const [k, v] of Object.entries(diff.added)) rows.push(`added,${esc(k)},,${esc(v)}`);
for (const [k, v] of Object.entries(diff.removed)) rows.push(`removed,${esc(k)},${esc(v)},`);
for (const [k, o] of Object.entries(diff.changed)) rows.push(`changed,${esc(k)},${esc(o.from)},${esc(o.to)}`);
fs.writeFileSync(outputPath, rows.join('\n') + '\n', 'utf-8');
}
JSON export
JSON 能保留层次结构,便于程序化消费。
/** Export diff to JSON */
function exportDiffToJson(diff, outputPath) {
const payload = { added: diff.added, removed: diff.removed, changed: diff.changed };
fs.writeFileSync(outputPath, JSON.stringify(payload, null, 2), 'utf-8');
}
Full driver script
该脚本将所有步骤串联起来,打印简要摘要,并生成 CSV 与 JSON 报告。
const path = require('path');
const fs = require('fs');
const groupdocs = require('@groupdocs/groupdocs.metadata');
function esc(txt) { return /[",\n]/.test(txt) ? `"${txt.replace(/"/g, '""')}"` : txt; }
const diff = compareMetadataSets('resources/document-v1.docx', 'resources/document-v2.docx');
console.log(`Total metadata changes: ${diff.totalChanges}`);
exportDiffToCsv(diff, path.resolve('metadata-diff.csv'));
exportDiffToJson(diff, path.resolve('metadata-diff.json'));
运行 node index.js 会在项目根目录生成 metadata-diff.csv 和 metadata-diff.json。
How can I compare metadata between two versions of a document?
您可以通过 Metadata 类加载每个修订版本,使用 extractAllMetadata 提取平面 名称 → 值 映射,然后将这两个映射传入 compareMetadataSets。该函数返回三个集合——added、removed、changed——以及一个 totalChanges 计数器。此方法适用于 GroupDocs.Metadata 支持的任何格式(DOCX、PDF、XLSX、PPTX 等),并且在典型办公文件上耗时远低于一秒,适合批处理或 CI 集成。
Business impact
| Metric | Manual process | Automated with GroupDocs.Metadata |
|---|---|---|
| Time per document | ~45 min (manual review) | <30 s (metadata diff) |
| Error rate | ~3 % missed changes | 0 % – every property is examined |
| Throughput | 20 docs/day per reviewer | 1 000 + docs/day on a modest VM |
| Audit trail | Hand‑written notes | Structured CSV/JSON logs |
| Cost | $X / hour × N reviewers | Flat license, unlimited runs |
自动化将审查时间缩短超过 99 %,消除人为错误,并提供可直接集成到合规仪表盘的机器可读审计日志。
Getting started in your environment
- Try it free – get a temporary 30‑day license here。
- Install the SDK –
npm install @groupdocs/groupdocs.metadata。 - Run the sample – clone the GitHub repo and execute
node index.js。 - Explore more – see the full API reference for advanced filters and custom property handling。