Additional version metadata

[JavaJ <po...@yahoo.com>]

For each version of a node, I would like to attach additional metadata such
as the uuid of the user who created the node, a "user-friendly" version
number, user comments, etc.  Has anyone tried to do something similar?

The only way I could see to do this was to add a label for each piece of
metadata.  For example:

label[0] = "user-uuid"
label[1] = "1"
label[2] = "user comments"

The business logic would have to populate and understand the label ordering
of the metadata.  This is a bit awkward, but should work fine as long as the
ordering of the labels are guaranteed.  

Does Jackrabbit/JSR-170 guarantee that the ordering of the labels are
guaranteed?  e.g. if you add label "user-uuid", then "1", then "user
comments", you should expect that when you retrieve the labels they would
come back in the same order.

Thanks!
-- 
View this message in context: http://www.nabble.com/Additional-version-metadata-tf2218551.html#a6145290
Sent from the Jackrabbit - Dev forum at Nabble.com.

Re: Additional version metadata

[JavaJ <po...@yahoo.com>]

That's an interesting idea.  I think I might do that.  Thanks!


David Nuescheler wrote:
> 
> Hi JavaJ,
> 
>> For each version of a node, I would like to attach additional metadata
>> such
>> as the uuid of the user who created the node, a "user-friendly" version
>> number, user comments, etc.  Has anyone tried to do something similar?
> I would recommend to populate the node with additional
> "versioning specific" properties before you check it
> in (maybe in a separate mixin describing your additional meta
> information).
> This should allow any structure of meta-data and also a very
> convenient query.
> 
> regards,
> david
> 
> 

-- 
View this message in context: http://www.nabble.com/Additional-version-metadata-tf2218551.html#a6156679
Sent from the Jackrabbit - Dev forum at Nabble.com.

Re: Additional version metadata

[David Nuescheler <da...@gmail.com>]

Hi JavaJ,

> For each version of a node, I would like to attach additional metadata such
> as the uuid of the user who created the node, a "user-friendly" version
> number, user comments, etc.  Has anyone tried to do something similar?
I would recommend to populate the node with additional
"versioning specific" properties before you check it
in (maybe in a separate mixin describing your additional meta
information).
This should allow any structure of meta-data and also a very
convenient query.

regards,
david