使用与引用Guide
一、站点结构1. Site structure
- 首页:项目导览与“从哪读起”推荐。
- 概念与思想史:术语对照、时间线与核心争论,适合教学与入门。
- 检索资料库:著作、论文、数据集三个分库,支持搜索、筛选与导出。
- 学者档案:研究者画像,可与资料库条目互相跳转。
- 中文世界研究:中文文献与译著汇总,以及面向中国的研究数据集。
- 使用与引用(本页):操作说明与维护指南。
- Home: overview and “where to start” picks.
- Concept & History: glossary, timeline, core debates — for teaching and orientation.
- Library: three sub-catalogues (books, papers, datasets) with search, filter, and export.
- Scholars: researcher profiles cross-linked with library entries.
- Research in Chinese: Chinese-language works, translations, and China-focused datasets.
- Guide (this page): instructions and maintenance notes.
二、检索与导出2. Searching & exporting
- 在资料库页输入关键词可检索标题、作者、摘要、期刊与出版社(中英文均可)。
- 可用“主题 / 年代 / 语言”下拉框组合筛选;点“清除筛选”恢复全部。
- “BibTeX”与“CSV”按钮导出当前筛选结果。BibTeX 适合 Zotero、EndNote、JabRef 等文献管理软件;CSV 可用 Excel / Numbers / R / Python 打开。
- 点击任意条目卡片可查看详情(含双语摘要、中译本信息、来源链接与单条 BibTeX)。
- Type keywords in the library page to search titles, authors, abstracts, journals, and publishers (in Chinese or English).
- Combine the topic / period / language dropdowns; “Clear” resets all filters.
- The “BibTeX” and “CSV” buttons export the currently filtered results. BibTeX suits Zotero, EndNote, and JabRef; CSV opens in Excel, Numbers, R, or Python.
- Click any card to see full details: bilingual abstract, Chinese-edition info, source links, and a ready-made BibTeX entry.
三、条目字段说明3. Entry fields
每条目是一个独立的 JSON 文件,存放于 data/books、data/papers、data/datasets 或 data/scholars。公共字段包括:id(唯一标识)、中英标题、作者、年份、出版信息(出版社/期刊/DOI/ISBN/URL)、lang(语言)、tags(主题标签)、related(关联条目)、双语摘要 abstractEn/abstractZh,以及 sources(核验来源)。各类型另有专属字段,例如论文的卷期页码、数据集的覆盖年份与访问方式、学者的学科与代表作。
主题标签使用受控词表(见 data/taxonomy.json),新增标签需同步维护词表。字段级说明见各目录下的 _template.json。
Each entry is a standalone JSON file under data/books, data/papers, data/datasets, or data/scholars. Common fields: id (unique), bilingual titles, authors, year, publication data (publisher/journal/DOI/ISBN/URL), lang, tags, related, bilingual abstracts abstractEn/abstractZh, and sources. Type-specific fields exist too — volume/issue/pages for papers, coverage years and access mode for datasets, discipline and key works for scholars.
Tags come from the controlled vocabulary in data/taxonomy.json; new tags must be added there. Field-level guidance is inside each _template.json.
四、如何新增 / 修改条目4. Adding / editing entries
- 在对应目录复制
_template.json,重命名为有意义的 id,如data/books/young-1958.json。 - 按字段说明填写;
id必须全站唯一,主题标签须在词表中存在。 - 在项目根目录运行刷新脚本,它会校验必填字段与 id 唯一性,并把全部条目合并进
assets/data/data.js:
- Copy
_template.jsonin the relevant directory and rename it with a meaningful id, e.g.data/books/young-1958.json. - Fill in the fields;
idmust be globally unique and tags must exist in the taxonomy. - Run the refresh script at the project root. It validates required fields and id uniqueness, then merges all entries into
assets/data/data.js:
powershell -ExecutionPolicy Bypass -File tools\refresh.ps1
Windows 也可直接运行 pwsh tools/refresh.ps1。脚本无需安装任何依赖。On Windows you may also run pwsh tools/refresh.ps1. The script needs no dependencies.
五、内容与版权原则5. Content & copyright policy
- 本站只提供元数据、摘要与来源链接,不转载全文;引用与使用请遵守原作者与出版社的版权与许可。
- 收录遵循“可核验”原则:条目依据公开来源(出版社、期刊、DOI、机构官网等)核对;无法核验者不收录或在备注中标明“待核验”。
- 摘要为编者撰写的简介,正式引用时请以原著为准;引用建议使用资料库导出的 BibTeX / CSV 并核对原文。
- This site provides only metadata, abstracts, and source links — never full texts. Respect the copyright and licenses of the original authors and publishers.
- Inclusion follows a “verifiable” rule: entries are checked against public sources (publishers, journals, DOIs, institutional sites); unverifiable items are excluded or marked “to verify”.
- Abstracts are editorial summaries; consult the originals for citation. We suggest exporting BibTeX / CSV from the library and double-checking against the source.
六、离线使用与部署6. Offline use & deployment
网站为纯静态页面,无外部字体、CDN 或后端依赖。本地双击 index.html 即可使用全部功能。若要发布到 GitHub Pages:把整个项目目录推送为仓库后,在仓库设置中开启 Pages 并选择根目录(默认分支 /root)即可,无需任何构建命令。
The site is fully static — no external fonts, CDNs, or backends. Double-click index.html locally to use everything. To publish on GitHub Pages: push the whole folder as a repository, enable Pages in repository settings, and select Deploy from a branch / root. No build step is needed.