Difference between revisions of "Faces Note Pads"

From MPDLMediaWiki
Jump to navigation Jump to search
Line 105: Line 105:
'''Constraints'''
'''Constraints'''


== UC_FAC_NPM_04 Delete note pad ==
== UC_FAC_NPM_05 Delete note pad ==
'''Status/Schedule'''
'''Status/Schedule'''
* Status: in specification
* Status: in specification

Revision as of 09:34, 28 November 2008

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.

Scenario[edit]

  • 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.
  • The note pad should only be visible for the owner of the album. It can be edited as long as it exists.
  • 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, the owner can decide if he wants to share the note pad, too.
  • When he shares it, the shared users can read and write it (independent from the state of the album). When not, the other users can not see it anyway.

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_NPM_01 Create note pad[edit]

Status/Schedule

  • Status: in specification
  • Schedule: R3.5

Motivation

Expected Outcome

Pre-Condition

Triggers

Steps

Alternatives

Actors Involved

Constraints

UC_FAC_NPM_02 View note pad[edit]

Status/Schedule

  • Status: in specification
  • Schedule: R3.5

Motivation

Expected Outcome

Pre-Condition

Triggers

Steps

Alternatives

Actors Involved

Constraints

UC_FAC_NPM_03 Edit note pad[edit]

Status/Schedule

  • Status: in specification
  • Schedule: R3.5

Motivation

Expected Outcome

Pre-Condition

Triggers

Steps

Alternatives

Actors Involved

Constraints

UC_FAC_NPM_04 Share note pad[edit]

Status/Schedule

  • Status: in specification
  • Schedule: R3.5

Motivation

Expected Outcome

Pre-Condition

Triggers

Steps

Alternatives

Actors Involved

Constraints

UC_FAC_NPM_05 Delete note pad[edit]

Status/Schedule

  • Status: in specification
  • Schedule: R3.5

Motivation

Expected Outcome

Pre-Condition

Triggers

Steps

Alternatives

Actors Involved

Constraints