Enterprise Content Management

Armedia Blog

Archive for the ‘Alfresco Development’ Category

Armedia Case Management – Content.gov Presentation

January 24th, 2012 by Allison Cotney

Did you miss Alfresco’s Content.gov event today in Washington, DC? Dont worry!! Here are the slides from Armedia’s presentation.

 

 

For more information about Armedia Case Management, CLICK HERE

Armedia Government Solutions: HUD and FOIA Compliance

January 17th, 2012 by Allison Cotney

The Freedom of Information Act (FOIA) is the law which requires federal agencies to provide access to documents and information that is controlled by the United States government. The resulting monumental amount of paper documents has had an effect on the efficiency in which federal agencies can respond to their FOIA requests. The U.S. Department of Housing and Urban Development (HUD) faced this exact problem.

This mass of paper was taking up much needed physical space in HUD as well as proving to be extremely difficult and time consuming when it came to locating specific documents. To add to the constraints, HUD and its separate divisions did not have an easy way to share and collaborate on documents with each other or various other federal agencies under the existing system.

It became clear that HUD needed to digitize paper documents and implement a document management system for managing, storing and collaborating on documents. However, as a federal agency, HUD needed the system to be able to meet its specific needs to aid it in more efficiently handling FOIA requests. On this aspect, Armedia had three specific focus points for the new system:

 

  1.      Provide a central location for managing case files
  2.      Enable rich text based (i.e. full-text) and metadata (i.e. attribute) searching.
  3.      Ability to share and collaborate on documents from any location on any device including tablets like iPad

 

Providing a Central Location

Providing a central location in which organizations manage documents and case files is a task that is at the core of Armedia’s strengths in terms of capabilities. However, one aspect was particularly important for this specific project. After scanning millions of paper documents and storing them in a database, Armedia faced the task of migrating those files to the cloud based Alfresco Enterprise Content Management system while automatically building a taxonomy based on the indexed information captured during the scanning process.

Using Armedia Caliente, a content migration product, Armedia was able to move HUD’s digitized documents and the indexed information captured in comma separated value (CSV) files into Alfresco while retaining the metadata tags (see picture below). The document’s metadata information was going to be vital to the success of the system later as this allows users at HUD to search for requested information under commonly listed categories such as name, date and location.

This centralized document management system provided HUD employees with the ability to search for documents across all case files without having to search within the different divisions. By providing the transfer of the original metadata, users can also search for documents using the same criteria they would have before.

 

Ability to Collaborate

The ability to collaborate and share documents with other federal agencies brought up a crucial factor in any situation dealing with government records: information security. Specifically, HUD needed to have the ability to protect individuals when documents were shared across agencies. To handle this task, Armedia integrated Daeja ViewONE Pro to allow users the ability to redact personally identifiable information before sharing across agencies or with the public. Once the redaction was burned into the document, it could be saved as a version in the Alfresco repository to keep the history of the case document.

HUD now has an extremely scalable and centralized case management system to manage its cases and the documents within them. Over three million pages of documents have been digitized and migrated into the new system. HUD Employees are able to share documents with other agencies and respond significantly faster to FOIA requests as a result of having the information at the tip of their fingers.

Click on the link for a full look at our U.S. Department of Housing and Urban Development Case Study

 

Annotate this!

July 28th, 2011 by cstephenson

Over the past 12 months (or maybe longer) and I have been involved with 2 separate projects to integrate Daeja ViewONE Pro with Alfresco.

Daeja ViewONE Pro is a java applet designed to allow users to apply annotations to any* document.  That is just the starting point.  The applet has been developed whereby an implementer can interact with it via javascript to enhance the user experience.  The implementer can also dynamically change what controls and features are available to a user based upon the user’s role and permissions within the CMS.  I could go on but I would probability end up repeating Daeja’s website :)

(more…)

Beginner Thoughts on Alfresco Architecture

February 15th, 2011 by jhsu

If you asked me three months ago if I enjoy developing to Alfresco’s repository and Share UI (specifically Enterprise 3.3.3), it would have been a frustrated “NO…” — Not frustration about WANTING to learn a new product, since that is always exciting and challenging, but frustration on not understanding the architecture, the BIG PICTURE, to know how to use the product.

I’m not going into any deep personal thoughts on Alfresco ECM architecture today; rather I am going to share my thoughts on working with the Alfresco repository and the Alfresco Share UI from a software developer’s standpoint that had (almost) no prior experience with Alfresco, or ECM platforms in general.

I am relatively new to Armedia, and went headfirst into learning Alfresco ECM.  NOTE! It is generally a good idea to get a “crash-course” in a new product from a product expert before jumping headfirst into a new product, even if Alfresco has thorough documentation via their Wiki (http://wiki.alfresco.com/wiki/Main_Page).  My coworkers and I had the pleasure to have an “Alfresco Architecture Crash-Course” presentation shared with us from Dimy Jeannot who was working on another Armedia Alfresco project.

The high-level architecture is as seen below.  Any numerous UI technology, frameworks, etc are represented by the presentation layer (Alfresco Share, jQuery, EXTJS, etc).  The presentation layer can communicate with the Alfresco repository, or via Alfresco data web scripts (data layer).

High-Level Alfresco Architecture

High-Level Alfresco Architecture

The more detailed Alfresco architecture is seen below; we use the Alfresco Share UI as our example here.  Share, and any custom Share code you write, calls RESTful presentation and/or data web scripts.  These web scripts, in turn, communicate directly with Java Core Services exposed by Alfresco (i.e. document, search, node), or any custom services you may need to add for your application, to communicate with the Alfresco Repository.

Never assume that Alfresco and Share are running on the same server host.  For example, you should not hardcode localhost or any other hostname in your Share code.  Instead, use Share’s proxy URL when invoking a data web script (i.e. from a Share ftl, use Alfresco.constants.PROXY_URI when invoking your data web script -> Alfresco.constants.PROXY_URI + “<URL>”).

Where should you store your web scripts?  If you are concerned with data, store your web scripts in the data layer.  When your data web scripts are deployed, they are stored at webapps\<alfresco webapp context>\WEB-INF\classes\alfresco\templates\webscripts, create custom packages for your application.  Else you are concerned with presentation (such as from a Share dashlet), store your code in the presentation layer (it should then in turn call a data web script to get its data!).  When your presentation web scripts are deployed, they are stored at webapps\<share webapp context>\WEB-INF\classes\alfresco\site-webscripts, create custom packages for your application.

Detailed Alfresco Architecture

Detailed Alfresco Architecture

Looking back now and reading the Alfresco Wiki’s, the Alfresco architecture makes sense, I just needed guidance on putting the big picture together to start feeling comfortable with working with a new product.  If you ask me do I enjoy developing with Alfresco now, I would say yes <with smiles>.

Think Alfresco from Documentum perspective –Take 1

July 14th, 2010 by bsampath

Open Source ...</ins>

When you work for a while in the software you get numbed to “technologies have come and gone…” occasionally though some become commodities and others trend setters. We have seen that with many products like Apache, Tomcat, Lucene, Drupal …etc that have stabilized and matured over the past years with the help of increased development from the open source realm. Wait! Did I mention the word “Open Source” and going to talk about the enterprise content management?

So without any more ado, we have Alfresco- catering to a rapidly increasing demand of the enterprise content management solutions which is built over the open source technologies such as Spring, Hibernate, and Lucene platforms. Having done years of Documentum development and several Alfresco projects of late, I think there are some interesting overlaps and differences of approach that I feel would make the developers get adapted quicker.

With the wiki site overwhelmed with Introduction, API’s, Development, Deployment and the Forums to answer all the questions regarding the issues faced during the project phase, I am here to talk purely from the developers perspective on what’s the key areas that I happen to witness the difference from the Documentum space.

The road map for my next series of blog is going to cover each of the areas mentioned below in more detailed, code abundant and developer centric approach which will answer the questions:

  • Does this feature exist in Documentum or Alfresco or both?
  • If yes, how different is the approach?

So with that preamble, and in no particular order, I give you my list of the key areas I got hands on and learnt how different Alfresco is:

Custom data model is the core for any enterprise content management solution. The use of “Aspects” as its core is the fundamental concept for content modeling in Alfresco. Although in the form D6, aspects was introduced, how different is the use and approach in Alfresco is something I will take a deep dive in my next blog.

Alfresco Web Scripts brings together the world of content repository and the web. Being a Documentum developer earlier ways of interaction with the repository have been either using DFC API’s or DQL. In Alfresco, Web Scripts provide RESTful access to content within the repository and we can build our own interface using java script. A custom move operation is implemented using the Web Scripts and the comparison of the implementation with the Documentum would be a something to be noted.

On my last project, we had requirements for the customers to be able to permanently redact Personally Identifiable Information (PII) from existing documents stored in the repository and version the original document upon save. For various reasons, we decided to integrate the 3rd party tool Daeja ViewOne module to provide this capability. I will discuss the topic as part of this blog series.

I started this series based on my experience implementing Alfresco projects and I invite you to share any of your experiences with any part of the road map wherein you run into interesting twists and turns? Did you drive off the road to get some help? I welcome your feedback as the blog takes its shape. See you all soon in Take 2.

Copyright © 2002–2011, Armedia. All Rights Reserved.