Cadmus repositories are all hosted in the VeDPH GitHub site.

The general organization of Cadmus repositories follows these guidelines:

  • backend and frontend repositories are always separate.
  • a bunch of basic repositories provides core infrastructure for backend and frontend.
  • data models and editors are grouped into repositories by subject: currently these are: general, philology, codicology, epigraphy, geography, imaging.
  • some repositories provide additional services (like for external bibliography) and tools.
  • each Cadmus-based project has its own repositories. At a minimum, they just have an API backend and a frontend. Most of them, which provide their own models, also have a models library. Conventional naming is as follows:
    • cadmus-PRJ: specialized models, if any.
    • cadmus-PRJ-api: API backend.
    • cadmus-PRJ-app: frontend app.
    • cadmus-PRJ-doc: optional documentation.

Backend

All the backend Cadmus libraries are distributed via NuGet.

Models

👉 General models:

  • Cadmus core: the core set of libraries for Cadmus backend, providing the infrastructure for core, indexing, storage, and mock data seeding.
  • Cadmus bricks: the core set of libraries including sub-models shared across many of the part/fragment models.
  • Cadmus graph: libraries used for the semantic graph projection and editing of Cadmus data. 👀 An essential online tool for building and testing mappings is available.
  • Cadmus migration: libraries used for data migration (e.g. TEI export).
  • Cadmus general models: libraries including generic-usage data models (parts and fragments). Practically all the Cadmus projects use one or more of these components. More specialized models are found in other libraries.
  • Cadmus philology models: libraries including philological data models (parts and fragments).

👉 Codicology models:

👉 Epigraphy models:

👉 Geography models:

👉 Imaging models:

Services

External bibliography service:

  • Bibliography: this is a generic bibliography service, based on its own database (MySql). Yet, it can be used by Cadmus projects with a high level of integration when you prefer a top-down approach for bibliography.

Tools

Frontend

All the frontend Cadmus libraries are distributed via NPM.

Shells

General shells:

  • Cadmus shell: the core set of frontend libraries of any Cadmus application. This can be run as an application, but its intended usage is just providing a playground (and an app sample) used for development. This shell includes the generical and philological frontend libraries, corresponding to the backend models in their respective libraries.
  • Cadmus bricks shell: the shell used for developing frontend sub-models. 👀 Its online version can be used to play with all the controls.
  • Cadmus graph shell: the shell used for developing frontend semantic graph components.

👉 Bibliography shell:

  • Bibliography shell: the shell used for developing frontend bibliographic models. Note that these are independent from Cadmus, except for a single component used to adapt the external bibliographic service to Cadmus.

👉 Codicology shell:

  • Cadmus codicology shell: the shell used for developing frontend codicological models, including the codicology frontend libraries.

👉 Epigraphy shell:

  • Cadmus epigraphy shell: the shell used for developing frontend epigraphic models, including the epigraphy frontend libraries.

👉 Geography shell:

  • Cadmus geography shell: the shell used for developing frontend geographic models, including the geography frontend libraries.

👉 Imaging shell:

  • Cadmus imaging shell: the shell used for developing frontend imaging models, including the imaging frontend libraries.

Applications

👉 CHICGC

👉 GISARC:

👉 Inquisitions Graffiti:

👉 Itinera:

👉 MapAeg:

👉 Musisque Deoque:

👉 PAGES and related projects:

👉 PURA:

👉 Re.Novella:

👉 VeLA:

👉 Sidonius Letters:

🏠 developer’s home