• As a hobby photographer
• I want that APhotoManager is able to support different xmp sidecare filenaming conventions
• to increase interoperability with other apps.

Background:

Unfortunately there are different xmp sidecar filenaming conventions for photo software

• digiKam uses $BASENAME.$EXT.xmp. (i.e. /path/to/photo.jpg.xmp belongs to /path/to/photo.jpg)
• jphototagger and APhotoManager use $BASENAME.xmp (i.e. /path/to/photo.xmp belongs to /path/to/photo.jpg)

[Update 2017-05-05] after discussion of this issue in digiKam-s bug tracker https://bugs.kde.org/show_bug.cgi?id=278935 also found on http://digikam.1695700.n4.nabble.com/Bug-278935-New-Please-make-XMP-Sidecar-filename-configurable-td3707654.html

implementation:

• Settings will get an option to choose default xmp sidecare filenaming convention
• Move/rename/delete of img.jpg will also handle img.xmp and img.jpg.xmp if they exist (no matter what xmp-naming-convention the seggings dialog has)
• if there is imp.jpg and img.jpeg the first one beeing moved/deleted/renamed wins (owns the xmp)
• the apm media scanner will assign the content of img.xmp to both: img.jpg and img.jpeg
• xmp update policy:
  • if there is imp.jpg.xmp update this file
  • else if there is img.xmp update this file
  • else if there is no xmp file yet create it according to xmp-naming-convention settings