Vista Combinata Vista Piatta Vista ad Albero
Discussioni [ Precedente | Successivo ]
toggle
James Denmark
Tagging assets should be easier
10 ottobre 2012 11.39
Risposta

James Denmark

Punteggio: Junior Member

Messaggi: 27

Data di Iscrizione: 19 novembre 2008

Messaggi recenti

Tagging a document during upload or web content while creating is quite easy but often community administrators want to go through and add more tags, change tags and perform other housekeeping of asset tags.

Currently this requires the asset to go through the edit action which has a number of shortcomings:
1. Time consuming
2. Increments version history of the asset
3. Triggers notifications on things like message board posts, rss feeds etc.

Tagging would be more functional if administrators and asset owners could add/remove tags dynamically without executing the edit action. i.e. right on the actions menu for an asset, include a categorize and/or tag action that will apply the tags but won't 'republish' the asset.

Additionally, in things like the documents and media portlet, this action should be available at the container (folder/store) level to permit the administrator to tag multiple items with in one pass.
Hamish Campbell
RE: Tagging assets should be easier
10 ottobre 2012 15.38
Risposta

Hamish Campbell

Punteggio: Junior Member

Messaggi: 87

Data di Iscrizione: 20 agosto 2008

Messaggi recenti

yep, like the idea.
Hitoshi Ozawa
RE: Tagging assets should be easier
10 ottobre 2012 15.42
Risposta

Hitoshi Ozawa

Punteggio: Liferay Legend

Messaggi: 7990

Data di Iscrizione: 23 marzo 2010

Messaggi recenti

+1 Categories too.

2. Increments version history of the asset
3. Triggers notifications on things like message board posts, rss feeds etc.


Prefer these to be only triggered when content is added/modified and not when attributes are added/modified.
Prefer to have properties to select when to trigger.
Jorge Ferrer
RE: Tagging assets should be easier
23 dicembre 2012 7.18
Risposta

Jorge Ferrer

LIFERAY STAFF

Punteggio: Liferay Legend

Messaggi: 2756

Data di Iscrizione: 31 agosto 2006

Messaggi recenti

I like the idea too. Although I'm not 100% sure about not incrementing the version number. In that case it would not be possible to keep track of changes in the tags or categorization.
Juan Fernández
RE: Tagging assets should be easier
24 dicembre 2012 1.11
Risposta

Juan Fernández

LIFERAY STAFF

Punteggio: Liferay Legend

Messaggi: 1227

Data di Iscrizione: 2 ottobre 2008

Messaggi recenti

+1!

Jorge Ferrer:
... I'm not 100% sure about not incrementing the version number. In that case it would not be possible to keep track of changes in the tags or categorization.


I think versioning makes sense when you modify the actual content, not the information around. You don't want to track versioning in things like display data, notification configuration, related assets, display pages (in web content)... or tags and categories. These are external "attributes" as Hitoshi said, and shouldn't always lead to reestarting a workflow process or incrementing the version.

Just my opinion emoticon
Jorge Ferrer
RE: Tagging assets should be easier
24 dicembre 2012 1.40
Risposta

Jorge Ferrer

LIFERAY STAFF

Punteggio: Liferay Legend

Messaggi: 2756

Data di Iscrizione: 31 agosto 2006

Messaggi recenti

Since you mentioned workflow, that makes things even more complicated. Do people want to review the tags, categories, etc. when an approval workflow is enabled?

I would say that in some (most?) cases they do. If so, then changing any of those need to be a new version that has to go through the approval process.

Also, even without workflow, in the context of several admins, it is sometimes important to be able to undo any change and if the versioning is not used when updating metadata then it is not possible to undo that change.

Do you guys think these considerations should not be taken into account?
Gaurav Jain
RE: Tagging assets should be easier
24 dicembre 2012 2.40
Risposta

Gaurav Jain

Punteggio: Regular Member

Messaggi: 141

Data di Iscrizione: 31 gennaio 2011

Messaggi recenti

James Denmark:
Additionally, in things like the documents and media portlet, this action should be available at the container (folder/store) level to permit the administrator to tag multiple items with in one pass..

Liked this.

I even prefer some more actions, like export on folder levels (or ability to select which folder data to export).
But, yes that is out of current topic emoticon

So, +1 from me
James Denmark
RE: Tagging assets should be easier
24 dicembre 2012 7.52
Risposta

James Denmark

Punteggio: Junior Member

Messaggi: 27

Data di Iscrizione: 19 novembre 2008

Messaggi recenti

I can see both cases continuing to be required so I guess it really comes down to the fact that editing metadata and editing content are both captured under a single edit action and these should probably be split into two actions.

e.g. I want admins to create/edit content but I'm happy for site members to tag it - to do this now they I would have to give the site member edit permissions.

If the content and metadata edit actions were separated (just like the models are) I could enable metadata editing without content editing. In addition, the kaleo workflows/versioning could be turned on/off for each action independently to suit either case.