> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ardoiseeduc.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Canteen & Library

> Stores and pupil wallet on one side, collection and digital resources on the other.

<Note>This page concerns Ardoise School in the OHADA scope, subject to enabled modules and permissions. School, school accounting and payroll are not offered in Austria. Check local requirements; CountryConfig does not certify compliance.</Note>

<Info>
  These are now **two separate Enterprise modules**: **Canteen & Stores** and **Library**.
  A school that wants a collection no longer has to subscribe to a point of sale. See
  [Subscription and pricing](/en/plateforme/abonnement).
</Info>

# Canteen & Stores

## Pupil wallet

Every pupil has an internal wallet. A parent (or the school) tops it up with a given amount; that balance is then used to pay for canteen meals or purchases at the stores, without the pupil handling cash day to day.

The top-up is recorded by authorised staff (canteen, library/stores, or cashier) and credits the balance immediately.

## Over-the-counter sales

A sale (a meal, a supply) debits the wallet at the moment of sale and updates the stock of the item concerned.

<Note>
  If the balance is insufficient, the sale is refused - there is no negative balance.
</Note>

## Stock and suppliers

Inventory movements in, out and adjustments are tracked per item. If the **Stock / inventory** module is enabled on the accounting side, movements are also valued in the accounts; otherwise tracking stays purely operational.

***

# Library and teaching resources

The library is not limited to a physical shelf. It brings **three sources** together in a single catalogue, with the same search and the same access rules.

<CardGroup cols={3}>
  <Card title="The school's collection" icon="book">
    The works the school owns: records, copies, loans and reservations.
  </Card>

  <Card title="Ardoise open library" icon="globe">
    Public domain works, shared between all schools.
  </Card>

  <Card title="Partner libraries" icon="handshake">
    The catalogue of a publisher or partner library, when the school has access to it.
  </Card>
</CardGroup>

## The catalogue

A **record** describes a work (title, authors, language, level, subject area). It can have:

* physical **copies**, each with its condition and availability;
* **digital resources**, each being one way of reaching the work.

## Loans and reservations

A copy is lent to a pupil or a member of staff, with a return date and a possible renewal. When every copy is out, a reader can **reserve**: the queue is kept in order, and the first in the queue is notified as soon as a copy comes back. A copy held for one reader cannot be lent to somebody else.

## Rights and licences

Every record carries its **licence** and its **provenance**, visible to the reader. That is what determines what Ardoise is allowed to do:

| Situation | What Ardoise does |
| - | - |
| Free / public domain work | Ardoise can host its own copy, readable even when the source is offline |
| A licence that forbids it | Ardoise keeps no copy and points to the authorised source |

<Warning>
  A resource whose licence forbids redistribution cannot be hosted by Ardoise, even through a mistake:
  the record is refused.
</Warning>

## Reaching a resource

When several paths exist, they are offered from best to worst:

<Steps>
  <Step title="The copy hosted by Ardoise">
    It opens directly and stays readable even if the external source is unavailable.
  </Step>

  <Step title="The exact link at the source">
    It opens **the work itself** at the provider, not its catalogue.
  </Step>

  <Step title="The provider's catalogue">
    Only when the provider does not allow the resource to be opened directly - and in that case
    it says so before you click, marked **Search required**.
  </Step>
</Steps>

<Note>
  A record with no access available says so clearly rather than implying a digital resource that does
  not exist.
</Note>

## Partner libraries

A school can have access to the catalogue of a publisher or a partner library. Those records appear in the same search, marked by their origin, and **the partner stays in control of its resource**: it decides on availability and lending, and Ardoise keeps no copy.

If the partner is temporarily unreachable, Ardoise says so instead of guessing on its behalf.

## Who sees what

| Reader | Access |
| - | - |
| School staff and pupils | The school's collection, the open library, and the partners the school has access to |
| Librarian | In addition: cataloguing, copies, loans, licences and hosted copies |

<Note>
  Exam papers published as revision resources join the catalogue after the exam, and
  never before - see [Academic](/en/guide-utilisateur/academique).
</Note>

## Barcode circulation and partner lending

The librarian creates a record and copies with barcodes. At the circulation desk, scan or enter the barcode, identify the pupil or staff member and confirm the loan with a return date. On return, open the loan and record its return; check reservations before reissuing the copy. A copy held for one reader cannot be issued to another.

For a partner catalogue, an authorised administrator configures the connector, probes connectivity, synchronises records and reviews result history in the existing panel. Readers open the authorised resource or catalogue from its record. The partner controls rights and availability. Interlibrary lending is wired: a reader requests a loan from a record, the request reaches the partner through the configured adapter, and the loan then appears in their own library with its due date and overdue state, with return and retry available. What it depends on is a partner that actually lends - the manual and OPDS adapters deliberately carry no lending capability, so a record they serve cannot be borrowed through this route.

Teacher-reviewed recommendations, semantic search and learning support use these resources under their access rights: see [Learning](/en/guide-utilisateur/learning).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.