Photini is a GUI program to create and edit metadata for digital photographs. It can set textual information such as title, description, and copyright as well as geolocation information by browsing a map or setting coordinates directly. It reads metadata in EXIF, IPTC, or XMP format and writes it to all three to maximize compatibility with other software.
FDRDF is a tool that builds a catalogue of descriptions in an RDF representation of the specified files. The descriptions currently include: file status (as per the stat system call); SHA-1 hash over the file contents; MIME type (as guessed by the file tool), geospatial metadata (as per GDAL), and GRIB file composition (as per GRIB API).
Vault is a Perl script to store away files, including metadata and integrity checks. Any file you want to keep, you put into a vault. This vault is just a directory. You can create any directory hierarchy allowed by your filesystem, and when you "vault" a file to a destination directory, a subdirectory is also created to store metadata files containing the MD5 hash of the file, the date it was vaulted, and any notes (i.e., metadata) you want to save regarding the file.
Athena Framework for Java is a full fledged enterprise object-relational mapping (ORM) framework that employs metadata as mapping configuration. It greatly simplifies Java Web application development by removing the requirement of manual mapping and manual database schema updating. In addition to features like Java object persistence, powerful EJBQL querying execution, and comprehensive code generation, Athena has built-in support for multi-tenancy, which enables developers to build cloud applications easily. Athena can be easily integrated with other libraries like Struts or Spring to provide full stacks of service.
The maven-buildmetadata-plugin is a Maven 2 plugin that helps you easily add build metadata to generated archive artifacts. When a product is running on an application server, this tool can tell you which version of which artifact is currently running on that server, which artifact maps to which source code version in the SCM repository, what configuration set (including profiles and environment variables) has been used to generate the artifact, on which machine was the artifact built, and when was the artifact built. The provided metadata include SCM information, build time, operating system, Java runtime, Maven execution information, build user, build host name, and build version.