Alfresco

Media Preview Configuration in Alfresco
Share

Screenshot:





Environment : Alfresco 3.4D, Windows Server 2008

Installation and Configuration Steps:

1. Download file media-preview.jar
http://code.google.com/p/share-extras/downloads/detail?name=media-preview-0.2.jar&can=2&q=

2. Create lib directory in "tomcat/shared" directory, so the directory structure will be like this : tomcat/shared/lib

3. Copy "media-preview.jar" to "tomcat/shared/lib" directory

4. Install FFmpeg on Windows, adjust whether you use 32 bit or 64 bit installer.
http://ffmpeg.zeranoe.com/builds/

5. On "alfresco-global.properties" file, add this line:

ffmpeg.exe=C:\Program Files\FFmpeg\ffmpeg.exe
ffmpeg.base=C:\Program Files\FFmpeg

6. To add the log content for this, add this configuration on file "webapps/alfresco/WEB-INF/classes/log4j.properties" :

log4j.logger.org.alfresco.util.exec.RuntimeExec=debug
log4j.logger.org.alfresco.repo.content.transform=debug
log4j.logger.org.alfresco.repo.thumbnail=debug

7. Restart Alfresco

8. Login to Alfresco Share

Environment : Alfresco 3.4D, Centos 5

Langkah-langkah instalasi dan konfigurasi:

1. Download file media-preview.jar
http://code.google.com/p/share-extras/downloads/detail?name=media-preview-0.2.jar&can=2&q=

2. Create lib directory in "tomcat/shared" directory, so the directory structure will be like this : tomcat/shared/lib

3. Copy file media-preview.jar to "tomcat/shared/lib"

4. Install FFmpeg with x264, installation steps:

-    Download x264-snapshot-20110817-2245
-    Chmod +x x264-snapshot-20110817-2245
-    cd x264-snapshot-20110817-2245
-    ./configure --enable-shared
-    ./configure --disable-asm
-    make
-    make install
-    ldconfig

-    yum install subversion
-    svn checkout svn://svn.mplayerhq.hu/ffmpeg/trunk ffmpeg
-    cd ffmpeg/
-    ./configure --enable-libx264 --enable-gpl --enable-shared --disable-yasm
-    make
-    make install
-    ldconfig
-    whereis ffmpeg

5. In alfresco-global.properties add:

### FFMPEG
ffmpeg.exe=/usr/local/bin/ffmpeg

6. To add the log content for this, add this configuration on file "webapps/alfresco/WEB-INF/classes/log4j.properties" :

log4j.logger.org.alfresco.util.exec.RuntimeExec=debug
log4j.logger.org.alfresco.repo.content.transform=debug
log4j.logger.org.alfresco.repo.thumbnail=debug

7. Restart Alfresco


8. Login to Alfresco
Share

Reference:
http://code.google.com/p/share-extras/wiki/MediaPreviews

File Deletion Mechanism in Alfresco Document Management System :

• When user delete files, it will go directly to the Recycle Bin/Deleted Items. And it will remain there forever until user/admin permanently delete from : Profile in the "Manage Deleted Items" section
• After that, the physical file will still exist in "alf_data/contentstore" directory. Only after passing system.content.orphanProtectDays (in repository.properties), physical files will be moved from "alf_data/contentstore" directory to "alf_data/contentstore.deleted" directory. The default value is 14 days.
• After that the admin manually/automatically using scheduler can erase the contents of "alf_data/contentstore.deleted " directory
  

It's a bit tricky, since Alfresco is designed handle file deletion carefully.

Some values that need to be adjusted in repository.properties:

• system.content.orphanProtectDays is the duration how many days deleted files will be moved from "contentstore" directory to "contentstore.deleted" directory
• system.content.orphanCleanup.cronExpression = 0 0 4 * * ? means the scheduler will run every morning at 4.

Alfresco Meetup, Jakarta, Indonesia has been regularly held every month since June 2011.

The first meeting was held on June 9, 2001 with discussion topic :

• Introduction to ECM/Document Management
• Introduction to Alfresco
• What distinguishes the Alfresco to other products or vendors

The second meeting was held on July 14, 2011 discussion topics:

• Alfresco Web Scripts Best Practices

An upcoming meeting held on August 4, 2011, 7-9 PM with discussion topic:

• The introduction of workflow
• Basic workflow creation
• Case studies

Venue:
Elite Club Meeting Room, Epicentrum,
Kompleks Epicentrum, Rasuna Said Kav C22
Jakarta, Indonesia
(the venua is right behind Pasar Festival)
 
The speaker in this meetup is the founder of Softbless Solutions.

The same information could be viewed at :
http://www.meetup.com/Alfresco/Jakarta-ID/298511/

 

In one of the ECM implementation - Alfresco - we need to implement content type and document metadata that have been designed previously.

There are about 24 types of documents, and there are about 100 metadata that need to be built in Alfresco. Of the 100 about metadata, there are several properties that are shared properties. If calculated, each document type on average has 15 metadata.

If using conventional methods, we estimate it will take about 1 week to make it. Then we try to find a way or tool that can be used to shorten the construction time, and we found SIDE-Labs. Sidelabs is an IDE that can be used developers to design custom models, and even workflow in Alfresco. By using the SIDE-Labs, we will save much time on custom model development.

Finally it only take 1 day to make 24 content types and approximately 100 metadata. For comparison, a web-client-config-custom.xml have around 1700 lines of code, and customModel.xml has about 2300 codes. Imagine if developers have to do it conventionally.

So if you plan to do in-house development with Alfresco, and you have a lot of types of documents, we strongly recommend to use the SIDE-Labs as a tool.

Enterprise Content Management (ECM) System Implementation is different with software implementation. For software, we can simply provide training to End Users.
For the system, in addition to training, there is a need to have Change Management done to achieve the successful implementation of the system, namely:

• Socialization to the End User
• Encourage early involvement from End User
• Build a user-oriented ECM
• Reward Socialization to End Users.
  
  Socialization needs to be done so that users have the correct expectations of system. And User can imagine how the activities to be conducted in later date. Basically, human beings tend to be reluctant to change in everything, including the day-to-day office activities.
  Socialization could reduce rejection from End Users. Socialization can be done through :
  
  Forum that is attended by the management, to provide a signal that implementation of this system is supported by the management. Top-Down Approach is tend to be more successful in system implementation. In this forum do not discuss technically about the ECM system, but rather to emphasize the benefits of this ECM
  Besides forum, then it could be done through a notification via company magazine or company newsletter
  
  Encourage early involvement from End User
  From the kick off the project, the End User must always be involved.
  They can be questioned useful inputs for them. In this way, End User have a sense of belonging to this system. Their inputs may not possible to be all fulfilled, but at least by involving them, they will more have an interest in this system.
  
  A User-Oriented ECM
  
  The majority of ECM can be customized according to need. However, the most important is how to make a more user friendly ECM system. Starting from little things like
  What information must be displayed on the frontpage, when the user first login
  Folder structure for the division in the ECM must be adapted to the structure an existing folder on the computer each End User.
  
  Reward
  
  To further motivate the End User, we could also use rewards, such as : the first division that use full ECM
  for office activities, will get a reward eg shopping vouchers with a specific value for each staff.