Hi Richard, Thank you for the problems enumeration. I would say that in our case:
1. the medatada is not very critical. 2. this one may be the worse point of all, but anyway we don't think we will reuse a lot of images through the website. In some cases, duplicated pictures will be uploaded, but from a user point of view this seems easier than remembering in what DMS folder the other one is located (since the folders would be created by us, and not by the user, this may have been confusing). 3. the user shouldn't have any access to admin-central anyway, so it may be problematic for us, but not for the user. And I think we can live with that. 4. we don't have any importation routine. So I think it's not the "cleanest" way to go, but since the problems are not critical, and the time is limited, we're going for the "pragmatic way" :) As you say, maybe the magnolia 5 admin central will be different and we will change our approach after that. Thank you and best regards, Leo -----Mensaje original----- De: Unger, Richard [mailto:[email protected]] Enviado el: martes, 22 de marzo de 2011 14:16 Para: Leo Lozes CC: 'Magnolia User-List' Asunto: AW: [magnolia-user] Upload document to DMS from CMS Hi Leo, That sounds like a pragmatic way to go. We certainly thought about it, but finally decided against it for these reasons: 1. Direct Upload does not include any metadata. When using DMS, documents have standard metadata fields. When using direct upload, there is no way to add metadata to the file. We would have to add appropriate metadata fields to each dialog that includes an upload. 2. Direct upload does not allow reuse of assets. This means that if the same image is reused, it needs to be uploaded a second time - this is a waste of space, not to mention that duplicated data can cause other troubles. 3. The uploads in the website repository are not displayed in the backend (admin-central) in any way. This means that once uploaded, the only way for an editor to "find" a file is to navigate back to the page containing it, and open the dialog for the relevant paragraph. 4. We are importing a lot of data from older systems into the new magnolia-based cms. The import routines are simpler for us if documents and webpage content are nicely separated. If you can live with these problems, then it is certainly easier to just use the upload. Direct upload is also generally easier for the editors to understand. It would also have the advantage that you can more easily benefit from future upgrades to the DAM subsystem (Magnolia 5 and beyond). For us, these problems outweighed the benefits, and we decided to take the plunge and create our own controls and ckEditor module to integrate DMS the way we needed it. Do feel free to let me know if you have any more questions about this. Regards from Vienna, Richard -----Ursprüngliche Nachricht----- Von: Leo Lozes [mailto:[email protected]] Gesendet: Dienstag, 22. März 2011 11:35 An: Unger, Richard Cc: 'Magnolia User-List' Betreff: RE: [magnolia-user] Upload document to DMS from CMS Hello Richard, I hope you had a good time in your holidays, and thank you for remembering me :) Truth is I think we will only allow the user to upload images directly to the page, because he has to be able to quickly add/edit/delete images, and it seems a bit too complicated to make a dms control for each of these actions when they are already available for the website part (unfortunately we don't have much time to implement everything). Anyway if you have comments / suggestions on that, I'm quite open to other approaches :) Regards from Mallorca, Leo -----Mensaje original----- De: Unger, Richard [mailto:[email protected]] Enviado el: martes, 22 de marzo de 2011 11:14 Para: Leo Lozes CC: Magnolia User-List Asunto: AW: [magnolia-user] Upload document to DMS from CMS Hi Leo, I'm back from Holidays... how is the implementation going? Do you still have questions about the DMS front-end integration? Regards from Vienna, Richard -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Leo Lozes Gesendet: Mittwoch, 16. März 2011 11:18 An: 'Magnolia User-List' Betreff: RE: [magnolia-user] Upload document to DMS from CMS Hi Richard, Your solution of showing the repo-browser is ok too (it seemed easier to avoid this step). And yes, any help is appreciated. Anyway, enjoy your holidays, we'll talk next week :) Leo -----Mensaje original----- De: [email protected] [mailto:[email protected]] En nombre de Unger, Richard Enviado el: miércoles, 16 de marzo de 2011 10:40 Para: Magnolia User-List CC: Magnolia User-List Asunto: Re: [magnolia-user] Upload document to DMS from CMS Hi Jan, hi Leo, Yes, we did something very like this, with the difference that we first show the repo-browser, meaning the user can choose the DMS location for the new file. It should be quite possible to do: If you want to use DAM write a handler that shows the DMS Upload dialog, supplying your desired path as a parameter. If you want fckEditor configuration, that will be a bit more tricky. I'm on holidays this week, but I'd be happy to write more when I'm back next week, if it's helpful to you. Regards from Austria, Richard (iPhone) On 15.03.2011, at 17:53, "Jan Haderka" <[email protected]<mailto:[email protected]>> wrote: What you are looking at is writing the custom DAMHandler that would do the job, similar to the "upload" (InternalAssetDAMHandler is the class that does it) that just uploads binary under the page in website. I think somebody already wrote something like that (and maybe they are willing to share ... anybody?) or at least there was a discussion about the topic in the past in the list. HTH, Jan On Mar 15, 2011, at 5:13 PM, Leo Lozes wrote: Hi everybody, As I explained last time, we are trying to avoid the end-user access to AdminCentral, so I'm trying to create a new dialog to upload documents directly to DMS from a web page. What we want to do is to upload a document to DMS, and maintain the same structure in the dms and website contexts. Meaning that if I upload a document from website:webpage/offers/, it should go to the folder dms:webpage/offers, and store the UUID in the page data. I took a look to the DocumentDialog class, but I don't see an easy way to do it. Have anyone tried to do something similar? Thank you very much, Leo ________________________________ ---------------------------------------------------------------- For list details see <http://www.magnolia-cms.com/home/community/mailing-lists.html>http://www.ma gnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <<mailto:[email protected]>user-list-unsubscribe@magnol ia-cms.com<mailto:[email protected]>> ---------------------------------------------------------------- ________________________________ ---------------------------------------------------------------- For list details see <http://www.magnolia-cms.com/home/community/mailing-lists.html>http://www.ma gnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]<mailto:user-list-unsubscribe@magnoli a-cms.com>> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
