<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Content Ranking in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/content-ranking/m-p/254696#M207826</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm glad you like the dashlet.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In order for SOLR to support sorting on your criteria, you need to find a way to derive sortable property values from the different criteria and maintain them at the node properties level. The main issue with time-related criteria is that you kind of have to recalculate the scoring of all your content in pre-defined intervals so that you have a consistent sort order.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you have a closer look at the Content Trends dashlet, you'll see that I track each calculated score (total score, comment score, edit score …) as a property on the scored node, and use these properties to provide the sort via the search service (which can be either SOLR or Lucene). With some additional configuration, it could also be used in the regular search / document library.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 04 Dec 2012 17:00:31 GMT</pubDate>
    <dc:creator>afaust</dc:creator>
    <dc:date>2012-12-04T17:00:31Z</dc:date>
    <item>
      <title>Content Ranking</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/content-ranking/m-p/254695#M207825</link>
      <description>Hi,Came across this cool dashlet which is part of the Dashlet Challenge 2012.&amp;nbsp; http://www.nabucco-source.org/confluence/display/MODALF/Content+TrendsWe are also looking at implementing a similar type of content ranking but wanted it to be incorporated with Search. Basically, the search results needs</description>
      <pubDate>Tue, 04 Dec 2012 03:40:18 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/content-ranking/m-p/254695#M207825</guid>
      <dc:creator>unknown-user</dc:creator>
      <dc:date>2012-12-04T03:40:18Z</dc:date>
    </item>
    <item>
      <title>Re: Content Ranking</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/content-ranking/m-p/254696#M207826</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm glad you like the dashlet.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In order for SOLR to support sorting on your criteria, you need to find a way to derive sortable property values from the different criteria and maintain them at the node properties level. The main issue with time-related criteria is that you kind of have to recalculate the scoring of all your content in pre-defined intervals so that you have a consistent sort order.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you have a closer look at the Content Trends dashlet, you'll see that I track each calculated score (total score, comment score, edit score …) as a property on the scored node, and use these properties to provide the sort via the search service (which can be either SOLR or Lucene). With some additional configuration, it could also be used in the regular search / document library.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Dec 2012 17:00:31 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/content-ranking/m-p/254696#M207826</guid>
      <dc:creator>afaust</dc:creator>
      <dc:date>2012-12-04T17:00:31Z</dc:date>
    </item>
  </channel>
</rss>

