Modules, Collections, and Records

The project's basic design is centered around the module: a specific class of objects or concepts related to an archaeological excavation.

Each module consists of a collection of instances (records) that may be filtered, ordered, and viewed in various ways. A user with editorial privileges may add and delete records, edit their properties, and attach and detach media and relations to them.

Our decision to divide the data into separate modules is based on the observation that the most pertinent characteristics and queries are module specific (e.g., stone queries have little overlap with metal queries).

Limiting queries to be module-specific significantly reduces the complexity of the software.