• 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

Why Can’t I Change My Object Model?

You are here: Home / ECM 101 / Why Can’t I Change My Object Model?

January 31, 2017

Can you first just tell me what an object model is?

In ECM, your object model is king. An object model is the organization of your digital content into specific types of folders and documents, as well as the attributes that reside on each one. It dictates so much about your system, both in the literal sense (here are the attributes that a type has) and the productivity sense (here is the hierarchy of my types that can make searching easier). That is why it is essential for a business to understand their object model and get it right from the start, especially since having the correct model allows users access to all of the metadata they need on the types they need them on from day one. However, as businesses and data evolve, the need can arise to alter an object model.

Why would I want to change my model?

There are numerous factors that can lead to an object model change, but three are the most common: we have new metadata we need to keep, we have old metadata we no longer need and we need to be able to search on multiple types at the same time.

Let’s tackle the last instance first, what exactly does that mean? Let’s say an insurance client has two major types of documents – claims and policies. Normally, one division handles claims and one division handles policies, and everyone can search for their documents without any problem. However, one claims adjuster has mentioned it would be great if he could see all the claims and policies paid out to a particular claim number, which is a metadata field on both types of documents. Sounds pretty straightforward right?

Well, if the object model was setup in a flexible way, it is very straightforward! You just need a parent type setup (called insurance document for example), it needs a claim number metadata field setup on its type, and both the claim and policy types need to be children of the generic insurance document. Then the claims adjuster can just search for the claim number on the “insurance document” type, and both policies and claims with that number will come back. The only catch is that generic insurance document type needs to be setup beforehand. The same thing applies for attributes that we now want to add on or remove after the fact, they should already be a part of the model.

Ok, but why can’t I change the model? Isn’t it just configuration?

Well yes, the object model is just configuration, but it is a very special configuration that drives your relational database behind the scenes as well. All of the tables have been created with special relationships and columns, and everything that was there from the start needs to be there at the end in order to keep everything working. On top of that, your index for quick searches is also built from your object model and is very particular that it never changes. In order to change those database tables, all of the rows (essentially, your metadata) would need to be removed before you could alter the table. Then all of the relations to the table would need to be redone as well to take into account the changes done to the table. Lastly, you would need to re-index everything in your content store, which normally takes multiple days depending on the content store size.

Fine, I get it, it is really hard to change the object model in place, but I really need to do it. Is there nothing I can do?

Of course you can, it just isn’t as easy as updating configuration. Check out our upcoming blog post on how to change your object model for all of the details!

Filed Under: ECM 101

Reader Interactions

You must log in to post a comment.

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

Primary Sidebar

Search

Related Posts

  • Reference Architecture for Content Management on Azure HDInsight with HBase
  • ECM 2.0 – Can you build it yourself?
  • NIRMA 2018 – TSG Booth 105 August 5th-7th
  • ECM Dinner Party
  • ECM Migrations – Top Ten Planning Tips For a Successful Migration
  • Enterprise Content Management: Watch for These Disruptors – Document Strategy Guest Contributor
  • When Should I Start Planning my ECM Project?
  • What makes migrating from a Legacy ECM systems so difficult?
  • Save Your Sinking Legacy ECM Implementation
  • Why should your company move from a shared drive to Enterprise Content Management (ECM)?

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