<?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: Public Facing RM with access restrictions? in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/public-facing-rm-with-access-restrictions/m-p/248505#M201635</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi and welcome to the Alfresco Community.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Sounds like you've got ingestion and organization figured out. Although I note you mentioned Records Management to help you organize your stuff. I think unless you plan to do things like retention periods, legal holds, and other Records Management specific functionality, you may want to not use the Records Management module and just use straight Alfresco. If you do need to treat your documents like legal records then go for it. I just don't want to see you adding additional code/modules unnecessarily.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Next, you are asking how to expose certain documents to end-users without using the Alfresco web client. Drupal is certainly one option and many people (including Alfresco corporate) take that approach. There is really no limit to what you can use. Here's a little example I put together using a Python web application framework called Pyramid: &lt;/SPAN&gt;&lt;A href="https://www.youtube.com/watch?v=B9nV3uUb0Hw&amp;amp;feature=g-upl" rel="nofollow noopener noreferrer"&gt;https://www.youtube.com/watch?v=B9nV3uUb0Hw&amp;amp;feature=g-upl&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Of course the devil is in the details. And one detail you point out is that you'd like to limit access to certain documents based on a quota. That is something you'll have to develop yourself–there is nothing like that out-of-the-box. So you'll have to track hits either in the front-end application that you write or in the repository. Then the front-end will have to determine whether it is okay for someone to see a requested doc based on the hit count. If it is okay, show the document, otherwise, redirect to an error page or something.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Jeff&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 20 Aug 2012 23:09:12 GMT</pubDate>
    <dc:creator>jpotts</dc:creator>
    <dc:date>2012-08-20T23:09:12Z</dc:date>
    <item>
      <title>Public Facing RM with access restrictions?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/public-facing-rm-with-access-restrictions/m-p/248504#M201634</link>
      <description>Hello, I am trying to but together a hi level direction for a project in which Alfresco will play a role. I do not have as much experience with Alfresco but I am hopping I can get get started in the right direction rather than find it along the way. The first part of the project is add value to some</description>
      <pubDate>Fri, 17 Aug 2012 14:29:39 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/public-facing-rm-with-access-restrictions/m-p/248504#M201634</guid>
      <dc:creator>tomdavidson</dc:creator>
      <dc:date>2012-08-17T14:29:39Z</dc:date>
    </item>
    <item>
      <title>Re: Public Facing RM with access restrictions?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/public-facing-rm-with-access-restrictions/m-p/248505#M201635</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi and welcome to the Alfresco Community.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Sounds like you've got ingestion and organization figured out. Although I note you mentioned Records Management to help you organize your stuff. I think unless you plan to do things like retention periods, legal holds, and other Records Management specific functionality, you may want to not use the Records Management module and just use straight Alfresco. If you do need to treat your documents like legal records then go for it. I just don't want to see you adding additional code/modules unnecessarily.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Next, you are asking how to expose certain documents to end-users without using the Alfresco web client. Drupal is certainly one option and many people (including Alfresco corporate) take that approach. There is really no limit to what you can use. Here's a little example I put together using a Python web application framework called Pyramid: &lt;/SPAN&gt;&lt;A href="https://www.youtube.com/watch?v=B9nV3uUb0Hw&amp;amp;feature=g-upl" rel="nofollow noopener noreferrer"&gt;https://www.youtube.com/watch?v=B9nV3uUb0Hw&amp;amp;feature=g-upl&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Of course the devil is in the details. And one detail you point out is that you'd like to limit access to certain documents based on a quota. That is something you'll have to develop yourself–there is nothing like that out-of-the-box. So you'll have to track hits either in the front-end application that you write or in the repository. Then the front-end will have to determine whether it is okay for someone to see a requested doc based on the hit count. If it is okay, show the document, otherwise, redirect to an error page or something.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Jeff&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Aug 2012 23:09:12 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/public-facing-rm-with-access-restrictions/m-p/248505#M201635</guid>
      <dc:creator>jpotts</dc:creator>
      <dc:date>2012-08-20T23:09:12Z</dc:date>
    </item>
  </channel>
</rss>

