<?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: Version numbers --&amp;gt; letters in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/version-numbers-gt-letters/m-p/297703#M250833</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 fear it won't be possible to address this properly on the Repository tier. Version numbers are expected to consist of numerical values separated by dots. You could add a custom property of your own to track the Version number and keep the Alfresco internal version. Then you'd Need to customize the standard name metadata renderer in the document list of Share as well as the node Header and version history components in the detail view.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The simplest solution I can see at the moment involves configuring a custom version Label provider that creates version labels consisting of only one number ranging from 1 - 26 (and above if they should start to have more Versions) regardless of the type of version in Alfresco Jargon. And convince the client that a single number is just as good as a single letter.&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>Fri, 27 Feb 2015 09:06:17 GMT</pubDate>
    <dc:creator>afaust</dc:creator>
    <dc:date>2015-02-27T09:06:17Z</dc:date>
    <item>
      <title>Version numbers --&gt; letters</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/version-numbers-gt-letters/m-p/297702#M250832</link>
      <description>Hello there,one of our customers asked us to set up a small Alfresco site to collaborate with other architects. There's nothing special aboutit, except for one thing: they don't want document versions to benumbered as you would expect, but to have alphabetical versions.Instead of a version "2.0" it</description>
      <pubDate>Thu, 26 Feb 2015 18:47:18 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/version-numbers-gt-letters/m-p/297702#M250832</guid>
      <dc:creator>hello_wrold</dc:creator>
      <dc:date>2015-02-26T18:47:18Z</dc:date>
    </item>
    <item>
      <title>Re: Version numbers --&gt; letters</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/version-numbers-gt-letters/m-p/297703#M250833</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 fear it won't be possible to address this properly on the Repository tier. Version numbers are expected to consist of numerical values separated by dots. You could add a custom property of your own to track the Version number and keep the Alfresco internal version. Then you'd Need to customize the standard name metadata renderer in the document list of Share as well as the node Header and version history components in the detail view.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The simplest solution I can see at the moment involves configuring a custom version Label provider that creates version labels consisting of only one number ranging from 1 - 26 (and above if they should start to have more Versions) regardless of the type of version in Alfresco Jargon. And convince the client that a single number is just as good as a single letter.&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>Fri, 27 Feb 2015 09:06:17 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/version-numbers-gt-letters/m-p/297703#M250833</guid>
      <dc:creator>afaust</dc:creator>
      <dc:date>2015-02-27T09:06:17Z</dc:date>
    </item>
  </channel>
</rss>

