Showing papers on "Data access published in 1980"

Obtaining access to data sources: an exploration of method, problems and possible solutions.

Abstract: A method, route and problems relating to the gaining of access to research data or respondents is discussed. In seeking permission to gather data from patients and staff in Scottish psychiatric hospitals, using Flanagan's Critical Incident Technique, a number of problems were encountered, viz. (i) the varying admnistrative levels to which the first formal request for entry had to be made; (ii) the varying routes which had to be followed in order to gain permission, and (iii) the time taken to obtain access to data sources. The problems, their possible consequences, and a number of long and short term recommendations are made. If implemented, these may go some way toward minimizing the difficulties associated with gaining access to data sources. The long term recommendations, including improved nurse representation on existing research and ethical committees, are directed to those who shape and influence policies relating to research practice generally. The short term recommendations are directed to the nurse researcher who is seeking access to field sites, with a view to minimizing problems relating to this aspect of planning and carrying out research activity.

Integrating a database system and programming / information environment

Abstract: Vast differences in terminology aside, there is considerable overlap between work in knowledge representation, programming language data types, and database models. Our current work on the Cedar programming environment has necessitated integrating a number of ideas in these areas.As part of the Cedar project in the Computer Science Lab at Xerox PARC, we have been constructing a database management system. The goal of the Cedar environment is to greatly increase our productivity by combining the best currently known principles from programming languages, programming tools, and user interfaces into a single integrated system. Cedar is based on the Mesa programming language [1]. The goal of our database subproject of Cedar is to provide a uniform prepackaged way to perform access to data structures, as contrasted to the current state of affairs in which Mesa programmers repeatedly re-invent the facilities we intend to provide to type, structure, index, link, robustly store, concurrently access, and cache data stored in the primary or secondary memory of one or more computers on a network.

Executive and communications services to support the IPAD environment

Abstract: The principal purposes of the prototype executive software are to provide a system independent interface to the underlying host system and to allow for extension to full IPAD executive services as described in the preliminary design. A basic set of functions is included in the prototype to meet the requirements of the other components of the prototype, principally IPID, the IPAD data management system. The functions were chosen so that they would be readily built on any of the proposed host systems with minimal redesign and execution overhead. The functions fall into five categories: access to host data, access to data files, access to communication services, data transformation, and instrumentation for performance measurement. Communication services provide message delivery between processes in a network of heterogeneous computers. Data transformation services and communication services ensure data type validity and data integrity of messages exchanged between processes.

Remote File Access: A Data-Access Protocol for Computer Networks

Abstract: This paper deals with defining and implementing high-level protocols for computer networks, a subject now being studied by private, national, and international organizations. While line-level protocols already exist in standard formats, and these organizations are defining end-to-end protocols, higher level protocols are still a matter for study. Since some services have to be provided by a computer network, such services must use standardized protocols if portability, compatibility, and internetworking are to be achieved. This paper considers a possible network service and its related protocol.

Data processing system with multiple logical space

Abstract: A data processing system comprises a main memory (100), a logical space number storage (480) for storing logical space numbers, a logical address storage (400) for storing logical addresses, address converter (600) for producing physical addresses in response to the logical space numbers and logical addresses to access the main memory. The logical space number storage (480) includes two storages (OPM1, OPM2) for storing logical space numbers to be used in a data access and a storage (ISM) for storing a logical space number to be used in an instruction access, thereby to reduce the time required for the switching between logical space numbers at the data processing.