Alfresco in a Jiffy


How is it different from Liferay ?

Alfresco is usually used for its exceptional support for Document management and Web content management. Usually document management should be used for intranet application and Web content for Internet applications.
Web content management in Alfresco supports versioning and archieving and stores content on the file system unlike Liferay which gives it an edge over other CMS (content management systems). For document management in Alfresco  the documents are stored on the file system and meta data of the documents are stored in the database which is similar to Liferay. However the documents are linked to each other in a fashion which make it every quickly searchable. Also the contents of he document is also searched (thru indexing in Luecen). the contents are stored in a non readable format for both web content and document management on the file system.

Fundamentals of Alfresco

Scopes

There are 3 scopes on a Alfresco application:
  1. Company home 
  2. My home 
  3. Guest home
Company home is viewable by all i.e is public information. the configuration groups, roles etc should be done in company home. Any information under 'My Home' is consider private to that user.
The toolbar contains navigation buttons that take us to the Home Space or you’re my

Alfresco Dashboard, if you are a guest, and also the Company Home and Guest Home if
you are logged in.

Groups

The default groups in Alfresco are :
  1. Email_contributors,
  2. alfresco-administrator

Content Creation

Role can be applied on each document in Alfresco as well as folder level. Mainly there are 3 types of elements :
  1. Space - which is nothing but equivalent of a folder
  2. Contents - which is nothing but equivalent of a documents
  3. Advanced space wizard - uses templates to create contents.
Creating content is the key feature of a alfresco application. "Create content" actually creates structure of the content and when you say "add content" you actually insert meta information about the content.

Roles

The typical of roles Alfresco application are:
  1. Coordinator 
  2. Collaborator
  3. Contributor 
  4. Editor 
  5. Consumer
A coordinator is nothing but a administrator role who has full access to manipulate the website. A collaborator has a ability to invite other users to his space. Its is the highest role on a given space.
A contributor has the permissions to create/update/delete content. An editor can add content and modify/delete the content. A consumer can only has read permission.  

Rules

One of the key features of Alfresco is the ability to define rules that affect content within a space.  These rules can be used to provide all kinds of creative solutions to automation and management of content.  Rules are fired when content comes in or out of a space and may also apply to content directly in the space or in sub-spaces.  A rule is made up of two main elements: the conditions on the content for the rule to match and the actions that are then performed.  Any number of conditions and actions may be defined in a rule.

References:

Comments

Post a Comment

Popular posts from this blog

jQgrid reload with new data

To reload a jQGrid with fresh data you need to set the data parameter on the grid and invoke reload on it. jQuery("#promotionsGrid").setGridParam({ 'data': newData}).trigger("reloadGrid"); Here newData is a JavaScript array with which I need to re-load the grid. The important thing here is that I had to place this statement just before the grid initialization code even though the reload was expected on change event of a text box. Without that there was simply no effect on my grid!
Read more

Rich Client based UI technologies- A Comparison of Thick Client UI tools

Rich Client v/s Thin Client Software developers face many difficult decisions when building new applications, not the least of which is graphical user interface. There are various graphical user interface technologies used, but broadly they can be classified as Rich Client User interfaces and the thin client or web based user interfaces. To understand them better let us look at the history of rich and thin clients. While the Rich client GUI applications would support high quality end-user experience with features such a drag-and-drop, perspectives, customization, high speed local processing; it has had a traditional disadvantage of high deployment and upgrade costs. It was becoming highly difficult and costly to deploy and upgrade these applications. Then came the thin clients or the Web based applications. Thin clients solved many of the deployment and upgrade problems, but that was not without a cost, the cost was in terms of functionality and capability. Thin clients, based on
Read more

OSS and BSS Systems

Image
OSS (Operational Support Systems) Software (occasionally hardware) applications that support back-office activities which operate a telco’s network, provision and maintain customer services. OSS is traditionally used by network planners, operations, architects, support, and engineering teams in the service provider. Increasingly product managers and senior staff under the CTO or COO may also use or rely on OSS to some extent. BSS (Business Support Systems) Software applications that support customer-facing activities. Billing, order management, customer relationship management, call centre automation, are all BSS applications. BSS may also encompass the customer-facing veneer of OSS application such as trouble-ticketing and service assurance – these are back-office activities but initiated directly by contact with the customer. OSS/BSS Structure Communication between OSS and BSS Apart from service assurance activities being cross-OSS-BSS processes, there are as m
Read more