Faces Browse and Display

From MPDLMediaWiki
Jump to: navigation, search
FACES
Scope · Functionalities
Disclaimer and Copyright
Support
Application Profiles
Release Agreement
Specification:
Browse and Display · Search
Albums · Users
Note Pads · Versioning
Related Projects:
Imeji
edit

Introduction

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 a new release, earlier states of the spec can be found in the history of this page:

Pictures

UCUse Case_FAC_BD_01 View picture list

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 pictures list in the default display type (Picture View) and the number of hits. The defaults for the sorting order and the number of hits per page are given by the system:
    • sorted by Emotion (alphabetically: anger, disgust, fear, happiness, neutrality and sadness) - Person-IDIdentifier (ascending) - Picture Set (ascending)
    • number of hits per page: 12
  3. (Optionally) The user changes the display type of the picture list.
    3.1 The system displays the picture list in the selected display type.
  4. (Optionally) The user changes the sorting order by changing one or several sorting criteria, one or several ascending/descending arrows and confirms his choice.
    4.1 The system displays the picture list depending on the selected sorting criteria.
  5. (Optionally) The user chooses another number of hits to be displayed per page (12, 24, 60, 90).
    5.1 The system displays the picture list with the selected number of hits per page.
  6. (Optionally) The user goes to a special page, to the last page or to the first page.
    6.1 The system displays the selected page.
  7. Extension point: add pictures to album
    7.1 If the user wants to add pictures to one of his (shared) private albums, include UC_FAC_AM_02 Add picture to album.
  8. The use case ends successfully.

Actors Involved

  • User

UCUse Case_FAC_BD_02 View picture details

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.
  3. Extension point: add pictures to album
    3.1 If the user wants to add pictures to one of his (shared) private albums, include UC_FAC_AM_02 Add picture to album.
  4. The use case ends successfully.

Actors Involved

  • User

UCUse Case_FAC_BD_03 View picture for comparison

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.
  3. Extension point: add pictures to album
    3.1 If the user wants to add pictures to one of his (shared) private albums, include UC_FAC_AM_02 Add picture to album.
  4. The use case ends successfully.

Actors Involved

  • User

Albums

UCUse Case_FAC_BD_04 View album details

Status/Schedule

  • Status: implemented
  • Schedule: R3 (without sharing and note pads)

Motivation

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

Triggers

  • This use case can be included by following use cases

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 Album Metadata Set)
    • the pictures of the album (include UC_FAC_BD_01 View picture list)
    • the number of pictures within the album together with an information when some of this pictures are private visible only (+ their number)
    • all available dates: created, last modified, published, withdrawn
    • the withdrawl comment (the PIDPersistent Identifer or Identification of the album will be crossed out)
    • for shared albums: the user who has done the last modification of the album, all active shared users (user names) and user groups and the owner of the album
    • for shared albums the user is the owner: all shared users (user names for active users and e-mail address for inactive users) inclusive the state of the shared users and all user groups.
  3. Extension point: remove picture from album
    3.1 If the album is in the state pending or submitted, the user is the owner of the album or a shared user of the album and 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 or submitted, the user is the owner of the album or a shared user of the album and wants to edit the album, include UC_FAC_AM_04 Edit album.
  5. Not implemented yet: Extension point: share album
    5.1 If the album is in the state pending and the user is the owner of the album, include UC_FAC_AM_09 Share album.
  6. Not implemented yet: Extension point: unshare album
    6.1 If the album is in the state submitted, the user is the owner of the album and at least one shared user for the album exists, include UC_FAC_AM_11 Unshare album.
  7. Extension point: delete album
    7.1 If the album is in the state pending or submitted, no shared user exists and the user is the owner of the album and wants to delete the album, include UC_FAC_AM_05 Delete album.
  8. Extension point: release album
    8.1 If the album is in the state pending or submitted, the user is the owner of the album and wants to release the album, include UC_FAC_AM_06 Release album.
  9. Extension point: export album
    9.1 If the album is not in the state withdrawn and the user wants to export the pictures of the album, include UC_FAC_AM_08 Export album.
  10. Extension point: withdraw album
    10.1 If the album is in the state released, the user is the owner of the album and wants to withdraw the album, include use case UC_FAC_AM_07 Withdraw album.
  11. Not implemented yet: Extension point: create private note pad
    11.1 If the user is the owner of the album or a shared user of the album and wants to create a private note pad for the album, include use case UC_FAC_NP_01 Create private note pad.
  12. Not implemented yet: Extension point: view note pad
    12.1 If a corresponding note pad in the state pending exists where the user is the owner or a shared user of the note pad and wants to view it, include UC_FAC_NP_02 View note pad.
    12.2 If a corresponding note pad in the state released or withdrawn exists and the user wants to view it, include UC_FAC_NP_02 View note pad.
  13. Not implemented yet: Extension point: view album event log
    13.1 If the user is the owner of the album or a shared user of the album and wants to view the event log of the album, include UC_FAC_VS_01 View album event log.
  14. The use case ends successfully.

Actors Involved

  • Account user

UCUse Case_FAC_BD_05 View album list

Status/Schedule

  • Status: implemented
  • Schedule: R3

Motivation

  • The user wants to overview all his albums that are visible for him.

Pre-Condition

  • One account user is selected.

Triggers

  • This use case can be included by following use cases

Steps

  1. The user chooses to overview all albums that are visible to him (all albums he is the owner of, all albums he shares and all published albums).
  2. The system displays the list of all albums the selected user is allowed to see in the default display type (GridGlobal Release Identifier View) and the number of list entries.
    • The defaults for the sorting order and the number of hits per page are given by the system (by default: date last modified (beginning with the newest date), number of hits per page: 10).
  3. (Optionally) The user changes the sorting order (each metadata can be used as sorting criteria).
    3.1 The system displays the album list in the selected sorting order.
  4. (Optionally) The user filters the displayed albums
    Following filter criteria are available:
    • all my albums
    • my private albums (incl. the ones I am sharing)
    • my public albums
    • all public albums
    • my withdrawn albums
    4.1 The system filters the album list based on the selected filter criteria.
  5. (Optionally) The user chooses another number of hits per page (following numbers are available: 10, 25, 50, 75, 100).
    5.1 The system displays the album list with the selected number of hits per page.
  6. (Optionally) The user goes to a special page, to the last page or to the first page.
    6.1 The system displays the selected page.
  7. Extension point: view album details
    7.1 If the user wants to view the details of a selected album, include UC_FAC_BD_04 View album details.
  8. Not implemented yet: Extension point: copy album content
    8.1 If the user wants to copy the content of one album, include UC_FAC_AM_12 Copy album content.
  9. The use case ends successfully.

Actors Involved

  • Account user

UCUse Case_FAC_BD_07 Resolve album by URLUniform Resource Locator

Status/Schedule

  • Status: implemented
  • 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 URLUniform Resource Locator 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 publishing date
    withdrawn: The publishing and withdrawn dates and the withdrawl comment (the PIDPersistent Identifer or Identification is crossed out)

Actors Involved

  • User

UCUse Case_FAC_BD_08 View file metadata

Status/Schedule

  • Status: implemented
  • 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 XMLExtensible Markup Language) of the selected resolution. The use case ends successfully.

Actors Involved

  • User

Further

UCUse Case_FAC_BD_10 View statistics

Status/Schedule

  • Status: implemented
  • Schedule: R3

Motivation

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

Steps

  1. The user chooses to view the usage statistics for Faces.
  2. The system displays the statistical data of the last 12 months (including the current month) which have been collected per month. The use case ends successfully.

Actors Involved

  • Administrator

UCUse Case_FAC_BD_11 Navigate within one picture

Status/Schedule

  • Status: in design
  • Schedule: ???

Motivation

  • The user wants to analyze one picture. Therfore, the Digilib tool will be used.

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

UCUse Case_FAC_BD_12 View note pad

Status/Schedule

  • Status: in design
  • Schedule: ???

Motivation

  • The user wants to view a note pad.

Pre-Condition

  • One note pad is selected.
  • Further pre-conditions are based on the state of the album:
    pending:
    • For private note pads: the user is the owner of the note pad.
    • For shared note pads: the user shares the notepad or is the owner of the note pad.
    released: None.
    withdrawn: None.

Triggers

  • This use case can be included by following use cases

Steps

  1. The user chooses to view the selected note pad.
  2. The system displays the note pad and its metadata (see Note Pad Metadata Set).
    For shared note pads, additionally following properties will be displayed
    1. For the owner of the note pad:
      • List of shared users (e-mail address, user name) and list of invited users (e-mail address)
    2. For the shared users of the note pad:
      • List of shared users (user name) and number of invited users
  3. Extension point: edit note pad
    3.1 If the note pad is in state pending, the user is the owner or shares the the note pad and wants to edit it, include UC_FAC_NP_02 Edit note pad.
  4. Extension point: delete note pad
    4.1 If the note pad is the state pending, the user is the owner of the note pad and wants to delete it, include UC_FAC_NP_04 Delete note pad.
  5. Extension point: release note pad
    5.1 If the note pad is in the state pending, the user is the owner of the note pad and wants to release it, include UC_FAC_NP_05 Release note pad.
  6. Extension point: withdraw note pad
    6.1 If the note pad is in the state released, the user is the owner of the note pad and wants to withdraw it, include UC_FAC_NP_06 Withdraw note pad.
  7. Extension point: view album details
    7.1 If the user wants to view the album the note pad corresponds to, include UC_FAC_BD_04 View album details.
  8. The use case ends successfully.

Actors Involved

  • Account user