Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Add Directory of Open Access Journal (DOAJ) as new source

未关闭
#244 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
python
领域
backend, data

调研方向

从现有的数据源集成和 https://doaj.org/api/docs 上的 DOAJ API 文档开始,然后检查 journals 端点、分页、速率限制以及列出的 BibJSON 字段。完成的标准是:DOAJ 期刊元数据已被导入,并且文档中说明的许可和历史数据限制得到了清晰的表示。

由索引模型根据 Issue 内容生成。

描述

✨ goal: improvement 💻 aspect: code 🟩 priority: low 🧹 status: ticket work required

Problem Statement

The quantifying commons project currently lacks coverage of open access academic journals, which represent a significant portion of the scholarly commons. DOAJ provides comprehensive metadata on over 22,000 open access journals with detailed Creative Commons licensing information. DOAJ provides rich metadata including license types, publisher information, country codes, subject classifications, and open access start dates, making it ideal for detailed commons analysis.

Relevant API Links
Useful Search Fields
  • License Information: bibjson.license[].type
  • Publisher Details: bibjson.publisher.name, bibjson.publisher.country
  • Open Access Start: bibjson.oa_start
  • Subject Classification: bibjson.subject[].code, bibjson.subject[].term
  • Language: bibjson.language[]
  • Last Updated: last_updated
  • Created Date: created_date
API Limitations
  • Rate Limits: Current delays 0.5 seconds between requests
  • Articles: No direct license information available
  • Pagination: Maximum pageSize appears to be 100
  • Historical Data: License information may reflect current status, not original licensing
  • Date Filtering: Only available through oa_start field, not license adoption date
  • Date Back Default: 2002 (to avoid CC license false positives)

Additional context

The DOAJ data source provides journal-level licensing policies rather than individual article licenses. The Creative Commons license information collected represents the default licensing framework that journals have committed to implementing, as declared in their editorial policies and reported to DOAJ (https://doaj.org/apply/guide/).

This data does not reflect the actual licensing status of individual published articles, which may vary from the journal's stated policy due to author choices, publisher agreements, or historical publishing practices predating the journal's current licensing framework.

The quantification derived from DOAJ therefore represents the scope of journals committed to Creative Commons licensing rather than a direct count of CC-licensed articles. This distinction is particularly relevant for temporal analysis, as journals may have adopted CC licensing policies after publishing content under different terms, and individual authors within CC-committed journals may still select more restrictive licensing options where permitted by editorial policy.

The DOAJ API documentation (https://doaj.org/api/docs) confirms that article-level license metadata is not available through their search endpoints.

Users of this data should interpret DOAJ-derived metrics as indicators of institutional commitment to open access licensing within the scholarly publishing ecosystem, rather than as precise measurements of the volume of CC-licensed scholarly content. This limitation does not diminish the value of DOAJ data for understanding trends in open access policy adoption, geographic distribution of OA-committed publishers, and the evolution of scholarly publishing practices toward more open licensing frameworks. Additional context on DOAJ's selection criteria and quality standards can be found in their information for publishers (https://doaj.org/publishers/) and their principles of transparency and best practice (https://doaj.org/bestpractice/).

Implementation

  • I would be interested in implementing this feature.
主要语言
Python
星标
48
派生
74
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

creativecommons/quantifying 的其他 Issue

查看 creativecommons/quantifying 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。