Digital Asset Management setup

Author Message

Rene Kloos

Sunday 08 March 2009 10:19:26 am

We are investigating the possibility to use eZ Publish etc. for the implementation of digital asset management system. Initially the system will be targeted at media companies that need to be able to download broadcast quality material (e.g. MPEG IMX @ 30Mbps), but we will also offer several consumer formats, e.g. Flash, MP4 (Hi/Lo), WMV (Hi/Lo).
I would like to know what the experiences are from users with a setup in this particular area, not only with regards to the eZ Publish setup, but also with regards to the ingestion setup. The idea is to have the eZ Publish system hosted externally, but the ingestion will be done from our pemises. Anyone interested in sharing his/her experience can drop me a line or two...

Ekkehard Dörre

Sunday 08 March 2009 2:04:42 pm

Hi Rene,

you had a look at the eZ Publish final cut server integration http://ez.no/software/final_cut_server_web_publishing ? It is a different approach, but interesting, I think. The access control and more comfortable extranet features you make with eZ Publish.

An the other hand, eZ Publish Publish has WebDAV, good search engine http://ez.no/ezfind , meta data support, native XMP implementation in eZ Publish shouldn't be so difficult, in Final cut server it is there, so you can import it to eZ Publish.

Greetings, ekke

http://www.coolscreen.de - Over 40 years of certified eZ Publish know-how: http://www.cjw-network.com
CJW Newsletter: http://projects.ez.no/cjw_newsletter - http://cjw-network.com/en/ez-publ...w-newsletter-multi-channel-marketing

Rene Kloos

Monday 09 March 2009 2:34:33 am

Thanks for sharing that. I am aware of the Final Cut integration, but we may not be in a position to go for that at the moment. Does anyone has experience with the Telestream Pipeline and FlipFactory setup at the ingestion side of things?

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 18 2025 16:05:35
Script start
Timing: Jan 18 2025 16:05:35
Module start 'layout'
Timing: Jan 18 2025 16:05:35
Module start 'content'
Timing: Jan 18 2025 16:05:35
Module end 'content'
Timing: Jan 18 2025 16:05:35
Script end

Main resources:

Total runtime0.0146 sec
Peak memory usage4,096.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0050 589.0234152.6250
Module start 'layout' 0.00510.0026 741.648439.4453
Module start 'content' 0.00770.0048 781.093889.2891
Module end 'content' 0.01250.0021 870.382834.3047
Script end 0.0145  904.6875 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002718.3315140.0002
Check MTime0.00117.6639140.0001
Mysql Total
Database connection0.00074.910310.0007
Mysqli_queries0.002315.555030.0008
Looping result0.00000.062110.0000
Template Total0.001711.810.0017
Template load0.00106.851210.0010
Template processing0.00074.911910.0007
Override
Cache load0.00074.897210.0007
General
dbfile0.00031.762780.0000
String conversion0.00000.040940.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs