Meta-metadata

Context refers to additional data or information that show how the record is related to its application as well as to other records or systems. Context is often described by metadata (i.e., data about data) or meta-information (i.e., information about information). 

This can be accomplished by allowing the user to define which metadata he wants to be represented in the file tree view. From a technical point of view, metadata are constructed with a meta-key that represents the name or category of the data and a value. By changing the metakey structure in his current session, each user would be able to see (1) only the documents he is interested in and (2) the files categorized in an appropriate sequence. Figure 8.4 shows an example of different metadata structures displayed for different users. 

Let us consider an example of an investigation of metabolic pathways with animal species. We would organize our tree view with the default meta-key Species for each metabolite structure uploaded to the workspace. Let us assume that the metabolite structure has not yet been confirmed. If we drag a structure file from the Mouse folder and drop it into the Rat folder, the system would ask us whether we want to keep the previously assigned metadata Mouse or not. Now we have three possibilities ... 

Metadata are most easily provided in pick lists that appear as dropdown menns in the nser interface. New files in the system wonld typically receive mnltiple metadata. To stay with the previous example, each new metabolite would receive metadata for Species, Matrix, Tissue, and so forth. There are certain cases in which previously selected metadata (primary metadata) may affect the number of entries in a pick list of other metadata (secondary metadata). Selecting the primary metadata would then lead to exclusion of several nonapplicable secondary metadata or exclusion of an entire meta-key. 

Another feature that becomes important for metadata management is metadata grouping. As an example, a blood sample is taken from a mouse and a new metabolite found. We can assign the metadata Mouse, Whole Blood, and In Vivo to this metabolite. We now do a second investigation where we unfortunately have to kill the mouse, take a brain sample, and find the same metabolite. We would now assign Mouse, Brain, and In Vitro to this structure. If we would look now at the metabolite metadata, it would list the meta-keys and its values ... 

Meta-Value refers to the value of metadata and is kept together with the meta-key. 

Coma++ is available for free for research purposes, and hundreds of institutes worldwide have used and evaluated the prototype. Surprisingly, the default match workflow of Coma++ (combining four metadata-based matchers) proved to be competitive in many diverse areas, particularly for matching XML schemas (Algergawy et al. 2009), web directories (Avesani et al. 2005), or even meta-models derived from UML (Kappel et al. 2007). Coma- — - successfully participated in the ontology matching contest OAEI 2006. 

FIGURE 7.1 Menu pages in the Acrobat 8 Professional program, relating to document information and meta-data for (a) a typical journal reprint, with (b) the standard metadata schemas and (c) the advanced menu, where additional, more chemically relevant, metadata schemas can be added. The values, or more accurately, the absence of values for the various fields are typical for most Web-resident PDF files. 

Mental assumptions, for effective performance management, 998-999 Mental models, 999-1000, 1210 Mentoring, 857-858, 860, 938 MESs, see Manufacturing execution systems Message-integrity protocols, 733, 734 Metabolic energy requirement, 1118-1119 Meta class level of abstraction, 281, 283 Metadata, 84... 

The concept of metamodel, an abstract language for describing different types of models and data, has contributed significantly to some of the core principles of the emerging MDA. The Meta Object Facility (MOF), an adopted OMG standard, (latest revision MOF 2.0) provides a metadata management framework, and a set of metadata services to enable the development and interoperability of model and metadata driven systems (MOF, 2006). 

The meta- or descriptive data are an essential part of the seismic data as without these the data is not complete. Data are identified by a so-called SCNL code (giving stations, component, network, and location) and the timing of the data. The station code represents the locality of the seismic station, the component code reflects the instrumentation, the seismic network code identifies the operator of the station, and the location code allows distinguishing between two instruments of the same type at one station. The metadata associated to the data streams will include information such as the location of the station (latitude, longitude, elevation), the orientation of the sensors (azimuth and dip), the sample rate, and the instmment response. 

---