I really does not make sense to me to store the meta data in the xml. You can always retrieve the meta data from the document, so why store it as xml? And indeed, last modified is an intrinsic webdav property on documents, so you will always end up with a catch-22
-Ard > > Hi guys, > > We have xml documents that contain a metadata block. This > block contains 'real' metadata (like keywords, description > etc.) but also some fields that are supposed to be filled > automatically by the CMS, like creator, creationdate, etc. I > am wondering how to do this. > As I can see it, there are two ways: > - on document load, using preprocess.xsl to insert the values > from a propfind into the corresponding xml elements, but then > things go wrong with things like lastmodified (document is > loaded, last modified is inserted, document is saved, last > modified is changed on property but not in xml) > - on document save, but then I find myself in a catch-22. I > have to save the document, do a propfind to get last > modified, insert it into the xml document, and save the > document again, thereby invalidating the last modified I just > inserted. > > Any ideas, or am I making this overly complex? I am toying > with the idea to leave the difficult metadata fields out of > the xml altogether, but I have to look into the consequences. > > Rogier > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
