Primary Use Cases

User Management

High-level description of the user management use cases.

Use-case attributes

  • Users are identified by a unique identifier, referred to as the user’s UID.

  • Groups consist of zero or more users and are identified by a unique identifier, referred to as the group’s GID.

  • Users may belong to a given group (groups are semantically equivalent to roles).

  • Users may belong to one or more groups simultaneously.

  • Users may map different UIDs to a single “real” identity.

Use-case scenarios

  1. Create a new user

  2. Create a new group (not implemented)

  3. Add a user to a group (not implemented)

  4. Remove a user from a group (not implemented)

  5. Delete a user

  6. Delete a group (not implemented)

  7. List all users in the system

  8. List all groups in the system (not implemented)

  9. List users in a group (not implemented)

  10. List groups a user belongs to (not implemented)

  11. A user logs into the system

  12. A user logs out of the system

  13. A user changes their password

  14. A user changes their email address

  15. A user changes their real name

Data Package Management

High-level description of the data package management use cases:

Use-case attributes

  • A data package is identified by a unique identifier, referred to as the package’s PID.

  • A data package is associated with a single user, referred to as the principal owner of the package.

  • A data package must be described by an Ecological Metadata Language (EML) document.

  • A data package must describe one or more data objects.

  • A “private” data package is one that is accessible only to the principal owner of the data package.

  • Accessibility to a data package must be explicitly granted within the EML document associated with the data package.

  • A “publicly accessible” data package is one that is accessible to all users of the system.

Use-case scenarios

  1. Create a new user

Audit Log Management

High-level description of the audit log management use cases:

Use-case attributes

  • An audit log entry contains the following attributes and attribute types:

    1. oid integer (primary key),

    2. entryTime timestamp,

    3. service string,

    4. category string,

    5. serviceMethod string,

    6. entryText string,

    7. resourceId string,

    8. statusCode integer,

    9. userid string,

    10. userAgent string,

    11. groups string,

    12. authSystem string

Use-case scenarios

  1. Create a new user