From Wiki

Jump to: navigation, search
A Context is a type of Admin Item. Context100.gif

A Context provides users of a particular application or data standard with a focused view of the contents of the Listpoint that has been tailored to their needs. A Context is like an iPod playlist but where Code Lists are being chosen rather than tracks.

A Context is a container for a set of Data Types (EDTs) each of which represents a choice of a Code List made by the owners/stewards of that Context from the large pool of available Code Lists. The names of Code Lists are often odd (they are subject to mutually incompatible naming standards imposed by the organizations that maintain them) so the EDT provides Context creators with a chance to give more appropriate local names to the code lists they wish to adopt without risk of name clashes with other EDTs in other Contexts.

Contexts come in two flavours:

  • A Data Standard context is a collection of Code Lists that are upheld by some standards body as exemplars of good practice or commonality. Application developers or integrators are recommended to adopt those Code Lists that appear in Data Standard contexts in preference to those that do not. Each user must assess which Data Standards are relevant or applicable to them and whether to adopt the recommendations or not;
  • An Application context is the collection of Code Lists that are actually used by a particular version of a software application whether compliant with standards or not. Many database columns, screen fields, dropdown boxes or message elements are constrained to a limited set of coded values. These should correspond with the sets of values exposed by the relevant EDTs. Ultimately, benefits will accrue to application maintainers from populating all application components that have enumerated contents from Application Contexts downloaded from Listpoint.

While at present a Context only holds a list of Enumerated Data Types, in future it is hoped to add Simple and Complex Data Types such that a Context could then hold a complete data dictionary for a data standard or application.

Each Context's template has the following properties:

Property Description
Live Start Date This is the date when the Context became or is due to become 'Live'. It can be used by the Steward Team to help control synchronization of dependent Contexts (e.g other applications) with this Context because it signifies when a particular application will switch from using one version of a Code List to a later one (which may contain more codes)

How To guides for Contexts are here

Context Business Rules are here

Personal tools