D

data enrichment

MarkLogic’s built-in RDF triple store allows you to enhance your document data with semantic metadata. You can also do Ontology Driven Entity Extraction to make your data more meaningful and discoverable.

data flow management

Two core concepts of a MarkLogic Data Hub are the ingest data flows and curation data flows. When using MarkLogic Data Hub Service, the repositories, tasks, and plugins are readily available to start creating these data flows. The Data Hub empowers Architects and Developers to leverage the power of MarkLogic to create data flows from a multitude of source systems.

data governance

When the data is sourced from many different silos, each with their own notions of data governance, you may use MarkLogic to implement, enforce, and verify policies around data security, sharing, provenance, and, retention. See Data Governance in an Unpredictable World.

data harmonization

Data from different sources should not get discarded. Instead, it gets harmonized so it’s consistently queryable. MarkLogic Data Hub does this by leveraging the flexibility of the document model, which allows for an iterative approach.

data hub

An application that takes in raw data from disparate sources and transforms the data into canonical business entities that can be used by applications without regard to differences in the original source.

database

MarkLogic. MarkLogic databases are made up of one or more forests, and forests are made up of one or more stands. See forest and stand.

database replication

Database. See Replicate.

DBPedia

Semantics. A project aiming to extract structured content from the information created as part of the Wikipedia project. Information in Wikipedia is represented as RDF triples, making it an excellent source of facts as triples.

dc (Dublin Core)

Semantics. A metadata vocabulary containing metadata terms maintained by the Dublin Core Metadata Initiative (DCMI). The current set of the Dublin Core vocabulary includes terms of the Dublin Core Metadata Element Set, along with elements, classes, and DCMI type vocabularies. The Dublin Core vocabulary existed before the Dublin Core Ontology, which is a lightweight Resource Description Framework Schema (RDFS) vocabulary for describing generic metadata.

declarative rewriter

HTTP server. An implementation of a “rewriter”, specified in a declarative syntax (a document) that doesn't require evaluation by a general purpose language. This is an XML document where the implementation is entirely in C++ and requires no evaluation of either XQuery or JavaScript.

deep time

General. The total time spent evaluating an expression, including time spent evaluating any expressions contained within the specific expression. See elapsed time and shallow time.

default graph

Semantics. The default graph is the RDF graph where triples are inserted if you don't specify a named graph. In MarkLogic, the default graph has the IRI here. You can specify a different collection during the load process and load triples into a named graph. See graph.

default partition

Database. A partition with no defined range. Documents that have no partition key, or a partition key value that does not fall into any of the partition ranges, are stored in the default partition.

DH (Data Hub)

MarkLogic. The Data Hub (DH) is a set of tools and libraries that help you build an operational data hub on top of MarkLogic.

directories

Database. Documents are located in directories in a MarkLogic database. Directories are hierarchical in structure (like a filesystem directory structure) and are described by a URI path. Directories are required for WebDAV clients to see documents.

distance

Geospatial. The distance between two geospatial objects refers to the geographical closeness of those geospatial objects.

DLS (Document Library Services)

MarkLogic. Library Services enable you to create and maintain versions of managed documents in MarkLogic Server. See Understanding Library Services in Develop Server-Side Applications.

DN (Distinguished Name)

MarkLogic. A sequence of Relative Distinguished Names (RDNs), which are attributes with associated values expressed by the form attribute=value. Each RDN is separated by a comma in a DN.

d-node

MarkLogic. A MarkLogic data (processing) node. See e-node.

document

MarkLogic. A document is a physical data model in the database. It can be a hierarchy of different types of data organized together, commonly used to represent an entity. Document, triple, and lexicon are examples of physical data models (documents) used to represent entities.

document format

MarkLogic. Refers to how a document is stored in MarkLogic databases; it can be encoded in XML, binary, JSON, or text format.

documents are like rows

Database. When modeling data for MarkLogic, think of documents more like rows than tables. In other words, if you have a thousand items, model them as a thousand separate documents not as a single document holding a thousand child elements.

Of course MarkLogic documents can be more complex than simple relational rows because XML and JSON are more expressive data formats. One document can often describe an entity (a manifest, a legal contract, an email) completely.

domain

Content Processing Framework. A domain defines the scope of documents to process. Domains are used to organize and demarcate different sets content in order to process groups of documents in different ways. See Flexible Replication and Understanding and Using Domains in Content Processing Framework.

DR (Disaster Recovery)

Database. Disaster recovery is the ability to rebuild part or all of your data should something happen to your cluster. See Database Replication for Disaster Recovery in Configure Database Replication. See also High Availability (HA).

dynamic content

MarkLogic. Dynamic content is content generated by your application, such as results returned by XQuery modules.

dynamic host

A real or virtual MarkLogic Server machine with a dynamic host token installed in its marklogic.conf file. You can add dynamic hosts to a cluster as extra e-nodes during spike query traffic and shut them down when unneeded. See Dynamic Hosts. [New in v12.0.0]

dynamic host token

A type of cluster API token that allows dynamic hosts to join the cluster. [New in v12.0.0]