Add Directory of Open Access Journal (DOAJ) as new source
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 35/100
Direzione di ricerca
Inizia con le integrazioni esistenti delle fonti di dati e con la documentazione dell’API DOAJ all’indirizzo https://doaj.org/api/docs, quindi esamina l’endpoint journals, la paginazione, i limiti di frequenza e i campi BibJSON elencati. Il lavoro è completato quando i metadati delle riviste DOAJ vengono acquisiti e le limitazioni documentate relative alle licenze e ai dati storici sono rappresentate chiaramente.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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
- Api Version: v4
- Base URL: https://doaj.org/api/
- Journals Endpoint: https://doaj.org/api/v4/search/journals/
- Articles Endpoint: https://doaj.org/api/v4/search/articles/
- API Documentation: https://doaj.org/api/docs
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
pageSizeappears to be 100 - Historical Data: License information may reflect current status, not original licensing
- Date Filtering: Only available through
oa_startfield, 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.
- Lingua principale
- Python
- Stelle
- 48
- Fork
- 74
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di creativecommons/quantifying
-
🏁 status: ready for work 💻 aspect: code 🛠 goal: fix help wanted 🟩 priority: low
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
creativecommons/quantifying#300 · 1 commento · 1 reazione ·
-
GCS free full web search ending 2026-12-31Forse di nuovo libera @TimidRobot l’ha presa 153 giorni fa e non c’è nessuna pull request aperta. Aperta🏁 status: ready for work 💻 aspect: code 🔒 staff only 🛠 goal: fix 🟧 priority: high
creativecommons/quantifying#293 · 1 commento · 1 assegnatario ·
-
Consolidate completion checkAperta✨ goal: improvement 🏁 status: ready for work 💻 aspect: code help wanted 🟩 priority: low
Difficoltà 4/5 3-5 giorni Idoneità per principianti 38/100
creativecommons/quantifying#288 ·
-
Add a stacked horizontal bar plotForse di nuovo libera @oree-xx l’ha presa 249 giorni fa e non c’è nessuna pull request aperta. Aperta✨ goal: improvement 💻 aspect: code 🚦 status: awaiting triage 🟩 priority: low
creativecommons/quantifying#274 · 1 assegnatario ·
-
✨ goal: improvement 🏁 status: ready for work 💻 aspect: code help wanted 🟩 priority: low
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
creativecommons/quantifying#249 ·
Tutte le issue di creativecommons/quantifying
Issue simili
-
needs-human needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
gke-labs/kube-agents#2400 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Device Details tables: FS/SF columns contradict each other (nfet_01v8 Vt row, pfet_01v8 Idsat row)Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
google/skywater-pdk#450 ·
-
Drained trajectory arrays are overwritten when the sequence buffer is reusedForse già presa @sylvesterkaczmarek l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
google-deepmind/bsuite#56 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
LearningCircuit/local-deep-research#7206 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
chingu-voyages/V62-tier3-team-33#285 ·
I maintainer di solito rispondono entro 1 giorno