Difference between revisions of "ViRR Export"
Jump to navigation
Jump to search
Kleinfercher (talk | contribs) |
Kleinfercher (talk | contribs) (updated uc shortcut) |
||
| Line 3: | Line 3: | ||
==Scan Export== | ==Scan Export== | ||
=== | ===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 | *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_VR_E_PIC_02 Export multiple scans=== | ||
The user wants to export multiple scans. | The user wants to export multiple scans. | ||
| Line 34: | Line 34: | ||
*1. The user selects one or multiple scans he wants to download. | *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). | *2. The user can choose the resolution he wants to download (thumbnail, web, full). | ||
*3. ''Optionally: Extension Point | *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 45: | Line 45: | ||
==Metadata Export== | ==Metadata Export== | ||
=== | ===UC_VR_E_MD_01 Export xml === | ||
'''Status/Schedule''' | '''Status/Schedule''' | ||
| Line 67: | Line 67: | ||
=== | ===UC_VR_E_MD_02 Export technical metadata=== | ||
'''Status/Schedule''' | '''Status/Schedule''' | ||
| Line 84: | Line 84: | ||
A link to the coreservice like in FACES should be sufficient. | A link to the coreservice like in FACES should be sufficient. | ||
=== | ===UC_VR_E_MD_03 Export to DFG Viewer=== | ||
'''Status/Schedule''' | '''Status/Schedule''' | ||
Revision as of 09:10, 18 May 2010
|
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]
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]
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]
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 open calls the DFG-Viewer with the selected works metadata. The use case ends successfully.