AnsweredAssumed Answered

Alfresco Share Viusalización del repositoy de alfresco

Question asked by psantis on Mar 5, 2010
Latest reply on Mar 6, 2010 by venzia
Estimados:


junto con saludarles quisiera plantear la siguiente inquietud, la versión de alfreseco 3.2r2 enterprise tiene la capacidad de conectarse con el repositorio mismo y desplegar todos los spaces del al fresco, no tan solo sites, ahora bien, dentro de las configuraciones que se realizan al archivo share-config-custom.xml permite hacer visibles aspectos customizados, ahora bien una vez echo esto efectivamente los spaces aparecen con dicho aspecto, pero aun así no es posible visualizar la meta-data personalizada de los archivos, alguna idea?

envió el código
<alfresco-config>

   <!– Global config section –>
   <config replace="true">
      <flags>
         <!–
            Developer debugging setting to turn on DEBUG mode for client scripts in the browser
         –>
         <client-debug>true</client-debug>

         <!–
            LOGGING can always be toggled at runtime when in DEBUG mode (Ctrl, Ctrl, Shift, Shift).
            This flag automatically activates logging on page load.
         –>
         <client-debug-autologging>false</client-debug-autologging>
      </flags>
   </config>

   <!– Document Library config section –>
   <config evaluator="string-compare" condition="DocumentLibrary" replace="true">

      <!–
         Whether the folder Tree component should enumerate child folders or not.
         This is a relatively expensive operation, so should be set to "false" for Repositories with broad folder structures.
      –>
      <tree>
         <evaluate-child-folders>false</evaluate-child-folders>
      </tree>

      <!–
         Used by the "Manage Aspects" action

ble>false</visible>For custom aspects, remember to also add the relevant i18n string(s)
    cm_myaspect=My Aspect
–>
<aspects>
<!– Aspects that a user can see –>
<visible>
    <aspect name="my:datosFactura"/>
    <aspect name="cm:complianceable" />
    <aspect name="cm:dublincore" />
    <aspect name="cm:effectivity" />
    <aspect name="cm:summarizable" />
    <aspect name="cm:versionable" />
    <aspect name="cm:templatable" />
    <aspect name="cm:emailed" />
    <aspect name="emailserver:aliasable" />
    <aspect name="cm:taggable" />
   
    <aspect name="app:inlineeditable" />
   
</visible>

         <!– Aspects that a user can add. Same as "visible" if left empty –>
         <addable>
         </addable>

         <!– Aspects that a user can remove. Same as "visible" if left empty –>
         <removeable>
         </removeable>
      </aspects>

      <!–
         Used by the "Change Type" action

         Define valid subtypes using the following example:
            <type name="cm:content">
               <subtype name="cm:mysubtype" />
            </type>

         Remember to also add the relevant i18n string(s):
            cm_mysubtype=My SubType
      –>
      <types>
         <type name="cm:content">
            <subtype name="cm:mycontentsubtype" />
         </type>

         <type name="cm:folder">
            <subtype name="cm:myfoldersubtype" />
         </type>
      </types>

      <!–
         If set, will present a WebDAV link for the current item on the Document and Folder details pages.
         Also used to generate the "View in Alfresco Explorer" action for folders.
      –>
      <repository-url>http://localhost:8080/alfresco</repository-url>
   </config>

   <!– Repository Library config section –>
   <config evaluator="string-compare" condition="RepositoryLibrary" replace="true">
      <!–
         Whether the link to the Repository Library appears in the header component or not.
      –>
      <visible>true</visible>

      <!–
         Root nodeRef for top-level folder.
      –>
      <root-node>alfresco://company/home</root-node>

      <!–
         Whether the folder Tree component should enumerate child folders or not.
         This is a relatively expensive operation, so should be set to "false" for Repositories with broad folder structures.
      –>
      <tree>
         <evaluate-child-folders>false</evaluate-child-folders>
      </tree>
   </config>

</alfresco-config>

Outcomes