Tools Keywords

Tools listed on the Metadata Tools section of the MMI site are categorized using a set of terms established by the DIVE team. This list of terms is currently being developed. What follows is three distinct sets of keywords that are used to completely characterize metadata tools.

Maturity Levels :: Functions :: Types

Definition of Maturity Levels

    1. Missing: The stage of maturity of the item cannot be determined
    2. Emerging: The item is actively being developed (for example, in draft, under community review, discussed on mailing lists or forums, mentioned in abstracts), but has not been formally released
    3. Existing: The item is available for public use, has been released or widely adopted, and is sponsored or maintained
    4. Engaging: The item is available for public use, has been released or widely adopted, has undergone and is currently undergoing updates, based on community input
    5. Declining: The item has less use, and is either no longer maintained on a regular basis, or is routinely superceded by another emerging or existing standard in the community

      Definition of Functions / Behaviours

        1. Acquire / Obtain: To obtain information external to a system (for example, to import a piece of metadata)
        2. Aggregate: To collect a set of objects or metadata, and present as a cohesive resource
        3. Archive: To place into a long-term storage solution
        4. Automate: To replace or enhance a specific activity with machine-driven routines
        5. Browse: To inspect or survey a collection of objects
        6. Compare / Inspect: To estimate, measure, or note the similarity or dissimilarity between multiple objects
        7. Connect: To bring together to provide access, integration and/or communication
        8. Convert: To transition an object from one system (for example, vocabularies, structure, standards) into another (replicates original system into a new system)
        9. Create: To bring an object (for example, metadata instance, vocabulary) into existence
        10. Crosswalk: To map metadata elements between different metadata standards (maintains original and mapped elements)
        11. Design / Architect: To purpose, plan or decide upon the look and function of a system (for example, metadata template, user interface)
        12. Discover: To use metadata values or vocabularies to identify metadata or data sets
        13. Display: To show information
        14. Document: To furnish with information that assists in implementation or use
        15. Edit: To change information (replaces original information with new information)
        16. Extract / Harvest: To take by selection - to derive from a body of information
        17. Format: To arrange or put into a specific structure and/or syntax
        18. Georeference: To associate an object with a specific location
        19. Harmonize: To represent two different vocabulary files in the same language (for example, OWL), so that further mappings or mergings can be accomplished
        20. Integrate: To combine multiple systems so they become one whole to the user community (the design of the original systems will probably be modified)
        21. Interoperate: To enable the exchange and use of information between multiple systems (the design of the original systems may or may not be modified)
        22. Map: To transition one system (for example, vocabularies, structure, standards) into another (maintains original system, along with mapped system)
        23. Measure / Observe: To record a value, remark, statement or comment based on something seen or noticed
        24. Mediate (Semantically): To intervene between the semantics of two systems (the two systems remain unchanged, and an intermediate transition is created/maintained)
        25. Merge: To combine two digital files (for example, metadata, data, or ontology) into a single coherent file
        26. Model: To display information in a relational way (for example, display relationships between vocabularies, individual concepts)
        27. Parse: To split a file or other input into bits of data that can be easily stored or manipulated
        28. Publish: To prepare and present metadata for use by other individuals and systems
        29. Query: To make a request of a computer system, for the purpose of information retrieval
        30. Reason / Infer: To form conclusions by associating available information (for example, to examine information in one or more ontologies and deduce classifications that are not explicitly stated)
        31. Register: To submit information (for example, metadata descriptions of data or services, vocabularies, or terms) to a centrally managed repository
        32. Report: To present single or aggregated instances of information, often in a specific or agreed format
        33. Share: To expose information for acquisition or use in external systems
        34. Store: To put information into a specific location (for example, for digital information, computer memory, database records, or off-line media)
        35. Transform: To create an instance of metadata in a prescribed format, based on an existing metadata instance (maintains original instance, along with the newly formatted instance), or to convert vocabulary files into an ontology representation language, such as RDF or OWL
        36. Validate: To authenticate that mandated characteristics have been satisfied; to test against a specification;
          for example, show through software or other audit that a metadata instance conforms to the applicable standard(s)
        37. Verify: To ensure that the desired requirements have been documented in systems development
        38. Visualize: To create a graphical representation of information (for example, metadata, vocabularies, or data)

          Definition of Tool Interaction Models

            1. Binary: An executable file written in a computer programming language that causes a computer to perform indicated tasks according to encoded instructions
            2. Database: A structured collection of metadata or data that is stored in a computer system
            3. Development Environment: Interactive computer-based system
              intended to help developers and decision makers utilize available
              resources (for example, data and models) to identify and solve problems
              and make decisions.
            4. Framework: A re-usable design for a system (or subsystem); may
              include support programs, code libraries, a scripting language, or
              other software to help develop and glue together the different
              components of a software project
            5. Graphical User Interface (GUI): The visual interface of any application
            6. Interpreted Code: An executable file written for a specific system that causes a computer to perform indicated tasks according to encoded instructions.
            7. Middleware: Software that functions at an intermediate layer
              between applications and operating system or database management
              system, or between client and server
            8. Network-Enabled Application: An application that is installed on one system, but utilizes network technology to perform its functionality.
            9. Source Code: Any sequence of statements or declarations written in some human-readable computer programming language.  The source code can be converted to some kind of computer-executable form.
            10. Standalone Application: An application that does not need the services of other networks once it is running
            11. Web Service: A software system designed to support interoperable machine-to-machine interaction over a network. Web services are frequently just application program interfaces that can be accessed over a network, and executed on a remote system hosting the requested services.
            12. Web-Based Tool: An application that is run within a web environment, and requires access to the internet