02-28-2011 11:18 AM
<!– …. –>
<constraint name="doctech:type" type="LIST">
<parameter name="allowedValues">
<list>
<value>Réunion</value>
<value>Suivi</value>
<value>Comité</value>
</list>
</parameter>
</constraint>
<!– …. –>
<type name="doctech:cpt-rendu">
<title>Compte rendu</title>
<parent>cm:content</parent>
<mandatory-aspects>
<aspect>doctech:compte-rendu</aspect>
</mandatory-aspects>
</type>
<!– …. –>
<aspect name="doctech:compte-rendu">
<title>Compte rendu</title>
<properties>
<property name="doctech:objet-jour">
<type>d:text</type>
<mandatory>true</mandatory>
</property>
<property name="doctech:date-proch-reun">
<type>d:datetime</type>
<mandatory>true</mandatory>
</property>
<property name="doctech:type-cpt-rendu">
<type>d:text</type>
<mandatory>true</mandatory>
<constraints>
<constraint ref="doctech:type"/><!– liste de valeurs–>
</constraints>
</property>
</properties>
</aspect>
<!– …. –>
fichier web-config-custom.xml
<!–ajouter un aspect "compte rendu" à votre fichier –>
<config evaluator="aspect-name" condition="doctech:compte-rendu">
<property-sheet>
<show-property name="doctech:objet-jour" display-label="Objet du jour"/>
<show-property name="doctech:date-proch-reun" display-label="Date de la prochaine réunion" />
<show-property name="doctech:type-cpt-rendu" display-label="Type de compte rendu" />
</property-sheet>
</config>
<!– …. –>
<meta-data aspect="doctech:compte-rendu" property="doctech:objet-jour" display-label="Objet du jour" />
<meta-data aspect="doctech:compte-rendu" property="doctech:date-proch-reun" display-label="Date de la prochaine réunion" />
<meta-data aspect="doctech:compte-rendu" property="doctech:type-cpt-rendu" display-label="Type de compte rendu" />
<!– …. –>
03-01-2011 03:31 AM
# Aspects
aspect.doctech_compte-rendu=Aspect compte rendu
# Types
type.doctech_cpt-rendu=Type de compte rendu
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE beans PUBLIC '-//SPRING//DTD BEAN//EN' 'http://www.springframework.org/dtd/spring-beans.dtd'>
<beans>
<bean id="doctech.i18n.resources" class="org.alfresco.i18n.ResourceBundleBootstrapComponent">
<property name="resourceBundles">
<list>
<value>alfresco.messages.doctech</value>
</list>
</property>
</bean>
</beans>
<alfresco-config>
<!– Document Library config section –>
<config evaluator="string-compare" condition="DocumentLibrary" replace="true">
<tree>
<!–
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.
–>
<evaluate-child-folders>false</evaluate-child-folders>
<!–
Optionally limit the number of folders shown in treeview throughout Share.
–>
<maximum-folder-count>-1</maximum-folder-count>
</tree>
<!–
Used by the "Manage Aspects" action
For custom aspects, remember to also add the relevant i18n string(s)
cm_myaspect=My Aspect
–>
<aspects>
<!– Aspects that a user can see –>
<visible>
<!– Mon aspect –>
<aspect name="doctech:compte-rendu" />
<aspect name="cm:generalclassifiable" />
<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" />
<aspect name="gd:googleEditable" />
<aspect name="cm:geographic" />
<aspect name="exif:exif" />
</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">
<!– Mon type –>
<subtype name="doctech:cpt-rendu" />
</type>
<type name="cm:folder">
</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>
<!–
Google Docs™ integration
–>
<google-docs>
<!–
Enable/disable the Google Docs UI integration (Extra types on Create Content menu, Google Docs actions).
–>
<enabled>false</enabled>
<!–
The mimetypes of documents Google Docs allows you to create via the Share interface.
The I18N label is created from the "type" attribute, e.g. google-docs.doc=Google Docs™ Document
–>
<creatable-types>
<creatable type="doc">application/msword</creatable>
<creatable type="xls">application/vnd.ms-excel</creatable>
<creatable type="ppt">application/vnd.ms-powerpoint</creatable>
</creatable-types>
</google-docs>
<!–
File upload configuration
–>
<file-upload>
<!–
Adobe Flash™
In certain environments, an HTTP request originating from Flash cannot be authenticated using an existing session.
See: http://bugs.adobe.com/jira/browse/FP-4830
For these cases, it is useful to disable the Flash-based uploader for Share Document Libraries.
–>
<adobe-flash-enabled>true</adobe-flash-enabled>
</file-upload>
</config>
</alfresco-config>
03-01-2011 08:07 AM
<aspects>
<!– Aspects that a user can see –>
<visible>
<!– Mon aspect –>
<aspect name="doctech:compte-rendu" />
<aspect name="cm:generalclassifiable" />
<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" />
<aspect name="gd:googleEditable" />
<aspect name="cm:geographic" />
<aspect name="exif:exif" />
</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>
+le fichier d'internationalisation ça fonctionne au quart de poil.
# Aspects
aspect.doctech_compte-rendu=Compte rendu
aspect.doctech_proc-install=Procédure d'installation
aspect.doctech_estim-charge=Estimation de charges
aspect.doctech_scenar-recette=Scénario de recette
aspect.doctech_etude=Etudes
aspect.doctech_bon-commande=Bon de commande
aspect.doctech_document-exploitation=Document d'exploitation
aspect.doctech_document-technique=Document technique
# Types
type.doctech_type-cpt-rendu=Type de compte rendu
#Properties
#property.doctech_type-cpt-rendu=Type de compte rendu
+
<types>
<type name="cm:content">
<subtype name="doctech:type-cpt-rendu" />
</type>
<type name="cm:folder">
</type>
</types>
A mon avis il faut mettre autre chose mais quoi. De plus ce que je ne comprend pas c'est que doctech:type-cpt-rendu n'est pas un sous-type appartenant au type content, c'est un attribut de l'aspect Compte rendu. Bon je reteste au cas où…03-01-2011 08:20 AM
<types>
<type name="cm:content">
<!– Mon type –>
<subtype name="doctech:cpt-rendu" />
</type>
<type name="cm:folder">
</type>
</types>
<type name="doctech:cpt-rendu">
<title>Compte rendu</title>
<parent>cm:content</parent>
<mandatory-aspects>
<aspect>doctech:compte-rendu</aspect>
</mandatory-aspects>
</type>
<aspect name="doctech:compte-rendu">
<title>Compte rendu</title>
<properties>
<property name="doctech:objet-jour">
<title>Objet jour</title>
<type>d:text</type>
<mandatory>true</mandatory>
</property>
<property name="doctech:date-proch-reun">
<title>Date prochaine réunion</title>
<type>d:datetime</type>
<mandatory>true</mandatory>
</property>
<property name="doctech:type-cpt-rendu">
<title>Type compte rendu</title>
<type>d:text</type>
<mandatory>true</mandatory>
<constraints>
<constraint ref="doctech:type"/>
</constraints>
</property>
</properties>
</aspect>
03-01-2011 08:27 AM
#Properties
property.doctech_type-cpt-rendu=Type de compte rendu
ça ne fait absolument rien. Autre chose il ne faut surtout pas mettre ceci:
<!–<config evaluator="aspect" condition="doctech:compte-rendu">
<forms>
<form>
<field-visibility>
<show id="doctech:type-cpt-rendu" label="Type de compte rendu"/>
<show id="doctech:date-proch-reun" label="Date de la prochaine réunion"/>
<show id="doctech:objet-jour" label="Objet du jour"/>
</field-visibility>
</form>
</forms>
</config>–>
car les champs de base mis par défaut dans Share disparaissent au profit seulement des attributs cités plus haut. Donc à éviter…
03-01-2011 08:41 AM
Sinon pour votre problème d'affichage des métadonnées, il suffit de définir des titres à vos propriétés dans votre modèle.
03-01-2011 08:48 AM
Au passage, je ne vois pas trop l'intérêt de faire un type s'il n'a aucune autre propriété que celle du mandatory-aspect ? Pourquoi ne pas utiliser seulement un aspect ou seulement un type ??En fait ça vient du fait que j'effectuais cette opération pour Explorer (ça me permettais de créer différents type de documents).
<config evaluator="string-compare" condition="Advanced Search">
<advanced-search>
<!– Aspects pour le compte rendu –>
<meta-data aspect="doctech:compte-rendu" property="doctech:objet-jour" display-label-id="Objet du jour"/>
<meta-data aspect="doctech:compte-rendu" property="doctech:date-proch-reun" display-label-id="Date de la prochaine réunion"/>
<meta-data aspect="doctech:compte-rendu" property="doctech:type-cpt-rendu" display-label-id="Type de compte rendu"/>
</advanced-search>
</config>
03-01-2011 08:53 AM
03-01-2011 09:13 AM
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.