Skip to content

feat: add enterprise export pipeline#72

Open
ryanll wants to merge 1 commit into
SCIBASE-AI:mainfrom
ryanll:enterprise-export-pipeline-19
Open

feat: add enterprise export pipeline#72
ryanll wants to merge 1 commit into
SCIBASE-AI:mainfrom
ryanll:enterprise-export-pipeline-19

Conversation

@ryanll
Copy link
Copy Markdown

@ryanll ryanll commented May 14, 2026

@algora-pbc /claim #19

Summary

  • Adds a self-contained enterprise-export-pipeline module for the Enterprise Tooling bounty.
  • Implements deterministic one-click export packages for institutional repositories, arXiv, PubMed Central, Zenodo, journal submissions, NIH RePORTER, and Horizon Europe.
  • Preserves DOI, ORCID, citation tracking, version history, content checksums, compliance evidence, formatting plugin hints, and signed webhook handoff metadata.
  • Keeps the implementation locally reviewable with no external accounts, API keys, or hosted services.

Requirement coverage

  • Admin dashboards: /api/dashboard summarizes export target readiness, blockers, warnings, lanes, package counts, and webhook topics.
  • API and webhooks: /api/targets, /api/export, /api/compliance, and /api/webhook expose reviewer-ready integration payloads.
  • Export pipelines: target profiles cover institutional repositories, preprints, indexed repositories, journal submission systems, and funder portals.
  • Formatting plugins: each package declares deterministic plugin metadata for repository bundles, LaTeX preprints, JATS indexed exports, journal submissions, and funder reports.
  • Metadata preservation: package manifests include DOI, ORCID, citation graph, version history, checksums, provenance, license, and repository URL.
  • Compliance tracking: funder mandates, open access status, data availability, ethics, retention, consent, audit review, and reproducibility score are surfaced per target.

Demo

  • enterprise-export-pipeline/demo/README.md documents the short reviewer demo flow.
  • enterprise-export-pipeline/demo/demo-text.txt contains the scripted demo summary.
  • The live demo is reproducible locally with the API smoke commands below.

Verification

cd enterprise-export-pipeline
npm run check
npm test
PORT=4349 npm start

API smoke tested locally:

curl -fsS http://localhost:4349/api/targets
curl -fsS "http://localhost:4349/api/export?target=zenodo"
curl -fsS "http://localhost:4349/api/compliance?target=nih-reporter"
curl -fsS "http://localhost:4349/api/webhook?target=journal-submission"

Local results:

  • npm run check passed
  • npm test passed: 7/7 tests
  • API smoke returned target list, Zenodo package, NIH compliance evidence, and signed journal webhook event

Notes

Prepared with OpenAI Codex assistance and locally validated before submission.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant