Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
#244 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
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 はありません

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

creativecommons/quantifying のほかの issue

creativecommons/quantifying の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。