Monorepo structure

[ddeboer]

A proposal to restructure the Network of Terms repositories and code that we currently have:

• Rename this repository to network-of-terms.
• Use NPM 7 workspaces for a monorepo with the following structure:
  • catalog (= network-of-terms-catalog)
  • query (shared query logic), which requires catalog (and Comunica)
  • graphql (or graphql-api), which requires query
  • reconciliation (or reconciliation-api), which requires query
• Publish both catalog and query to NPM.
• Archive network-of-terms-catalog.
• Should we rename the packages from the unwieldy @netwerk-digitaal-erfgoed/network-of-terms-graphql etc. to @network-of-terms/graphql etc.?

A downside is the cascade of package updates if we make changes to catalog.

To make the contents of catalog better pluggable and easier to customise, we could apply a further subdivision:

• Make catalog purely RDF and add a web server (move TypeScript files from catalog to query).
• Host catalog as a separate app in the infrastructure; query then reads the catalog’s RDF from a configured HTTP address. Now query no longer has a package dependency on catalog.