Jailer is a database subsetting and browsing tool. It is a tool for data exporting, schema browsing, and rendering. It exports consistent, referentially intact row-sets from relational databases. It removes obsolete data without violating integrity. It is DBMS agnostic (by using JDBC), platform independent, and generates DbUnit datasets, hierarchically structured XML, and topologically sorted SQL-DML.
Conary is a distributed software management system for Linux distributions. It replaces traditional package management solutions (such as RPM and dpkg) with one designed to enable loose collaboration across the Internet. It enables sets of distributed and loosely connected repositories to define the components which are installed on a Linux system. Rather than having a full distribution come from a single vendor, it allows administrators and developers to branch a distribution, keeping the pieces which fit their environment while grabbing components from other repositories across the Internet.
Boar provides simple version control and backup for photos, videos, and other binary files. Boar aims to be the perfect way to make sure your most important digital information, like pictures, movies, and documents, is stored safely. It makes it possible for you to restore any or all of your files from any point in time. It makes it easy to maintain verified backups of your data, including file history. It imposes no limits on file or repository sizes. Using boar is an effective way to prevent data loss due to human or machine error.
JBup (Java Backup) aims to become a robust, professional backup tool. It creates a mirror of the current file set and compares it to the previous version. The deltas are saved and the previous mirror is removed. By applying the increments in reverse time order, complete backups of arbitrary versions can be created. It is an Ant task and can therefore be used in Ant scripts that perform additional backup actions, such as archiving directories or sending emails.
Skwish is a fast, simple, lightweight Java library for storing blobs on the file system. It allows multiple concurrent readers and writers, provides all-or-nothing write semantics, and is designed to survive abnormal, unclean shutdown. Skwish is a structured implementation of storing all blobs in a single file to save on file system I/O. Skwish is premised on the proposition that blob storage ought to be orthogonal to the task of indexing. It is meant to be a clean and simple store on which some other index can be built.
Associations Indexing Service (AIS) was originally done as an extension of human memory for tagging (storing under personal keywords and associations) resources, URIs, bookmarks, and memos (for fast access to the information in future) by using the same keywords or queries, similar to popular search engines. It can be seen as a local search engine, used as an automatic indexer of big file hierarchies (e.g. personal archives or files repositories). It is based on Lucene, so the application will remain very fast with any size index.
VeriTAR [Veri(fy)TAR] is a command-line utility that verifies the MD5 sums of files within a tar archive. Due to the limitations of the tar ("ustar") format, the MD5 sums are retrieved from a separate file and are checked against the MD5 sums of the files within the tar archive. The process takes place without actually exctracting the files. It works even with corrupted tar archives. The program carries on to the next file within the archive, skipping the damaged parts. At the moment, this relies on internal functions of Python's tarfile module.
With the Cibet framework, it is very easy to add various control mechanisms into a JPA and/or EJB-based Java application. The actual version includes control schemes like Archiving (manipulation of domain objects; data and execution of business processes are archived). From the archived state, domain objects can be reconstructed and business processes can be re-invoked with the same parameters at any time. The archive entries are secured against manipulation to make them audit-proof and revision safe. Four-eyes principle: this scheme is an example of a dual control mechanism: A user wants to perform some critical data manipulation or business process. With an applied dual control mechanism, the action is not executed in the production system directly, but stored and postponed. A second user must check the data and the action and can approve or decline. Only when the second user approves, the data manipulation or business process is executed in the production system; otherwise it is discarded. An even stricter example for a dual control mechanism is the six-eyes principle. In this case, a third user must approve a data manipulation or business process before it will become productive.