Epub Collector

the epub collector works on content that is either an epub file or a zip file containing an epub and a pdf file it handles any arbitrary sub folder structure containing config files the collector uses meta data from the epub, which is stored under ops/package opf ops/package opf within epub content \<?xml version="1 0" encoding="utf 8"?> \<package xmlns="http //www idpf org/2007/opf" version="2 0" unique identifier="1234567890"> \<metadata xmlns\ dc="http //purl org/dc/elements/1 1/" xmlns\ opf="http //www idpf org/2007/opf"> \<dc\ title>example paper\</dc\ title> \<dc\ creator> \</dc\ creator> \<dc\ publisher> \</dc\ publisher>\<dc\ rights/> \<dc\ identifier id="1234567890">1234567890\</dc\ identifier> \<dc\ language>en\</dc\ language> \<dc\ date opf\ event="publication">2025 10 02\</dc\ date> \</metadata> from the metadata it uses dc\ title and dc\ date by default the title of the publication is matched with the purple publication name if that doesn't match, you can use the configuration options below to make it match the date is used to map the publication date if the issue is published the evening before the actual publication date, this can also be controlled by configuration by default the name of the issue is also derived from the date (german date format), but the name pattern as well as all other meta data can be set in a config properties file having the following configuration options (amongst all other transformer configuration docid\ uepzjnme7gszocvwsa8ox options) configuration options publication= (static publication name in purple for all content) publication xyz= (mapping publication xyz to a purple publication name) namepattern= (name pattern for the issues) iosproductidpattern= (ios product name pattern for the issues) androidproductidpattern= (android product name pattern for the issues) webproductidpattern= (web product name pattern for the issues) issuenumberpattern= (issue number product name pattern for the issues) issuealiaspattern= (issue alias product pattern for the issues) each pattern is a value that may contain the following variables variable example description {d|\<date pattern>|\<language} english date formatted issue name namepattern={d|dd/mm/yyyy|en} german date formatted issue name namepattern={d|dd mm yyyy|de} date pattern ( full pattern doc ) {0} iosproductidpattern={0} {1} publication title from epub {1} androidproductidpattern=com mydomain {1} publication date fro