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

UC_VR_BD_01 Browse content

Status/Schedule

• Status: in design
• Schedule: R1

Motivation

• The user wants to browse the content of the collection.

Steps

1. The user chooses to browse the content of the collection.
2. The system displays the notation (bibl. metadata in the short display type) of all available multivolumes and monographs within ViRR. By default, the notations should be sorted alphabetically by author/title (see alphabetical list of the digitalized works). Rules for the alphabetical sorting:
   • If the creator is the editor ("HRSG.") or the legislator ("Kaiser"), the title is used as sorting key (=> roleTerm != aut)
   • Else the creator is used as sorting key
3. (Optionally) The user chooses to view the volumes of a selected multivolume.

   3.1. The system displays all volumes of the selected multivolume.

4. Extension point: view multivolume details

   4.1 If the user wants to view the details of a multivolume, include UC_VR_BD_02 View multivolume details.

5. Extension point: view volume or monograph details

   4.1 If the user wants to view the details of a volume or monograph, include UC_VR_BD_03 View volume or monograph details.

6. The use case ends successfully.

Actors Involved

• User

UC_VR_BD_02 View multivolume details

Status/Schedule

• Status: in design
• Schedule: R1

Motivation

• The user wants to see all details of a multivolume.

Triggers

• This use case can be included by the use cases
  • UC_VR_BD_01 Browse content
  • UC_VR_BD_03 View volume or monograph details

Steps

1. The user selects a multivolume.
2. The system displays the bibliographic metadata of the selected multivolume and all its volumes (in the full display type). The use case ends successfully.

Actors Involved

• User

UC_VR_BD_03 View volume or monograph details

Status/Schedule

• Status: in design
• Schedule: R2

Motivation

• The user wants to see all details of a volume or monograph.

Triggers

• This use case can be included by the use cases
  • UC_VR_BD_01 Browse content
  • UC_VR_BD_04 Browse volume or monograph

Steps

1. The user selects a volume or monograph.
2. The system displays the bibliographic metadata of the selected volume or monograph (in the full display type) and if a volume is selected, the notation of the corresponding multivolume in the short view.
3. Extension point: view multivolume details

   3.1 If a volume is selected and if the user wants to view the details of the volume's multivolume, include UC_VR_BD_02 View multivolume details.

4. Extension point: browse volume or monograph

   4.1 If the user wants to browse through the pages of the volume or monograph, include UC_VR_BD_04 Browse volume or monograph.

5. Extension point: view table of contents

   5.1 If the user wants to view the table of contents of the selected volume or monograph, include UC_VR_BD_06 View table of contents.

6. The use case ends successfully.

Actors Involved

• User

UC_VR_BD_04 Browse volume or monograph

Status/Schedule

• Status: in design
• Schedule: R2

Motivation

• The user wants to browse through the pages of a volume or monograph.

Pre-Condition

• One volume or monograph is selected.

Triggers

• This use case can be included by the use cases
  • UC_VR_BD_03 View volume or monograph details
  • UC_VR_BD_06 View table of contents

Steps

1. The user chooses to browse within the selected volume or monograph.
2. The system displays the first content page and the notation (in the full display type) of the volume or monograph.
3. (Optionally) The user chooses to go to the previous, to the next, to the first or to the last page.

   3.1 The system displays the selected page.

4. (Optionally) The user chooses to go to a special physical page number.

   4.1 The system displays the selected page.

5. Extension point: view table of contents

   4.1 If the user wants to view the table of contents of the selected volume or monograph, include UC_VR_BD_06 View table of contents.

6. Extension point: view volume or monograph details

   5.1 If the user wants to view the details of the volume's or monograph's metadate, include UC_VR_BD_03 View volume or monograph details.

7. Extension point: view picture

   6.1 If the user wants to view one picture in its original size, include UC_VR_BD_05 View picture.

8. The use case ends successfully.

Alternatives

1.a The use case has been triggered by UC_VR_BD_06 View table of contents where the user has selected a structural element where he wants to start the browsing.

1. The system displays the first content page of the selected structural element and the notation (in the full display type) of the selected volume or monograph. Continue with Step 3.

Actors Involved

• User

UC_VR_BD_05 View picture

Status/Schedule

• Status: in design
• Schedule: R1

Motivation

• The user wants so view one picture in its original size.

Pre-Condition

• One page is selected.

Triggers

• This use case can be included by the use cases
  • UC_VR_BD_04 Browse volume or monograph

Steps

1. The user chooses to view the picture in its original size.
2. The system displays the selected picture in its original size. The use case ends successfully.

Actors Involved

• User

UC_VR_BD_06 View table of contents

Status/Schedule

• Status: in design
• Schedule: R2

Motivation

• The user wants to view the table of contents of a volume or monograph.

Pre-Condition

• One volume or monograph is selected.

Triggers

• This use case can be included by the use cases
  • UC_VR_BD_03 View volume or monograph details
  • UC_VR_BD_04 Browse volume or monograph

Steps

1. The user chooses to view the table of contents of the selected volume or monograph.
2. The system displays the table of contents (all titles of the structural elements in their hierarchical order and their corresponding start page labels) with all its hierarchy levels open.
3. (Optionally) The user wants to modify the view, in order to see a certain range of open hierarchy levels.

   3.1 The system displays the hierarchy levels in the selected way.

4. (Optionally) The user chooses to view more metadata about a selected structural element within the table of contents.

   4.1 The system displays all available (descriptive) metadata values about the selected structural element.

5. Extension point: browse volume or monograph

   5.1 If the user wants to browse through the pages of the corresponding volume or monograph, he selects a structural element where he wants to start the browsing. Include UC_VR_BD_04 Browse volume or monograph.

6. The use case ends successfully.

Actors Involved

• User

UC_VR_BD_07 View pages in DFG Viewer

Status/Schedule

• Status: in design
• Schedule: R2

Motivation

• To demonstrate the compatibility of ViRR with the DVG viewer, the user should have the possibility to view a selected volume or monograph in the DFG viewer.

Pre-Condition

• One volume or monograph is selected.

Steps

1. The user chooses to view the selected volume or monograph in the DFG viewer.
2. The system opens a new tab, goes to the DFG viewer and displays the first content page of the selected volume or monograph in the DFG viewer (with all its functionalities available). The use case ends successfully.

Actors Involved

• User

UC_VR_BD_08 View editors workspace

Status/Schedule

• Status: in design
• Schedule: R2

Motivation

• The user wants to get an overview about all editing tasks (based on the metadata elements) he can do. This should include the information of the current state of all metadata elements.

Steps

1. The user chooses to view the editors workspace.
2. The system displays the editors workspace with all works within ViRR. For each work, following information about the related container is displayed (if available):
   • date last modified, date released, state

   Each work has following sub-entries (depending on the type of the work):

   • Multivolume: bibliographic metadata (part of the container)
   • Volume: structural content (separate item related to the container)
   • Monograph: bibliographic metadata (part of the container) and structural content (separate item related to the container)

   For each structural content, following information about the related item is displayed (if available):

   • date last modified, date released, state

3. Extension point: edit bibliographic metadata

   3.1 If the user wants to edit the bibliographic metadata of a multivolume or monograph, include UC_VR_ED_08 Edit bibliographic metadata.

4. Extension point: edit structural content

   4.1 If the user wants to edit the structural content in the state "submitted" of a volume or monograph, include UC_VR_ED_01 Edit structural content.

5. Extension point: release structural content

   5.1 If the user wants to release the structural content in the state "submitted" of a volume or monograph, include UC_VR_ED_06 Release structural content.

6. Extension point: modify structural content

   6.1 If the user wants to modify the structural content in the state "released" of a volume or monograph , include UC_VR_ED_07 Modify structural content.

7. The use case ends successfully.

Actors Involved

• Editor

Constraints

• For the bibliographic metadata and the structural content, only the latest version of the container or item will be displayed.

Remarks

• The system can display the editors workspace with a list of all multivolumes, volumes and monographs within ViRR (multivolumes are displayed in the short, volumes in the full display type).
• The system can display the browsing tree of the works within the editors workspace.

Additional Information

States

• The bibliographical metadata are metadata about a released item. This means, that the bibliographical metadata can not change their state without changing the state of their corresponding item. Therefore, they will always be in the state released.
• The structural content is a separate item. Following states are available:
  1. submitted: in the process of being edited, but not finished for a release
  2. released: the editor was finished with the editing of the metadata part and has published it so that all users can view the recorded data

For each state of the metadata parts (structural content, bibliographic metadata) within ViRR, different actions are available:

	State	Actions
Structural Content	"submitted"	edit, release
Structural Content	"released"	modify
Bibliographic Metadata	"released"	edit

Ingestion

• During the ingestion, following metadata parts have automatically be created by the system within the editor workspace:

1. Bibliographic metadata in the state "released" for each ingested multivolume or volume
2. Structural content in the state "submitted" for each ingested monograph or volume

Further Requirements

Quality correction of the pictures

• The black frames should be minimized from the jpgs (Rupert)
• The jpgs will be newly created as jpg 2000 (Technical: Does Digilib needs any special resolution of the pictures?)

Currently there is no native browser support for jpg 2000 (needs a plugin); alternatively via download. --Rupert 11:39, 23 July 2008 (UTC)

Who will provide those images and when? --Wilhelm 16:57, 29 July 2008

• Systematical browsing tree as alternative entrance to the collection´s content (see systematical list of the digitalized works)
• Index list

What should be indexed? --Wilhelm 16:57, 29 July 2008

Detailed views

• Digilib functionalities to navigate within one picture (in the "detailed view")
  • Zooming in, zooming out, framing of a zoom area, switching back to see the whole picture
  • Left, right, up and down navigation within a zoomed picture
  • "View negative" functionality
  • Dynamic creation of a "identification stamp" (Herkunftsnachweis) on all pictures in the "detailed view" (also after zooming)
• METS document in XML of one book

What is the purpose and the content of this METS document? --Wilhelm 16:57, 29 July 2008

Linking to the OPAC of the institute

• Each multivolume, volume or monograph can be linked to the corresponding entry in the OPAC of the institute.

Open Points

• Is a browsing via the names of the documents (law titles) needed?

Use Case

Virtueller Raum Reichsrecht

Deutsche Forschungsgemeinschaft

Web Based Server Technology for Viewing and Working with Images

Coordinated Universal Time

Metadata Encoding and Transmission Standard

Extensible Markup Language

Online Public Access Catalogue