This interface defines the objects of the SAS Open Metadata Architecture model as constant variables. These should be used
where you need a string representation of a metadata type. For example: PhysicalTable = MetadataObjects.PHYSICALTABLE.
These are generated to match the SAS Open Metadata Architecture Model.
ABSTRACTEXTENSION
Model description of the metadata type: The SAS Metadata Model supports extensions to enable end users and application developers to define additional attributes that are not part of an object's metadata type definition.
ABSTRACTJOB
Model description of the metadata type: A job is a set of processes that initiate a process or create an output such as a data store or output table.
ACCESSCONTROL
Model description of the metadata type: An access control is an object that relates an identity and a permission to a resource in order to regulate access to the resource.
ACCESSCONTROLENTRY
Model description of the metadata type: The AccessControlEntry metadata type is used to define an access control directly on a resource.
ACCESSCONTROLTEMPLATE
Model description of the metadata type: The AccessControlTemplate (ACT) metadata type enables you to define a template of individual users, groups, and permissions that can be applied to multiple resources.
ASSOCIATIONPROPERTY
Model description of the metadata type: The SAS Metadata Model provides a Prototype metadata type to define templates that can be used to create metadata entities.
ATTRIBUTEPROPERTY
Model description of the metadata type: The SAS Metadata Model provides a Prototype metadata type to define templates that can be used to create metadata entities.
AUTHENTICATIONDOMAIN
Model description of the metadata type: Authentication domains provide logical groupings for resources and logins in a metadata repository.
CONFIGUREDCOMPONENT
Model description of the metadata type: Installed software that has configuration information in addition to the licensing information.
DATASOURCENAME
Model description of the metadata type: Represents a data source name (DSN) that is a construct used by the SAS table server to identify a data source definition.
DOCUMENT
Model description of the metadata type: A Document is a web page or other conent that contains documentation pertinent to the object to which this document is related.
EXTENSION
Model description of the metadata type: Extension enables end users and application developers to define additional attributes that are not part of an object's metadata type definition.
EXTERNALIDENTITY
Model description of the metadata type: This is an ID associated with the object in some other context, such as a GUID or DN for LDAP .
GLOBALFORMULA
Model description of the metadata type: PROC OLAP and OLAP CUBE Studio enable users to define formulas for the dimensions of a cube that result in the creation of calculated members and named sets.
LOCATION
Model description of the metadata type: This type represents a location that includes a type (is it a street address, or an office number), as well as address information (street, city, country).
LOGICALCOLUMN
Model description of the metadata type: The supertype for Column, which is part of a relational table, and Measure, which is used with OLAP types.
MININGRESULT
Model description of the metadata type: Represents a SAS Enterprise Data Mining Model that is a formula or algorithm that computes outputs from inputs.
OPENCLIENTCONNECTION
Model description of the metadata type: An abstract type that represents the connection information needed by an open client to access a deployed component.
PERMISSION
Model description of the metadata type: A permission represents an action that a user may attempt against a resource in the metadata server.
PERMISSIONCONDITION
Model description of the metadata type: Stores an expression that is applied to conditionally grant a user or group access to a resource.
PROPERTYSET
Model description of the metadata type: A PropertySet contains a complete set of properties to be used by the OwningObject in a particular context.
PROTOTYPE
Model description of the metadata type: Used to create a template for creating other metadata objects or set of metadata objects that represent a concept.
PSPORTALPROFILE
Model description of the metadata type: A SAS Information Delivery Portal user's portal information, which defines the basic functionality of the portal.
PSPORTLET
Model description of the metadata type: A Web component that is managed by a Web application and that is aggregated with other portlets to form a page within the application.
QUERYCLAUSE
Model description of the metadata type: This abstract type represents types that are used to define the transformations that are performed.
SASCATALOG
Model description of the metadata type: Represents a SAS file that stores many different kinds of information in smaller units called catalog entries.
SASFILEREF
Model description of the metadata type: Represents a name temporarily assigned to an external file or to an aggregate storage location that identifies it to SAS.
SECURITYTYPECONTAINMENTRULE
Model description of the metadata type: A SecurityTypeContainmentRule tells the authorization facility how to find parent objects for a particular metadata type.
TABLECOLLECTION
Model description of the metadata type: A classifier that defines a set of tables that all share the same characteristics but that should be treated as one classifer for display purposes.
TARGET
Model description of the metadata type: Represents a variable whose values are known in one or more data sets that are available (in training data, for example) but whose values are unknown in one or more future data sets (in a score data set, for example).
The SAS Metadata Model supports extensions to enable end users and application developers to define additional attributes that are not part of an object's metadata type definition. Two types of extended attributes are supported:
end user-defined attributes
application-specific attributes
An example of a user-defined extended attribute is an attribute that is defined in the Extended Properties tab of a SASLibrary or Table object in SAS Management Console. Any attribute defined in this tab can be viewed and modified by any user who is authorized to view and modify the library or table resource. An example of an application-specific extended attribute is a SortType attribute on a Column. If the data in a column's source table is stored chronologically and an application has a need to access the data alphabetically, then the SortType attribute can specify how the application should rearrange or request the data from the data store.
AbstractExtension is the supertype for describing end user-defined attributes. As a supertype, it defines attributes that are common to the Extension and NumericExtension metadata types and should not be instantiated. The SAS Metadata Model requires that you distinguish between character and numeric attributes when defining end-user attributes. Use the Extension metadata type to define attributes that store character values. Use the NumericExtension metadata type to define attributes that store numeric values.
Extensions are provided for end-users to extend a metadata type and should be supported by all top-level objects in a UI.
Application-specific attributes are defined by using the AbstractProperty and Property metadata types.
Model description of the metadata type: A job is a set of processes that initiate a process or create an output such as a data store or output table. A given job can produce a single output or multiple outputs. In addition, jobs can be scheduled. As a supertype, the AbstractJob metadata type defines metadata that is common to all metadata types that define a job and should not be instantiated. When actually defining a job, use the Job metadata type and follow the recommendations for other metadata types provided in the documentation for the feature for which you want to create metadata. For instance, if you want to create a job for the LSF Scheduler, read the documentation for the scheduler.
Model description of the metadata type: Used to contain name/value pairs. The AbstractProperty metadata type defines attributes and associations that are common to all of the property types; however, as a supertype, it should not be instantiated. When defining a metadata object to contain an actual name/value pair, use the Property metadata type or one of the other property metadata types, depending on the usage goal.
Model description of the metadata type: The parent type for transformation types. Transformation types are used to document transformation of data. This includes extraction, transformation, and loading of data, stored procedures, and logical to physical mappings. AbstractTransformation is a supertype that defines common attributes and associations that are shared by metadata types that describe the steps and activities in the transformation process. This metadata type should not be instantiated. Instead, use the appropriate subtype to represent the steps and activities in a transformation.
Model description of the metadata type: An access control is an object that relates an identity and a permission to a resource in order to regulate access to the resource. The SAS Open Metadata Architecture authorization facility uses the information in access controls to return authorization decisions on resource requests. The SAS Metadata Model defines two basic types of access controls: AccessControlEntry, which associates identities and permissions directly with a resource; and AccessControlTemplate, which enables users to define a template of identities and permissions that can be applied to multiple resources. AccessControl is a supertype and should not be instantiated. When defining an actual access control, use the AccessControlEntry and AccessControlTemplate metadata types. AccessControl objects should not be explicitly created or deleted. Access controls are managed programmatically using the SAS Open Metadata Interface ISecurityAdmin method class, which is documented in the SAS 9.2 Open Metadata Interface: Reference and Usage. The ISecurityAdmin class provides methods for defining and managing direct access controls as well as access control templates.
Model description of the metadata type: The AccessControlEntry metadata type is used to define an access control directly on a resource. The access control is stored with the resource definition and is unique to that resource. That is, the AccessControlEntry (ACE) cannot be applied to another metadata object. An ACE can specify permissions for both individual users and for groups. If a given identity is referenced more than once in the ACE, for example, both directly and by virtue of membership in one or more groups, the permission assigned directly to the identity will take precedence. When the SAS Open Metadata Architecture authorization facility evaluates access controls, a permission assigned in an ACE will take precedence over a permission assigned in an AccessConrolTemplate (ACT). A resource-specific access control also takes precedence over any inherited access controls and permissions assigned in the Repository ACT. An ACE should not be explicitly created or deleted. Access controls are managed programmatically using the SAS Open Metadata Interface ISecurityAdmin server interface, which is documented in the SAS 9.2 Open Metadata Interface: Reference and Usage. ISecurityAdmin provides methods for defining and managing direct access controls as well as access control templates.
Model description of the metadata type: The AccessControlTemplate (ACT) metadata type enables you to define a template of individual users, groups, and permissions that can be applied to multiple resources. This template is stored as an independent resource that can be associated with other resources. Use this metadata type when you want to confer the same set of authorizations on multiple resources. Because an ACT is independent of the resources that it controls, it is also easy to maintain when an update is needed. Any change that you make to the ACT will be enforced on all resources that reference the ACT. An ACT should not be explicitly created or deleted. ACTs are managed programmatically using the SAS Open Metadata Interface ISecurityAdmin method class, which is documented in the SAS 9.2 Open Metadata Interface: Reference and Usage. The ISecurityAdmin class provides methods for defining and managing direct access controls as well as access control templates.
Model description of the metadata type: A summary of detail data that is stored with or referred to by a cube. Aggregations support rapid and efficient answers to business questions. Developers are discouraged from creating or consuming Cube metadata directly with the SAS Open Metadata Interface. Instead, Cubes should be defined by using either SAS OLAP Cube Studio or PROC OLAP. For more information, see the documentation for SAS OLAP Cube Studio and PROC OLAP.
Model description of the metadata type: Contains analytic attributes to apply to a column. These attributes include information such as upper and lower limits, and cost of acquiring a variable, level, and distribution. Used by SAS Enterprise Miner.
Model description of the metadata type: References a location that has SAS analytic content. An associated server context should be a SAS server that can reference this location and interpret the content. Directory role should be set. See directory for a list of possible roles.
Model description of the metadata type: Contains analytic attributes to apply to a table. These attributes include information such as the sampling rate and a description of the group of observations in this table. Used by SAS Enterprise Miner.
Model description of the metadata type: Represents a feature/action of an application. These are used in conjunction with Roles (IdentityGroup objects with a type of Role) to control which application features are made available to different users. Application actions are designed by applications and created by them during installation and/or configuration. The user manager can be used to create roles and manage user access to those features. Since applications are designed to respond only to certain actions there is no need for users to explicitly create their own application actions.
Model description of the metadata type: One of several metadata types used to describe the physical location of some form of content. ArchiveEntry describes a unit of content in an archive file.
Model description of the metadata type: Represents an archive, such as a tar file or a zip file, which may contain entries. It is one of several metadata types used to describe the physical location of some form of content.
Model description of the metadata type: The SAS Metadata Model provides a Prototype metadata type to define templates that can be used to create metadata entities. The AssociationProperty metadata type is used with other prototype objects to define the associations that are needed in a given scenario.
Model description of the metadata type: The SAS Metadata Model provides a Prototype metadata type to define templates that can be used to create metadata entities. The AttributeProperty metadata type is used with other prototype objects to define the attributes and the values that are needed in a given scenario.
Model description of the metadata type: Authentication domains provide logical groupings for resources and logins in a metadata repository. An individual uses the same user ID and password for all of the resources in a particular authentication domain. For example, when an application needs to locate credentials that enable a particular user to access a particular server, the application searches the metadata for logins that are associated with the authentication domain in that the target server is registered.
Model description of the metadata type: Beginning in SAS 9.3, represents a new member in a dimension of a cube. A CalculatedMember object is required to have an association to a Hierarchy object and supports an optional association to a Level object in addition to having an association to the owning Cube object. If the associated Hierarchy object is deleted, the CalculatedMember is deleted as well.
Model description of the metadata type: This type is used by Change Mangement. Change represents the identity who made the change and is associated to all objects checked back into a repository.
Model description of the metadata type: A classifier is an element that describes structural and behavioral features. In the metadata model, a Classifier may declare a collection of Features. Classifier is an abstract metadata class.
Model description of the metadata type: Represents the information required to connect to a server. It is associated with the deployed component, i.e. server, that can be accessed using the connection information. It may also be associated with the deployed components that can use the connection information to access the server..
Model description of the metadata type: Describes the type of content contained in the associated object. This will allow application that deliver content to determine if content may be displayed and/or the best way to display the content.
Model description of the metadata type: A logical set of data that is organized and structured in a hierarchical, multidimensional arrangement. A cube is a directory structure, not a single file. A cube includes measures, and it can have numerous dimensions and levels of data.
Model description of the metadata type: A relational schema that contains tables that are not in SAS data sets. In order to use a SAS application server to access the tables in a database schema, the tables must also be registered with a SAS library.
Model description of the metadata type: Represents a data source name (DSN) that is a construct used by the SAS table server to identify a data source definition. A data source definition specifies how to locate and access a data source, including any authentication (such as a user name and password) that a user must supply in order to access the data and any properties used to connect to a particular data source or data sources. By using a DSN, a user can avoid specifying connection parameters to connect to a data source. An administrator can also configure a data source, determine the level of security, and share the DSN with others.
Model description of the metadata type: An abstract type that represents an object that contains a set of columns. When creating metadata, use the subtype of DataTable that best describes the entity that you want to represent.
Model description of the metadata type: An abstract metadata type that represents installed software. This software might or might not be licensed as indicated by the IsLicensed attribute. When creating metadata, use the subtype that best represents the software that you want to describe. ConfiguredComponent represents software that is configured to run, such as Java components or customizers. ServiceComponent represents software that acts as a service. ServerComponent represents servers and spawners. LogicalServer represents a grouping of homogeneous servers for the purpose of load balancing or pooling.
Model description of the metadata type: A container of data files (files that contain data) or other Deployed Data Packages. This type has associations with DeployedComponents that can access the package. This type could be a directory, a database catalog or schema or a SAS library. Database schemas and catalogs should be associated with the DBMS that provides access to those packages.
Model description of the metadata type: A group of closely related hierarchies. Hierarchies within a dimension typically represent different groupings of information that pertains to a single concept. For example, a Time dimension might consist of two hierarchies: (1) Year, Month, Date, and (2) Year, Week, Day. See also hierarchy.
Model description of the metadata type: Represents a physical operating system path. Directory objects should not be shared by multiple public objects.
Model description of the metadata type: A Document is a web page or other conent that contains documentation pertinent to the object to which this document is related.
Model description of the metadata type: Extension enables end users and application developers to define additional attributes that are not part of an object's metadata type definition. Use the Extension metadata type to define attributes that store character values.
Model description of the metadata type: A feature is a property that is encapsulated within a Classifier. In the metadata model, a Feature declares a structural or behavioral characteristic of an instance of a Classifier or of the Classifier itself. Feature is an abstract metadata class.
Model description of the metadata type: Usually a measure of the accuracy of a predicted value. Maybe a measure of the accuracy/performance of the model. Used by SAS Enterprise Miner.
Model description of the metadata type: PROC OLAP and OLAP CUBE Studio enable users to define formulas for the dimensions of a cube that result in the creation of calculated members and named sets. In SAS 9.2, the GlobalFormula metadata type was used to store the formula that created the calculated member or named set. In SAS 9.3, it was decided that this modeling was not sufficient to enable the object to refer back to the dimension, hierarchy, or level to which the calculated member or named set belongs. Therefore, the GlobalFormula metadata type was changed to an abstract type, and the CalculatedMember and NamedSet metadata types were introduced. The new metadata types are used in cubes that have a UsageVersion of 5.0 or higher. The CONVERT option of PROC OLAP can be used to change a 4.0 cube to a 5.0 cube. A 4.0 cube is also converted to a 5.0 cube by OLAP CUBE Studio when a shared dimension is added to the 4.0 cube. For more information, see CalculatedMember and NamedSet.
Model description of the metadata type: An arrangement of members of a dimension into levels that are based on parent-child relationships. Members of a hierarchy are arranged from more general to more specific. For example, in a Time dimension, a hierarchy might consist of the members Year, Quarter, Month, and Day. In a Geography dimension, a hierarchy might consist of the members Country, State or Province, and City. More than one hierarchy can be defined for a dimension. Each hierarchy provides a navigational path that enables users to drill down to increasing levels of detail. See also CalculatedMember, Level.
Model description of the metadata type: Represents a level within one and only one hierarchy. A level may participate in multiple heirarchies as represented by the levels association to HierarchyLevel objects. A HierachyLevel object is not deleted when a level is deleted, OLAP will instead collapse the hierarchy if the associated level object is not found.
Model description of the metadata type: A content distribution center. A channel is sort of like a mailing list. A list of subscriber entries is maintined, and new content can be published to that list. It's also a content access point that aggregates published content with a common subject or intended for a common audience.
Model description of the metadata type: A filter string is used to include or exclude content going to a specific subscriber. It can be used to filter entries in a package, or the entire package.
Model description of the metadata type: A subscriber profile is used to control how published content is delivered to a user. Typical delivery mechanisms are mail, message queue or none. None is used by Portal users who will check the channel for new archived packages and view them on demand, rather than having them delivered at publication time.
Model description of the metadata type: The output of a Join is limited to one JoinTable. A Join may have at most two inputs. A Join may not exist without a Select. For nested joins a Join should be documented for each pair of joined tables. For example: Table1 is joined to Table2 that results in JoinTable1. JoinTable1 is then joined with Table3 to create JoinTable2. JoinTable2 now acts as in input into a Select that documents the rows and columns that are to be included in the final output table.
Model description of the metadata type: Represents the relationship between two columns in a foreign key, unique key relationship. For example, if table a has a unique key of columns a1 and a2, and table b has a foreign key, of columns b1 and b2, into table a, there is a keyassociation between the columns that relate to each other, for ex. b1 to a1 and b2 to a2.
Model description of the metadata type: An element of a dimension hierarchy. Levels describe the dimension from the highest (most summarized) level to the lowest (most detailed) level. For example, possible levels for a Geography dimension are Country, Region, State or Province, and City.
Model description of the metadata type: Contains the localized values for a particular locale as defined by the LocalId attribute. Locale information contained in the LocalizedResource is used when displaying information contained in the associated LocalizedObject. The Value attribute contains the localized version of the value for the property specified by the Name attribute.
Model description of the metadata type: This type represents a location that includes a type (is it a street address, or an office number), as well as address information (street, city, country).
Model description of the metadata type: A special dimension that contains summarized numeric data values that are analyzed. Total Sales and Average Revenue are examples of measures. For example, you might drill down within the Clothing hierarchy of the Product dimension to see the value of the Total Sales measure for the Shirts member.
Model description of the metadata type: Represents a SAS Enterprise Data Mining Model that is a formula or algorithm that computes outputs from inputs. A data mining model includes information about the conditional distribution of the target variables, given the input variables.
Model description of the metadata type: Describes the name of the service and how the name is used (as rebind, bind, or lookup). This type is associated to one DeployedComponent that is being named, and to (possibly multiple) DeployedComponents that provide a naming service.
Model description of the metadata type: Beginning in SAS 9.3, represents a named set in dimension of a cube. A NamedSet object can be associated with one or many Hierarchy objects, in addition to the owning Cube.
Model description of the metadata type: An attribute associated with members of a given dimension level. It is a feature of a Dimension, and can associated with a Level, and to a Column through a FeatureMap.
Model description of the metadata type: An abstract type that represents the connection information needed by an open client to access a deployed component.
Model description of the metadata type: A permission represents an action that a user may attempt against a resource in the metadata server. Permission objects are created in pairs within the metadata server. One instance will have its Type attribute set to "GRANT", the other will have Type= "DENY". A Permission object is associated with a resource by defining an access control. The access control relates the Permission object and one or more identities with the resource on which the permission is being applied. Permission objects should not be explicitly created or deleted. Permissions that are enforced by SAS programs are defined for you by the system. Access controls are managed programmatically using the SAS Open Metadata Interface ISecurityAdmin method class, which is documented in the SAS 9.2 Open Metadata Interface: Reference and Usage. The ISecurityAdmin class provides methods for defining and managing direct access controls as well as access control templates.
Model description of the metadata type: Stores an expression that is applied to conditionally grant a user or group access to a resource. The syntax of the expression is not explicitly defined as it varies depending on the resource to which it applies. PermissionCondition objects should not be explicitly created or deleted. PermissionCondition objects are created for you by the authorization tab as appropriate.
Model description of the metadata type: Primary types are the starting point for modeling a public object or component. When used to model public objects, the PublicType= attribute must be set to indicate the type of object. Public objects may be copied, deleted, moved, and secured as a unit and are usually contained in a folder. They must have the PublicType= attribute set. Some public objects may be embedded in other objects; these are cosidered components. A component may be secured apart from the containing object. For example, a column may have security different from the containing table. A component may also be copied, deleted, and secured etc as a unit apart from the containing object. All other types are secondary objects. Secondary objects may not reside in a folder and are contained, directly or indirectly, by a public object or component. Secondary objects may not be shared between two public objects.
Model description of the metadata type: For use by the SAS Prompt Interface. The SAS Prompt Interface allows prompts to be defined as either shared or private. A private prompt is visible and used only by the prompt enabled object and may reference a shared prompt. A shared prompt is a prompt that is publicly visible and may be used by multiple objects. A prompt will be either associated to a single metadata object or, if acting as a shared prompt, a member ofa SAS Folder.
Model description of the metadata type: For use by the SAS Prompt Interface. A prompt group will be either associated to a single metadata object or, if acting as a shared prompt group, a member of the SAS tree.
Model description of the metadata type: Represents a group of properties. The properties that are part of this group are associated using the GroupedProperties association.
Model description of the metadata type: A PropertySet contains a complete set of properties to be used by the OwningObject in a particular context. The properties that are part of this set are associated using the SetProperties association. Additional information regarding the charateristics or context of the PropertySet is modeled using the Properties association. Note that Properties extend the PropertySet and SetProperties are the set of Properties that extend the OwningObject.
Model description of the metadata type: Defines the data type of a property. Beginning with SAS 9.2, PropertyType is no longer a shared resource; instead, it is contained by the Property object that it helps to define. PropertyType is no longer considered to be an owning type. The SQL type of a Property object is now recorded in the SQLType= attribute of the Property object. Use PropertyType when the SQL type is set to other, 1111, or array, 2003 and more detail is needed to describe the type.
Model description of the metadata type: Used to create a template for creating other metadata objects or set of metadata objects that represent a concept. Any metadata type may be associated with a prototype. The prototype includes all possible valid options or properties that may be used to describe the metadata object that is represented by the prototype. The prototype may then be used to drive a UI that will aid an end user in the creation of metadata. The model allows for any metadata type to be considered a prototype, however, there is currently no defined way to specify that the given metadata object is a prototype that does not represent a particular entity. It is recommended that only metadata types that have a role attribute be considered candidates for defining new prototypes. The role attribute is typically used by clients to filter the metadata before displaying to end users.
Model description of the metadata type: This is the super type for types that define properties that are for prototype objects only. These are either AttributeProperty or AssociationProperty objects.
Model description of the metadata type: A SAS Information Delivery Portal user's portal information, which defines the basic functionality of the portal.
Model description of the metadata type: A Web component that is managed by a Web application and that is aggregated with other portlets to form a page within the application. Portlets can process requests from the user and generate dynamic content.
Model description of the metadata type: This abstract type represents types that are used to define the transformations that are performed. These include types that subset, group and order data.
Model description of the metadata type: Represents a relational table, one that does not have a physical representation. If the table resides in a DBMS or file system, it should be represented by a PhysicalTable. If it is a transient table, one that has a physical representation but is temporary, it should be represented as a WorkTable.
Model description of the metadata type: Represents the result of data being transformed into a report. The report has an association to a physical location, such as a SAS catalog entry or file.
Model description of the metadata type: This metadata type associates a responsibility with an identity. Later, this ResponsibleParty object can be associated with one or more resources. A ResponsibleParty object must be created in the same SAS Metadata Repository as the Person or IdentityGroup object of the identity that it describes. New methods have been added to the SAS Open Metadata Interface that create and get ResponsibleParty objects in the appropriate repository, regardless of whether the requesting identity has WriteMetadata permission to that repository or not. For more information, see AddResponsibleParty and GetResponsibleParty in the SAS 9.2 Open Metadata Interface: Reference and Usage.
ResponsibleParty objects
May be associated with only a single identity.
Are considered to be contained by the identity.
Are deleted when the associated identity is deleted.
May not be edited or extended after creation.
May have a SAS supplied or user-defined role.
Have the name of the associated identity.
Inherit security from its associated identity
Do not imply security based roles.
Are stored in the same repository as the identity object by default (Foundation).
Responsibility not Role should be used when options are presented to end-users. Role can imply security roles.
Model description of the metadata type: Represents a SAS file that stores many different kinds of information in smaller units called catalog entries. A single SAS catalog can contain several different types of catalog entries.
Model description of the metadata type: Represents a separate storage unit within a SAS catalog. Each entry has an entry type that identifies its purpose to SAS. Some catalog entries contain system information such as key definitions. Other catalog entries contain application information such as window definitions, help windows, formats, informats, macros, or graphics output.
Model description of the metadata type: Represents a name temporarily assigned to an external file or to an aggregate storage location that identifies it to SAS. The associated ContentLocations (and this should be a single object except for concatenated files) represent the location used by the fileref.
Model description of the metadata type: Represents a SAS library. A SAS library is a collection of one or more SAS files that are recognized by SAS software and that are referenced and stored as a unit. Each file is a member of the library. SAS libraries are accessed with a LIBNAME statement. The LIBNAME statement specifies the data engine and any required or optional parameters for accessing the data source. The SASLibrary metadata type stores the LIBNAME statement arguments necessary to access a particular data source in a metadata repository.
Model description of the metadata type: Represents the storage of SAS passwords for SAS tables or connections. There will be one of these for each type of password associated with a file.
Model description of the metadata type: Secondary types are used along with primary types to help define a public object or component. Secondary objects may not reside in a folder and are contained, directly or indirectly, by a public object or component. Secondary objects may not be shared between two public objects.
Model description of the metadata type: This is an abstract class from which other "SecurityRules" will derive. Security rules are used to tell the authorization facility the rules it should use when making authorization decisions.
Model description of the metadata type: This class is used to group SecurityRules into a unit. The rules in a scheme were generally created together and will most likely need to be deleted together. The SecurityScheme provides the common link needed to facilitate this functionality.
Model description of the metadata type: A SecurityTypeContainmentRule tells the authorization facility how to find parent objects for a particular metadata type. There may be more than one rule for any class.
Model description of the metadata type: The types of services available from a DeployedComponent. Examples of types are DBMS, FileSystem, OperatingSystem.
Model description of the metadata type: Shared dimension is contained by its schema and may be used by more than one cube. The shared dimension will be removed when the olap schema is removed. Security for the dimension is independent of the cubes that use the dimension.
Model description of the metadata type: Used to define an application hierarchy. The application hierarchy contains information sepcific to the application including configuration properties. An application would use the SoftwareComponent that represents the application as a starting place to navigate through the hierarchy that is made of Trees and Groups and their members.
Model description of the metadata type: The SyncStep is used to define a part of workflow. This step does not represent a process step, but instead a point of synchronization to help define complex flow algorithms. Valid roles for this type are: AND, OR, EVENTWAIT, or CASE An AND SyncStep would have multiple PredecessorDependencies that all must occur before the SuccessorDependencies are activated. An OR SyncStep would have multiple PredecessorDependencies. Any one of these would have to occur before the SuccessorDependencies are activated. An EVENTWAIT SyncStep is activated by TriggeringEvents. A CASE SyncStep signals the start of case logic.
Model description of the metadata type: A classifier that defines a set of tables that all share the same characteristics but that should be treated as one classifer for display purposes. It is often not known until the table definition is used how many physical representations will exist for a given definition.
Model description of the metadata type: Represents a variable whose values are known in one or more data sets that are available (in training data, for example) but whose values are unknown in one or more future data sets (in a score data set, for example). Data mining models use data from known variables to predict the values of target variables. Used by SAS Enterprise Miner.
Model description of the metadata type: Type definition is used to describe members of the object type dictionary. A type definition contains information used to describe a public object type. The Notes association will include additional configuration information and a template describing the metadata structure of the public object for objects that are persisted to metadata.
Model description of the metadata type: A representation of the unique and primary keys of a table. It is also associated with the columns in the table that comprise the key.
Model description of the metadata type: Represents a table that is created as part of running SAS code that is not intended to be persisted. Usually, these types of tables are in the WORK library. These are a separate type from PhysicalTable because they have a transient physical existence and are not persisted.