Last checked with GitLab: . Status comes from GitLab using a 2-minute cache. Merge events clear affected cached statuses. An already-open page does not update itself. Refresh page.

An MR completes this bounty when it is merged into main with Closes #286 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.

Description

The research-citations guide recommends Zotero and citation traceability. Provide a small offline metadata check for a CSL-JSON export, without scraping sources or generating facts.

Who might enjoy this

  • Community interests: Research, Tech
  • Skills: python, docs, data
  • Experience: starter; work style: automation.
  • Readiness: ready; bounty size: S (existing points tier; standard merge award stacks separately).

Current behavior and starting points

Source-reviewed against main cf05b29c6256dba70d0ebc09b22cc9867cdb786a on2026-10-18. Check current main and related issues/MRs before implementing so existing work is reused.

Relevant Files

Deliverables

  • A Python standard-library checker for the documented CSL-JSON subset: stable ID, title, author or organization, date/unknown and source locator.
  • Synthetic bibliography fixtures and a guide showing how to interpret duplicate/missing-field findings.

Dependencies and decisions

No prerequisite issue is required. Re-read current main and linked MRs before starting.

Acceptance criteria

  • [ ] Known-good fixture passes; duplicate IDs, duplicate normalized DOI strings, absent title and malformed dates yield record-specific findings and a nonzero status.
  • [ ] An explicitly unknown date remains different from an omitted field; Unicode names and organization authors survive intact.
  • [ ] The tool reads only the selected JSON file, never resolves URLs/DOIs, and does not rewrite the bibliography.
  • [ ] Record named baseline failures and the exact commands used. A behavior fix includes a real route/database/protocol check observed failing before the change. Knowledge work includes source traceability and reproducible reviewer evidence.
  • [ ] Run the affected app's existing checks. Explain any baseline failures rather than reporting a matching failure count as proof.

Try it locally

Start from the existing source files above. The following is the target demo your contribution should enable; a newly proposed script or fixture is part of the deliverable:

Run python3 apps/wiki/scripts/check_research_citations.py <synthetic-csl.json>; remove one title and inspect the record-specific finding.

Use public or synthetic examples. Starter work should run without production access; explicitly name any software/device prerequisite before claiming it is ready.

Out of scope

  • No bibliography authoring AI, network link checker, archive manifest audit or new citation service.
  • Distinct from #204 broken-link reporting and #252 archive manifests.
  • Unrelated refactors, new services/providers, bulk dependency changes, production access changes, unrequested notifications, and copying private member material. Keep credentials and unresolved security findings outside the issue and repository.

For a coding agent and reviewer

Read AGENTS.md, applicable .cursor/rules/, app instructions and docs/contributing/agentic-bounty-review.md. Reuse the existing shared helpers, identity/access paths and app styling. Implement one bounded story and provide evidence the accepting app maintainer can reproduce. State updated / pre-release verified / released / live verified accurately.

A parent index carries no duplicate award for these child deliverables. Open one scoped MR using this issue's actual number after the closing keyword. Link your GitLab identity on Scoreboard; the existing merge webhook handles eligible points.

Catalog index: #258.

<!-- community-interest-bounty:2026-10-18:research-citation-metadata -->

Relevant files

Hints

No hints yet.

Activity

  • +50 Hugo Zarate earned S bounty Oct 19

Comments

No comments yet. Be the first to weigh in.

↑ Top