• 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-Numbering Content in Alfresco

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

November 24, 2014

To continue our series of posts highlighting common design patterns that we see in many Alfresco implementations (see previous posts on Auto-Filing and Data List-Drive Value Assistance, this post will focus on another Alfresco module package (AMP) that TSG has developed that provides a configurable way to automatically number content with a unique numbering sequence upon creation.

Introduction

Many of our ECM implementations have requirements for labeling content with a unique identifier that is separate from the unique ID that is generated by the content management platform (r_object_id in Documentum and sys:node-uuid in Alfresco).  Auto-numbering requirements are particularly prevalent in regulated industries using controlled document systems.  Overall, it’s a best practice  to implement a unique identifier aside from the system generated unique ID because looking forward, it is likely that at some point in the future, the content will be migrated to a newer version of the ECM platform, or to a different platform altogether.  In these cases, it’s often impossible to have the new system generate identifiers in the same way as the old system.  See our previous post on Documentum r_object_id – Thoughts and Best Practices for more information.

Generating a unique ID separate from the ECM platform’s unique ID can also allow content to be more easily identified by its ID using prefixes and suffixes along with a sequence number.  Different document types can be given different prefixes or suffixes.  For example, standard operating procedure documents can be given a prefix of “SOP” followed by a sequence number.  That way users will know that the document is a standard operating procedure just by looking at the ID.

To make auto-numbering simple in Alfresco, we’ve developed a configurable AMP module to automatically generate a unique ID for new content at creation time, and set that ID as a property of the content.  A single numbering configuration can be created to apply to all document types in the repository, or separate configurations can be defined for different document types.  Here’s how it works:

Configuration

In order to avoid code changes for each implementation, the auto-numbering module is configurable.  System administrators can simply initiate a web service call from a browser in order to set up the auto-numbering configuration(s) 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-numbering configurations include the following parameters:

  • Prefix – optional prefix to be added to the sequence number
  • Suffix – optional suffix to be added to the sequence number
  • Starting Number – starting number for the auto-numbering scheme. The numbering sequence can have any number of leading zeros (e.g. “00000001”)
  • Types – Alfresco content types that the auto-numbering configuration applies to
  • Set Properties – the property or properties that auto-number will be applied to. For example, the number can be set as the document name, title, or any other custom metadata field.

Aspects and Behaviors

Similar to the auto-filing functionality described in our previous post, once the auto-number 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.  The auto-numbering AMP uses behaviors to watch for new content being created in the repository so that the next number in the sequence can be generated and automatically applied as a property of the new content.

The final piece of the puzzle is telling the repository which content should be auto-numbered.  We utilize an Alfresco aspect for this.  Any content that should be auto-numbered receives an “Autonumber” aspect.  Aspects can be automatically applied to content by making them mandatory aspects in the content model, or by setting up folder rules in the repository to apply the aspect.

Summary

Many ECM implementations have a need for a unique identifier that is different from the unique ID given by the ECM system.  In fact, auto-numbering is in the list of TSG best practices for any ECM implementation because it can help make the system more future-proof when considering upgrades and migrations down the road.  Auto-numbering requirements can be easily met in a configurable manner using the Alfresco auto-numbering AMP.

Please add comments and feedback below.

Filed Under: Alfresco, Product Suite, R&D, 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

  • Alfresco Data List-Driven Value Assistance
  • Documentum Transformation Services (DTS) – Alternative Approaches with Adobe LiveCycle and OpenOffice
  • Documentum Annotations – TSG View of the different solutions
  • Documentum Open Source Software
  • Extending Alfresco Security Beyond ACLs
  • Harnessing the Power of Alfresco Data Lists for Cascading Value Assistance
  • Auto-Filing Content in Alfresco
  • Documentum Client for Outlook, Notes Connector, iPhone and other thoughts on Content Management and Email
  • Thin Client Annotation tool uses Google Web Toolkit
  • Documentum Migration – OpenMigrate for both large migrations and ongoing capture

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