Editing DbDIPview
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
{{Infobox tool | {{Infobox tool | ||
| − | |purpose= | + | |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. |
|homepage=https://github.com/dbdipview/dbdipview/wiki | |homepage=https://github.com/dbdipview/dbdipview/wiki | ||
|license=EUPL-1.2 | |license=EUPL-1.2 | ||
|platforms=linux | |platforms=linux | ||
| − | |function=Access | + | |function=Access |
|content=Database | |content=Database | ||
}} | }} | ||
{{Infobox tool details}} | {{Infobox tool details}} | ||
== Description == | == Description == | ||
| − | dbDIPview provides | + | 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 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==== | ====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. | 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 | + | 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. |
| − | When dissemination is not needed anymore, the database can be removed, or it remains available as persistent DIP (DIPp). | + | 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==== | ====Documentation and user support==== | ||
| − | Demonstration examples are included with sample databases and related Representation Information. | + | Demonstration examples are included with sample databases and related Representation Information Packages. |
====Usability==== | ====Usability==== | ||
| − | End-users interact with the system through a browser user interface | + | 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==== | ====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. | 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 61: | Line 46: | ||
== User Experiences == | == 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. --> | <!-- 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 == | == Development Activity == | ||
<!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --> | <!-- 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 | |