An extent is a collection of objects in a self-contained container. Within the DatenMeister, this is a file, a database, or a dynamic object collection, each of which has been loaded via a configuration (LoaderConfig).
Resolving Objects
Each UriExtent has one or more addresses through which it can be found.
Elements can be retrieved via an ID.
The UriExtent supports the following query scheme:
| Type | Description |
|---|---|
Query by ID |
The URI of the extent is appended with an '#' and the object ID. The text following this identifies the object by ID.
|
Query by Name |
The URI of the extent is appended with '?fn=' and the full name of the object.
|
Query a Property |
After the element has been identified via one of the above methods, a property of the object can be selected via the QueryString parameter 'prop'. The content of the property is returned.
|
Query a Data View |
After a reflective collection (reflectiveCollection) has been selected via one of the above schemes, it can be modified via a data view. The collection is passed to this data view as an 'input' node. Note: The URL of the data view must be URL-encoded.
|
Composites |
By specifying the parameter &composites=, it can be indicated whether the containing elements should also be returned. There are various values:
Example: dm:///database/&composites=onlyComposites |
Filter by Metaclass |
A metaclass can be filtered here.
Note: The parameter in curly braces must be URL-encoded and is only not encoded here for clear presentation. |