Model Manager User Interface (UI)
Click the 'play' button on the video below to learn about this course.
Traditionally in Alfresco, a content model:
Key Takeaway: Content Modeling in XML is difficult and technical.
The required components of an XML content model include:
Each of these components essentially uses and represents metadata, or “data about data.” It’s this metadata that defines all of the relationships and structure for your ECM content in the repository.
Key Takeaway: XML Structurer and Rules are very important in XML Modeling
It’s important to get each component of an XML content model correct, because there are several risks involved if you don’t:
Caution: Content models using XML are very technical in nature, and should not be attempted unless you have an advanced skill set with Alfresco, because there can be very nuanced and subtle deployment considerations.
Key Takeaway: Content Modeling in XML can be dangerous and error-prone and should only be attempted in a controlled test environment first.
Dynamic models allow developers:
Key Takeaway: Put simply, dynamic models allow you to use content models “on the fly” in the repository.
While dynamic modeling is definitely useful, XML poses some special difficulties:
Key Takeaway: For these reasons, dynamic modeling only offers part of the solution to the natural issues that an XML-based content repository can bring up.
Model Manager fix those problems as depicted in the table below.
The Model Manager is designed to:
Key Takeaway: Model Manager is designed for ease of use and is geared toward a Business Analyst or a Developer that wants to create a quick model without all the head aches of XML.
While XML-based content model development:
Model Manager-based content model development:
Key Takeaway: Model Manager alleviates the need for a Business Analyst to be XML literate and to understand the rules and structure of a content model.
Note: This lesson is meant to be interactive. In various parts of this lesson are narration controls. Click the narration where appropriate and when complete, move to the next.
Things to consider when planning a content model:
Content Models should focus on the essentials for a collaborative environment:
We have created a scenario, which will give you predefined criteria for the content model during this training.
Key Takeaway: Plan content models appropriately focusing on the essentials of workflow, content sharing, and metadata.
Fictional Company: Colt Automotive
The following events occurred and tasks have been assigned:
Constraints defined from a business need:
Name of Constraint: Plant List
Why the Constraint is needed: Anytime someone loads a Plant List they must use a drop-down list and select the location associated with the document.
Custom Content Type defined from a business need:
Name of Type: Vehicle Type List
Why the Type is needed: The cm:content Type is not specific enough to capture what we need in our repository.
Aspect defined from a business need:
Name of Aspect: Sales Manager Review
Why is the aspect needed: Starts the workflow of the Sales Manager reviewing an order of received vehicles.
Key Takeaway: Understand the input of content into the ECM and how the Content Model structures the content and applies constraints.
Now that we've introduced the scenario, you can select the Elements of a Content Model below to gain a deeper understanding.
Note: Click the narration tool bar adjacent to the Element to hear about that element. Also refer to the graphic below as you listen to the narration of that element.
|Custom Content Types|
|Aspects and Properties|
|Searching and Indexing|
Key Takeaway: Content Models are structured for a reason and each element plays a role in the overall function of the content model.
Key Takeaway: Custom Models are built to suit specific needs and differentiates an ECM from a File Sharing application.
Key Takeaway: Analyze the business needs, determine the need for a Custom Content Model, and understand the essential components of a Content Model.
Distinct, reusable elements
Suggestion: Whenever there is a point of contention as to when a custom content type should be developed, meet with business and reassess the need.
Key Takeaway: Custom Content types are used to make a healthier and more robust repository when content is structured properly.
Next, let’s go into a demonstration from the Colt Automotive Content Model
Table 1: Data Types
Table 2: Property Requirement Options
Table 3: Multi-valued Property and Constraint Options
Table 4: Indexing Options
Key Takeaway: Aspects allow cross-cutting which is multiple inheritance of Types and other Aspects properties across the content model eliminating the need to create a Custom Type for every type of content and their properties.