deanable

It would be great if, when we save searches, we could have the option to save the search only for "this catalog only" or "server-wide." Then we could create searches that apply to the whole server, e.g. "no country" search applied to any catalog on the entire server and another search that only applies only to a specific catalog, e.g. models without age and height in "studio shoots" catalog.

Can we include tag count as a search field with less than and more than operands in desktop client? As administrators one of the challenges we face is getting an idea of the overall state of metadata in the catalog. There is no easy way to generate reports on the state of metadata. We have to generate endless queries and saved searches to ensure metadata compliance manually in our catalogs. I know that the web client has a required metadata feature to ensure compliance with metadata policies, but if most users in the organization use the desktop client this policy is simply ignored. Are there any plans to implement this required metadata feature in the desktop client? Maybe a staging area (like the webclient) where we can examine assets that do not comply with a rule set OR search for tag count that we can use as an operand in building queries? I know this can not be available on "Everywhere" but it will be a great addition to the search functionality if we can have something like Keywords + "tag count <=" and "tag count >="? This will simply expand and enhance the "is empty" and "is not empty" functionality that we already have in searches. Administrators are always in the position where we have to estimate how well a catalog is tagged. This can also be incorporated into queries to include reporting functionality regarding metadata compliance.

Could we please get a Max Catalog Size / quota setting per catalog? This way administrators can allocate resources across teams that share catalogs on a single server.

Hi Dan Would you be open to sharing your source repo? I, for one, would love to take a look.

I, for one, can not wait for this implementation. It is after-all an optional feature, that you can activate/deactivate as a value added service. I am certain that the format and file size limitations (of the web preview) will be taken into consideration when the final integrations is pushed out to release. In the final release, I am sure that you will be able to set the accuracy threshold. I will experiment with a prediction threshold percentage (E.g. all tags above 80% probability) that I consider reasonably accurate. I will set up a new temporary catalog for imports so I can review and approve all newly assigned Google Vision tags. Once I am happy with the auto-discovered metadata I will move these assets into the working catalog. My tagging workflow will become one of revision and minor correction where the AI algorithm misidentifies. For those of us who have hundreds of thousands of digital assets to process yearly, this will save months in the tagging workflow. I DO NOT see this integration replacing human tagging, but rather to serve as a tag suggestion feature to increase productivity. This AI development is new and cutting edge in the DAM industry and I predict that as the technology matures the accuracy will too. You also have to consider that Google Vision uses a generically trained model. You can invest the time and effort to train your own specific model on the AI platform if you have a super specific domain.

I agree!!! Vast improvement in searching and tag assignment speed in this build! Good job.

I was wondering if on the Server Administration we can have a setting to activate / de-activate some kind of archiving system to indicate record age. E.g. if I set my asset lifecycle to 5 years, older records can have an overlay icon on the thumbnail to indicate that they can be archived - batch or manual move to a separate archive catalog. I know that we can sort, search and filter by date but especially with large and old archives we have to be very aware of asset lifecycle as part of the organisation's asset management strategy. The advantage of having this built in to the server is also that Daminion will automate a repetitive task (weekly / monthly flagging of aged records) that takes up Administrator's time. It would be interesting to hear other Administrator's take on how they deal with ageing records in their catalog and if they have a strategy or solution using Daminion Server to accomplish this in their workflow.

1 100 878 records today...

Hi Jistme You can take the folder (containing all assets) and drop it in to the interface, that will recursively scan for media in all subfolders...

I have files in the Unsynced search. When I select multiple files and apply the Write Tags To File command from the context menu, then refresh, only the first file is removed from the Unsynced search.

I am running Windows Server 2012 R2 Standard Intel Xeon CPU E3-1220 v3 @ 3.1GHz 16 GB RAM on a 64bit machine Assets are located on a NAS drive, but the thumbnails & PostreSQL files are stored on the same drive as the Daminion installation.

Hi Guys I am interested to see if other users have pushed the limits of Daminion Server. We have recently gone over the 1 000 000 records mark and I have not experienced any issues with performance. Share your Daminion catalog size screenshot and let's see the winner!!!

Hi Uwe Did you perhaps Lock Tag Editing? I encountered the same error with users logged in as editors and then when I removed the tag editing restrictions, this exception was also gone. This was on 1021. I haven't checked on 1022 yet.

Hi guys Yes, you are right. I assumed that if it works for keywords tag-type, it would work for all other tag types too... :|

Hi Rene If you rename the "wrong" tag with the exact name of the "right" tag, Daminion will merge them.