YAG - Yet Another Gallery

Hi Bernd,

thanks for this one. In fact I thought about integrating DAM into YAG for quite some time. There are several problems, which I encountered so far and I do not have a propper solution yet:

1. DAM and YAG Metadata is "same, same but different" :-) This means, that you have to add some DAM data when doing an import into YAG instead of being able to use the DAM data directly.

1. What happens, if DAM data changes? How can you achieve changing YAG data as well. What so ever an import would look like, this problem should be managed automatically, so that you don't have to change information twice.

1. At the moment, YAG copies original image files to a separate folder. What about DAM image files? Should they be copied to or should there be a reference to the original file? What happens, if a DAM object / file gets deleted? Deletion of YAG file should happen automatically.

Despite those problems, it is quite easy to import files from YAG. For an "import-only" process, all you have to do is:

• Select the files from DAM that you want to import
• Create a new importer for DAM (this should be a 3rd party extension, I suppose)
• For each DAM object gathered in step 1, create a yag item object, fill it with DAM data and save it. Your import is done.

As I don't know much about DAM and its internals, I suppose there should be some kinds of hooks that are triggered it one of the following YAG actions occur:

• deleting a file
• changing a file

So the solution for the problems mentioned above could be:

• Create a new domain object "dam_yag_item" that is kind of a DAM:YAG mm relation object.
• Store dam object UID and yag item UID in this object and perhaps some further information like "delete_if_dam_deletes" and "update_if_dam_updates"
• Hook "deletion of dam object" and delete yag item, if flag is set
• Hook "update of dam object" and update yag item, if flag is set

So the only thing we have to think about is whether we copy the dam file, when importing or not. This could be a parameter of the import process and I think stands in relation to "delete_if_dam_deletes" as otherwise, it would make no sense to keep a yag object alive, if its original image file is deleted.

Are you willing to join implementation of this? Sadly I don't have the time at the moment, but if you want to help us out on this one, be sure to get some technical support from us!

Greetings

Mimi

Hi

I am very pleased to hear that fast from you. This speaks very much for your work.

Michael Knoll wrote:

....

Are you willing to join implementation of this? Sadly I don't have the time at the moment, but if you want to help us out on this one, be sure to get some technical support from us!
Sadly I have no experience in programming extensions. So I fear I will not be of any help.