Export a drama list without losing IDs or unknowns

A worked route from title links to a reusable spreadsheet, including duplicates, language editions and missing fields.

Page updated
Use tool Sign-in required to use tools.

Start with links you can check

The exporter turns supported title links into selected fields. Supported title links can come from your list or a bounded source discovery. Each platform and discovery mode states its availability; no source represents the complete catalog. Each input keeps its own outcome.

  1. In your dashboard, open Tools → Collect & export dramas. Add a batch of original title links or choose a supported keyword or category source, then select candidates.
  2. Choose CSV for a spreadsheet or JSON for exact machine-readable strings.
  3. Review matched, missing, unsupported and duplicate inputs before downloading.

Export a current batch

Sign in and open Tools → Collect & export dramas. Paste title links or import a TXT, CSV or JSON list. Where supported, discover bounded candidates by keyword or category and add selected original links. Discovery and metadata enrichment are separate priced steps.

Each task shows duplicate, unsupported, pending and successful inputs. Follow the task progress; use Continue task if it pauses. Successful records create immutable CSV/JSON revisions, so partial progress remains downloadable. Stopping and resuming reuses the same task.

  1. Choose the fields and output format, then create the task.
  2. Follow the source check and review each input outcome.
  3. Download the current file; prepare an episode table from a completed owned result when supported.

A reproducible example

Add the same supported original title link twice. The duplicate appears in the input outcomes, but the result file contains one copy of the successful record. Unsupported or unavailable links remain explicit; successful records remain downloadable.

Keep platform, platform ID, language, source URL and snapshot date when you want to compare the list later. A title's language edition is part of its identity.

Read counts and empty cells correctly

Reported episode count comes from the source. Observed regular episodes and trailers are separate fields, and either can be unknown. An empty cell means unavailable information, not zero or false.

JSON preserves long IDs as strings. CSV protects numeric IDs from spreadsheet rounding and protects formula-like cells. Do not turn an ID column into a number after import.

Check the file against the input outcomes

A title export contains successful unique records, so its row count can be smaller than the number of links you submitted. Use the task's input outcomes to account for duplicates, unsupported links and missing records. Do not count the CSV header as a title.

Open the file and check a title's platform ID, metadata language and source URL against the result. If you selected an observation date, keep it with the data. Downloading an existing file again does not refresh its observations.

Recover a current export without losing completed records

If checking stops, open the same task from Activity and choose Refresh status. Review the input notes before continuing or resuming the same task when offered. A connection failure alone does not establish that the source request failed.

Download an available partial result before starting another export. Later progress can create a new file revision; an earlier download does not change. An episode table made from a completed result uses the episode rows actually retained, which can be fewer than the title's reported episode count.