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=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 | |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 | ||
}} | }} | ||
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 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). | + | When dissemination is not needed anymore, the database can be removed, or it remains available as persistent DIP (DIPp). |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
====Documentation and user support==== | ====Documentation and user support==== | ||
Line 65: | Line 50: | ||
== 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. |