S04-映射表构建

Builds a CSV mapping table assigning unique IDs and search-term hit data to each bibliographic record.

Updated May 18, 2026
One-click install
npx skills add https://github.com/heyixue511-creator/ai --skill s04-heyixue511-creator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: S04-映射表构建
Source: https://github.com/heyixue511-creator/ai/tree/main/My-Own-Skills-main/%E6%96%87%E7%8C%AE%E8%AE%A1%E9%87%8F%E5%88%86%E6%9E%90%E6%8A%80%E8%83%BD/S04-%E6%98%A0%E5%B0%84%E8%A1%A8%E6%9E%84%E5%BB%BA
Command: npx skills add https://github.com/heyixue511-creator/ai --skill s04-heyixue511-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Literature screening projects need a single operational hub that tracks every record's ID, verdict, and revision history across multiple cleaning rounds. Without a unified mapping table, judgments get lost, records are missed, and revisions cannot be traced. ## Core Features & Use Cases - Unique ID Assignment: Assigns an immutable sequential number (seq) to every record, guaranteeing full coverage with no omissions or duplicates. - Search-Term Hit Analysis: Decomposes the search query into concept groups (G1, G2, G3...) and records which groups and exact word forms hit each record. - Multi-Round Revision Tracking: Preserves verdict history and per-round noise types so every modification leaves an auditable trace. - Use Case: After exporting 2,000 records from Web of Science, run this skill to create the master mapping CSV with seq, source_id, title, year, concept group, and hit words, ready for downstream relevance judgment rounds. ## Quick Start Build the literature mapping table from my exported records file and save it to the classification output directory.

Frequently Asked Questions about S04-映射表构建

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a mapping table for literature screening records?▼

Iterate through the raw export file and create one row per record with an incrementing seq number, the platform's unique source ID (UT/DOI/PMID), title, year, and document type. Then fill concept group and hit word fields from search-term analysis, leaving verdict fields empty for later rounds.

How to track search term hits per bibliographic record?▼

Decompose the search query into independent concept groups (e.g., G1, G2, G3), then test each record against every group. Record which groups matched in the concept_group field and the exact matched word forms in the hit_words field.

What fields should a literature screening mapping table include?▼

Core fields are seq (immutable ID), source_id, title, publication year, document type, concept_group, hit_words, verdict, noise_type, reason, and round. Extended fields like verdict_history and per-round noise types preserve revision traces across cleaning rounds.

Should the mapping table be rebuilt in later screening rounds?▼

No. Later rounds load the existing table and only update verdict, noise_type, reason, and round fields in place. When revising an earlier judgment, note the history in the reason field, and never modify the seq identifier.

How do I validate consistency of a bibliographic mapping CSV?▼

Check that row count equals the raw record count, seq values run continuously from 1 to N without gaps or duplicates, source_id values are unique, and the file is saved as UTF-8 with BOM encoding.