DbDIPview - Revision history

Regrat at 13:23, 3 April 2023

2023-04-03T13:23:54Z

Regrat at 13:03, 29 November 2022

2022-11-29T13:03:44Z

Regrat: /* Development Activity */

2022-01-26T12:12:30Z

Development Activity

Regrat: /* Functional notes */

2022-01-26T12:07:52Z

Functional notes

Prwheatley at 12:20, 15 June 2021

2021-06-15T12:20:15Z

Regrat at 17:16, 14 June 2021

2021-06-14T17:16:56Z

Regrat at 19:58, 13 June 2021

2021-06-13T19:58:56Z

Regrat: /* Description */

2021-06-13T19:52:21Z

Description

Regrat: /* Functional notes */

2021-05-08T06:28:15Z

Functional notes

Rcdeboer: Added links to Function and/or Content Type

2021-04-20T19:33:10Z

Added links to Function and/or Content Type

@@ Line 1: / Line 1: @@
 {{Infobox tool
-|purpose=Database Representation Information packaged and used for quick and user-friendly access to information stored in databases. Different combinations of Content Data Objects are supported by an automated deployment mechanism.
+|purpose=Framework for packaging the database Representation Information and pre-configured user-friendly access. Different combinations of Content Data Objects are supported by an automated deployment mechanism. Enables access to the archived databases in the archive reading room for non-technical users.
 |homepage=https://github.com/dbdipview/dbdipview/wiki
 |license=EUPL-1.2

@@ Line 1: / Line 1: @@
 {{Infobox tool
-|purpose=Database Representation Information packaged and used for quick and user-friendly access to information stored in databases. Different combinations of Content Data Objects are supported by automated deployment mechanism.
+|purpose=Database Representation Information packaged and used for quick and user-friendly access to information stored in databases. Different combinations of Content Data Objects are supported by an automated deployment mechanism.
 |homepage=https://github.com/dbdipview/dbdipview/wiki
 |license=EUPL-1.2
 |platforms=linux
-|function=Access, Quality Assurance
+|function=Access, Quality Assurance, Redaction
 |content=Database
 }}

@@ Line 65: / Line 65: @@
 == Development Activity ==
 <!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. -->
-All development activity is visible on GitHub.
+The tool is stable but new features are added from time to time. All development activity is visible on GitHub.

@@ Line 28: / Line 28: @@
 In the SIP/AIP Audit Phase in the archives, an expert needs to validate the content. For the archivist, the most convenient way is to use a dissemination package. During the validation process, database queries are prepared to show the content of the tables in the same way it is shown in the reports from the original environment. The queries are written in pure (portable) SQL and are stored in long-term storage as part of the Representation Information Package. The queries can be prepared using the information provided by the creator, using some dedicated query builder, or simply manually. When a basic query is ready, the search criteria panel including drop-down fields, and drill down behaviour can be configured. The test serves as proof that the information in the database is well understood, described for future use and is ready for dissemination.
-Upon request by an end-user, the order fulfilment process enables that packages are transferred to the dedicated dbDIPview server. There, the information in the database Representation Information Package enables seamless automated deployment of data package(s) of the archived database data objects and setting up of the rendering module. Automated database redaction and creation of additional views are possible at this stage. The user can be redirected via a unique code directly to the menu with queries for the desired database.
+Upon request by an end-user, the order fulfillment process enables that packages are transferred to the dedicated dbDIPview server. There, the information in the database Representation Information Package enables seamless automated deployment of data package(s) of the archived database data objects and setting up of the rendering module. Automated database redaction and creation of additional views are possible at this stage. The user can be redirected via a unique code directly to the menu with queries for the desired database.
 When dissemination is not needed anymore, the database can be removed, or it remains available as persistent DIP (DIPp).
 ====Documentation and user support====

@@ Line 4: / Line 4: @@
 |license=EUPL-1.2
 |platforms=linux
-|function=Access
+|function=Access, Quality Assurance
 |content=Database
 }}

@@ Line 1: / Line 1: @@
 {{Infobox tool
-|purpose=dbDIPview offers a way to store database representation information, automatically deploy the archived databases and provide access to multiple databases for non-technical end-users.
+|purpose=Database Representation Information packaged and used for quick and user-friendly access to information stored in databases. Different combinations of Content Data Objects are supported by automated deployment mechanism.
 |homepage=https://github.com/dbdipview/dbdipview/wiki
 |license=EUPL-1.2
@@ Line 9: / Line 9: @@
 {{Infobox tool details}}
 == Description ==
-dbDIPview provides parallel access to multiple archived databases for non-technical end-users in the electronic reading rooms. To the archivist, it offers a way to work with Representation Information. It deals with:
+dbDIPview provides simultaneous access to multiple archived databases for non-technical end-users in the electronic reading rooms. To the archivist, it offers a way to work with Representation Information. It deals with:
-::- representation information that supplements original database data packages,
+:- representation information that supplements original database data packages,
-::- automatic deployment of database packages (data objects) and related access packages, including redaction
+:- automatic deployment of database packages (data objects) and related access packages, including redaction
-::- access mechanism to the database via a browser menu with report selection and search screen for a selected database that mimics the original application.
+:- access mechanism to the database via a browser menu with report selection and search screen for a selected database that mimics the original application.
 ====Licensing and cost====
@@ Line 28: / Line 28: @@
 In the SIP/AIP Audit Phase in the archives, an expert needs to validate the content. For the archivist, the most convenient way is to use a dissemination package. During the validation process, database queries are prepared to show the content of the tables in the same way it is shown in the reports from the original environment. The queries are written in pure (portable) SQL and are stored in long-term storage as part of the Representation Information Package. The queries can be prepared using the information provided by the creator, using some dedicated query builder, or simply manually. When a basic query is ready, the search criteria panel including drop-down fields, and drill down behaviour can be configured. The test serves as proof that the information in the database is well understood, described for future use and is ready for dissemination.
-Upon request by an end-user, the order fulfilment process enables that packages are transferred to the dedicated dbDIPview server. There, the information in the database Representation Information Package enables seamless automated deployment of data package(s) of the archived database data objects and setting up of the rendering module. Automated database redaction is possible at this stage. The user can be redirected via a unique code directly to the menu with queries for the desired database.
+Upon request by an end-user, the order fulfilment process enables that packages are transferred to the dedicated dbDIPview server. There, the information in the database Representation Information Package enables seamless automated deployment of data package(s) of the archived database data objects and setting up of the rendering module. Automated database redaction and creation of additional views are possible at this stage. The user can be redirected via a unique code directly to the menu with queries for the desired database.
-When dissemination is not needed anymore, the database can be removed, or it remains available for other users among other active databases as persistent DIP (DIPp).
+When dissemination is not needed anymore, the database can be removed, or it remains available as persistent DIP (DIPp).
 ====Documentation and user support====
-Demonstration examples are included with sample databases and related Representation Information Packages.
+Demonstration examples are included with sample databases and related Representation Information.
 ====Usability====
-End-users interact with the system through a browser user interface. On the server, they can work on any of the accessible databases. The hierarchical reports menu enables selection between available reports to access the information without the assistance of an expert. In the results pane, drill-down links to further reports may be available based on column values. BLOB data and external files may be shown. Additional metadata can be shown with each report to provide a detailed description of the given report.
+End-users interact with the system through a browser user interface and work with the accessible databases. The hierarchical reports menu enables selection between available reports to access the information without the assistance of an expert. In the results pane, drill-down links to further reports may be available based on column values. BLOB data and external files may be shown. Additional metadata can be shown with each report to provide a detailed description of the given report.
 ====Expertise required====
 Basic knowledge of Linux system administration is needed for initial installation and configuration. Familiarity with basic SQL commands and an understanding of database structure is needed to configure the viewer. No special skills are required for the end-user.
@@ Line 46: / Line 46: @@
 == User Experiences ==
 <!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. -->
 == Development Activity ==
 <!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. -->
-All development activity is visible on GitHub: https://github.com/dbdipview/dbdipview/wiki
+All development activity is visible on GitHub.

@@ Line 9: / Line 9: @@
 {{Infobox tool details}}
 == Description ==
-dbDIPview provides parallel access to multiple archived databases for non-technical end-users in the electronic reading rooms. To the archivist, it offers a way to configure and store access information. It deals with
+dbDIPview provides parallel access to multiple archived databases for non-technical end-users in the electronic reading rooms. To the archivist, it offers a way to work with Representation Information. It deals with:
-::- representation information that supplements original data packages
+::- representation information that supplements original database data packages,
 ::- automatic deployment of database packages (data objects) and related access packages, including redaction
 ::- access mechanism to the database via a browser menu with report selection and search screen for a selected database that mimics the original application.
 ====Licensing and cost====
 Free/open-source EUPL-1.2
 ====Development activity====
-dbDIPview has been initially created in 2009 and is often being improved to cover requirements by new use cases.
+dbDIPview has been initially created in 2009 and is continuously being improved to cover requirements by new use cases in the area of long‐term preservation of databases.
 ====Platform and interoperability====
 Linux, PHP, Apache2, PostgreSQL
 ====Functional notes====
-A database can be stored in SIARD or dbDIPview (based on simple CSV) format. Complex combinations of packages are possible. The queries can be prepared using the information from the creator, using some dedicated query builder, or simply manually. When a basic query is ready, the search criteria screen and drill down behaviour can be added. A typical use case assumes relatively simple relational database data and excludes direct graphical data visualization.
+Before export from the original environment is started, no modification of the data is needed, like de-normalization or the creation of additional views. This is important to ensure data integrity and authenticity.
-The ordering process in the archives will result in packages, transferred to the dedicated dbDIPview server. There a database can be deployed and its access package activated. The user can be redirected via a unique code directly to the access menu for the desired database. When access is finished, the database can be removed, or it remains available for other users among other active databases.
+When dissemination is not needed anymore, the database can be removed, or it remains available for other users among other active databases as persistent DIP (DIPp).
 ====Documentation and user support====
-A demonstration example is included with a sample database and related viewer package.
+Demonstration examples are included with sample databases and related Representation Information Packages.
 ====Usability====
-End-users interact with the system through a browser user interface. Users can work in parallel on the same server on any of the accessible databases.
+End-users interact with the system through a browser user interface. On the server, they can work on any of the accessible databases. The hierarchical reports menu enables selection between available reports to access the information without the assistance of an expert. In the results pane, drill-down links to further reports may be available based on column values. BLOB data and external files may be shown. Additional metadata can be shown with each report to provide a detailed description of the given report.
 ====Expertise required====
-Basic knowledge of Linux system administration is needed for initial installation and configuration. Familiarity with basic SQL commands and understanding of database structure is needed to configure the viewer. No special skills are required for the end-user.
+Basic knowledge of Linux system administration is needed for initial installation and configuration. Familiarity with basic SQL commands and an understanding of database structure is needed to configure the viewer. No special skills are required for the end-user.
 ====Standards compliance====
-dbDIPview uses its XML schema for storing information about the queries, and its format for packaging the access package and optional CSV package. The queries should not use any SQL dialect to minimize compatibility issues with a target database.
+dbDIPview uses its XML schema for storing information about the queries, and its format for packaging the Representation Information Package and optional CSV package. The queries should not use any SQL dialect to minimize compatibility issues with a target database.
 ====Influence and take-up====