Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

A group may be classified , according to the to APS 2.6 and UW Data Classification  guidelinesProcess.

The API attribute class is "classification" and may have the values:

...

  • Effective members: An effective member is either a direct member of the group or an effective member of a member group

Use of POST method

The Groups API accepts the POST method for two purposes:

URI too long
If your uri would be too long for likely transport to the web service you may enclose it in a POST, with the elements:

...

Code Block
<span class="_method"> GET | PUT | DELETE </span>
<span class="_uri"> uri </span>

included in the POST document.  The path components of you actual URL must match those in the posted "_uri".

PUT content too big
If your PUT content would be too big for likely transport to the web service you may enclose it in a POST, with the element:

...

Code Block
<span class="_method">PUT</span>

...

Large membership changes

If you are making large membership changes, say more than a few hundred, your experience will be better if you split your activity into adds or deletes of fifty to a hundred members at a time.  This tends to give you immediate feedback on successful changes and avoids possible session or connection timeouts.

API Resources

Versions

Groups API supports version v1, v2 and v3 (recommended). 

...

Email help@uw.edu to contact the staff in UW-IT who oversee this wiki space and the groups service.

Announcements : Join groups-announce@uw.edu for service announcements.

Discussion : Discuss the service with other customers and users on groups-users@uw.edu.