Faces Note Pads

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.
Please enter all comments concerning the use cases on the discussion page.

Scenario

• A note pad should be like an electronic post-it for an album where the user can save private notes.
• It should be about the size of half a page (similar to a text editor).
• As a note pad is like a text document, editing the not pad means editing the whole text.
• Editing an album and editing the related note pad are two separate use cases.
• The note pad should only be visible for the owner of the album. It can be edited as long as it exists.
• When creating an album, its related note pad will be automatically created by the system. Because of this, there is not use case "Create note pad". As for deleting a note pad, that will also happen automatically when deleting the related album. That includes, that it is not possible to delete an note pad by itself (but it is possible to delete all content (text) of the note pad during the use case "edit note pad").
• When releasing/withdrawing the album, the note pad will not be released and is still visible (and editable) for the owner.

Sharing an album

• When sharing an album, each user gets a private note pad for the album + one shared note pad will be available.
• The shared note pad can be read and write by all shared users.

Open points

• Will the note pad be handled like a component of the album?

Not possible, containers are aggregations and they can not have components.--Natasa 07:39, 19 September 2008 (UTC)

• Will the note pad be handled like detailed metadata of the album (similar the the description)?
• As discussed in a meeting with Natasa, Michael, Ulla and me, the note pad can be a separate item (which always stays in the state pending) which will be related to the album. --Kristina 14:23, 18 September 2008 (UTC)

UC_FAC_NP_01 View note pad

Status/Schedule

• Status: in specification
• Schedule: R3.5

Motivation

• The user wants to view a note pad.

Pre-Condition

• One note pad is selected.
• For private note pads: the user is the owner of the notepad.
• For shared note pads: the user shares the notepad.

Triggers

• This use case can be included by following use cases

• UC_FAC_BD_04 View album details

Steps

1. The user chooses to view the selected note pad.
2. The system displays the note pad.
3. Extension point: edit note pad

   3.1 If the user wants to edit the note pad, include UC_FAC_NP_02 Edit note pad.

4. The use case ends successfully.

Actors Involved

• Account user

UC_FAC_NP_02 Edit note pad

Status/Schedule

• Status: in specification
• Schedule: R3.5

Motivation

• The user wants to edit a note pad. (As a note pad is like a text document, editing the not pad means editing the whole text within it.)

Pre-Condition

• One note pad is selected.
• For private note pads: the user is the owner of the notepad.
• For shared note pads: the user shares the notepad.

Triggers

• This use case can be included by following use cases

• UC_FAC_NP_01 View note pad

Steps

1. The user chooses to edit the selected note pad.
2. When the selected note pad is a private note pad, the system displays the edit mask of the note pad.
3. The user edits the note pad and confirms his changes.
4. The system saves the changes of the note pad. The use case ends successfully.

Alternatives

2.a When the selected note pad is a shared note pad, the system checks if it is currently edited by another user.

1. When the note pad is currently edited by another user, the system displays a message (MSG_FAC_AM_01). The use case ends without success. Else, the system displays the edit mask of the note pad. Continue with Step 3.

Actors Involved

• Account user

Coordinated Universal Time

Use Case