Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] Stems and attribute definitions

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] Stems and attribute definitions

Chronological Thread 
  • From: Chris Hyzer <>
  • To: Julio Polo <>, "" <>
  • Subject: RE: [grouper-users] Stems and attribute definitions
  • Date: Tue, 24 May 2011 02:39:52 -0400
  • Accept-language: en-US
  • Acceptlanguage: en-US

They are in a stem for namespaces... You can keep them centrally or closer to
where they are used. I don't think we have a recommendation, though I would
think that if you are only going to use the attribute on objects in a certain
folder, you should create them in that folder or an attributes folders in
that folder :) but it is up to you.


-----Original Message-----

On Behalf Of Julio Polo
Sent: Monday, May 23, 2011 9:25 PM

Subject: [grouper-users] Stems and attribute definitions

All examples in
seem to imply that a stem is required when defining an attribute:

studentsAttrDef = attrStudentsStem.addChildAttributeDef("students",

AttributeDef attributeDef = stem.addChildAttributeDef("someName",
AttributeDefType.attr); attributeDef.setAssignToGroup(true);

attributeDef = folder.addChildAttributeDef("attr01", AttributeDefType.attr);

If a stem is indeed required, what is the significance of this stem
with regards to the attribute being defined? Do we just arbitrarily
create a etc:attributes: stem where we define all attributes that we
plan to use? Or is it better if we define attributes closer to where
they'll be actually used? e.g. if I have group3.1, group3.2,
group3.3, group3.4 within stem1:stem2:stem3, is it recommended that i
define attributes to be associated with those groups and their
memberships under stem3?

Julio Polo
University of Hawaii

Archive powered by MHonArc 2.6.16.

Top of Page