Use Case 21: Collaborate with Other Users

From Earth Science Information Partners (ESIP)

Use Case EIE21: Collaborate with Other Users


ESIP Earth Information Exchange

Version 1.0 draft

Prepared by Karl Benedict

Earth Data Analysis Center, University of New Mexico

November 22, 2005

1.Use Case Identification

1.1.Use Case Number


1.2.Use Case Name

Provide an environment that facilitates collaboration between portal members.

2.Use Case Definition

This use case represents the establishment of tools and capabilities within the portal that facilitates collaboration between portal members. These capabilities may include: versioned document sharing, shared calendaring, and threaded discussions.


  • Users
  • Providers
  • Operators


  • 1.User is registered as a member of the portal.
  • 2.User’s identity has been authenticated.
  • 3.User has sufficient privileges to access collaboration tools.


  • 1.Modifications to the content of the collaboration system have been written (for review?)
  • 2.Collaboration system updates have been presented to moderator for review and publication (assuming a moderated approach)

2.4.Normal Flow

  • EIE21.0.1) User logs into the system
  • EIE21.0.2) User is authenticated (if authentication fails go to EIE21.1.1)
  • EIE21.0.3) User is presented summary page with access to collaboration area content: recently updated documents, new calendar events, new discussions.
  • EIE21.0.4) User selects a particular collaboration area for more detailed information: calendar, documents, discussions.
  • EIE21.0.5) User reviews content of specific collaboration area (documents, calendar, discussion)
  • EIE21.0.6) If permitted, user modifies existing content
  • EIE21.0.7) If permitted, user adds new content
  • EIE21.0.8) If permitted, user deleted existing content.

2.5.Alternative Flows

Authentication Failure

  • EIE21.1.1) User fails to authenticate
  • EIE21.1.2) Offer to send authentication information to predefined email location
  • EIE21.1.3) Exit


  • 1.User authentication fails. Log and offer to send login information to contact email address associated with an account
  • 2.Content is modified while user is viewing. Periodically refresh status of content in viewer reflecting whether or not it has been changed since being loaded into the browser.
  • 3.Concurrent edits to the same collaboration content. Attempt to reconcile changes. Prevent updates based upon out of date document versions.

2.7.Extension Points

  • 1.Additional use cases that reflect management of collaboration content may be warranted as extensions to this use case.
  • 2.EIE08 - Manage Working Group (Communities)


Lower (?)

2.9.Frequency of Use

Invoked at least once per session, but more frequently during active collaboration activities.

2.10.Business Rules

  • 1.Collaboration users must be registered as portal users
  • 2.Different roles within the collaboration area may define privileges to add/modify/delete collaboration area content.

2.11.Special Requirements

Clear instructions regarding content management procedures must be made available.



2.13.Notes and Issues

Comprehensiveness of collaboration tools needs to be defined.

The use of moderated vs. unmoderated areas within the collaboration space needs to be considered.

How is the potential for concurrent edits handled in the system?