Promenade: An Internet Database Server for a Virtual Botanical Image Library

Both object-oriented and relational database management systems are referred to as DBMS. The web-scale is expanding at an incredible rate, and with it comes an increase in mobile applications, technologies, and social media platforms. The rapid growth of these technologies produces a variety of structured and unstructured data in various forms, each of which has various consequences for data security. Using RDBMS and OODBMS, this study's methodology outlines the development, installation, and management process of multiple and complicated data sets. This study gives a documented study comparing different kinds of data stored in databases by employing two types of database techniques: relational database method and object-oriented database technique. We use a different fingerprint database for the web and mobile devices. This database is also managed using different technologies, such as MySQL, and it accommodates data generated using distinct methods. In addition, this study explores the benefits and advantages of the various databases and determines the ideal database management system for organizations. According to the survey's findings, RDBMS stores data and the relationships between them in tables, but OODBMS stores data in objects, in a manner analogous to Object-Oriented Programming (OOP). According to the study's findings, the primary distinction between relational database management systems (RDBMS) and object-oriented database management systems (OODBMS) is that RDBMS is a Database Management System based on the relational model. In contrast, OODBMS is a Database Management System that facilitates creating and modeling data as objects.

We present a strategy for the validation of an Object Oriented Database Management System (ODBMS), an off-the-shelf component software, when we deliberately introduced faults and observe its behavior in the presence of these faults. A tool designed for the injection of faults in OO applications, specially Java language systems, was used. This Software Fault Injection tool, Jaca, was developed at UNICAMP and has the ability to inject faults in objects’ attributes and methods. For the experiments we used an ODBMS performance test benchmark, Wisconsin OO7. The experiments were aimed at validating the robustness of the ODBMS component in the presence of errors originated at the application. For that purpose a fault injection strategy was proposed to help answer the questions: Where to inject? What error model to use? This strategy was applied, so some results and their analysis are presented. Improvement for Jaca were addressed as a experiments’ result.

Results and observations gathered while implementing the ANSI T1M1.5 GNM-T1.214 standard within an object-oriented database management system (ODBMS) framework are discussed. The generic network model (GNM) proposes a dynamic network modeling methodology that encompasses a wide spectrum of managed telecommunication network resources. Within the GNM, managed telecommunication resources are modeled from building blocks of lower-level resource elements (logical or physical). The complex relationships between GNM resource elements are described either by specialization/generalization or user/containment; therefore, an ODBMS is well suited for implementation of the GNM as compared to conventional database management systems. The ODBMS framework described also allows the database model to evolve with the GNM. It is demonstrated that a proposed refinement of the GNM into subclasses results in a functional database design that can model a large variety of network resources in accord with a standardized network view. >

As information systems and, more specifically, database management systems, attempt to model particular application environments, they must be able to account for and keep track of how the entities in the environments relate to each other. In the first or navigational generation of DBMS, relationships were maintained by pointer chains that connected the records representing the related entities. In the second or relational generation of DBMS, the tuples, representing related entities were not connected by pointers, but could be “joined†at query time based on common values of particular fields. In the third or object–oriented generation of DBMS, there are two major structural approaches. One is a pointer–based approach while the other, is designed to add advanced, object–oriented features to the relational model. Recently, perhaps inevitably, interest in the object–oriented pointer–based approach has led to questions of whether it is, in some sense, a return to navigational DBMS. While object–oriented database clearly has major features that go far beyond the capabilities of first generation DBMSs, this article will show that a comparative analysis of pointer usage in navigational DBMS and in object– oriented DBMS can yield interesting results, plus a better understanding of the object–oriented DBMS paradigm.

PurposeTo describe the evolution of a content management system at the University of Maine Library that would function as a universal, extensible metadata repository, thereby eliminating the need to build separate databases for new digital collections, and facilitating both end‐user access and the management of electronic resources in an integrated technology environment.Design/methodology/approachBeginning with the development of a prototype system that mapped EAD encoded finding aids to a relational database, this paper discusses the evolution of this prototype into the design and implementation of a RDBMS (and continuing development of an object‐oriented database management systems (OODBMS) system) to actively manage digital objects and associated metadata. The key to the system design is metadata: extracting and mapping, transforming, and managing the processing of MARC‐based metadata into non‐MARC schemes to build digital collections. Other relevant CMS architecture issues discussed are the design of a functional bibliographic structure and utilities for metadata harvesting and indexing.FindingsProvides information on the use of the Dublin Core Abstract Model and a flexible and adaptable collection‐centric approach in the overall CMS architecture as implemented on a non‐MARC RDBMS, and provides an explanation of the advantages of an object oriented database system over the complexity of evolving relational database tables.Practical implicationsA useful source for the development of an in‐house CMS, and a contribution to the growing body of literature about the transformation of MARC‐based metadata for database design.Originality/valueThis paper is a case study of actual work conducted at the University of Maine Library. The RDBMS manages digital collections; the OODBMS manages digital video and other multimedia resources.

We describe the implementation of a version manager on an object-oriented database management system. The version manager supports various version semantics and version derivation graphs. Especially, it supports the version propagation to effectively manage versions of design objects and the efficient storage management for versions. All functionalities of the presented version manager are integrated with an object-oriented database programming language seamlessly. Therefore, designers can simply develop their applications which manipulate design objects.

In several working environments, production involves repeated executions of certain procedures. A workflow describes the individual tasks performed in these procedures and their interrelationships. Current workflow management systems (WFMSs) use a database management system (DBMS) to store task descriptions, and implement all workflow functionality in modules that run on top of the DBMS. Motivated by scientific workflows, we propose a much more DBMS-centric architecture, in which conventional database technology provides much of the desired scientific WFMS functionality. A key element of our approach is viewing the workflow as a web of data objects interconnected with active links that carry process descriptions. The workflow is fully defined as a database schema, and its execution is the gradual buildup of an instance of this schema through the active object links. For our work, we use the modeling and querying tools of Horse, the object-oriented DBMS that we have developed in the context of the Zoo Desktop Experiment Management Environment.

Ripple down rules (RDR) is an incremental knowledge acquisition (KA) methodology, where a knowledge base (KB) is constructed as a collection of rules with exceptions. Nested ripple down rules (NRDR) is an extension of this methodology which allows the expert to enter her/his own domain concepts and later refine these concepts hierarchically. In this paper we show similarities between incremental knowledge acquisition and database schema evolution, and propose to use the F2 object-oriented database management system (OODBMS) to implement an NRDR knowledge based system. We use the existing non-standard features of F2 and show how multiple instantiation and object migration (known as multiobjects feature in F2), and schema evolution capabilities in F2 easily accommodate all the update mechanisms required to incrementally build an NRDR KB. We illustrate our approach with a KA session.

The OO7 Benchmark was first published in 1993, and has since found a home in the marketing literature of various object-oriented database management system (OODBMS) vendors. The OO7 Benchmark (as published) was the initial result of an ongoing OODBMS performance evaluation effort at the University of Wisconsin. This paper provides an update on the status of the effort on two fronts: single-user and multi-user. On the single-user front, we review and critique the design of the initial OO7 Benchmark. We discuss some of its faults, the reasons for those faults, and things that might be done to correct them. On the multi-user front, we describe our current work on the development of a multi-user benchmark for OODBMSs. This effort includes changes and extensions to the OO7 database and the design of a family of interesting multi-user workloads.

The architecture of the open object-oriented database (OODB) management system, its requirements, and its computational model, which builds database functionality as an extensible collection of transparent extensions to existing programming languages, are described. The way in which open OODB's system architecture is decomposed into a kernal meta-architecture and a collection of modules implementing specific behavioral extensions is discussed. The potential risks of the open OODB architecture are reviewed.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">&gt;</ETX>

The V 3 Video Server is a demonstration showing a multimedia application developed on top of the VODAK database management system. VODAK is a prototype of an object-oriented and distributed database management system (DBMS) developed at GMD-IPSI. The V 3 Video Server allows a user to interactively store, retrieve, manipulate, and present analog and short digital video clips. A video clip consists of a sequence of pictures and corresponding sound. Several attributes like author, title, and a set of keywords are annotated. The highlights of the demonstration are as follows. (1) It is shown that an object-oriented database management systems is very useful for the development of multimedia applications. (2) The video server gives valuable hints for the development of an object-oriented database management system in direction to a multimedia database management system .

The V3 Video Server is a demonstration showing a multimedia application developed on top of the VODAK database management system. VODAK is a prototype of an object-oriented and distributed database management system (DBMS) developed at GMD-IPSI. The V3 Video Server allows a user to interactively store, retrieve, manipulate, and present analog and short digital video clips. A video clip consists of a sequence of pictures and corresponding sound. Several attributes like author, title, and a set of keywords are annotated. The highlights of the demonstration are as follows. (1) It is shown that an object-oriented database management systems is very useful for the development of multimedia applications. (2) The video server gives valuable hints for the development of an object-oriented database management system in direction to a multimedia database management system.

Opportunistic prioritised clustering framework for improving OODBMS performance

There are many problems facing scientists in their efforts to use computers to manage, access, and analyze data. One serious problem is the heterogeneity of data sources. Previous research into accessing heterogeneous data has not addressed problems with accessing large data sources that are not managed by database management systems. We believe that an object-oriented database management system can be used to implement an object-oriented heterogeneous database (OOHDB) that efficiently addresses the problem of heterogeneity among large scientific property databases. The object-oriented data model provides a powerful modeling paradigm for representing complex scientific data. Objects within the OOHDB hide heterogeneity among various data sources. Efficient access to external data is achieved by representing external data with a small amount of data stored within the OOHDB.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">&gt;</ETX>

The underlying hypothesis of the case study described is that the development, implementation, operations, and maintenance of large, complex, data-intensive applications, such as computer-integrated manufacturing, can be simplified through the use of object-oriented database management systems (DBMSs). The objective of the case study is to verify this hypothesis. The approach is to prototype selected representative components of a computer-integrated-manufacturing system; these components have been developed on top of a relational DBMS, using an object-oriented DBMS, called Iris. The fundamental elements of the data model of Iris are objects, types, and functions. An Iris object is represented by a unique identifier. Each object is associated with at least one type. This association supports classification. An object is said to be the instance of the types with which it has classification associations. The results of the study illustrate that the object-oriented prototype has a superior schema, is capable of providing convenient access to information, and is easier to extend and maintain. >