Difference between revisions of "ViRR Export"

From MPDLMediaWiki
Jump to navigation Jump to search
 
(7 intermediate revisions by one other user not shown)
Line 3: Line 3:
==Scan Export==
==Scan Export==


===UC_E_PIC_01 Export a single scan===
===UC_VR_E_PIC_01 Export a single scan===
The user wants to export a single scan.
The user wants to export a single scan.


Line 14: Line 14:
'''Flow of Events'''  
'''Flow of Events'''  
*1.  The user wants to export the scan which he is currently viewing
*1.  The user wants to export the scan which he is currently viewing
*2.  ''Optionally: Extension Point UC_E_MD_02 Export technical metadata.'' The user can choose to additionally export the technical metadata of that scan.
*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)
*3.  The user can download the picture by using the browser download functionality (right mouse click, download picture)


Line 21: Line 21:




===UC_E_PIC_02 Export multiple scans===
===UC_VR_E_PIC_02 Export multiple scans===
The user wants to export multiple scans.
The user wants to export multiple scans.


Line 33: Line 33:
'''Flow of Events'''  
'''Flow of Events'''  
*1.  The user selects one or multiple scans he wants to download.
*1.  The user selects one or multiple scans he wants to download.
**1.1. Optionally: The user can choose to download all scans of a work.
*2.  The user can choose the resolution he wants to download (thumbnail, web, full).
*2.  The user can choose the resolution he wants to download (thumbnail, web, full).
*3.  ''Optionally: Extension Point UC_E_MD_02 Export technical metadata.'' The user can choose to additionally export the technical metadata of the scans.
*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).
*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.
*5.  The system starts to download the scans. The use case ends successfully.
Line 41: Line 42:
* 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.
* 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==


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


==Metadata Export==
===UC_E_MD_01 Export xml ===


'''Status/Schedule'''
'''Status/Schedule'''
Line 60: Line 61:


'''Comment'''
'''Comment'''
* Further possible formats:
* Further possible formats:
** MARC21 (transformation already available)?
** MARC21 (transformation already available)?
Line 66: Line 66:
* Export of a search result (whole or partly)
* Export of a search result (whole or partly)


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


===UC_E_MD_02 Export technical metadata===


'''Status/Schedule'''
'''Status/Schedule'''
Line 84: Line 85:
A link to the coreservice like in FACES should be sufficient.
A link to the coreservice like in FACES should be sufficient.


===UC_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'''
Line 95: Line 98:
'''Flow of Events'''  
'''Flow of Events'''  
*1.  The user chooses one work he wants to view in the DFG-Viewer.
*1.  The user chooses one work he wants to view in the DFG-Viewer.
*2.  The system open calls the DFG-Viewer with the selected works metadata. The use case ends successfully.
*2.  The system calls the DFG-Viewer with the selected works metadata. The use case ends successfully.
 




[[Category:Virtueller Raum Reichsrecht|Future Scenarios]]
[[Category:Virtueller Raum Reichsrecht|Export]]
[[Category:VIRR_Functional_specification | Export]]
[[Category:VIRR_Functional_specification |Export]]

Latest revision as of 12:28, 3 August 2011

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.
    • 1.1. Optionally: The user can choose to download all scans of a work.
  • 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.

Use Case

Metadata

Portable Document Format

Uniform Resource Locator

Metadata Encoding and Transmission Standard

Metadata Object Description Schema

JSTOR Harvard Object Validation Environment

Deutsche Forschungsgemeinschaft

Retrieved from "https://colab.mpdl.mpg.de/mw010/index.php?title=ViRR_Export&oldid=66953"