Represents a named address. The address can be in either the standard US format or in a somewhat free format for international addresses. Use the boolean field 'USFormat' to declare whether the address is using the standard US format or not. The country field must follow the convention of the ISO 3-letter country code, which is summarized at http://www.un.org/Depts/unsd/methods/m49alpha.htm.

The US format requires at least one street address to be filled as well as have the city, state, zip code, and country fields filled out. While an international address can still be filled in a US format, a US address (where the country field is 'USA') can not take a non-US format.

The non-US format only requires one street address, city, and the country field. In the non-US free format all the five street fields should be used to fill out most of the address information. Keep in mind, the country and city fields must always be filled out.

The unique id. The user specified name of this address. This field is restricted to 100 characters. Indicates that the address is in a US format (true) or an international format (false). The first street of the address. This field is restricted to 1024 characters. The optional second street. This field is restricted to 1024 characters. The optional third street. This field is restricted to 1024 characters. The optional forth street. This field is restricted to 1024 characters. The optional fifth street. This field is restricted to 1024 characters. The city. This field is restricted to 100 characters. The state. This field is restricted to 100 characters. The zip code. This field is restricted to 20 characters. The 3 letter country code. This field is restricted to 3 characters. Special instructions related to this address as supplied by the user such as "Leave packages with the front desk". This field is restricted to 1024 characters. A condition that is always true or false The name of the condition. The description of the condition. Flag to indicate the type of the condition, either true or false. The preferences selected by a user that ECHO will use in various locations such as ordering. The guid assigned to these preferences. Contact used for shipping items. This preference is normally used when placing an order. Contact used for billing items. This preference is normally used when placing an order. Contact used for general communications with the user in response to some requested action. This preference is normally used when placing an order. The notification level to use when placing an order. This may be set explicitly when placing the order or it will be defaulted to the given preference. This is the only preference that ECHO will automatically use. The other user preferences should be used by a client application when placing an order. Custom properties set by a client application. ECHO does not normally use these internally, but can simply store them for a client application. A client application should honor and preserve the custom properties set by a different client application. Contains all the policies related to ordering from the provider. This information includes the endpoint URI and retry information. Normally a provider establishes the policies to initialize ordering support in ECHO for the provider's data. The provider's server location. This is in the form of a URI. For provider that speak HTTP, this would be a full URL. For providers with a specialized server and protocol, this would be in the format of server:port. Number of times that ECHO will try to connect to the provider if the transmission fails. Amount of time that ECHO will wait before trying to connect. The time is measured in seconds. Indicates the routing mechanism used to contact the provider. The routing mechanism determines if ECHO is using a local order adapter, a remote order adapter, or connecting to the provider directly. The SSL policy for these provider policies. The SSL policies contain all the SSL related information for this provider. This indicates whether or not the provider supports separate order items with the same catalog item in the same order. If this is set to false ECHO will not allow an order to contain more than one order item to have a particular catalog item. The transactions that provider supports. Each supported transaction will be listed in this set. Extra information that will not be used by ECHO but will simply be passed through ECHO to the provider. If the provider is using an adapter, the adapter may make use of this information to contact the real provider endpoint or perform actions on behalf of the provider (such as quoting). Contains all the provider policy information related to establishing an SSL connection to the provider when sending an order for submit, cancel, or quote. A flag to indicate if the certificate has been activated by operations. If false, the certificate has not been activated and should not be used for order transmissions. A flag to indicate if the certificate is enabled. If false, the certificate should not be used for order transmissions, even if the certificate has been activated.

The actual SSL certificate.

The certificate must be encoded according to the standards for privacy-enhanced mail (PEM) as defined in RFC 1421 (http://tools.ietf.org/html/rfc1421) which depends on RFC 934 ( http://www.apps.ietf.org/rfc/rfc934.html). In its printable encoding format, the encoded certificate is bounded at the beginning by

-----BEGIN CERTIFICATE-----[CRLF]

and at the end by

[CRLF]-----END CERTIFICATE-----

where [CRLF] represents the new line character.

The date the ssl certificate was last updated. Describes an entry in the ECHO product catalog such as a collection or granule. The guid of the catalog item. The type of the catalog item. This will be one of collection or granule. The guid of the provider that owns this catalog item. The price of the catalog item if it were to be ordered from the provider. Not all catalog items are orderable. The GUIDs of the assigned Option Definitions to this catalog item. Ordering this catalog item will require an option selection for one of the associated option definitions. Used to describe entries in the ECHO product catalog and any information required for ordering the item. The catalog items that may be ordered. Each catalog item has a list of option definition guids that indicate what the associate option definitions are. A list of option definitions for the catalog items. The option definitions indicate information such as how the item may be ordered. Normally selections must be provided to these definitions when ordering the item from the provider. Represents a classification using a taxonomy entry. The classification type. The taxonomy entry being used to classify. Information about a client application and the user of the application. This information is used for metric information within ECHO and is required by some providers when placing an order. The identifier of the client application. This is used by ECHO and providers to track which client applications are being used to interface with ECHO. The IP address of the user interacting with ECHO. Note that this may be different than the client IP address if the client application is a web application. The user IP address should be the address where the actualuseris making requests from. Contact information for an individual including name, address, phone numbers, and email address. The contact may be named, such as "Manager" or "Billing Specialist". The role is used to aid users in identifying a particular contact. The unique id of the contact. The user supplied role of the contact. This field is restricted to 50 characters. The first name of the person to contact in regards to the address this data type is associated with. This field is restricted to 30 characters. The last name of the person to contact in regards to the address this data type is associated with. This field is restricted to 100 characters. The address information for the contact. Must be supplied in contacts associated with orders. The phone numbers for the contact, including home, business, and fax numbers. At least one phone number must be supplied in contacts associated with orders. The email address of the contact. This field is restricted to 100 characters. The organization name of the contact. This field is restricted to 1024 characters.

A rule in the Echo system that applies to data. A rule applies to a specific set of meta data with specific criteria. A rule contains a condition which is used when applying the rule. A rule can only contain one condition, therefore only one condition type may be specified in a rule.

It is important to note that a list of group guids is part of this data type. The current implementation ignores the guids if the rule type is a RESTRICTION.

The unique id of the rule. The name of the rule as specified by the user. The human readable description of the rule. The type of the rule. Permissions grant access to specific groups while restrictions remove access to all groups. The action that the user may perform that would cause this rule to apply. A boolean condition for this rule. Only one condition type my be specified. A temporal condition for this rule. Only one condition type my be specified. A rolling temporal condition for this rule. Only one condition type my be specified. A restriction flag condition for this rule. Only one condition type my be specified. The comparator to use when applying the condition. Some conditions only support a subset of the comparators. The guids of the groups that this rule applies to if it is of type permission. The type of the data that this rule applies to. This is one of collection or granule. The values that this rule applies to. The values are the dataset ids if the data type is collection or the granule UR if the data type is granule. If the data values are null, then the rule will apply to all collections or granules. Note that an empty array will be treated as a null array. Contains delivery information. set as EMAIL or FTPPUSH in the format of userid@domain.name specified only if the deliveryType is a FTPPUSH specified only if the deliveryType is a FTPPUSH measured in MB(bytes) The error code constant supported by ECHO. The operations message for this error code. This field may not be set if the error code has no ops message. Represents a subscription to an event in ECHO. When the event occurs, the filter will be applied to see if the notification should be delivered to the notify to address. The guid of this event subscription. The user assigned name of the subscription. The URL to post the message indicating that the subscription has ended before the expiration date.

The URI to send all notifications to. This URI takes on different forms depending on the deliver mode.

Ftp Push: An FTP URL in the formatftp://[user ID:password@]<host_name>[:port]/[path_name/][file name]
Email: a standard email address
HTTP Soap: An HTTP URL normally to a web service endpoint implementing the event notification sink WSDL defined interface.

The selected delivery mode for the subscription. Based on the delivery mode, different notify to addressing schemes can be used. The expiration date of the subscription. The filter to apply to all outgoing notifications. The selected filter dialect. Based on the filter dialect, different filterlanguages and structures acan be used. The reference properties provided by the client. These properties will be sent back to the client with each notification. Contains any XML elements. It is important to note that any CDATA sections received in the reference properties will be sent to the client escaped as normal text. Clients should not be made dependent on processing the XML by looking for the CDATA tags. This is normally used when ECHO does not use the data, but simply stores it or passes it to a third party on behalf of a client application. For an example, see the provider policies or user preferences. Contains any single XML element. It is important to note that any CDATA sections received in the reference properties will be sent to the client escaped as normal text. Clients should not be made dependent on processing the XML by looking for the CDATA tags. This is normally used when ECHO does not use the data, but simply stores it or passes it to a third party on behalf of a client application. This data type is used to describe the information contained within a group. The unique id for the group. The user supplied name of the group. The description of the group. The guids of all the managers in the group. The guids of all the users in the group. One parameter to use when invoking an operation. the name of the parameter the value to pass to the operation The results of an invocation. This contains the last status and the results if the invocation is complete. The unique id of the invocation the results returned from the operation invoked the status of the invocation A list of address information A list of metric constraints. A list of order transaction types. Represents any actions to take on the data. used to define the attributes that will be returned set as UNCOMPRESSED or GZIP set as BOTH, COLLECTIONS_ONLY, GRANULES_ONLY, or ALL_COLLECTIONS This represents a way to filter the metadata subscribed to. Any Valid IIMS AQL. If this is a granule query then collection events will be filtered out for this subscription. The opposite applies if this is a collection query. If a provider guid of * is specified in the subscription, the query must use a data center id of 'all'. If a single provider guid is a specified in the subscription, the data center id must be a single 'value' element (not a 'list') which matches the data center id for the provider. Rolling temporal condition which limits the results to any items added to the catalog within the given number of days from the date the subscription is executed. A path into the metadata of a collection or granule. The path includes the item guid and one or more XPaths into the metadata. Standard XPaths into the metadata. The XPath must be valid against the metadata that is normally retrieved for an item. The guid of the item the path applies to. A resolved metadata path. A resolved path includes the item guid and the values that were resolved based on the XPaths given in the original path. The values extracted from the metadata using the previously supplied XPaths. The guid of the item the path applies to. This type represents the info for a metadata subscription request. The unique id of the subscription. The current state of the subscription. This is one of paused, active, or expired. the name of the subscription the provider the subscription references. you may use * to indicate all providers. A provider guid of * can be used in a subscription with a filter query if and only if the query data center id is set to 'all'. If a specific provider guid is specified and a filter query is used, the filter query may only list the single data center id for the provider using a single 'value' element (not a 'list'). the dataset the subscription references. you may use * to indicate all datasets. the narrowing information used to limit the size of the metadata subscribed to any actions to take on the data prior to delivery the delivery information for the subscription when the MetadataSubscription should expire. The subscription is active and will be processed when new data is detected. The subscription is expired and will no longer be process unless it is renewed. The subscription is paused and will not be processed until it is resumed. A metric constraint is some constraint on the count of the metric. This limits the number of events or objects that are counted to produce the metric. This contains the value used in the constraint. See the constraint type documentation for information on what values are used. The type of the constraint. A generic type that represents the count of an event or object in ECHO. The type field indicate what event or object this metric is counting. The number of objects or events that occured. The type of event or object being counted. A list of constraints on the count. If there are no constraints then the count is for all events or objects that occured/existed in ECHO at the time this metric was produced. Represents a report of metrics from one month in ECHO. The month and year this metric report is from. A list of metrics for this metric report. The list of id's of data providers that existed in ECHO when this report was generated. A simple type that contains a name and guid. This type is normally used when listing a large number of items to allow a client application to display the name to the user while using the guids to page through the objects using other services. The human readable name of the item. The value of the name field changes depending on the use of this type, however the name is human readable and a client can depend on being able to present it to the user. The unique id for the item corresponding to the human readable name. The client application can use this field to request the entire object of interest. An assignment of a catalog item option definition to a catalog item collection and its granules. The assignment to granules is determined throught the filter XPath. The unique id assigned by ECHO for this option assignment. The GUID of the option definition to assign to the catalog item. The GUID of the catalog item to assign the option definition to. Only collections may be indicated here. An optional XPath into the granule catalog item metadata that will indicate if the granules in the collection are assigned the option definition. If this is not given then the granules will have the option definition applied to them. Option definitions describe XML using some description language. This allows third parties to define parts of the API on ECHO. Option Selections contain XML that must conform the definition of the form in this. The unique id assigned by ECHO for this option definition. The name of the definition. This must be unique per provider The scope of the definition. Only administrators may add system level definitions and only providers may add provider level definitions.

Indicates if the definition is deprecated. Deprecated definitions will be returned to the client and will be considered valid when validating an order, however new order items cannot be added using the definition and existing order items cannot be updated using the definition.

This flag is ignored when creating an option definition, however it will always be set and returned once the definition has been created in ECHO.

The ECHO Form. Contents must conform to ECHO Forms schema. See the ECHO Forms Specification for more information. Option Selections contain XML that must conform to option definitions. The unique id assigned by ECHO for this The name of the definition. The XML content of the selection. This must conform the XML described by the form in the option definition. This data type is the top-level structure for a user order from one or more providers. An order is comprised of many provider orders. A provider order is a request for data that will be fulfilled by a particular provider. The order type type is used to express global order option selections, order status, pricing as well as possibly necessary shipping, billing, or contact information. The guid of the user who owns this order. This field will be null for orders owned by a guest user. The domain of the user that placed this order. The region the user was located in when they placed the order. The unique ID of an order in the system. This data type is used to categorize the state of an order for products or services. This state is derived from the aggregation of the states of associated provider orders. [STATE]_WITH_EXCEPTIONS indicates that there is an anomaly in the states of the order's associated provider orders For example, PROCESSING_WITH_EXCEPTIONS could indicate that one or more associated provider orders have been rejected or canceled while the remainder of the order has been accepted normally. The date that the order was created in GMT. The date that the order was submitted in GMT. The date that the order was last updated in state or by the provider. Describes the postal address to which an order for data should be delivered. Represents the address to which billing information will be sent. Represents the contact to be used for general inquiries or problems with the order. This data type is used to categorize the user's preference for receiving the updated status of a particular order. The types of email that will received with each level is documented in the service. Unique ID of the client who access ECHO software. This information will also pass over along with the order to the data providers. This information is extracted from the client information provided at login. The total price calculated by summing the provider order prices when the order was accepted by the providers. A request for data from a particular provider. The provider order does not contain information on the particular order line items. That information must be obtained separately. A provider order is automatically added to an order when an item owned by that provider is added to the order. Used to define ordering characteristics for particular catalog item so as to be used within an order. An order item defines both the product to be ordered, and the amount to be ordered. It may also include specifying options associated with and available for that catalog item. Generally, these options are packaging and distribution options. Only the particular options specified for this catalog item are available for setting. To retrieve all the available options for a catalog item (including whether an option is required or not), use the order management service to get the catalog item order information. The unique id of the order item. The guid of the provider order to which this item belongs. The guid of the item being ordered. The state of the order item. This state may change as the order is processed by the provider. The quantity of the item being ordered. The selection for a catalog item option definitions assigned to the item being ordered. This data type is used to express telephone information such as a home, business, or fax number. The unique id of the telephone number. The custom type name of the phone if the phone type is CUSTOM. This field allows a user to specify a type name for the phone that is not a standard type name. Be aware that the type name may not be recognized by clients because it is custom. This field is restricted to 150 characters. The phone number. This field is restricted to 50 characters. The type of the phone number. If none of the standard types meet the needs of the user, a type of CUSTOM can be used and the custom type name can be specified as a string. Price information about an order from a provider. Normally a provider returns price information in response to a quote or submit request from the client. The total price of the order. The price for the actual data. The price for the media used to distribute the data. The fee for shipping the media. The fee for handling and packaging the media. Any discount that was given to the order. The number of media units used to fulfill the order. Any additional information about the price information that the provider needs to relay to the user.

A provider in the ECHO system. A provider can provide data or services. Although a provider is a top level entity and is associated with information, a provider never actually logs into the system. A user can be granted access to a provider role and can then act on behalf of that provider. This allows multiple users to act on behalf of the same provider while maintaining system security.

Acting on behalf of a provider is required when maintaining the provider's assets such as data or services.

The unique id for the provider. The readable provider id. This id is normally unique in ECHO, however it is a name that is negotiated between ECHO operations and the provider. This name may change as the provider's organization or operational goals change. This ID is different from the guid in that the guid is uniquely machine generated and may never change for the lifetime of the provider. The organization name that the provider represents. The type of the provider such as service or data. A data provider can provide data such as collections or granules. A service provider can provide web service items such as advertisements, implementations, interfaces, and guis. A provider may be both a service and data provider. Identifies a provider web site so users can find more information about the provider or obtain direct access to data or services. A description of the type of data holdings the provider maintains. This field may not contain data for service providers. A description of the type of service holdings the provider maintains. This field may not contain data for data providers. Any additional information about the provider that is relevant. Contacts for the provider such as the primary maintainer or the data access center. A description of a data set owned by a data provider. The dataset ID of a collection owned by a provider. The ECHO collection GUID of a collection owned by a provider. The number of granules in the collection. Represents a request for products and services from a particular provider. A provider order is contained within a larger order. ECHO automatically maintains creating and removing provider orders when items are added and removed from an order. The provider orders will be delivered to providers when the order is quoted or submitted. The unique ID of a provider order in the system. The provider specified tracking id used to track the order when it is being processed. The state of the provider order. The date that the provider order was closed in GMT. The quoted price information for the provider order. This field will only be valid after a quote is requested and the provider has supplied the information. The submitted price information for the provider order. This field will only be valid after a submit is requested and the provider has supplied the information. The authentication key selected by the user to be used when the order is submitted to the provider. Some providers require that an order have an authentication key before being submitted. All of the status messages supplied by the provider as the order is being processed. The unique ID of a provider order in the system. It's an aggregate of the provider's guid and the order guid from the order which the provider order belongs. The provider guid that the items in the order belong to. The guid of the order to which this provider order belongs. Used to express the quoted price for an order from a provider. The price information for the items in the quoted order. The date that this quote expires. After this date, the provider may change the prices originally provided. The recommended media for the order based on the provider's calculations. This data type represents information about a provider order when the provider accept the user's submitted order. The last date that the order may be cancelled. A provider cannot promise to cancel an order if the cancel request is received after this date. The date that the order is estimated to ship from the provider if a physical media type is required in the order. This field may not be set if the provider does not support estimating a ship date. The date that the provider accepted the order in GMT. The price information for the final order as calculated by the provider. Contains the results of executing a query on the ECHO catalog. The contents of this type will depend upon the Result Type specified in the Query Request. The result type that was requested in the original query. The inline results if they are appropriate for the given result type. The inline item guids if they are appropriate for the given result type. The inline result information from executing a query on the ECHO catalog. The unique id of the result set. This ID is only valid if the result type is one that stores results on the server. The inline return data. This field is only valid if the result type is one that returns data. The current position of the cursor in the overall result set. The cursor can be thought of as a pointer to some row in the result set. The total number of hits in the result set. The status of the query. This field is only useful if the query is executing asynchronously. Indicates if the cursor is at the end of the available results. If true, there is currently no more data available in the result set. If false, another request can be made to access more data. Note that if the query is asynchronous, this flag may be true but more data could be added to the result set at a later time. The number of hits in the result set. The size of the result set in number of items If this is true it indicates the size is estimated. A data rule condition based on a restriction flag in the data. The name of the condition. The description of the condition. The lower value of the restricted field. This data type is used to represent the access level that a user in the system may have. Currently users can have either provider roles or administrator roles The type of the role, either provider or admin. The name of the role. For a provider role, this is the provider guid. For an admin role, this field is not used. The unique id of the role. A data rule condition that is based on time. The time is a rolling time expressed as a duration. The name of the condition. The description of the condition.

The duration of the rolling time in milliseconds. The conversion used for v8 is only accurate to hours. Any seconds or millisecond remainder will be truncated. In v9 the accuracy will be preserved.

The XML Schema type duration was not used because of a lack of support in major languages and tools. In the future, this field may be converted to an XSD duration.

The time field of the data that should be used when performing the comparison with this condition. Contains all the information about a query that was previously saved. A saved query may be executed at a later time using the catalog service. The user specified name of the query. The unique id of the query. The AQL query that was previously saved. Contains the information behind a token in ECHO. The token string used by the user and client. The guid of the user assigned this token The guid of the user the user is acting as. Only ECHO Administrators are allowed to act as another user The guid of the provider the user is acting on behalf of. Only ECHO Administrators and those users that are specifically granted Provider role for a particular provider are allowed to act on behalf of a Provider Date that this token was created Date that this token expires. Null indicates that this token never expires Whether this token is for a guest (true) or a registered user (false) Date that this token was revoked. Null indicates token in not revoked This is a string annotation to a status state. It is similar to a log message. the actual string annotation the date the string annotation was added This represents one state of a transaction. It holds the state and string annotations to that state. Guid of the transaction this status entry is for a state entered on the transaction A list of string annotations to this state. The date the transaction entered this state A taxonomy can be used to classify web service objects. A taxonomy contains a tree of taxonomy entries which are name value pairs. The value of any taxonomy entry must be unique within the taxonomy. name of the taxonomy Universally unique id for the taxonomy. Unlike other guids in ECHO, this UUID must be specified by the user. Overview url for the taxonomy. This is the url that a user may use to find more information about the taxonomy. The description of the taxonomy A name value pair in a taxonomy that represents one classification within the taxonomy. The name of the taxonomy entry. unique value for this taxonomy entry. The value must be unique within the owning taxonomy. universally unique id for the taxonomy which this entry belongs to A data rule condition that is based on a start and end time. The name of the condition. The description of the condition. The start time that the date must be after. This only has a precision of seconds. The stop time that the date must be before. This only has a precision of seconds. The time field of the data that should be used when performing the comparison with this condition. Provides a set of attribute name and value type pairs. The name of the metadata attribute. The primitive type of the value of the metadata attribute. A registered user in ECHO. A user is the most common actor in the ECHO system. A user has general information such as addresses and phone numbers as well as access levels called roles. After being granted provider roles, a user can act on behalf of a provider to manage data or services. A user can also execute queries and place orders. A user is used to enforce basic security within ECHO. The unique id of the user in ECHO. The domain of user this is. The region the user is located in. The user name of the user. This is sometimes referred to as the user ID. This field is selected by the user when the account is created. The user's first name. The user's last name. The email address of the user. Indicates if user wants to be notified of changes within ECHO or not. Name of the organization the user is a part of. The addresses to be used when communicating with the user. Addresses are optional. A null list will be treated as an empty list. An empty list will always be returned if there are no addresses. The phone numbers associated with the user. A phone number may be a home, business, or fax number. Phone numbers are optional. An null list will be treated as an empty list. An empty list will always be returned if there are no phones. The roles the user has been granted. The roles currently include one or more provider roles and an admin role. An empty list will be returned if there are no roles. A user authenticator is used to define credentials for users when they submit an order to a provider. The provider defines authenticator option definitions and a user provides selections for the authenticators. An authenticator can then be attached to a provider order at a later time. The unique id of the authenticator. The user specified name of the authenticator. The guid of the provider to which this is an authenticator for. The option selection that is a valid selection on the authenticator definition created by the provider. The guid of the user who owns the authenticator. Indicates the visibility flag setting (visible or not visible) for a set of datasets. The visibility flag of the datasets. This is one of open or restricted. The ids of the datasets that this flag applies to. This is an advertisement for a service that may be available through the web. Unique identifier for this web service Guid of the provider who owns this Name of the web service Url where this service can be accessed Description of this web service The taxonomy values that this web service is classified by This represents a user interface to a web service. It can represent user interfaces to web service implementations and interfaces registered in ECHO. Unique identifier for this web service Guid of the provider who owns this Name of the web service Url where this GUI can be accessed Description of this web service Service guids of the associated interfaces registered in ECHO Service guids of the associated implementations registered in ECHO The taxonomy values that this web service is classified by This represents an executable web service with an available endpoint. Unique identifier for this web service Guid of the provider who owns this Name of the web service. Taken from the service element in the WSDL. Url of the WSDL Description of this web service. This comes from the documentation of the service element in the WSDL file. Guids of the interfaces in ECHO that this implementation implements. This is determined by the interfaces in the WSDL file that the implementation imports. The taxonomy values that this web service is classified by Represents an interface to a web service. Unique identifier for this web service Guid of the provider who owns this Name of the web service Url of the WSDL Description of this web service The taxonomy values that this web service is classified by This represents an operation on a web service. Note that this only represents operations that take simple types as parameters and return only zero or one simple type. The name of the operation The namespace the operation belongs to. The operation description The return type of the operation. The names and types of the parameters to the operation The soap action to call the operation. This represents a simple type parameter to a web service operation. The name of the parameter. The parameter simple type. This contains a list of web service interfaces, implementation, GUIs, and advertisements. The list of implementations The list of interfaces The list of GUIs The list of advertisements This data type provides an enumeration of the types of action that can be taken on metadata. Viewing the metadata through a simple get operation. Ordering the data using the ordering API. This enumeration is used to identify the type of a catalog item. A collection of granules. This is also referred to as a dataset. A granule or a single unit of data. An enumerated type for the different types of classifications. This means the classification was inherited from an associated object. This means the classification was applied by ECHO. This means the classification was explicitly applied by the provider. This data type provides an enumeration of all the different methods of comparison within the Echo system. The left operand is less than the right operand. The left operand is less than or equal to the right operand. The left operand is greater than the right operand. The left operand is greater than or equal to the right operand. The left operand equals the right operand. The left operand does not equal the right operand. The possible usage types for a complex option definition. The selection for the definition may contain any number of children or fields. The selection for the definition may contain only a single child or field. A list of supported compression types. No compression. Standard g-zip compression. Possible data delivery types. An email attachment. Pushed to an FTP server directory. Possible filter dialects used in subscription filters. The dialect indicates the type of filter. ECHO will apply the filter based on the dialect indicated in the subscription.

The filter must be an XPath that must match in order for the notification to be delivered. The XPath will be executed on the event notification XML that is about to be delivered to the subscriber. The event notification XML is defined by the Event Notification schema.

The XPath context will be setup such that the context node is the root node of the document. Also, theeventv9namespace alias will be mapped tohttp://echo.nasa.gov/v9/eventnotification/events.

The XPath will be evaluated in aboolean()XPath function to determine if the XPath matches.

The filter must be one or more topics that must match for the notification to be delivered. The topics may be space separated to indicate anorrelationship. If multiple topics are specified in this way, if any of them match, the notification will be delivered.

The known topics are:

extendedservices: notification relates to extended services such as update, remove, or create web services
catalog: notification relates to the ECHO catalog such as update, remove, or create catalog items.
provider: notification relates to the ECHO providers such as update, remove, or create providers.
eventnotification: notification relates to event notifications
eventnotification.subscription: notification relates to a specific event notification subscription
eventnotification.subscription.end: notification relates to a specific event notification ending

Possible delivery modes for notification of events. Used to categorize the user's preference for receiving the updated status of a particular operation. In most cases this is only a preference and the user can always come back to ECHO and check the status of the operation through the specific service. The system will email all state changes and status message updates to the user. The system will email the user when only state changes are made. The system will email the user when the operation reaches a final state. The system will email the user when the operation has failed or is rejected. The system will not send the user email and the user will have to come back to ECHO and use operations on the specific service to obtain status information. This defines the possible states that an order item can be in while the order is being processed. Note that not all providers support individual order line item states and may only be able to update the provider order state. No state has been specified for this order item. The order item is being processed by the provider. The order item was cancelled from the order at the provider's request. The order item has been processed and is now closed. This defines the different states an order can be in. The order has not yet been validated to ensure that all the information in the order is correct. The order has been validated and all the information in the order is correct. It is important to note that although an order may be in the validated state, if a provider modifies the underlying data being ordered, an order may no longer be valid. The order has been sent to the provider for quoting and the provider has not yet responded. The order was sent to the provider for a quote and the provider has delivered the quote. The order was sent to the provider for a quote and the provider has delivered the quote however some part of the order could not be quoted. This is most likely because one of the providers in the order does not support quoting. The order was submitted to the provider and the provider has not yet accepted the order. The order was submitted to the providers and only some of the providers have accepted the order. The order has been accepted by all providers and it is being filled. The order has been accepted by all providers however one or more providers has found a problem with the order. A cancel request has been sent to the provider but the provider has not accepted the request yet. The provider has accepted a cancel request or the provider has cancelled the order directly. The order has been filled and is now complete. The order has been filled and is now complete however one or more of the providers encountered problems completing the order. This defines the different scopes for an option definition. This indicates the scope of the option definition is at the level of the provider who created it. This indicates the option definition is a global definition Order transactions that data providers may optionally support. Indicates that the provider is using the WSDL for order fulfillment defined in versions before ECHO V9. When this routing type is used, the endpoint specified in the provider policies should be the endpoint of the service implementing this WSDL. In the case of a provider using an ECHO supported order adapter this would be the endpoint of the order adapter. SSL is not supported through this routing type. Indicates that the provider is implementing the version 9 order fulfillment interface. ECHO will make a connection directly to the endpoint specified in the provider policies and transmit the data. If SSL is enabled, an SSL connection to the provider will be used. Order transactions that data providers may optionally support. Indicates that the provider supports quote requests and will return a valid quote for an order. Indicates that the provider supports submit requests and will fulfill any submitted orders. Indicates that the provider supports cancel requests and will cancel any orders being processed if possible. The types of phone numbers. It is possible to use a custom type with a phone number, however by using one of the standard types there is a better chance that client applications will be able to process and make use of the phone numbers. The first or primary business phone number. The second business phone number. The business fax number. The first or primary home phone number. The second home phone number. The home fax number. The mobile or cell phone number. The pager phone number. Indicates a custom phone number that does not fall into one of the other phone types. The user should specify the name of the custom phone type when using this value. An enumeration of primitive types. A string date in ISO date format. This should be of the format "yyyy-MM-dd HH:mm:ss"
y = year
M = month
d = day
H = hour
m = minute This data type is used to categorize the state of a provider order. The order has not yet been validated to ensure that all the information in the order is correct. The order has been validated and all the information in the order is correct. It is important to note that although an order may be in the validated state, if a provider modifies the underlying data being ordered, an order may no longer be valid. The order has been sent to the provider for quoting and the provider has not yet responded. The order was sent to the provider for a quote and the provider has delivered the quote. The provider was unable to process the quote request or the provider could not be contacted. The provider rejected the quote request. The order was submitted to the provider and the provider has not yet accepted the order. The provider was unable to process the submit request or the provider could not be contacted. The provider rejected the submit request. The order has been accepted by the provider and it is being filled. A cancel request has been sent to the provider but the provider has not accepted the request yet. The provider has accepted a cancel request or the provider has cancelled the order directly. The order has been filled and is now complete. An enumeration that is used to identify the type of items the provider offers. A provider is normally a single type of provider, however they may support multiple types. The provider offers web services such as interfaces, implementations, advertisements, or GUIs. The provider offers data such as collections and granules. This type is currently unused. Possible query status for an asynchronous query. Because an asynchronous query runs in the background, the status can be used to monitor the progress of the query. The query completed successfully and there are results available. The query is being processed. The query is queued for future execution when the system is ready to handle it. The query encountered an error. The query failed to execute properly. The query is executing but it is being cancelled as soon as possible. The query was cancelled and is no longer running. Indicates the mutability and usage of a simple option definition. The read/write rule can be used to hide data from users or to send only information data to clients in option definitions. The option value is constant and cannot be changed. FIXED option definitions are sent to the client and to the provider when used as catalog item order options. A client should not provide a selection for a FIXED option. The value of the FIXED option will be expressed in the default values. The option value is constant and cannot be changed. OBSCURED option definitions are sent only to the provider when used as catalog item order options. A client should not provide a selection for an OBSCURED option. The value of the OBSCURED option will be expressed in the default values. The option value is constant and cannot be changed. INFO_ONLY option definitions are sent only to the client. A client should not provide a selection for an INFO_ONLY option. The value of the INFO_ONLY option will be expressed in the default values. The option value is mutable and can be changed. MUTABLE option definitions are sent to the client and to the provider when used as catalog item order options. A client should provide a selection for a MUTABLE option based on the multiplicity values of the definition. The desired result type of a query execution. The result type can be used to limit the amount of data returned or to tell ECHO to store the data on the server for future use. Returns the result set guid of the results that are stored on the server. The results are not returned and must be retrieved with separate calls to get query results using the Catalog operations. Returns the number of hits (matches) to the query and a result set guid for the results stored on the server. Returns the detailed metadata for items that match the query directly in the response. Returns the catalog item guids which match the specified query. Returns the number of hits (matches) to the query. Returns the result set guid immediately. This result set guid can be used to check the status of the query as it executes in the background. Once the query is started, the results can be presented and viewed in partial form. Enumeration of the possible metric types. Indicates metric is count of orders submitted. Indicates metric is count of average number of order submitted. Indicates metric is count of distinct granules ordered. Indicates metric is count of distinct collections ordered. Indicates metric is count of registered users that exist in ECHO. Indicates metric is count of registered users who ordered. Indicates metric is count of registered users who searched. Indicates metric is count of searches performed Indicates metric is count of average searches performed. Indicates metric is count of subscriptions that exist. Enumeration of the possible metric constraint types. The types will be documented to indicate what they represent and what the value of the constraint will be. Constrained by the type of user. The value of the contraint will be "Registered User" or "Guest". Constrained by the User who did the thing being metric'd. Value of the contraint will be the user id. The client that the User was using when the action was performed. Value will be the name of the client. The domain of the user who did the action. Value will be one of the values of the UserDomain type. The region of the user who did the action. Value will be one of the values of the UserRegion type. The hour of the day that the actions occured in. Value will be 0 - 23. The provider the action was executed in the context of. Value will be the provider id. The dataset the action was executed in the context of. Value will the Dataset Id or a search string the user gave for dataset id. The datacenter the action was executed in the context of. Value will be the Datacenter Id or a search string the user gave for datacenter id. Indicates if a search metric is counting browse only searches. Value will not be set. Indicates if a search metric is counting online only searches. Value will not be set. Indicates if a search metric is counting spatial searches. Value will not be set. Indicates if a search metric is counting temporal searches. Value will not be set. Indicates if a search metric is counting searches using the day night flag. Value will not be set. Used to categorize the types of roles a user in the system may have. An admin role gives the user access to all administrator functionality. A provider role allows the user to act on behalf of a provider. The provider guid is specified as the name of the role. Indicates the type of data rule. The type of the rule affects how it will be applied. A restriction hides data from all users in the system if the data matches the rule. A permission grants access to the data to a set of users in a group if the data matches the condition. These are the different domains of users. Government agencies and the military. School levels K through 12 (high school). Colleges and universities. Non-governmental corporations. Any other type of domain not available in the standard list. Indicates that the domain is not specified. This type is used as a default in ECHO for orders as well as to support legacy users who have not set a specific domain. This value is normally not supported for operations that require a domain to be set. This represents the region a user is located in. The United States of America. Any country other than the United States of America. Indicates that the region is not specified. This type is used as a default in ECHO for orders as well as to support legacy users who have not set a specific region. This value is normally not supported for operations that require a region to be set. Indicates when a metadata subscription should be processed. The subscription will be processed whenever collections change. The subscription will be processed whenever granules change. The subscription will be processed whenever any collections change. The subscription will be processed whenever collections or granules change. A data rule condition that is based on a start and end time. The start time that the date must be after. This only has a precision of seconds. The stop time that the date must be before. This only has a precision of seconds. The time field of the data that should be used when performing the comparison with this condition. Enumeration of the possible fields that can be used when doing a temporal comparison with a collection or granule. This is most commonly used with data rule conditions that are based on time. The date the item was produced. The date the item was acquired. The date that the item was added to the ECHO catalog. The date that the item was last updated in the ECHO catalog. Used to allow providers to indicate how they wish to update the provider order state when processing an order. Indicates that the provider does not wish to update the provider order state. ECHO will therefore automatically maintain the provider order state. Indicates that the provider wishes to manually update the provider order state. ECHO will not modify the state and will depend on the provider to notify ECHO when the state should be changed. Enumerated type of the different virtual taxonomy types. A virtual taxonomy is one for which there are not stored explicit taxonomy entries. A virtual taxonomy is constructed on the fly from some other data source. The virtual taxonomy type for the primary input type. The taxonomy will be constructed by using the providers and all the datasets owned by the providers. Indicates the visibility of data in ECHO. The provider can maintain the visibility flag on all collections in ECHO to ensure that only public data is viewable. Visibility flags are used in combination with data rules to restrict or permit access to data. The collection(s) or granule(s) will be searchable, viewable, browsable, and orderable by all the users before the ACL examination. The collection(s) or granule(s) will be only searchable, viewable, browsable, and orderable by the user who acting on behalf of the provider who owns the data. For others, a data with restricted visibility can only be searched but not viewable, browsable, and orderable.