nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Categories and Custom types

pjcaracuel

Hi,

I'd been working with Documentum for seven years and now I've started work with Alfresco, then I would like when is recommended that the use of categories instead of custom type metadata, because I think that using custom type is more usefull to end users.

TIA

PD:smileyfrustrated:orry, but my English is a bit poor

Find more posts tagged with

Comments

ribz33

Hi Pedro,

in my view categories are interresting when you need to have a tree of metadatas…
For instance to select a language :

-US -GB

- CL - CO - ES

- FR - CA - …

I think categories is very interresting, but need a browser (coming in next release probably) and component to select categories is not very friendly and easy-to-use for final user. Categories allow you to have a "transversal" organization of information (its very powerfull) but I according to you that in most of case "standard properties" are enough.

Best regards.

pjcaracuel

Hi Pierre,

but I according to you that in most of case "standard properties" are enough.

I think that you have meant "but I according to you that in most of case "standard properties" are NOT enough. "

In my opinion custom properties in Alfresco are easier to developer but when I need use the advance search, is not easier.

Salu2

mabayona

For a good comment about when to use custom types (or aspects) have a look at the documents created by Jeff at:

http://www.ecmarchitect.com

worth reading everyone of them!