Language:DeutschEnglish Last updated: 2026-11-03

Contract

Under Administration › Users and loans › Contract the archive sees what it has booked, what it uses and what it ordered (since v0.118.0, anton#805). All admins see the page; accounts holding Contract and contacts can order.

What the page shows

• Plan: tier, since when, term and notice, operation (Anton as a Service, own server, DIMAG).
• Storage: booked and in use. Counted are the masters and the kept versions, from the database. Beside it stands the whole directory as Anton measures it at night, with derivatives and caches.
• Modules and packages: each with its status (included, booked, available) and price.
• Orders and usage statements.

Kränzle & Ritter keeps the contract data in anton-ansible; Anton only reads them. Without data on file the page shows the storage only.

Ordering

Booking, cancelling and a storage tier go as a confirmation by mail to the contact persons for the overall responsibility. The order holds once one of them confirms; the mail names the module, the price and refers to the terms of the offer. Kränzle & Ritter then sets up what was ordered and updates the contract data. Until then the module shows as «ordered».

The package Technical care is not booked here but with the preservation mandate «Technical care»: the page shows its state and links there. Confirming the mandate counts as ordering the package, revoking it as cancelling; the overall responsibility confirms once.

Usage statement

Every month Anton records a usage statement: storage in use and booked, number of media and accounts, the month's cost of AI cataloguing, the plan and what was in force. A month is written once and not changed afterwards. The statements are on the page and can be downloaded as CSV; the accounts of Kränzle & Ritter fetch them over GET /api/usage-statements.

php artisan contract:usage-statement --env=<slug>                 # previous month
php artisan contract:usage-statement --env=<slug> --month=2026-10

For operations: the contract file

anton-ansible places the data per installation as customers/<slug>/contract.json (elsewhere: CONTRACT_FILE). Labels and descriptions are a text or given per locale. A file that does not match the schema counts as missing; the log names the reason.

{
  "schema": 1,
  "updated": "2026-11-03",
  "plan": {"key": "pro", "label": {"de": "Pro"}, "since": "2024-01-01",
           "term": {"de": "jährlich, Kündigung drei Monate vor Ablauf"}},
  "operating_model": "A",
  "show_prices": true,
  "storage": {"booked_gb": 50, "tiers": [{"gb": 100, "yearly": 300}]},
  "items": [
    {"key": "oai", "label": "OAI-PMH", "status": "included", "bookable": true, "price": {"yearly": 500}},
    {"key": "sru", "label": "Archives Online", "status": "available", "bookable": true, "price": {"once": 2500, "yearly": 500}},
    {"key": "technical_care", "label": "Technische Betreuung", "status": "active", "since": "2026-11-03", "bookable": true}
  ]
}

Field	Meaning
status	included (in the base offer or the plan), active (booked), available (can be booked)
bookable	whether the item can be booked or cancelled on the page
price.once, price.yearly	CHF; without, «as offered»
storage.booked_gb	booked storage; without a file the setting maximum_storage applies
technical_care	the item the preservation mandate «Technical care» depends on