Documentation for publishers

How an article reaches Eiger Vault, and what we do with it.

1. Eiger Vault for publishers: overview

   For editors-in-chief and management: push and fetch, the key, the seal, versions, withdrawal, recovery.

   1. 1. How an article reaches us
   2. 2. The key that identifies each deposit
   3. 3. Sealing, versions, withdrawal
   4. 4. Recovery after an interruption
   5. 5. What we do with the content, and what we never do with it
   6. 6. Where to read on
2. The fetch: what Eiger Vault reads at the publisher

   For the technical team: what we fetch from the publisher, how often, and how to limit or cut it.

   1. 1. What we read
   2. 2. At what pace
   3. 3. How we identify ourselves
   4. 4. How the publisher limits us, or cuts us off
3. The push: the deposit contract, version 1

   For publishers writing their own plugin: the deposit contract, its examples and its error codes.

   1. 1. The principle
   2. 2. Authentication
   3. 3. The request
   4. 4. The native document
   5. 5. The response
   6. 6. Idempotency
   7. 7. Versions
   8. 8. Withdrawals
   9. 9. Recovery after an interruption
   10. 10. Refusals
   11. 11. What will be clarified
   12. 12. The vectors
4. What is transmitted?

   For publishers we deliver the plugin to: what it transmits, when, and what it never reads.

   1. What the plugin does
   2. When it runs
   3. What it sends
   4. What it never reads, and never sends
   5. Where your key goes
   6. What we check
   7. If it goes wrong