Book Image

Alfresco One 5.x Developer's Guide - Second Edition

By : Benjamin Chevallereau, Jeff Potts
Book Image

Alfresco One 5.x Developer's Guide - Second Edition

By: Benjamin Chevallereau, Jeff Potts

Overview of this book

Do you want to create more reliable and secure solutions for enterprise apps? Alfresco One 5.x is your gateway to developing the best industry-standard enterprise apps and this book will help you to become a pro with Alfresco One 5.x development. This book will help you create a complete fully featured app for your organization and while you create that perfect app, you will explore and implement the new and intriguing features of Alfresco. The book starts with an introduction to the Alfresco platform and you’ll see how to configure and customize it. You will learn how to work with the content in a content management system and how you can extend it to your own use case. Next, you will find out how to work with Alfresco Share, an all-purpose user interface for general document management, and customize it. Moving on, you write web scripts that create, read, and delete data in the back-end repository. Further on from that, you’ll work with a set of tools that Alfresco provides; to generate a basic AnglularJS application supporting use cases, to name a few authentication, document list, document view. Finally, you’ll learn how to develop your own Alfresco Mobile app and understand how Smart Folders and Search manager work. By the end of the book, you’ll know how to configure Alfresco to authenticate against LDAP, be able to set up Single Sign-On (SSO), and work with Alfresco’s security services.
Table of Contents (17 chapters)
Alfresco One 5.x Developer’s Guide - Second Edition
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Manage property indexing


Directly in your content model, you can specify how your properties will be indexed by Solr. Below each property, you can add an index element like this one (that contains the default value):

<index enabled='true'> 
    <atomic>true</atomic> 
    <stored>false</stored> 
    <tokenised>true</tokenised> 
</index> 

Here is the list of possible configuration:

  • Change the enabled attribute to false to do not index this specific property. It means that you won't be able to search on it.

  • Change the atomic property depending if you want properties to be indexed as part of the transaction commit (true), or indexed in the background (false). For example, the properties using  typed:content are indexed in the background because some transformations need to be done before indexing.

  • Change the stored property if you want to store the property value in the index. This property should never be changed in production...