Faces Browse and Display

From MPDLMediaWiki
Jump to navigation Jump to search
eSciDoc Solutions

PubMan:
Overview · Functionalities
Interfaces · Support

Faces:
Overview · Functionalities
Scope · Support

ViRR:
Overview · Functionalities
Scope · Support

imeji
Digitization Lifecycle

edit


Introduction[edit]

A small glossary for the used terms can be found under Miscellaneous.
Please enter all comments concerning the use cases on the discussion page.

As the current state of the spec focuses on R3, earlier states of the spec can be found in the history of this page:

UC_FAC_BD_01 View picture list[edit]

Status/Schedule

  • Status: implemented
  • Schedule: R1

Motivation

  • The user wants to view several or all pictures of the collection in the list view.

Triggers

Steps

  1. The user chooses to view the whole list of available pictures or executed one of the above mentioned use cases.
  2. The system displays the number of pictures and the list of pictures (list view). The defaults for the sorting order and the number of hits per page are given by the system (by default: sorted by emotion, number of hits per page:12).
    • Sorted by Emotion (default)
    Emotion (alphabetically: anger, disgust, fear, happiness, neutrality and sadness) - Person-ID (ascending) - Picture Set (ascending)
  3. (Optionally) The user changes the sorting order of the first sorting criteria.
    3.1 The system displays the picture list depending from the first sorting criteria in the following order (by default all sorting criteria are ascending):
    • by Age - Person ID - Emotion - Picture Set
    • by Emotion - Person-ID - Picture Set
    • by Gender - Person-ID - Emotion - Picture Set
    • by Person-ID - Emotion - Picture Set
    • by Picture Set - Person-ID - Emotion
  4. (Optionally) The user changes the sorting order of the second, third or forth sorting criteria.
    4.1 The system displays the picture list in the selected sorting order.
  5. (Optionally) The user changes the ascending/descending order of a sorting criteria.
    5.1 The system displays the picture list in the selected sorting order.
  6. (Optionally) The user chooses another number of hits to be displayed per page.
    6.1 The system displays the picture list containing the selected number of hits per page.
  7. (Optionally) The user goes to a special page, to the last page or to the first page.
    7.1 The system displays the selected page.
  8. The use case ends successfully.

Actors Involved

  • User

UC_FAC_BD_02 View picture details[edit]

Status/Schedule

  • Status: implemented
  • Schedule: R1

Motivation

  • The user wants to view one picture in detail (a higher resolution of the picture and its attributes).

Steps

  1. The user selects one picture.
  2. The system displays the picture in the web resolution (detailed view) and all available attributes of the picture. The use case ends successfully.

Actors Involved

  • User

UC_FAC_BD_03 View picture for comparison[edit]

Status/Schedule

  • Status: implemented
  • Schedule: R1

Motivation

  • The user wants to see both picture sets of one image to compare them with each other.

Pre-Condition

  • One picture is selected (in the detailed view).

Steps

  1. The user chooses to view the picture for comparison (same image from the other picture set).
  2. The system displays the picture for comparison next to the selected one in the web resolution. The use case ends successfully.

Actors Involved

  • User

UC_FAC_BD_04 View album details[edit]

Status/Schedule

  • Status: in design
  • Schedule: R3

Motivation

  • The user wants to view the details of an album.

Pre-Condition

  • One album is selected.
  • Further pre-conditions are based on the state of the album:
pending: The user is the owner of the item or has administrator rights.
released: None.
withdrawn: None.

Steps

  1. The user chooses to view the selected album.
  2. The system displays the metadata of the album (see Application Profile Album) and following further information depending on the state of the album:
    pending: The created and last modified dates. If the user is an account user, include UC_FAC_BD_01 View picture list.
    released: The affiliation of the album owner, the PID of the album and its publishing date. If the user is an account user, include UC_FAC_BD_01 View picture list.
    withdrawn: The affiliation of the album owner, the crossed out PID of the album, its publishing and withdrawn dates and the withdrawl comment. If the user is the owner of the item or has administrator rights, include UC_FAC_BD_01 View picture list.
  3. Extension point: remove picture from album
    3.1 If the album is in the state pending and the user wants to remove a picture from the album, include UC_FAC_AM_03 Remove picture from album.
  4. Extension point: edit album
    4.1 If the album is in the state pending and the user wants to edit the album, include UC_FAC_AM_04 Edit album.
  5. Extension point: delete album
    5.1 If the album is in the state pending and the user wants to delete the album, include UC_FAC_AM_05 Delete album.
  6. Extension point: release album
    6.1 If the album is in the state pending and the user wants to release the album, include UC_FAC_AM_06 Release album.
  7. Extension point: export album
    7.1 If the album is in the state pending or released and the user wants to export the pictures of the album, include UC_FAC_AM_08 Export album.
  8. Extension point: withdraw album
    8.1 If the album is in the state released, the user is the owner of the album and he wants to withdraw the album, include use case UC_FAC_AM_07 Withdraw album.
  9. Extension point: add picture to album
    9.1 If the album is in the state released and the user wants to add one of the pictures within the album to one or more of his own pending albums, include use case UC_FAC_AM_02 Add picture to album.
  10. The use case ends successfully.

Actors Involved

  • User

UC_FAC_BD_05 View my albums[edit]

Status/Schedule

  • Status: in design
  • Schedule: R2

Motivation

  • The user wants to overview all his albums (R4: or the administrator wants to overview all albums of a special user).

Triggers

  • This use case can be included by following use cases

Steps

  1. The user chooses to overview his albums.
  2. The system displays the list of all albums the (selected) user is owner of and the number of list entries. In this list are displayed following information about each album: the name, the number of pictures, the description if available, the date last modified and the state. The defaults for the sorting order and the number of hits per page are given by the system (by default: sorted by name (alphabetically), number of hits per page:12).
  3. (Optionally) The user changes the sorting order.
    3.1 The system displays the album list in the selected sorting order.
  4. (Optionally) The user chooses another number of hits to be displayed per page.
    4.1 The system displays the album list containing the selected number of hits per page.
  5. (Optionally) The user goes to a special page, to the last page or to the first page.
    5.1 The system displays the selected page.
  6. Extension point: view album details
    6.1 If the user wants to view the details of a selected album, include UC_FAC_BD_04 View album details.
  7. The use case ends successfully.

Alternatives

1.a R4: The administrator chooses to overview all albums of a selected user. Continue with Step 2.

Actors Involved

  • Account user

UC_FAC_BD_06 View released albums[edit]

Status/Schedule

  • Status: in design
  • Schedule: R2

Motivation

  • The user wants to overview all released albums.

Steps

  1. The user chooses to overview all released albums.
  2. The system displays the list of all released albums and the number of list entries. In this list are displayed following information about each album: the name, the number of pictures, the description if available, the owner, the affiliation of the owner and the date published. The defaults for the sorting order and the number of hits per page are given by the system (by default: sorted by name (alphabetically), number of hits per page:12).
  3. (Optionally) The user changes the sorting order.
    3.1 The system displays the album list in the selected sorting order.
  4. (Optionally) The user chooses another number of hits to be displayed per page.
    4.1 The system displays the album list containing the selected number of hits per page.
  5. (Optionally) The user goes to a special page, to the last page or to the first page.
    5.1 The system displays the selected page.
  6. Extension point: search within album list
    6.1 If the user wants to search within the album list, include UC_FAC_SR_03 Search within list.
  7. The use case ends successfully.

Actors Involved

  • User

UC_FAC_BD_07 Resolve album by URL[edit]

Status/Schedule

  • Status: in design
  • Schedule: R2

Motivation

  • A not logged in user follows a (published) link to a released album.

Steps

  1. The user requests an album by providing the URL assigned by the system for persistently citing the album.
  2. The system displays the metadata of the album (see Application Profile Album) and following further information depending on the state of the album:
    released: The affiliation of the album owner, the PID of the album and its publishing date.
    withdrawn: The affiliation of the album owner, the crossed out PID of the album, its publishing and withdrawn dates and the withdrawl comment.

Actors Involved

  • User

UC_FAC_BD_08 View file metadata[edit]

Status/Schedule

  • Status: in specification
  • Schedule: R3

Motivation

Pre-Condition

  • One picture is selected.

Triggers

Steps

  1. The user chooses to view file metadata about the selected picture.
  2. The system displays the available resolutions (thumbnail, web resolution, original resolution) of the selected picture.
  3. The user chooses one resolution for which he wants to see the file metadata.
  4. The system displays the file metadata (in XML) of the selected resolution. The use case ends successfully.

Actors Involved

  • User

UC_FAC_BD_09 View administrator workspace[edit]

Status/Schedule

  • Status: in specification
  • Schedule: R3

Motivation

  • A user wants to have an overview about all tasks he can perform with his special rights as administrator.

Steps

  1. The user chooses to view the administrator workspace.
  2. The system displays the administrator workspace, where all tasks that can be performed by an administrator are listed.
  3. Extension point: view statistics
    3.1 If the user wants to view the Faces statistics, include UC_FAC_BD_11 View Statistics.
  4. R4: Extension point: view account users
    4.1 If the user wants to get an overview about all account users of Faces, include UC_FAC_BD_10 View account users .
  5. R4: Extension point: create account user
    3.1 If the user wants to create an account user, include UC_FAC_UM_03 Create account user.
  6. The use case ends successfully.

Actors Involved

  • Administrator

UC_FAC_BD_10 View account users[edit]

Status/Schedule

  • Status: in specification
  • Schedule: R4

Motivation

  • The user wants to overview all account users.

Triggers

  • This use case is included by the use cases

Steps

  1. The user chooses to overview all account users.
  2. The system displays the list of all account users and the number of list entries. In this list is following information displayed about each account user: the user-id, the name, the organization, the name of the study for which Faces is used, the state of the account user, the creation date of the account user and possible actions for each account user. The defaults for the sorting order and the number of hits per page are given by the system (by default: sorted by name (alphabetically), number of hits per page: 12).
  3. (Optionally) The user changes the sorting order.
    3.1 The system displays the account user list in the selected sorting order.
  4. (Optionally) The user chooses another number of hits to be displayed per page.
    4.1 The system displays the account user list containing the selected number of hits per page.
  5. (Optionally) The user goes to a special page, to the last page or to the first page.
    5.1 The system displays the selected page.
  6. Extension point: search within list
    6.1 If the user wants to search within the list, include UC_FAC_SR_03 Search within list.
  7. Extension point: edit account user
    7.1 If the user wants to edit a selected account user, include UC_FAC_UM_04 Edit account user.
  8. R4: Extension point: view albums of account user
    8.1 If the user wants to view all albums of a selected account user, include UC_FAC_BD_05 View my albums.
  9. Extension point: deactivate account user
    9.1 If the user wants to deactivate a selected account user, include UC_FAC_UM_05 Deactivate account user.
  10. The use case ends successfully.

Actors Involved

  • Administrator

UC_FAC_BD_11 View statistics[edit]

Status/Schedule

  • Status: in specification
  • Schedule: R3

Motivation

  • The user chooses view the usage statistics (see Faces Statistics) for the Faces solution.

Triggers

  • This use case is included by the use cases

Steps

  1. The user chooses to view the usage statistics for Faces.
  2. The system displays the statistical data for each month (all finalized months and the current one) in a list. The use case ends successfully.

Actors Involved

  • Administrator

Further Development[edit]

Identified Use Cases[edit]

UC_FAC_BD_ Navigate within one picture[edit]

Status/Schedule

  • Status: in specification
  • Schedule: R3.5

Motivation

  • The user wants to analyze one picture.

Pre-Condition

  • One picture is selected (in the detailed view).

Steps

  1. (Optionally) The user zooms in and out within the picture.
  2. (Optionally) The user navigates left, right, up and down within the zoomed picture.
  3. (Optionally) The user switches back to see the whole picture.
  4. The use case ends successfully.

Actors Involved

  • User