![]() ![]() All these have one thing in common: they are Cataloguing tools. ![]() We’ve all pretty much assumed and wished that Affinity's DAM would be in the likes of Aperture, Lightroom or Capture One. Optionally a suffix may be added to the new file's image number, showing whether it derives directly from the original or from another derivative (Photoshop is notorious for not respecting all metadata.)ĭatabase is updated with the new file being derivative of the original file. If the new file's metadata has a match for an existing file, then existing file metadata is used to repopulate missing data in the file. If there has been a new file created it is checked for metadata. When a file is closed, this is also noted. When a file is edited, a file system watcher notes that the file was opened. I addition all metadata in the file is slurped into a database. ![]() If the master is unwritable, it's written to a sidecar file. This ID is written to a set of fields in meta data that most editors will leave at least one intact. This could be a checksum of the file preview image, or Camera model+serial number + shutter count. To budnip answers of the form "This is impossible" here's how it could be implemented:įor each master image generate a unique ID based on the content of the file. That question has a more general set of requirements and received no answers. Similar question: Advanced software to organize and manage a life of photos (They have server based software too that is big bucks.) Has to read metadata from images/sidecar files on startup. One man shop.įotostation: AFAIK no underlying database. Photomechanic is fast for keywording and culling, but has very limited search capability. Lightroom: Doesn't support PNG, very clunky interface, slow on large catalogs Nothing I've found supports version tracking. Simple non-destructive editing - crop, brightness, contrast. Reasonable speed with catalogs of more than 100,000 images.Ībility to rebuild corrupt database from sidecars. Support for previews of all common image formats and most raw formats. Relevant sidecars are also renamed, and the database updated with new file location/name. Through file system watching, name changes and directory reorganization are caught. Metadata is also written to sidecar files. If Photoshop is used to create a jpeg image, that too is tracked. If I edit a program in photoshop, it will mark the PSD file as being derived, restore as much of the metadata as the PSD format allows. ![]() Metadata applied to a master should propagate down to derived images.Ībility to track through external editing programs. Derived images are not linear but form a multi-branched tree. A master should be able to list derived images. Version tracking If a lower resolution or a black and white image is produced from a master, the system should show that it's a derived image, and allow access to the master. Synonyms - I can define "Picea glauca" as a synonmym for "White Spruce" entering one, enters the other. (With the correct database link, this comes free as a side effect of the point above. Parent items are automatically entered as keywords. Separate entries for Birds -> raptors -> falcon and Planes -> fighters -> falcon. (Additional fields are written to sidecars) Runs on Mac or on local apache web server.įull access to standard metadata, subject to limits of the file format. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |