Difference between revisions of "DbDIPview"
m |
|||
| Line 6: | Line 6: | ||
|homepage=https://github.com/dbdipview/dbdipview | |homepage=https://github.com/dbdipview/dbdipview | ||
|license=EUPL-1.2 | |license=EUPL-1.2 | ||
| − | |platforms= | + | |platforms=linux |
}} | }} | ||
<!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --> | <!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --> | ||
| Line 21: | Line 21: | ||
::- access mechanism to the data via browser menu with report selection and search screen for a selected database that mimics the original application. | ::- access mechanism to the data via browser menu with report selection and search screen for a selected database that mimics the original application. | ||
| − | Before export from the original environment into SIARD format is started, no modification of the data is needed (de-normalization, additional views, etc.). This is important when we want to maintain data integrity. As the next step, when a database package is being ingested by the archives, an expert needs to validate it. In the process, queries are manually prepared to show the content of the tables, and also serve as proof that the information is well understood and described in the archives. The queries are stored in | + | Before export from the original environment into SIARD format is started, no modification of the data is needed (de-normalization, additional views, etc.). This is important when we want to maintain data integrity. As the next step, when a database package is being ingested by the archives, an expert needs to validate it. In the process, queries are manually prepared to show the content of the tables, and also serve as proof that the information is well understood and described in the archives. The queries are stored in long-term storage as an access package for a related database AIP and thus enable future users to search in the database using the typical (parameterized) searches. Finally, when access is requested by the end-user, the archivist deploys the archived database. Now the user can use the menu to access the information without the assistance of an expert. |
====Licensing and cost==== | ====Licensing and cost==== | ||
| − | Free | + | Free/open-source EUPL-1.2 |
====Development activity==== | ====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 often being improved to cover requirements by new use cases. | ||
Revision as of 18:00, 1 October 2019
Description
dbDIPview provides parallel access to multiple archived databases for a non-technical end-user. It offers a way to configure and store access information based on queries, written in pure (portable) SQL and stored in XML. It also enables deployment of the packages on the dedicated server for end-user access. It deals with
- - packaging the access information
- - automatic deployment of the database packages and related access packages
- - access mechanism to the data via browser menu with report selection and search screen for a selected database that mimics the original application.
Before export from the original environment into SIARD format is started, no modification of the data is needed (de-normalization, additional views, etc.). This is important when we want to maintain data integrity. As the next step, when a database package is being ingested by the archives, an expert needs to validate it. In the process, queries are manually prepared to show the content of the tables, and also serve as proof that the information is well understood and described in the archives. The queries are stored in long-term storage as an access package for a related database AIP and thus enable future users to search in the database using the typical (parameterized) searches. Finally, when access is requested by the end-user, the archivist deploys the archived database. Now the user can use the menu to access the information without the assistance of an expert.
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.
Platform and interoperability
Linux, PHP, Apache2, PostgreSQL
Functional notes
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 data visualization. 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 immediately removed, or it remains available for other users among other active databases. The access menu lists the available reports. For each report, a search screen is configured for entering the search criteria, including drop-down fields. In the results pane, links to further reports can be available from a value in a certain column.
Documentation and user support
A demonstration example is included with a sample database and related viewer package.
Usability
End-users interact with the system through a web interface. Users can work in parallel on the same server on any of the accessible databases.
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.
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.
Influence and take-up
Information about wider use is unavailable.