Or you change the search XSLs so it will display the lastSaved if available and otherwise the existing lastModifiedDate. Something similar is done for the caption/displayname.
2009/12/18 Reinier van den Born <[email protected]>: > So I would have to use a new property, let's call it lastModified, for this > solution. > And then I might want to modify the Documents view as well to show > lastModified instead. > > To reduce the number of changes to make, I could use an extractor and > disable it while touching content. > Hmmm..... > > Reinier > > > On Fri, Dec 18, 2009 at 11:04 AM, Jasha Joachimsthal < > [email protected]> wrote: > >> 2009/12/18 Reinier van den Born <[email protected]>: >> > Hi Jasha, >> > >> > Thanks for explaining how I can customise Search without having to work >> in >> > the editor tree. Handy! >> > >> > I had already played with the configuration. First thing was along the >> lines >> > of your suggestion: to replace modificationdate by lastSaved. >> > That is not a real good solution because only documents that have been >> > edited have a lastSaved property. >> > So for assets or documents that are written from other tools, nothing is >> > showed. >> > The way Search is configured I don't see a way to support something like: >> > "show lastSaved or, if not set, modificationdate", >> > like it is done in the Documents view. >> > >> > Something that might do better is to have two date columns in Search: one >> > for lastSaved and one for modification date >> > and add a filter on lastSaved. Or even show creationdate instead of >> > modification date, since for assets creationdate >> > is more likely to equal lastSaved than modification date. Unless an asset >> or >> > documents is overwritten from outside the CMS, of course. >> > So none of these solutions are really satisfactory. >> > >> > The solution could be improved by making sure all resources have a >> > lastSaved. Problem is that I'd have to add this to all tools, >> > that write to the repository, including the CMS asset upload, document >> > creation etc. Except for the touching tools, of course. >> > Would be nice to be able to use an extractor, but extractors, as far as I >> > see, cannot exclude tools or make conditional decisions. >> >> The presence of lastSaved is a condition for the >> ReviewedActionsWorkflow to enable (request for) publication. >> >> >> > Anyway, so far my thoughts. >> > I was (still am :-) hoping someone might have come up with a smarter >> > solution. >> > >> > >> > Reinier >> > >> > >> > >> > On Fri, Dec 18, 2009 at 8:15 AM, Jasha Joachimsthal < >> > [email protected]> wrote: >> > >> >> 2009/12/17 Reinier van den Born <[email protected]>: >> >> > (sent this before but it didn't show up in the forum?) >> >> > >> >> > Hi all, >> >> > >> >> > After some investigation I found that the CMS Search >> >> > view (tab) displays another date (DAV:modificationdate) than the >> >> > Documents view (Hippo:lastSaved if present, DAV:getlastmodified >> >> > otherwise). lastSaved is only set when a document is saved from the >> >> editor. >> >> > >> >> > Normally this is no problem because these dates are >> >> > usually in sync, but things go wrong when an update on the content is >> >> > run. Then both DAV: properties are updated, but lastSaved is not >> >> > affected. As a result things seem normal in the Documents view (at >> >> > least for documents that have been edited at least once), but in the >> >> > Search view all content shows the same timestamp (the day of the last >> >> > update). Searching on modification time becomes effectively useless. >> >> > >> >> > I thought up/tried a couple of solutions, but haven't found anything >> >> really >> >> > satisfactory. >> >> > Did anyone run into this before and has a suggestion? >> >> > >> >> > Tnx, >> >> > >> >> > >> >> > Reinier van den Born >> >> >> >> Hello Reinier, >> >> >> >> the lastSaved property was introduced to indicate when a document has >> >> been saved through the workflow. Sometimes it's necessary to "touch" >> >> all documents to trigger (new) extractors but the content itself has >> >> not been changed. That's why we use the lastSaved date in the >> >> documents perspective. >> >> I think we overlooked this in the search perspective. You can modify >> >> the search configuration so it does display the lastSaved property. >> >> The default configuration is in src/site/search/config and you can put >> >> the whole search configuration in the repository. Copy the >> >> defaultconfig.xml to /configuration/search/config.xml and modify the >> >> paths of the files you want to customise. >> >> >> >> >> >> Jasha Joachimsthal >> >> >> >> [email protected] - [email protected] >> >> >> >> www.onehippo.com >> >> Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 >> >> San Francisco - Hippo USA Inc. 185 H Street, suite B, Petaluma CA >> >> 94952 +1 (707) 7734646 >> >> ******************************************** >> >> Hippocms-dev: Hippo CMS development public mailinglist >> >> >> >> Searchable archives can be found at: >> >> MarkMail: http://hippocms-dev.markmail.org >> >> Nabble: http://www.nabble.com/Hippo-CMS-f26633.html >> >> >> >> >> > ******************************************** >> > Hippocms-dev: Hippo CMS development public mailinglist >> > >> > Searchable archives can be found at: >> > MarkMail: http://hippocms-dev.markmail.org >> > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html >> > >> > >> ******************************************** >> Hippocms-dev: Hippo CMS development public mailinglist >> >> Searchable archives can be found at: >> MarkMail: http://hippocms-dev.markmail.org >> Nabble: http://www.nabble.com/Hippo-CMS-f26633.html >> >> > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > > Searchable archives can be found at: > MarkMail: http://hippocms-dev.markmail.org > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
