Difference between revisions of "ViRR Export"

From MPDLMediaWiki
Jump to navigation Jump to search
(→‎Metadata Export: added short desc.)
Line 46: Line 46:


===UC_VR_E_MD_01 Export xml ===
===UC_VR_E_MD_01 Export xml ===
The user wants to export the metadata of a work.


'''Status/Schedule'''
'''Status/Schedule'''
Line 68: Line 70:


===UC_VR_E_MD_02 Export technical metadata===
===UC_VR_E_MD_02 Export technical metadata===
The user wants to export the metadata of a scan.


'''Status/Schedule'''
'''Status/Schedule'''
Line 85: Line 89:


===UC_VR_E_MD_03 Export to [[DFG Viewer]]===
===UC_VR_E_MD_03 Export to [[DFG Viewer]]===
The user wants to view a work in the DFG-Viewer.


'''Status/Schedule'''
'''Status/Schedule'''

Revision as of 09:15, 18 May 2010

Virr Medium Multivolume 31 Static.gif Virtueller Raum Reichsrecht

Overview
Functionalities
Support
Copyright and Disclaimer
Scope

Metadata:
Application Profile · Content Models
Metadata Display · ViRR Metadata
Action Matrix

Transformations:
virr 2 mets · mab 2 mods
mods 2 oai dc · mods 2 marc21

Specification

Intern:
Meetings · GUI · Miscellaneous
Development · Planning · Feedback
Related Projects:
Judicial Journals · Late Scholasticism
Digitization Lifecycle

edit


Scan Export[edit]

UC_VR_E_PIC_01 Export a single scan[edit]

The user wants to export a single scan.

Status/Schedule

  • Status: provided

Actors

  • Any user

Flow of Events

  • 1. The user wants to export the scan which he is currently viewing
  • 2. Optionally: Extension Point UC_VR_E_MD_02 Export technical metadata. The user can choose to additionally export the technical metadata of that scan.
  • 3. The user can download the picture by using the browser download functionality (right mouse click, download picture)

Comment

  • As this functionality is anyway provided by the browser we will not implement a single scan export additionally


UC_VR_E_PIC_02 Export multiple scans[edit]

The user wants to export multiple scans.

Status/Schedule

  • Status: specified
  • Schedule:tbd

Actors

  • Any user

Flow of Events

  • 1. The user selects one or multiple scans he wants to download.
  • 2. The user can choose the resolution he wants to download (thumbnail, web, full).
  • 3. Optionally: Extension Point UC_VR_E_MD_02 Export technical metadata. The user can choose to additionally export the technical metadata of the scans.
  • 4. The user can choose the format in which he wants to download the selected scans (jpegs as zip, pdf).
  • 5. The system starts to download the scans. The use case ends successfully.

Comment

  • The pdf can be automatically expanded with a cover page containing (identification) information like the origin of the pages, the usage rights, the URL and the bibliographical metadata about the book.


Metadata Export[edit]

UC_VR_E_MD_01 Export xml[edit]

The user wants to export the metadata of a work.


Status/Schedule

  • Status: implemented
  • Schedule:R3.0

Actors

  • Any user

Flow of Events

  • 1. The user chooses a work where he wants to export the metadata.
  • 2. The user can choose in which format he wants to export the metadata (for start only METS/MODS).
  • 3. The system provides a file in the specified format for download. The use case ends successfully.

Comment

  • Further possible formats:
    • MARC21 (transformation already available)?
    • ePub format?
  • Export of a search result (whole or partly)


UC_VR_E_MD_02 Export technical metadata[edit]

The user wants to export the metadata of a scan.


Status/Schedule

  • Status: specified
  • Schedule:tbd

Actors

  • Any user

Flow of Events

  • 1. The user chooses to download the technical metadata of a scan
  • 2. The system offers the xml (currently only JHOVE format) for download. The use case ends successfully.

Comment

A link to the coreservice like in FACES should be sufficient.

UC_VR_E_MD_03 Export to DFG Viewer[edit]

The user wants to view a work in the DFG-Viewer.


Status/Schedule

  • Status: implemented
  • Schedule:R1.5

Actors

  • Any user

Flow of Events

  • 1. The user chooses one work he wants to view in the DFG-Viewer.
  • 2. The system calls the DFG-Viewer with the selected works metadata. The use case ends successfully.