Ticket #506 (closed defect: fixed)

Opened 2 years ago

Last modified 22 months ago

Metadata informatie

Reported by: peter Owned by: forgacs
Priority: major Milestone: MediaMosa 3.0
Component: Support for PDF issue Version:
Keywords: Cc:
MoSCoW: Must Have Estimated time after impact analysis:
Related to project: none Tested: no
Accepted: no Estimated Hours: 32

Description

In de fysieke bestanden bestaat de mogelijkheid om metadatainformatie
op te nemen. Dit zou voor voor het Archipel project dan specifiek gaan
om de pdf/tiff bestanden. Om een voorbeeld te geven:

$ pdfinfo projectplan.pdf
Author: Dries Moreels
Creator: Writer
Producer: OpenOffice?.org 3.0
CreationDate?: Fri Jan 15 18:44:21 2010
Tagged: no
Pages: 61
Encrypted: no
Page size: 595 x 842 pts (A4)
File size: 1817643 bytes
Optimized: no
PDF version: 1.4

Na Upload van dit bestand kan in de analyse automatisch een aantal
metadatavelden van de asset gevuld kunnen worden als Title, Author,
Creator, Created enz... De mapping van analyse metadata naar in
MediaMosa gedefinieerde metadatadefinities moet in de beheer interface
kunnen worden ingesteld.

Binnen MediaMosa wordt reeds gediscussieerd over de implementatie van
dit principe voor audio en video
(http://mediamosa.org/trac/ticket/390), het lijkt logisch om wat
betreft concept hier op aan te sluiten. Voor deze offerte gaat het
specifiek om de inzet van pfdinfo voor pdf en exiv2 (Exif, IPTC and
XMP image metadata) voor images. Het analyse concept moet voor andere
bestandsondersteuning worden gesplitst door een eerste mimetype
detectie en naar aanleiding van de resultaten hiervan een tweede fase
analyse starten.

Change History

Changed 2 years ago by forgacs

  • owner set to forgacs
  • status changed from new to assigned

Changed 2 years ago by forgacs

  • owner changed from forgacs to robert

Changed 2 years ago by forgacs

  • owner changed from robert to forgacs

Changed 2 years ago by forgacs

  • status changed from assigned to closed
  • resolution set to fixed

The development is ready.
- Tool mapping was added.
Example data:

Name | Tool | Property
copyright | image | rights (dublin_core)
creationdate | pdf | (qualified_dublin_core)
creator | pdf | creator (dublin_core)
exif comment | image | description (dublin_core)
title | pdf | title (dublin_core)

- Tool parameter was developed for non ffmpeg tools;
Example data:

Name | Tool | Parameter | Min | Max | Allowed | Default | Required | Description
def_viewer | pdf | -b |	 |  | ;<use> |  | FALSE | Therefore the swf file will be "browseable", i.e. display some buttons for turning pages. The viewer swf to be used is determine
fonts | pdf | -f |   |  | ;<use> |  | FALSE | Store full fonts in SWF. (Don't reduce to used characters).
flash_version | pdf | -T | 8 | 9 | 8:9 | 9 | TRUE | Set Flash Version in the SWF header to num.

- Transcode profile was developed.
Example data:

Name: Convert image,
Default: FALSE,
Encoder: image,
Application: Global profile (no owner),
File extension: tool
Name: PDF to SWF,
Default: FALSE,
Encoder: pdf,
Application: Global profile (no owner),
File extension: tool
PDF parameters: Flash version: 9, Fonts: <use>, Def viewer: <use>

- Job servers needs configuration for tools:

ANALYSE|ffmpeg|STILL|pdf|image

- Two new streaming servers are needed:
Example data:

Name: JPG / PNG / GIF
Description: General image server for JPG, PNG and GIF.
URI: http://mediamosa_23/ticket/{TICKET}
Mime types: image/jpeg|image/png|image/gif
Object code: <img src="{TICKET_URI}" width="{WIDTH}" height="{HEIGHT}">

Example data:

Name: SWF
Description: SWF object server.
URI: http://mediamosa_23/ticket/{TICKET}
Mime types: application/x-shockwave-flash
Object code: 
<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"
        width="{WIDTH}"
        height="{HEIGHT}"
        codebase="http://active.macromedia.com/flash5/cabs/swflash.cab#version=8,0,0,0"> 
        <param name="MOVIE" value="{TICKET_URI}"> 
        <param name="PLAY" value="true"> 
        <param name="LOOP" value="true"> 
        <param name="QUALITY" value="high"> 
        <param name="FLASHVARS" value="zoomtype=1"> 
          <embed src="{TICKET_URI}" width="{WIDTH}" height="{HEIGHT}"
                 play="true" ALIGN="" loop="true" quality="high"
                 type="application/x-shockwave-flash"
                 flashvars="zoomtype=1"
                 pluginspage="http://www.macromedia.com/go/getflashplayer"> 
          </embed> 
</object>

Changed 22 months ago by forgacs

In the MediaMosa 3.x version the URI is separated into two parts for streaming servers. Eg.

URI:  http://mediamosa.local/
Path: {base_uri}ticket/{TICKET}

Changed 22 months ago by Frans

  • component changed from Core to Support for PDF issue
  • milestone changed from Support for PDF to MediaMosa 3.0

Changed 22 months ago by forgacs

Tool metadata mapping page:
 https://beheer.acceptatie.vpcore.snkn.nl/admin/mediamosa/config/tool_mapping

App_id = 1
/asset/U1OO4neUbBKlCgxafSDRZ5ZS

Enabling and disabling this collecting metadata definition:
 https://beheer.acceptatie.vpcore.snkn.nl/admin/mediamosa/config/app
Choose your app, and check the "Tool section" part.

Note: See TracTickets for help on using tickets.