Hiyori CLI is being developed to create and maintain HiyoriDB — a relational Anime and Manga Database.

Hiyori CLI has two main primary functions:

1. Ingesting transformed data based on the Hiyori Schema ingested from available sources
2. Combining the ingested data into HiyoriDB

Hiyori also collects relational mappings from other sources (if available) and uses that to populate references in the schema. Supported references have parsers and are able to extract the ID of the entry for that source and store them in reference_ids.

WIP. 🚧

1. Install PHP8.2+, MongoDB, MongoDB PHP Driver, Composer
2. git clone https://github.com/Hiyori-API/hiyori-cli.git
3. cd hiyori-cli && composer install
4. chmod +x hiyori
5. Run commands

You can use the cli tool as ./hiyori, php hiyori or php src/run.php.

php hiyori ingest myanimelist --delay 1

php hiyori ingest kitsu --delay 1

php hiyori ingest anilist --delay 1

php hiyori combine {base} --strategy {strategy}

• {base} the name of the source to dataset to use
• There are multiple combining strategies available. The default one is relational_mapping.

// example
php hiyori combine myanimelist
// specify a stratgegy
php hiyori combine myanimelist --strategy relational_mapping

This strategy simply checks for matching source IDs across available source datasets and combines values based off of those.

This strategy cross-checks all reference_ids across available source datasets in hopes to find a matching ID between sources.

This strategy compares other metadata across available source datasets. The metadata properties are given weights and are cross checked using various algorithms. Based on this, a score is given. If the score is above a certain threshold, it is merged.

Common data with different representations like status (MAL: "Finished Airing", Anilist: "Finished") are transformed into a common value via Hiyori's Enums.

TBD.

The following URL type, if detected in an entry's references, will be parsed.

Right now the main focus is to integrate the initial 3 sources and build a combined relational Anime metadata DB.

• Tests
• Sweepers - Remove dead entries (or create a separate collection of them)

• Ingestion: Allow re-try of failed requests
• Ingestion: Alow resume
• Caching
• Ingestion: Allow flag for metadata update
• EV for secrets
• Logging
• Tool: Combiner
• Tool: Export
• Manga Relational DB
• Dependency Injection / Service Containers

• MyAnimeList Integration via REST API
• Kitsu Integration via REST API
• AniList Integration via REST API

Why does Hiyori Schema consist of metadata?

In the event an entry from a source does not contain relational IDs or mapping provided by sources, the metadata will be used to find the relation instead.