• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer
TSB Alfresco Cobrand White tagline

Technology Services Group

  • Home
  • Products
    • Alfresco Enterprise Viewer
    • OpenContent Search
    • OpenContent Case
    • OpenContent Forms
    • OpenMigrate
    • OpenContent Web Services
    • OpenCapture
    • OpenOverlay
  • Solutions
    • Alfresco Content Accelerator for Claims Management
      • Claims Demo Series
    • Alfresco Content Accelerator for Policy & Procedure Management
      • Compliance Demo Series
    • OpenContent Accounts Payable
    • OpenContent Contract Management
    • OpenContent Batch Records
    • OpenContent Government
    • OpenContent Corporate Forms
    • OpenContent Construction Management
    • OpenContent Digital Archive
    • OpenContent Human Resources
    • OpenContent Patient Records
  • Platforms
    • Alfresco Consulting
      • Alfresco Case Study – Canadian Museum of Human Rights
      • Alfresco Case Study – New York Philharmonic
      • Alfresco Case Study – New York Property Insurance Underwriting Association
      • Alfresco Case Study – American Society for Clinical Pathology
      • Alfresco Case Study – American Association of Insurance Services
      • Alfresco Case Study – United Cerebral Palsy
    • HBase
    • DynamoDB
    • OpenText & Documentum Consulting
      • Upgrades – A Well Documented Approach
      • Life Science Solutions
        • Life Sciences Project Sampling
    • Veeva Consulting
    • Ephesoft
    • Workshare
  • Case Studies
    • White Papers
    • 11 Billion Document Migration
    • Learning Zone
    • Digital Asset Collection – Canadian Museum of Human Rights
    • Digital Archive and Retrieval – ASCP
    • Digital Archives – New York Philharmonic
    • Insurance Claim Processing – New York Property Insurance
    • Policy Forms Management with Machine Learning – AAIS
    • Liferay and Alfresco Portal – United Cerebral Palsy of Greater Chicago
  • About
    • Contact Us
  • Blog

Auto-Filing Content in Alfresco

You are here: Home / Alfresco / Auto-Filing Content in Alfresco

October 22, 2014

After working with Alfresco for a while, we’ve noticed a number of design patters and functionality that are common amongst many clients across various industries.  Alfresco module packages (AMPs), make it easy to package up components and reuse them in different Alfresco implementations.  This article will focus on one reusable module that automatically files content into a folder structure in an Alfresco repository based on metadata.

Introduction

At TSG, more times than not, we recommend that clients throw out the folder paradigm in favor of utilizing metadata and search to classify documents in their ECM systems.  See our previous post “Working with Folders in Documentum User Interfaces – D2, Webtop, HPI, and xCP” for a more in-depth discussion on using folders to classify documents.  For “do all” applications like Alfresco Explorer and Alfresco Share, creating and managing content in a folder structure is a key component of the application.  This makes sense because in order to satisfy the widest range of users, it’s good to use a paradigm that users are already familiar with.  Most users are already accustomed to filing documents on their PCs into folders using Windows Explorer or Mac OS Finder, so it’s understandable that many ECM user interfaces take a similar approach.

Alternative user interfaces, like TSG’s High Performance Interface (HPI), can operate without any folder structure at all.  Part of what makes HPI “High Performance” is that users don’t have to know where to put content when they’re uploading it.  That being said, because Alfresco and other ECM applications are built with a folder paradigm already in place, all content must be in a folder behind the scenes.  For performance and maintainability reasons, it’s often important that folderless user interfaces file content into a folder structure in the back-end repository.

To make this simple in Alfresco, we’ve developed a configurable AMP module to automatically file content into a folder structure based on metadata that is applied to content at creation time.  Here’s how it works:

Configuration

In order to avoid code changes for each implementation, the auto-filing module is configurable.  System administrators can simply initiate a web service call from a browser in order to set up the auto filing configuration for their Alfresco repository.  Behind the scenes, configurations are stored as contentless objects in the repository and can be modified/deleted at any time.  Auto-filing configurations include the following parameters:

  • Root Path – path to the root Alfresco folder where auto-filed content will be stored
  • Types – list of Alfresco content types that the auto-file configuration applies to
  • Properties List – list of metadata properties that determines the folder path that content will be auto-filed into. For example, if you wanted to file documents by 2 metadata fields, “Project Name” and “Document Type,” you’d configure auto-filing for these two properties, and then new content would be filed into the folder, “/{Root Path}/{Project Name}/{Document Type}”.
  • Auto Create Folders – indicates whether folders should be automatically created if they don’t already exist in the repository
  • Auto Create Folder Type – if folders are to be automatically created, this property is used to configure the content type that new folders will be created as
  • Auto Rename Duplicates – this flag tells the system whether or not to automatically rename a document if a document with the same name already exists in the target folder during auto-filing

Aspects and Behaviors

Once the auto-file configurations are in place, Alfresco behaviors do the rest of the work.  Behaviors allow custom functionality to be to be injected into the repository when certain events occur, such as new content being created, or properties changing on existing content.  The auto-filing AMP uses behaviors to watch for new content and properties being updated so that content can be automatically filed into the correct folder structure based on the configuration.

The final piece of the puzzle is knowing when to trigger the behaviors.  We utilize an Alfresco aspect for this.  Any content that should be auto-filed receives an “Autofile” aspect.  The nice thing about using aspects is that they can be automatically applied to content by making them mandatory aspects in the content model, or by setting up folder rules in the repository.

Summary

Because most ECM repositories are closely coupled with a folder paradigm, folder structure is an important component of the overall content architecture, even in systems that utilize interfaces that hide folders from the end user.  Organizing content into a folder structure based on metadata is a common requirement in many systems that can be easily met using the Alfresco auto-filing AMP described in this post.

Please add comments and feedback below.

Filed Under: Alfresco, OpenContent Management Suite, Tech Tip, TSG Labs

Reader Interactions

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Primary Sidebar

Search

Related Posts

  • Office 365 – Check-in and Check-out with Documentum, Alfresco or Hadoop
  • Harnessing the Power of Alfresco Data Lists for Cascading Value Assistance
  • Auto-Numbering Content in Alfresco
  • Documentum or Alfresco – Gmail integration for Case Management – TSG/HPI Labs
  • Documentum and Alfresco – Cloud content attached to emails – Bulk uploading
  • Alfresco Data List-Driven Value Assistance
  • Documentum Client for Outlook, Notes Connector, iPhone and other thoughts on Content Management and Email
  • Documentum Open Source Software
  • Alfresco – Viewing Annotations on Versions
  • Content Accelerator Labs – Document View Timeline for Efficient Content Navigation

Recent Posts

  • Alfresco Content Accelerator and Alfresco Enterprise Viewer – Improving User Collaboration Efficiency
  • Alfresco Content Accelerator – Document Notification Distribution Lists
  • Alfresco Webinar – Productivity Anywhere: How modern claim and policy document processing can help the new work-from-home normal succeed
  • Alfresco – Viewing Annotations on Versions
  • Alfresco Content Accelerator – Collaboration Enhancements
stacks-of-paper

11 BILLION DOCUMENT
BENCHMARK
OVERVIEW

Learn how TSG was able to leverage DynamoDB, S3, ElasticSearch & AWS to successfully migrate 11 Billion documents.

Download White Paper

Footer

Search

Contact

22 West Washington St
5th Floor
Chicago, IL 60602

inquiry@tsgrp.com

312.372.7777

Copyright © 2023 · Technology Services Group, Inc. · Log in

This website uses cookies to improve your experience. Please accept this site's cookies, but you can opt-out if you wish. Privacy Policy ACCEPT | Cookie settings
Privacy & Cookies Policy

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Non-necessary
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
SAVE & ACCEPT