User stories= DOMS Functionality =
Administration of users
- An administrator wishes to update user roles and rights
- An interface exists to do this
NyeFunktioner1
Reporting
- A manager wishes a report of data in DOMS
- An interface exists to get this
NyeFunktioner1
Authorization
- A client wants to access an object in DOMS
- DOMS compares login information to license
- Object is delivered, only if allowed
- Otherwise an error is given
- A method to get a human readable information about license for an object exists
DOMS-102,DOMS-103,DOMS-104,DOMS-121,DOMS-130,DOMS-142,DOMS-23
Backup
- DOMS is backed up at regular intervals
- In case of catastrophic failure, there is a process for recovery
- Backup is bit preserved
DOMS-108,DOMS-109
System malfunctions
- A user experiences what appears to be a problem in the software
- The user contacts HelpDesk
- HelpDesk inspects the error
- HelpDesk resolves the problem OR
- HelpDesk contacts IT development or IT operations for resolution
- IT development or IT operations inspects the error
- Problem is resolved
3.1,3.4
DOMS-110,DOMS-111,DOMS-112
New software versions
- New functionality has been implemented
- IT Development tests the software
- IT Development package the system for IT Operations
- IT Operations installs system in stage
- IT Development and Users test the system
- System is declared OK (or bugs are fixed)
- System is installed in production
- Hilarity ensues
3.2,3.3,4.1,4.2,4.3
API access to DOMS
- An external partner wishes access to DOMS data
- She accesses an API
5.1
DOMS-105,DOMS-119,DOMS-120,DOMS-121
Importing new license
- A new license agreement arises
- The license is expressed as a DOMS license object
- The license object is ingested in DOMS
- Objects with this license are updated
DOMS-130
Importing new or editing old content model
- The content model is expressed in DOMS
- The content model is ingested or updated.
- The content model is applied to objects. The objects are checked.
- If objects already had that content model, they are checked.
DOMS-132
...
Logout
- A user presses log out
- System is no longer acessible
pAbstract
See status???
- Logout/see status
- Search history
- Edit history
- Ask Lars
p36
...
Search to edit/publish
- User searches for data
- Direct clickthrough to edit is available
- Direct clickthrough to publish is available (Misclick protection for direct publishing)
Søgning4
...
Edit locking
- Two users simultanously open a record
- Both users edit it
- Both press save
- The last user is notified that the record has changed
2.10
Strict datamodel enforcement
- A user tries to publish an invalid object
- Error message is human readable and invalid fields are clearly highlighted
- A button is available for checking validity without publishing
Felter3
2.11.3,2.11.4
Identifiable object titles
- A user wishes objects to be identifiable with identifier and human readable labels
- The labels are shown in object trees and search results
- The labels are editable in edit mode
5.2
...
Reorganizable object graph
- A user wants the object graph in a different order
- Drag and drop
- Persistent
Ikoner1
...
Export
- User presses export
- Types in archive number (?!)
- Data is exported as XML to ...?
pAbstract,p13-15,p37
2.9
Print
- A user wishes to print metadata
- He presses a print button
- Metadata is formatted for printing and printed on printer
NyeFunktioner3
Email
- A user wishes to email metadata
- He presses an email button
- Metadata is formatted for emailing
- User uses email program to attach metadata
NyeFunktioner4
...
Download file described from DOMS
- A user finds a record in DOMS
- He selects an object that describes a file
- He clicks the link to the file
- The file is downloaded
DOMS-134,DOMS-143
...
Quick Start
- A new user needs to learn the system
- A guide walks the user through the basics
1.1
Documentation
- A user is unsure how to use the system
- The documentation provides easy-to-access information
1.2
...
Look&Feel
- Better styling and positioning of fields
- Alphabetic sort in dropdown
- Variable width object tree navigation area in left part of screen
- More icons per record to indicate state and properties (archival copy, disemmination copy, ...)
- Use of icons in object hierarchy
- Skinnable by users
Felter1,2
Ikoner3,Ikoner6,Ikoner7,Andet1
2.11.5
...
= Digitization =
Import data from digitization
- A user selects import in interface
- Select source of import
- Data is imported into DOMS
- In case of conflicts, a conflict view is presented
- User presses save
pAbstract,p13-15,p23,p37
Esben5
2.8
File upload
- A user wants to upload a file to preservation
Felter4 (modificeret)
= Radio/TV =
Ingest of Radio and TV
- We have new radio/tv data
- Recordings come as mpeg and wav files
- Metadata comes from Ritzau and Gallup
- Technical metadata comes from FFProbe and Crosscheck
- All metadata is stored in DOMS and available in DOMS-GUI
- Program metadata is stored in PBCore
- All metadata is also stored in original form
- Given object already exists, only new metadata is updated
5.6
DOMS-82,DOMS-83,DOMS-99,DOMS-114,DOMS-115
Radio/TV programs are editable in GUI
- A user wishes to edit program metadata
- He finds the relevant program using search
- He clicks edit
- The relevant fields are editable
- The mandatory fields are marked
- Freeform fields are text areas, other fields are input lines
- Repeatable fields can be repeated, other fields can not.
- There is a field for recording a known bad stream
- User presses save and publish
6.1
DOMS-146
Update of broadcast times of Radio/TV.
- A user finds a program
- He updates time of broadcast in metadata
- This is reflected in dissemination copies
6.2
DOMS-159,DOMS-161,DOMS-162,DOMS-163,DOMS-144,DOMS-147,DOMS-148,DOMS-149,DOMS-150,DOMS-151,DOMS-152,DOMS-153,DOMS-154,DOMS-155,DOMS-158
Radio/TV programs in DOMS disseminated in Mediestream
- A radio/TV program is registered in DOMS
- It is then available in Mediestream for dissemination
DOMS-64
Radio/TV file objects in DOMS ready for digital preservation
- A radio/tv file is regestered in DOMS
- It has sufficient technical metadata for digital preservation
DOMS-75
See subpages for individual user stories.
Points that did not get on a user story subpage are listed below.
Bugs
DOMS-51,DOMS-122,DOMS-127,DOMS-131,DOMS-133,DOMS-140
...
Already implemented
2.2.1,2.2.2,2.5,2.6,2.7
Scrapped
Andet3