Faces Browse and Display

eSciDoc Solutions PubMan: Overview · Functionalities Interfaces · Support Faces: Overview · Functionalities Scope · Support ViRR: Overview · Functionalities Scope · Support imeji Digitization Lifecycle edit

Introduction

A small glossary for the used terms can be found under Miscellaneous.

UC_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

• This use case can be included by the use cases
  • UC_FAC_SR_01 Search within the collection
  • UC_FAC_SR_02 View all pictures of one person
  • UC_FAC_BD_05_View album details

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

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

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 Navigate within one picture

Status/Schedule

• Status: in specification
• Schedule: R3

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

UC_FAC_BD_05 View album details

Status/Schedule

• Status: in design
• Schedule: R2

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:

State
submitted	The user is the owner of the item.
released	None.
withdrawn	The user is the owner of the item.

Steps

1. The user chooses to view the selected album.
2. The album is in the state released. The system displays the name of the album, the owner of the album, the affiliation of the owner, the album description if available, the PID of the album and its publishing date. Include UC_FAC_BD_01 View picture list.
3. Extension point: export album

   3.1 If the user wants to export the pictures of the album, include UC_FAC_AM_09 Export album.

4. The use case ends successfully.

Alternatives

2.a The album is in the state "withdrawn". The system displays the name of the album, the owner of the album, the affiliation of the owner, the album description if available, the crossed out PID of the album, its publishing and withdrawn date and the withdrawl comment. Include UC_FAC_BD_01 View picture list.

1. The use case ends successfully.

2.b The album is in the state submitted. The system displays the name of the album, the album description if available and the created and last modified dates. Include UC_FAC_BD_01 View picture list.

1. Extension point: remove picture from album

1.1 If the user wants to remove a picture from the album, include UC_FAC_AM_04 Remove picture from album.

2. Extension point: rename album

2.1 If the user wants to rename the album or change its description, include UC_FAC_AM_05 Edit album.

3. Extension point: delete album

3.1 If the user wants to delete the album, include UC_FAC_AM_06 Delete album.

4. Extension point: release album

4.1 If the user wants to release the album, include UC_FAC_AM_07 Release album.

5. The use case ends successfully.

4.a The user is the owner of the album.

1. Extension point: withdraw album

1.1 If the user wants to withdraw the album, include use case UC_FAC_AM_08 Withdraw album.

2. The use case ends successfully.

Actors Involved

• Account user

UC_FAC_BD_06 View my albums

Status/Schedule

• Status: in design
• Schedule: R2

Motivation

• The user wants to overview all his albums.

Steps

1. The user chooses to overview his albums.
2. The system displays the list of all albums the 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: search within album list

   6.1 If the user wants to search within the album list, include UC_FAC_SR_03 Search within album list.

7. The use case ends successfully.

Actors Involved

• Account user

UC_FAC_BD_07 View released albums

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 album list.

7. The use case ends successfully.

Actors Involved

• User

UC_FAC_BD_08 Resolve released album by URL

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 a released album by providing the URL assigned by the system for persistently citing the released album.
2. The system displays the metadata of the released album (not the pictures) and a message (MSG_FAC_AM_06). The use case ends successfully.

Actors Involved

• User

Further Development

Identified Use Cases

• UC_FAC_BD_ View technical metadata -->R3

Use Case

Identifier

Persistent Identifer or Identification

Uniform Resource Locator