Editing DiPS (Digital Preservation Solution)

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
|image=Dips_Logo.jpg
 
 
|purpose=DiPS (OAIS compliant '''Di'''gital '''P'''reservation '''S'''olution)
 
|purpose=DiPS (OAIS compliant '''Di'''gital '''P'''reservation '''S'''olution)
 
|homepage=https://go.sergroup.com/dips-kommunal
 
|homepage=https://go.sergroup.com/dips-kommunal
|license=Proprietary
 
 
|platforms=Linux and Windows as well as the common database systems
 
|platforms=Linux and Windows as well as the common database systems
 
|language=Java 8 / 11
 
|language=Java 8 / 11
Line 14: Line 12:
 
== Description ==
 
== Description ==
 
DiPS is an OAIS compliant long-term archive solution based on the ECM systems from SER Group ([https://www.sergroup.com/en/ sergroup.com]).
 
DiPS is an OAIS compliant long-term archive solution based on the ECM systems from SER Group ([https://www.sergroup.com/en/ sergroup.com]).
The long-term data is stored as XMLs within the AIPs and managed in the ECM index management. It uses PREMIS to store technical object information (format information, hash values, file sizes, etc.), events (pre-ingest, ingest, conversions, etc.), agents (natural persons and systems) and relationships between objects. The preservation metadata is acquired both from internal mechanisms and from external sources.
+
The long-term data is stored as XMLs within the AIPs and managed in the ECM index management. It uses PREMIS to store technical object information (format information, hash values, file sizes, etc.), events (pre-ingest, ingest, conversions, etc.), agents (natural persons and systems) and relationships between objects.
 
Due to the extensive use of Java and standardized APIs it can be extended and customized in many ways.
 
Due to the extensive use of Java and standardized APIs it can be extended and customized in many ways.
 
Furthermore the system is based on:
 
* DROID and custom developments for format recognition
 
* JHOVE and a number of custom modules for format validation
 
* Custom development and free tools (including ffmpeg/ffprobe) for metadata extraction from content objects
 
* Custom development and free tools for format conversion
 
  
 
== Stakeholder/Audience ==
 
== Stakeholder/Audience ==
The primary focus are (long-term) archives but the solution can also be used in other environments with appropriate extensions (e.g. Geographic Information Systems).
+
The primary focus are (long-term) archives but can also be used in other environments with appropriate extensions (e.g. Geographic Information Systems)
For example, it is offered as a service in the digital archive network "DiPS.kommunal" in North Rhine-Westphalia, Germany ([http://www.danrw.de danrw.de] / [https://www.danrw.de/ueber-das-da-nrw/da-nrw-ein-loesungsverbund details]).
+
For example, it is offered as a service in the digital archive network "DiPS.kommunal" in North Rhine-Westphalia, Germany ([http://www.danrw.de danrw.de])

Please note that all contributions to COPTR are considered to be released under the Attribution-ShareAlike 3.0 Unported (see COPTR:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)