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.

making a TAG

akba

Is it possible to make TAG's in Alfresco, so you could mark sertain version to sertain documents as one TAG so those could be called out if needed? This is common feature in most SW version control system, but I could not figured out how to do it on Alfresco.

Thanks

Find more posts tagged with

Comments

pmonks

The repository used for the Web Content Management functionality (the "AVM") supports this (via snapshots) - see http://wiki.alfresco.com/wiki/WCM_Overview for an overview.

The repository used for the Document Management functionality (the "ADM") uses a per-asset versioning model that means that tags that encompass a set of documents are not provided directly by the repository itself. It might be possible to emulate that using a separate object that refers to the assets and versions that make up the tag, although if documents are deleted this model would break down (deleting a document in the ADM repository deletes the document and its version history, whereas deletes are a versioned operation in the AVM ie. deleted files are resurrected as you move back through the version history).

Cheers,
Peter

akba

Thanks for your reply. I tried to figure out "might be possible to emulate that using a separate object" but I couldn't . Can you please give some more info?

pmonks

Basically the idea would be to create another piece of content (to represent the tag) that has pointers to the content and versions that make up the tag. Alfresco doesn't provide any direct support for this, so you'd have to model that "tag" content type yourself, but there are a variety of ways it could be done (via a content model with associations and version #s, as an XML file stored literally in the repo, …).

Cheers,
Peter

akba

That solution is out of my skill level, sorry.
So if I install Web Content Management functionality, then that could be done, right?