Catalogs

by Murat on April 27th, 2010

Daminion has made the retrieval of imported assets extremely fast and simple; it stores all the media descriptions in a database named, Catalog. Stand-alone versions of Daminion will use .dmc file extensions.

Pictures (digital images) and other media files – of different formats or themes – can be separated into individual catalogs. For example, private.dmc can be used for private photos; music.dmc for songs; landscapedesign.dmc for the collection of landscape designs, etc.

We recommend creating the catalog in the same folder where all the media files belonging to this catalog are located. The catalog has paths relative to the imported files, so you can copy the Media folder to your laptop or other PC and immediately work there with the copied catalog.

media-database-organizing-scheme

Sample scheme of organizing a media archive.

Photo and media thumbnails are cached into the separate folders; this means the catalog files stay compact, and can be easily and quickly backed-up.

Several catalogs can be opened under different tabs in the thumbnail browser like web pages in the tabbed web browser.

3 catalogs are opened in different tabs

  • Ralph Hobert

    What database format is used in Daminion?

  • http://daminion.net Murat

    Ralph Hobert: SQLite for the standalone version and Postgre for the multi-user version. Both are open-source, free, well tested, have a solid performance and get wide adoption.

    Using the open-source database formats and storing the information as a metadata allows for digital media library do not totally be depended from a single DAM system.

  • http://fotoremco.nl Remco Boerma

    Sounds great, especially the usage of sqlite for standalone is a wise decision. Please keep it a standard version (not like Corel Paint Shop Pro that uses sqlite but an own version, you can’t modify data using other applications).

    The splitting of the thumbs from the database can be a good thing, but i would prefer a second database. Storing the database and thumbs near the images needs to be an option, not a design decision. This is because more and more often people use a NAS and want the database and thumbs to be local, not somewhere over a wire.

    Why storing the thumbs in a database? Mostly because of windows overhead. Virusscanners, Windows Explorer and many other tools do not gain performance when there are a lot of files in a single directory. With the current disk sizes i think it will waste a lot of slackspace as well. Storing the thumbs solves the issue of backing up only the important data and keeps things smooth while at it. I hope this helps in rethinking the subject.

  • http://www.daminion.net Murat

    Remco Boerma: Thanks for the suggestions.

    We consider various storage schemes and decided to keep thumbnails and database separated due to performance reason. Plus it keeps the database file smaller and as you said you can decide whether to backup both thumbnails and database file or just the database file.
    Daminion uses local database to cache the intensive traffic so in case of a NAS or using a Daminion Server the data will be cached to improve the performance.
    Regarding anti-viruses: Thumbnail files are separated into sub-folders (inside the Thumbnails folder) to avoid keeping a lot of files in a single directory. Most anti-viruses have the option to exclude folders from scanning or scan files by mask. Probably this might be a solution.

    Anyway thanks for the suggestion!