Managing Diagram Metadata

Our system manages two kinds of files, images and metadata. These are traditionaly kept in source control and updated by editing in the diagram viewer, downloading updates, and checking them in from the command line.

# Batch

For this wiki hosted version we use asset folders and rollup the overall index by logging into the server and running the update script there.

cd .wiki/simnet.ward.asia.wiki.org cd assets/pages/diagrams-as-base-model deno run --allow-read=. indexer.js > new.json mv new.json index.json

The indexer reports changes it has found.

new { team: "trail-maps" }
new { team: "trail-maps", diagram: "thprd-trail-map" }

The cautious administrator double-check before installing the new index.json.

diff index.json new.json

>     "trail-maps": {
>       "thprd-trail-map": {
>         "extension": "jpg",
>         "things": [],
>         "types": []

# Online

Our approach to metadata integration allows for any individual team to add or update content in the aggregation. We exploit that by providing an indexer that can run with access to one team's assets.

pages/diagrams-as-base-model