Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Introduction

Different Contents can be created with multiple terms with the same meaning. As part of search API, we should provide contents which satisfies the filter criteria as well as the relevant content which are relatively nearer to the search criteria.

Background & Problem Statement

Before implementation of Framework, content creation were having very limited set of generic term which were utilised to categorise content. These were very much generic at LP layer. Later, it was realised that - there should be an infrastructure which can be utilised to make the terms specific to the instance. This requirement brought the concept of Framework APIs.

But with availability and ease of framework terms creation, it is becoming easy to create large numbers of terms that may lead to duplication of terms, terms with same meaning, terms with incomplete metadata, no association or no translation.

Vocabulary layer is considered a dictionary of terms, which will be independent of framework. It holds the association among the terms. Each term can be part of set of related terms and have associationship with other terms.

The main target of vocabulary is to enrich framework terms and enhancement of search service.


  • No labels