Distribution-draft
•Descargar como PPTX, PDF•
0 recomendaciones•271 vistas
eBooks distribution
Recomendados
Más contenido relacionado
Similar a Distribution-draft
Similar a Distribution-draft (8)
Último
Último (20)
Distribution-draft
- 2. What is distribution? eBook Archive Platforms with Retail and Institutional customers Institutions Direct retail customers Valeria Hodgkinson
- 3. What exactly we distribute content metadata Valeria Hodgkinson
- 6. The way we did it before • Manual • Excel spread sheets • ISBN by ISBN in GT • 1 hour per 1 batch of 10 titles • Production turnaround 2,500 titles a year • 10 distribution channels • 2 people in team Valeria Hodgkinson
- 7. The way we do it now Takes 5-10 min per batch up to 1,500 for newly converted Takes 5-10 min per batch up to 18,000 titles to be distributed to 40 channels Annual production turnaround 12,000 Members in team Valeria Hodgkinson
- 8. Upload files and metadata to CS Run metadata report (GT and database) Metadata health preflight check eBooks arrived to eBooks Archive Simple step by step Upload to TFO To MARC records conversion Valeria Hodgkinson
- 9. We can do it this way because: • Clean eBook archive • Tools for moving content • Metadata issues being fixed outside the team • Using CoreSource Valeria Hodgkinson
- 10. What CS does for us: CONTENT METADATA AGGREGATO RS Valeria Hodgkinson
- 11. When it arrives to destination: • Tailored metadata feed • Tailored naming convention • Filtered content We can access some of the platforms for better control Valeria Hodgkinson
- 12. FUTURE: BIG DATA FASTER LARGER MORE CONTRO L DAC CODE RIGHTS MANAGEMENT POD INTEGRATION FRONT LIST PRODUCTION INTEGRATION Valeria Hodgkinson
Notas del editor
- eBook archive to CS: before: manual filling xls spreadsheet from GT, 1 hr for 1 batch 10 titles; plus 2 hours metadata spread sheet. Production turnaround 2500 annually. 2 people in the team, 10 channels? after:Notification (how) so we know that files have been returned from conversion/checked in QA/mobi converted and now ready for distribution. Check metadata – preflight report – second roundPrepare metadata: ONIX from GT and additional metadata from Pricing toolUpload metadata to ftp for CSUse script to pack filesUpload files to ftp for CS + upload files to TFE (then goes to Instituitional customers subscribers of tandfebooks.com )+ upload files to Backstage for MARC records production+ upload files and metadata to eBook store (goes to retail customers) Challenges:Metadata is still in a bad state in GTNo pricing in GTDuplicated format ISBNs are allowed in GTStill some gaps in content Jargon explained: ePUB, WebPDF, Mobipocket/KF8, MARC records, Institutional and retail customers
- What CS does: keeps files secure, keep track of versions, store them in order, reports on missing content; sorts and puts at the right place when new arriveskeeps metadata secure, keeps track of versions, stores it in order; reports on missing; sorts and puts at the right place when new arrivesdeals with aggregators – accept and pack orders (check exactly what they want to receive from us); distribute orders when told; recall withdrawn ones, remembers special requests – like text types and BISAC codes to offer only those what are allowed to be sold; keeps track of distributions and history of distributionsChallenges:DAC code integrationRights managementMetadata gapsContent gapsCRC titlesOrphansMp3 content to be uploadedIntegrate with TFEIntegrate with eBookstore
- Aggregators to end usersEach of them receives a tailored metadata feed and packed files named as they have been requested to be named;They then process and include in there platform – we can access some (the biggest ones) backstage – check inventories , fix errors etcCustomers will see and access the books
- Future:We want this to work even quickerEven more seemlessInclude print filesIntegrate into front list production