About · How to cite

What this site is

RISE — Research Information Systems Engineering is a public, living knowledge base introducing RISE as a sub-discipline of information systems concerned with the design and study of information systems whose primary purpose is to produce scholarly knowledge. The framing, scope, and intellectual lineage are laid out under Concept.

The site is a hobby project, maintained in the open — not yet a peer-reviewed scientific contribution. Treat the synthesis, scorings, and classifications as the curator's current best-effort view, subject to revision as the field moves.

Who maintains it

Björn Hanneke — Goethe University Frankfurt, Faculty of Economics and Business.

• Email: hanneke@wiwi.uni-frankfurt.de
• GitHub: @bhanneke

Corrections, suggestions, and PRs are welcome via the GitHub repository (see Contributing).

How it was built

Curation is done through Claude Code (Anthropic) workflows under the curator's review. Specifically:

• Paper notes are drafted by Claude Code from the source PDF and verified by the curator against the original before being committed.
• Project scorings are produced by Claude Code from the project's README, paper(s), and code base, with the curator setting the rubric and approving final scores.
• Skill packs are bundled from upstream sources (Anthropic, EvoScientist, ARIS, P. Sant'Anna, et al.) with attribution intact; the curator does not modify upstream skill text.
• Builds and indexes are regenerated by the scripts under scripts/ from YAML / BibTeX sources; the rendered pages under docs/papers/index.md, docs/projects/index.md, and docs/skills/*.md are auto-generated.

The same operational approach the site documents — augmentation, not automation, with human verification at every commit — is the one used to produce the site itself.

How to cite

If you reference this knowledge base in academic or technical work, please use the citation below.

DOIs

The Zenodo deposit issues two DOIs:

• Concept DOI (always resolves to the latest version): 10.5281/zenodo.20396427 — use this when citing the project.
• Version DOI (this release, v0.2.0): 10.5281/zenodo.20396428 — use this when citing a specific snapshot (recommended for academic work, so your citation does not silently drift as the site grows).

BibTeX

BibTeX

@misc{hanneke2026rise,
  author       = {Hanneke, Bj{\"o}rn},
  title        = {{RISE} --- Research Information Systems Engineering
                  ({Knowledge Base})},
  year         = {2026},
  version      = {0.2.0},
  publisher    = {Zenodo},
  doi          = {10.5281/zenodo.20396428},
  url          = {https://doi.org/10.5281/zenodo.20396428},
  howpublished = {GitHub Pages knowledge base},
  note         = {CC-BY-4.0 licensed; source at
                  \url{https://github.com/bhanneke/RISE};
                  concept DOI for all versions:
                  \url{https://doi.org/10.5281/zenodo.20396427}}
}

APA

Hanneke, B. (2026). RISE — Research Information Systems Engineering (Knowledge Base) (Version 0.2.0) [Knowledge base]. Zenodo. https://doi.org/10.5281/zenodo.20396428

CITATION.cff

A machine-readable CITATION.cff file is kept at the repository root, conforming to the Citation File Format v1.2.0.

Citing a specific snapshot

For a frozen-in-time reference, use the version-specific Zenodo DOI above (e.g. 10.5281/zenodo.20396428 for v0.2.0). Each tagged release on GitHub triggers an automatic Zenodo deposit via the GitHub–Zenodo integration, so every published version has its own DOI alongside the concept DOI.

The Zenodo record ships a zip bundle (rise-knowledge-base-v<VERSION>.zip) containing the papers BibTeX, the project YAMLs, the rubric, the concept pages, and the bundled skill packs as of that release.

Licensing

• Content (paper notes, project descriptions, concept pages, curator commentary, rubric, vocabularies): CC-BY-4.0. You may reuse with attribution.
• Code (build scripts, fetchers, bundlers under scripts/): MIT.
• Skill packs bundled under docs/skills/ retain their upstream licenses (named in each pack's YAML and in the per-skill page metadata card). RISE redistributes them under each pack's original terms.
• Underlying papers referenced in the papers catalog remain the intellectual property of their authors and publishers. RISE indexes them; it does not relicense them.

Provenance and what to trust

Three classes of content with different epistemic status:

• Curator notes on papers — verified by reading the source PDF; treat as a faithful summary. Any quote is checked against the PDF text; if you spot a divergence, please file an issue.
• Project scorings on the rubric — the curator's best-effort judgement from publicly available materials. Reasonable people may disagree on individual sub-scores; the per-dimension notes on each project page show the reasoning.
• Concept-page synthesis — opinionated. The framing argues a position; it is not a neutral survey. Counter-arguments from the literature are linked where the framing risks overstating.

When uncertain, trust the source documents (the linked papers and project repositories) over RISE's summaries.

Acknowledgements

• Anthropic for Claude Code, the agent that does most of the drafting and verification work.
• The maintainers of every upstream project bundled in the skills catalog — attribution lives in each pack's page.
• The authors of every paper in the papers catalog — RISE exists to point readers to your work.

Contact

For typos, broken links, scoring disputes, missing papers, or missing projects: open an issue on GitHub or email hanneke@wiwi.uni-frankfurt.de.

For collaboration on the underlying research agenda (a sub-discipline identity for RISE, an empirical study of agentic-research pipelines, a position piece for the ISR special issue): same address.