Map Annotation and packaging
Contents
Annotation and packaging[edit]
From the annotation and packaging section the user can manage his own item annotations and the content aggrgegation processes.
Content[edit]
Links[edit]
Functionalities[edit]
- #Export to content package: export a folder or the entire lightbox to content package
Export to content package[edit]
Once the user has selected the folder he wants to export and he has the rights to obtain the contained items from the related content owner, the folder itself is exported to a content package.
The minimum set of data that should be produced for a content package is:
- a JPG thumbnail for each item (image or video) contained in the selected folder and subfolders
- all the items (image or video) in the original file format with the size/resolution/watermark related to the user rights on the items themselves
- one XML file (item_ID.xml) for each item containing:
- the item file name
- the thumbnail file name
- the item type
- all the item metadata
- one "structure" XML file containing:
- the folder structure
- all the folder items (the basic information, like the item ID, the filename, the title and the type)
- all the folder descriptions
- all the item annotations
In order to let the user get a kind of "product" directly from the eChase site, it would be useful to have, inside the package, also:
- a little static web site already usable by the user for browsing the package content. The eChase system should automatically generate this web site starting from the same XML files of the package and a pre-defined, simple XSL stylesheet. This site should be composed of:
- one index.html page with a representation of the folder structure from which the package has been generated: a sort of "content package map"
- one html page for each folder of the package. This page should show the folder name and description and the contained items (thumbnail and title, for example)
- one html page for each item where the user can see all the associated metadata and look at the item with the right player
- on CSS stylesheet file
- the XSL file used for the site generation
- a readme file with all the useful information for:
- modify the XSL template
- modify the CSS stylesheet
- generate the web site starting from the XML and XSL files
- get the component needed for the site generation from the web (like a XML parser)
All the file of the package should be packed into a single, downloadable ZIP file.
For the first prototype eChase could provide just one simple XSL template for the generation of a simple web site like the one described. For future releases, additional templates could be created (for example, for the generation of a PDF representation of the content package) or it could be developed some kind of on-line tool to give the user the capability of building its own personalized template.
