Asset description, context, identity, and REST name
Each type of information asset has its own identity string that contains the assets that are needed to identify the asset in the catalog. The context and identity string of an information asset are used in the import files of extended data sources and of extension mapping documents.
Context and identity string of an asset
The context of an asset is the list of assets that contain it, without which the asset has no identity. When you import extended data sources or an extension mapping document with its mappings, the import process puts the imported assets in their correct context in the catalog.
An identity string concatenates the context and the name of the asset. The identity string fully identifies the asset as a unique asset in the catalog.
For example, if the context of an asset that is called column5 is host1.database2.schema3.table4, then the identity string of the asset is host1.database2.schema3.table4.column5. This identity string uniquely identifies the asset as being in table4, which is in schema3, which is in database2, which is on host1.
- You must include all asset types above the asset type that you are identifying.
- All assets above the asset type that you are identifying must not be null.
- The assets in a context are separated by a period (.).
- The asset names in the context are not case-sensitive. They must contain only alphanumeric characters and no spaces.
The following table lists assets that are displayed in the catalog. If an asset can be used as a source or target asset in extension mapping documents, or if it is a type of an extended data source type, its context and identity string are given.
Asset type | Definition | Context, identity string, and REST name |
---|---|---|
Amazon S3 bucket | A type of data file folder that can contain other data file folders or Amazon S3 data files. |
|
Amazon S3 data file | A container that stores data that is used by the Amazon S3 web service. |
|
Amazon S3 data file field | A data field that is contained in an Amazon S3 data file record. |
|
Amazon S3 data file folder | A folder that is contained in another Amazon S3 data file folder. |
|
Amazon S3 data file record | A component within an Amazon S3 data file. |
|
Annotation | A comment that is created by developers of IBM® InfoSphere® DataStage® and QualityStage® jobs to explain, summarize, or describe a job design or to help identify parts of a job design. |
|
Application | An extended data source asset that includes a collection of methods and parameters for reading or writing data. |
|
Attribute | A type of master data model asset from IBM InfoSphere Master Data Management that
is a characteristic or trait of an member type that describes the
member. For example, the entity type Personhas the attribute Date of Birth. |
|
Attribute type | An attribute type describes a generic master
data characteristic. Two types of attribute types are available in IBM InfoSphere Master Data Management:
Date of Birthhas the attribute type PersonDOB. |
|
Attribute type field | An attribute type field describes the specific
parts or entities of an attribute type. For example, the attribute
type PersonDOBhas the attribute type field BirthYear. |
|
BI collection | A data structure that provides a view of data that is stored in databases and files. BI collections are the data sources of BI reports. |
|
BI collection member | A different representation of a data value that is in the database column. BI collection members define the structure of the BI collection that owns them. |
|
BI hierarchy | An organizational structure that defines an ordering or relationship of data within a BI collection. |
|
BI level | A position within a BI hierarchy. |
|
BI model | A grouping of BI collections that are relevant to a BI application. |
|
BI report | A report that is based on information in a database or a BI model. |
|
Blueprint | A collection of diagrams that represents an information architecture for a project. A blueprint can be published to the catalog from IBM InfoSphere Blueprint Director. |
|
Category | A word or phrase that classifies and organizes glossary content into a hierarchy. A category can also contain other categories. |
|
Collection | A group of assets that you can move to IBM InfoSphere Data Click, add to other collections, edit properties of an individual asset, or batch edit properties of several assets. |
|
Column analysis | An IBM InfoSphere Information Analyzer process that describes the condition of data at the field level. |
|
Column definition | A column-level data definition that stores data values within an InfoSphere DataStage and QualityStage table definition. |
|
Column mapping | A row in an IBM InfoSphere FastTrack mapping specification that describes a transformation from one or more source columns and terms to one or more target columns and terms. |
|
Composite view | Composite view describes the way in which to display master data from different attributes. For example, the composite view might be either enterprise most current attribute or source-specific attribute values for a person. |
|
Connector | A software component that provides access from InfoSphere DataStage and QualityStage to an external source of data, such as relational databases or messaging software. |
|
Custom attribute | A user-defined property for an asset that further describes assets of that type. |
|
Data class | An asset from other products in InfoSphere Information Server or created in InfoSphere Information Governance Catalog that categorizes database columns and data file fields according to the type of the data and how it is used. |
|
Data element | An asset from IBM InfoSphere DataStage that specifies the type of data a column contains, which in turn determines the transforms that can be applied in a transformer stage. |
|
Data file | A file that stores data, can be segmented into data file records, and are the file equivalents of database tables. |
|
Data file definition | Defines the structures of data files. A data file definition does not represent a file asset that is imported into the metadata repository or a file that physically exists in the real world. It represents the structure of files that might be created and imported later. |
|
Data file definition field | A field in a data file definition record. Data file definition fields are column-like elements within data file definition records. A data file field can implement a data file definition field. |
|
Data file definition record | Defines the format of the data file records in a data file definition. Data file definition records represent table-like objects within data file definitions. A data file record can implement a data file definition record. |
|
Data file field | A field within a data file record. A data file field is equivalent to a database column and is the smallest data unit that is used to store the data values of an object. |
|
Data file folder | A data file folder is the storage medium for data files and can contain other data file folders and data files. |
|
Data file record | A collection of related fields in a data file. A data file record is the file equivalent of a database table. |
|
Database | A relational storage collection that is organized by schemas and procedures. A database stores data that is represented by database tables. |
|
Database column | A column in a database table. |
|
Database connection | A connection for accessing a database or file, for example, an ODBC or Oracle connection. |
|
Data policy | A high-level, natural-language description of a subject area. A policy documents and captures additional information about business rules and processes. Data policies are created in InfoSphere Information Analyzer. |
|
Database schema | A named collection of related database tables and integrity constraints. A schema defines all or a subset of the data that is in a database. |
|
Database table | The structure that represents and stores columns within a database. |
|
Data rule | The implemented binding to a database column and the rule logic in InfoSphere Information Analyzer. |
|
Data rule set | A collection of data rules that were generated in InfoSphere Information Analyzer. |
|
Data rule definition | A method to define specific tests, validations, or constraints associated with your data. The published and unpublished data rule definitions that were created in InfoSphere Information Analyzer project and that are assigned to a term. |
|
Data rule set definition | A group of published and unpublished data rule definitions that were created in InfoSphere Information Analyzer. |
|
Endpoint | The connection point for a streams application to process data as a target. Each endpoint contains one top-level tuple. |
|
Entity | A master data asset from IBM InfoSphere Master Data Management that is a single unique object that is used to calculate master data. Examples of an entity are a single person, single product, or single organization. |
|
Entity type | A person, organization, object type, or concept about which information is stored. An entity type describes the type of the information that is being mastered. An entity type typically corresponds to one or several related tables in a database. For example, an entity type might be “Person”. |
|
Extension mapping | An extended data source asset that represents an external flow of data from one or more sources to one or more targets. |
|
Extension mapping document | A type of an extended data source asset. It is a document with rows that contain extension mappings. |
|
File | An extended data source asset that represents a storage area for capturing, transferring, or reading data. |
|
Folder | A user-defined container that is used to organize the contents of InfoSphere DataStage and QualityStage projects. |
|
Foreign key | A non-unique identifier that defines a relationship between two database tables. A foreign key in one table typically matches the primary key in the related table. |
|
Foreign key definition | A relationship between pairs of table definitions that is based on a foreign key column. |
|
Host | A computer that is either an engine system or a remote node that is used by an engine system to distribute parallel jobs. |
|
Engine | A computer that hosts the engine components of IBM InfoSphere Information Server products. |
|
IMS database | Stores data in a hierarchical model that uses blocks of data that is known as segments. |
|
IMS field | A field of an IMS segment. |
|
IMS segment | A block of data in an IMS database, its position in the IMS hierarchy, and its relationships to other segments. |
|
In parameter | An extended data source asset that delivers information from a client to a stored procedure definition. |
|
Information governance policy | A high-level, natural-language description of a governance subject area. Information governance policies are created in Information Governance Catalog. |
|
Information governance rule | A natural language definition of a characteristic to make information assets compliant with business objectives. Information governance rules are created in Information Governance Catalog. |
|
Information Server report | A report that is created and saved in the console or the web console. |
|
Information service | A single operation or a collection of operations that exposes results from processing by information providers. |
|
Information services application | A container for a set of services in IBM InfoSphere Information Services Director. |
|
Information services operation | A container for the business logic of an information service. The operation describes the actual task that is done by the information provider. |
|
Information services project | A collaborative environment in IBM InfoSphere Information Services Director that contains applications, services, and operations. |
|
In parameter | An extended data source asset that delivers information from a client to a stored procedure definition. |
|
InOut parameter | An extended data source asset that represents a parameter that combines the input parameter and the output parameter. |
|
Input parameter | An extended data source asset that delivers information from a client. |
|
Job | The set of design objects and compiled programmatic
elements that can connect to data sources, extract, and transform
that data, and then load that data into a target system. There are
several types of jobs:
|
|
Job run | The specific run of a job. A job can run multiple times, producing multiple job runs. |
|
Job run activity | The action of running a job from a control flow job. Such actions are connected by triggers. |
|
Label | More descriptors that authors of catalog content can apply to terms, categories, and other information assets in the catalog. |
|
Local container | A grouping of job content and logic, such as stages and links, that can be reused within the same job. |
|
Logical data model | A set of related entities and their business associations that is defined in an entity-relationship model. |
|
Machine profile | The paths and parameters to access a mainframe computer. Machine profiles are created in IBM InfoSphere DataStage and QualityStage Designer. |
|
Mapping project | A container that organizes mapping specifications and associated data resources in IBM InfoSphere FastTrack. |
|
Mapping specification | A container for a set of mappings in IBM InfoSphere FastTrack. The mapping specification describes how data is extracted, transformed, or loaded from one data source to another. |
|
Mapping specification generation | A set of mappings in IBM InfoSphere FastTrack that define an InfoSphere DataStage and QualityStage job. |
|
MDM model | A representation of physical master data
assets or virtual master data assets from IBM InfoSphere Master Data Management.
For physical master data assets, master data is created in, stored
in, and accessed from a central system. For virtual master data assets,
master data is maintained in a distributed fashion and remains fragmented
across systems but with a central indexing service. An MDM model asset
can contain member types. Master Data Management model organizes
and defines data to provide a single point of reference of the data.
The single point of reference is called Master Data.
|
|
Member type | A master data asset that defines the kind of member data that is stored and managed. Defining member types enables products for use in multiple business environments. For example, member types might be Patient, Client, or Provider. |
|
Member attribute | A master data asset that is a predefined type. For example, MemName, MemAddr, and MemIdent are all predefined attribute types. |
|
Method | An extended data source asset that represents a function or a procedure. |
|
Notes | Annotations that a user creates about an asset. |
|
Object type | An extended data source asset that represents a grouping of methods or a defined data format that characterizes the input and output structures within a single application. |
|
Out parameter | An extended data source asset that returns data to the stored procedure definition asset. |
|
Output value | An extended data source asset that represents the data that is returned to the client or to an application asset. |
|
Parameter | A processing variable that can be used at various points in a job design and overridden when the job is run in order to dynamically influence the processing of the job. |
|
Parameter set | A group of job parameters that are assigned to a job as a unit and that can be reused. |
|
Physical data model | A design schema for information assets that defines the physical structures and relationships of data within a subject domain or application. |
|
Physical object | A master data asset for the physical MDM model. Address, Party, or Claim are sample objects with a defined set of attributes. |
|
Physical object attribute | A single property of a physical object. |
|
Primary key | A unique identifier of a database table that can also be used to define relationships between tables. |
|
Result column | An extended data source asset that represents the data that is returned from a database query. |
|
Routine | A built-in or user-defined function that is called in a derivation or constraint, or that is called before or after a job or stage. |
|
Server | A supertype of host that includes data servers and engines. |
|
Shared container | A grouping of job content and logic, such as stages and links, that can be used by multiple jobs. |
|
Stage | An element of a job design that describes a data source, a data processing step, or a target system and that defines the processing logic that moves data from input links to output links. There are separate icons for each type of stage. |
|
Stage column | A flow variable or column that is used to denote data flow items within a link or stage. |
|
Stage type | An object that defines the capabilities of a stage, the parameters of the stage, and the libraries that the stage uses at run time. Each stage is associated with a stage type. |
|
Stage variable | A type of stage that is defined by InfoSphere DataStage and that typically has an action, such as concatenate or a calculation, which is associated with it. |
|
Standardization object | A component file in a standardization rule set. |
|
Standardization rule set | A series of customizable files that define how to process input data for the Standardize and Investigate stages in IBM InfoSphere QualityStage. |
|
Steward | A user or group who is designated as responsible for one or more information assets in the catalog. |
|
Stored procedure | A procedure that is stored in the database to encode behavioral aspects of data manipulation, such as assertions, constraints, and triggers. |
|
Stored procedure definition | An extended data source asset that represents a procedure that is stored in the database. The stored procedure definition includes the parameters and details of the stored procedure. A stored procedure definition can also be used to produce data in a table format. |
|
Table analysis summary | An InfoSphere Information Analyzer process that consists of primary key analysis and the assessment of multicolumn primary keys and potential duplicate values. |
|
Table definition | A table-level data definition that structures data values within an InfoSphere DataStage and QualityStage project. Table definitions contain column definitions. |
|
Term | A word or phrase that describes a characteristic of an asset. A term in the published glossary is published. Alternatively, a term in the development glossary is unpublished. |
|
Term history | The changes that were made to the description or other properties of a term since the term was first defined. |
|
Transforms function | A built-in or user-defined macro expression that is used in a derivation or constraint in InfoSphere DataStage and QualityStage. |
|
Transformation project | A project that is created in InfoSphere DataStage and QualityStage. Projects hold collections of objects such as jobs, stages, and table definitions. |
|
Tuple | An ordered set of values. |
|
Tuple attribute | The equivalent of an InfoSphere DataStage column definition. |
|
User group | A group of users of InfoSphere Information Server. |
|
View | A dynamic or virtual database table whose data is computed or collated. |
|
Warehouse mapping document | An extended data source asset that is a document with warehouse mappings from IBM InfoSphere Warehouse. A warehouse mapping represents an external flow of data from one or more source databases to one or more target databases. |
|
Examples
- Context and identity string for a method asset
- You need to update the quarterly sales revenue in the main office by using a sequential file that contains invoice information from each sales region. The results of the SQL transformations are stored in seql_total_qrt_invoice.
- Context and identity string for a file asset
- You need to use a SQL file, seql_customer_info, that has customer contact information. This file is generated by an ETL tool from an independent software vendor.