All Activity

Thank you! Tested and works.

Hi Juha, yes, fixed in the lastet build: https://daminion.net/files/DaminionServerSetup-10.0.zip This functionality is now regulated by the config parameter: isSupportItemsGroup="true" Please edit the config file (setting is to be applied to each catalog), restart the server, and the groups will be available

working in build 3668 but you has to set the "true" option in the config file

Hi! Any updates on this one?

Thank you!

So my support end in 2023 but there is no way to prolong it. Daminion Home server edition.

even if I am annoying: as long as the existing and working support of Thunderbird is not officially declared as terminated, I expect the bug to be fixed - still existing in 3668: System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt. bei Daminion.Addons.EmailAddon.EmailAddon.EmailByDefaultClient(List`1 fileRefs) in C:\Daminion\code\Addons\EmailAddon\EmailAddon.cs:Zeile 112. bei PicaJet.Daminion.ClientCommon.ExportPresenter.DoFinishExport(ExportProgressPresenter presenter) in C:\Daminion\code\ClientCommon\Presenters\ExportPresenter.cs:Zeile 770. bei PicaJet.Daminion.ClientCommon.ExportPresenter.LaunchExportingProcess() in C:\Daminion\code\ClientCommon\Presenters\ExportPresenter.cs:Zeile 764. bei PicaJet.Daminion.ClientCommon.ExportPresenter.Execute() in C:\Daminion\code\ClientCommon\Presenters\ExportPresenter.cs:Zeile 278. bei PicaJet.Daminion.ClientCommon.PicaJetEnginePresenter.LaunchExportAddon(ExportAddonData addonData) in C:\Daminion\code\ClientCommon\Presenters\PicaJetEnginePresenterExport.cs:Zeile 254. bei PicaJet.Daminion.ClientCommon.PicaJetEnginePresenter.LaunchExportAction(Object sender, ActionExecuteEventArgs e) in C:\Daminion\code\ClientCommon\Presenters\PicaJetEnginePresenterExport.cs:Zeile 218. bei PicaJet.Daminion.ClientCommon.Action.ExecuteAction(Object sender, ActionExecuteEventArgs e) in C:\Daminion\code\ClientCommon\Classes\Action.cs:Zeile 411. bei PicaJet.Daminion.GUIComponents.ContextMenuGenerator.MainMenuItemClick(Object sender, EventArgs e) in C:\Daminion\code\GUIComponents\Classes\ContextMenuGenerator.cs:Zeile 596. bei System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e) bei System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e) bei System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) bei System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) bei System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea) bei System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea) bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) bei System.Windows.Forms.Control.WndProc(Message& m) bei System.Windows.Forms.ToolStrip.WndProc(Message& m) bei System.Windows.Forms.ToolStripDropDown.WndProc(Message& m) bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Hi Trevor, it should be one week by default.

Hello if I use the API to sign in programatically (ie POST /account/login), how long is the Cookie valid for?

HI, in another forum I asked the same question and got this answer: "There should never be two sources of truth for metadata. Many tags in XMP, EXIF, GPS IPTC are linked and mirror each other. Many "entry-level" applications out there don't bother to synchronize properly, which always causes problems." Of course, Daminion is not an entry-level app. So my question is along the following lines: as a Daminion user, do I have to live with ‘two truths’ regarding the time stamps and how can users to whom I have to send the original photos find out the truth? The way I interpret the XMP sidecar file, it should keep the RAW file as ‘original’, which is not possible with the timestamp. I have only briefly tested (combination RAW+XMP) which timestamp is used for sorting by date taken. I hope I haven't made a mistake! XnView: RAW - Exif:DateTimeOriginal Imatch: RAW - Exif:DatetimeOriginal DxO Photolab: XMP:DateTimeOriginal LuminarNeo: RAW - Exif:DateTimeOriginal W11 Explorer, ignores XMP: RAW - Exif:DateTimeOriginal W11 Photo Viewer: RAW - Exif:DateTimeOriginal I am interested in how other Daminion users deal with this issue. I am looking forward to it and best regards, Uwe

Hi Uwe, If you set the tool to write tags in XMP, we follow the settings and modify the XMP only. If you want to modify the RAW file, please change the settings to writee tags to RAW file. Unfortunately, it is either of two. We cannot write both to RAW and XMP. Kind regards, Daria

Hello, in the preferences it is set that for RAW files tags are written to the XMP sidecar file. So far so good. But should/must this also apply to the DateTimeOriginal tag, for example? If you have to adjust the timestamp of the RAW file after the XMP sidecar file exists, then Daminion only changes the XMP file. This therefore leads to a difference between the DateTimeOriginal tag in the RAW file and the XMP file! How are other systems/apps/DAM supposed to know which timestamp is correct - DateTimeOriginal of the RAW file or the XMP file? Is the generated difference an error in Daminion? In comparison, IMatch, for example, changes the DateTimeOriginal tag in both the RAW file and the XMP file in the above-mentioned case, but does not write any other metadata to the RAW file, as Daminion does. Regards, Uwe

Hi, We are going to be enabling the web client access so that we can give outsiders the ability to watch video previews. Since these will be people outside our organization, we want to exercise administrative controls, such as not being able to download, copy, or record the preview. Has anybody set up that kind of controls using Daminion over the web? Thanks, Diane

Hello, in the attachment you will find three files. The paper was scanned on 29.01.2025 14:31 with a flatbed scanner and saved as PDF, TIF and JPG. Unfortunately, Daminion interprets the data differently. For TIF the FileCreateDate is used, for JPG the tag CreateDate and for PDF CreateDate but with interpretation of the time zone. I then assigned the date 29.1.2025 12:00:00 to all three files in the Properties Panel and also wrote ‘Write tags to file’ to the files. JPG: Date/Time Original 2025:01:29 12:00:00 PDF: Date/Time Original 2025:01:29 12:00:00+01:00 TIF: Date/Time Original 2025:01:29 12:00:00 Then I called the action ‘read tags from file’. While the JPG and TIG format CreateDate in the Properties Panel are unchanged, the PDF now reads 25.1.2025 14:31:29 What now Daminion? Regards, Uwe 20250128_120000.pdf 20250128_120000.tif

Hello Rupert, this functionality has been changed. Now sorting is only available if you made a query. Sorting on the whole database was disabled due to slowness of the results display on large databases (1 mln and more)

Since version 10.0 the option to sort is gone. It's "none" and grayed out and I have no chance to change it. When I use some kind of filters, the sorting works properly. But when I remove all filters, it's "none" and gray again. Please fix that. I don't want to use filters all the time. Thanks! Kind regards, Rupert

Hi Cincytriguy, You would need to remove Daminion Server, Daminion Client, and PostgreSQL from your machine. Then remove the following directories: - PostgreSQL Data Directory - its path will be indicated at the end of PostgreSQL uninstall - C:\Program Files\Daminion Software - C:\ProgramData\Daminion Software Please don't forget to create the backups of the catalogs prior to removing PostgreSQL. You can do it via Daminion server admin panel > Catalogs > select a catalog > actions > Backup. You will need them to restore the databases on the new machine. You can also copy the thumbnails to the new machine unless you want to let Daminion regenerate them after the installation. If any help is needed, please let me know. Kind regards, Daria

I'm on Daminion Server 8.4 and need to move it to another server host. I want to ensure all Daminion components are completely removed from the previous host. Is there a current topic or article that discusses how to do this?

Hi Uwe, unfortunately, this option is not available right now and is not planned to be added in the nearest releases.

Hello, how can I prevent IPTC metadata from being written? In the past I repeatedly had problems because parts of the IPTC content were cut off due to the length limit, while they were correct in the corresponding XMP metadata. It seems to me that IPTC has completely overslept the development towards XMP. With the old IPTC data, there are problems with umlauts if non-ASCII was written and the IPTC data does not contain any character set information. I can delete all IPTC metadata using the exiftool command -IPTC:all=, but I don't want to repeat this every time. I would therefore like to have a way of preventing the ITPC metadata from being written in the preferences. Best regards, Uwe

Also can't read this or enlarge the box:

I have the same issue with the properties panel and some items are cut off. Please make these windows adjustable.

Hi, These instructions don't seem to apply to ver. 10. This sync button is not there.

https://daminion.net/support/. this page has a user guide link that links to ver 6.2

Hi Juha, this is a known issue, we are working on it