« January 2008 | Main | March 2008 »

February 22, 2008

Process to do an itemexport for a collection in dspace

There is a way to extract items in a collection from dspace so that they have the form of a plane pdf and a flat xml files. This directories can be batch ingested back into dspace or another repository.

Finding a collection's ID

The file below shows how to find a collection's ID in dspace. getCollectionID

Brad Teal's filter_media.sh script

The filter-media.sh script will find all the handles of all the collections.

Execute the command to extract the data

[silvi003 /dspace/dspace-ir/bin]$ ./dsrun org.dspace.app.itemexport.ItemExport -t COLLECTION -i 29 -d /dspace/assetstore/udc_export/ima/ -n 0

Resulting Directory Structure

Resulting directories from ItemExport command.

February 15, 2008

Ports that must be set in server.xml so that more than one instance of Tomcat runs on a box

The following ports must changed if a new instance of tomcat is going to be set up on the same box:

Excepts from server.xml (Ports that must be changed)

<!-- A "Server" is a singleton element that represents the entire JVM, which may contain one or more "Service" instances. The Server listens for a shutdown command on the indicated port. Note: A "Server" is not itself a "Container", so you may not define subcomponents such as "Valves" or "Loggers" at this level. --> <Server port="9035" shutdown="SHUTDOWN">

<!-- Define a non-SSL HTTP/1.1 Connector on port 8080 --> <Connector port="9030" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" redirectPort="8043" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" URIEncoding="UTF-8" />

<!-- Define a SSL HTTP/1.1 Connector on port 8443 --> <Connector port="9031" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" disableUploadTimeout="true" acceptCount="100" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" />

<!-- Define an AJP 1.3 Connector on port 8009 --> <!-- <Connector port="9039" enableLookups="false" redirectPort="8443" protocol="AJP/1.3" /> -->

Check that abort page for license contains no logic for AgEcon

We have moved the license page form the last [page of the submit to the first. The wording of the page says that the entry will be saved, but of course there is no entry. The wording can be easily changed, but I needed to check that the jsp was not executing any code (i.e. trying to write to a file or the DB). It is not so all is well.

February 5, 2008

Lunch with Colin Clustering, Qmaster, Flash codec


I had lunch with Colin McFadden today and he told me how he was using clustering to increase Media Mill's throughput.

Qmaster and clustering

Apple Qmaster is a system made by Apple Inc. that provides automated work distribution and processing for high-volume projects created with certain digital visual effects software packages: Shake, Alias Maya, Final Cut Pro, Compressor, DVD Studio Pro and any UNIX command-line program. It processes such jobs on a cluster of Macintosh or Xserve computers. Colin says that the time form opening the box to having a new computer in the cluster is about 1 hour. In the end, the limiting factor will be network speed.

Compressor used by Qmaster

Compressor is a video and audio media compression and encoding application for use with Final Cut Studio and Logic Studio on Mac OS X. It can be used with Qmaster for clustering.

Codec and clustering

A video codec is a device or software that enables video compression and/or decompression for digital video. Flash uses VP6: A proprietary video codec developed by On2 Technologies and used in Adobe Flash Player 8 and above. Colin tells me that VP6 can only run a job on one box at a time.
Adobe is moving to: H.264 is a standard for video compression. It is also known as MPEG-4 Part 10, or MPEG-4 AVC (for Advanced Video Coding). It was written by the ITU-T Video Coding Experts Group (VCEG) together with the ISO/IEC Moving Picture Experts Group (MPEG) as the product of a partnership effort known as the Joint Video Team (JVT). Colin explains that this codec is multi-machine aware.