waougri/athenaeum

Purpose and Entry Point

Athenaeum is a .NET book-catalog API that persists book records in a local database and extracts metadata/content from EPUB and PDF inputs. The application starts at api/Program.cs; project and runtime dependencies are defined by api/Athenaeum.csproj and api/Athenaeum.sln.

API Host and Composition Root

api/Program.cs is the composition boundary: it likely configures the HTTP pipeline, dependency injection, application settings, and catalog services. Environment-specific configuration is provided through api/appsettings.json and api/appsettings.Development.json.

Catalog Application Service

api/src/Athenaeum.Core/BookCatalogService.cs is the primary use-case layer for catalog operations. It should coordinate input payloads, format extraction, and persistence rather than expose storage or document-format concerns directly to the API host.

Book Domain and Transport Models

Core book representations are separated by responsibility:

• api/src/Athenaeum.Core/BookData.cs represents stored or domain-facing book information.

• api/src/Athenaeum.Core/BookPayload.cs represents incoming book data/request payloads.

• api/src/Athenaeum.Core/EPUBData.cs and api/src/Athenaeum.Core/PDFData.cs carry format-specific extracted results.

This boundary lets catalog operations use common book data while retaining source-format details where needed.

Format Extraction Pipeline

Document ingestion is abstracted behind api/src/Athenaeum.Core/IBookExtractor.cs. Concrete implementations, api/src/Athenaeum.Core/EPUBExtractor.cs and api/src/Athenaeum.Core/PDFExtractor.cs, parse their respective formats and produce the corresponding data models. api/src/Athenaeum.Core/BookExtractor.cs is the likely dispatcher/facade that selects an extractor based on the uploaded or referenced book format.

Primary flow: API request or ingestion input → BookCatalogService → BookExtractor/IBookExtractor → EPUB or PDF extractor → normalized book data → repository.

Persistence Boundary

api/src/Athenaeum.Core/BookRepository.cs isolates database access from catalog and extraction logic. The checked-in database file is api/db/books.db, indicating a local file-backed database, likely SQLite. Repository methods should be the sole boundary for reading and writing catalog records.

Deployment Runtime

The API runs in a containerized .NET environment via api/Dockerfile. api/compose.yaml provides local multi-container or service orchestration, while api/db/books.db is the local persistence artifact that must be handled deliberately for container volume/lifecycle behavior. The core library is packaged independently in api/src/Athenaeum.Core/Athenaeum.Core.csproj, separating reusable catalog logic from the HTTP host.