This site is a bibliographic survey dedicated to research on port-Hamiltonian systems. Its goal is to provide a curated collection of publications that helps researchers follow developments in the field, identify potential research gaps, and discover related work.

The canonical bibliography is updated through reviewed maintenance cycles. A separate arXiv cache is refreshed automatically on a schedule so that recent preprints can be displayed without becoming part of the canonical bibliography.

Powered by BibReview

PHRAISE is powered by BibReview, an open-source, human-reviewed bibliographic engine for reproducible literature-review websites. BibReview manages the generic bibliographic workflow, provider integration, canonical metadata, contributor identities, audit/review tools, and deterministic generation of publication, author, and year pages. PHRAISE remains responsible for the port-Hamiltonian scope, scientific curation, project configuration, and Jekyll presentation.

How to Contribute?

Contributions are welcome for published work within the PHRAISE scope.

If the publication has a DOI, the preferred path is the automated one:

  • Submit a pull request adding a typed doi:<value> entry to data/newID.txt on the project’s GitHub repository.
  • Or send an email with the DOI or a metadata correction.

If the publication has no DOI, do not invent one and do not place another identifier such as an ISBN, arXiv ID, PMLR ID, or publisher ID in data/newID.txt. Instead, provide an official landing page or publication PDF together with the bibliographic information needed to verify the record. DOI-less publications are added through BibReview’s reviewed manual-import workflow, which keeps the metadata source, provenance and BibTeX inspectable before the normal staging and merge steps.

DOI is therefore PHRAISE’s sole strong/automatable identifier, but it is not a requirement for canonical inclusion.

Canonical bibliography changes are never merged automatically from provider output alone. Provider metadata, manual-import evidence, relevance decisions, and ambiguous contributor identities remain reviewable, and repository changes reach the production main branch through pull requests.

Scope & Methodology

Why DOIs for automation?

A DOI remains the preferred identifier whenever one exists because it provides a stable, normalized key for provider-based discovery, metadata collection, reconciliation and reproducible maintenance. In BibReview terminology, this makes DOI PHRAISE’s only current strong identifier: the only identifier allowed to drive the automated acquisition chain.

PHRAISE can also include published work without a DOI. Such records receive a persistent internal BibReview UUID and are added through a reviewed manual-import path using an official source, explicit provenance and tracked BibTeX. Other external identifiers such as PMLR, ISBN, arXiv or publisher-specific IDs may be retained as useful metadata, but they are not promoted to automatic merge keys.

Provider metadata and manual source material are both treated as evidence rather than unquestionable truth and may be corrected after review.

The PHRAISE project configuration is publicly available on the GitHub repository, while the generic bibliographic engine is maintained separately in the BibReview repository.

Data Sources

PHRAISE uses several external services for different purposes rather than relying on a single strict provider hierarchy:

  1. OpenAlex is used to discover DOI-backed candidate publications, provides independent comparison evidence during bibliography audits, and can supply an abstract when publisher/CrossRef enrichment leaves that field empty.
  2. CrossRef is the core metadata source for DOI-backed collection and also contributes independent audit evidence.
  3. Publisher APIs from Elsevier / Scopus, Springer Nature and IEEE Xplore can enrich records with information such as abstracts, keywords, or event metadata when available.
  4. Semantic Scholar and Mendeley also provide optional abstract fallback enrichment when configured. BibReview cleans fallback candidates before comparing them and retains the longest valid abstract available from OpenAlex, Semantic Scholar, or Mendeley. Semantic Scholar also contributes independent evidence to the audit workflow.
  5. DOI content negotiation is used for citation and BibTeX retrieval when available.

Provider output is never assumed to be infallible. BibReview keeps canonical data, staging, BibTeX, audit evidence, and enrichment proposals inspectable so that corrections can be reviewed before publication. Missing-field enrichment such as abstracts is explicitly human-reviewed before staging. Refresh operations cannot silently replace already-populated canonical metadata: provider differences on existing values remain review evidence rather than automatic changes.

PHRAISE stores bibliographic metadata, abstracts, keywords and related citation information when available; full texts are not collected.

The canonical database is available for download as JSON.

arXiv

The arXiv API is used by BibReview’s optional arXiv module to maintain a small display-only cache of recent preprints related to port-Hamiltonian systems.

The browser does not query arXiv dynamically. A scheduled GitHub Actions workflow refreshes the cache, opens or updates a dedicated pull request when the cache changes, validates that change through the PHRAISE integration workflow, and only then merges it. The published arXiv page therefore reads a static JSON cache from assets/data/arxiv.json.

arXiv entries remain separate from the canonical bibliography. They are not converted automatically into canonical publications, do not change the canonical bibliography update date, and are not included in the search tool.

Handling Authors’ Names

The Author pages need reviewed mappings because the same person can appear under several source-visible name variants.

BibReview compares canonical author names with the reviewed mapping file and can apply only safe, unambiguous proposals automatically. Possible identity collisions remain under manual review rather than being guessed. You can inspect the author-name mapping and suggest corrections when needed.

Curation Process

PHRAISE does not perform an additional scientific peer review of the works it lists. Inclusion means that a work matches the bibliographic scope of the survey; it is not an endorsement of its results.

Bibliographic metadata is curated separately from scientific content. New records pass through explicit staging and merge steps, ambiguous author identities remain human-reviewed, historical metadata can be audited against independent evidence from CrossRef, OpenAlex, and Semantic Scholar, and missing canonical fields can be proposed through reviewed backfill. Refresh is also review-first and non-destructive: only explicit human decisions on safe missing-field proposals can reach staging, while collateral provider differences on existing values remain informational. Audit history is retained locally so routine audits do not repeatedly request publications already visited; a deliberate full audit can still be run when fresh evidence is required for the entire bibliography.

Community

  • PHSys: Community website for researchers in port-Hamiltonian Systems (PHS).
  • PH-Seminar: Monthly seminar, usually first Wednesday, 4 pm (CET) via Zoom.
  • EMS-TAG on PHS: A thematic activity group related to PHS.
  • French-Dutch-German Doctoral College: “Port-Hamiltonian Systems: Modeling, Numerics and Control” supported by the Franco-Bavarian University Cooperation Center BayFrance, coordinated by P. Kotyczka, B. Maschke and J. Scherpen.

Softwares

  • SCRIMP: A finite element framework for port-Hamiltonian PDE simulations.
  • EPHS: A compositional, energy-based (software) framework for modeling mechanical, electromagnetic, and thermodynamic systems in Julia.
  • port-Hamiltonian Benchmark: A repository collecting various port-Hamiltonian systems for numerical benchmarking.
  • PyPHS: A Python software (Py) dedicated to the simulation of multi-physical Port-Hamiltonian Systems (PHS) described by graph structures.

GDPR Policy

Cookies are small text files stored by your web browser when visiting websites. We have chosen not to use any cookies or tracking technologies on this website.

However, to better understand how the site is used and to improve its content, we collect anonymous traffic statistics using GoatCounter, a privacy-friendly analytics tool that does not use cookies.