Difference between revisions of "Talk:ViRR Scope"

From MPDLMediaWiki
Jump to navigation Jump to search
Line 1: Line 1:
ToDo's, comments for each Rélease
ToDo's, comments for each Release:


== FIRST PHASE - Publication of the digital collection ==
== FIRST PHASE - Publication of the digital collection ==
Line 16: Line 16:
#* browsing tree (books and pages), sorted alphabetically by title
#* browsing tree (books and pages), sorted alphabetically by title


ToDos:
'''ToDo:'''
*  ingestion of bibliografic data: either mapping MAB to eSciDoc XML or to Dublin Core, or enter data manually (evaluation by inga?)
*  ingestion of bibliografic data: either mapping MAB to eSciDoc XML or to Dublin Core, or enter data manually (evaluation by inga?)
* relation to eSciDoc METS profile (first draft based on Ingas mapping ebinds<=>METS)?
* relation to eSciDoc METS profile (first draft based on Ingas mapping ebinds<=>METS)?


''Already some input from Inga: Generic Mapping MAB=> eSciDoc is not of great help, as MAB is poor in bibliografic information, in addition, each MAB user uses his own adapted MAB and using MAB means running into severe character set problems. If a mapping is needed, mapping to DC might be sufficient. In addition, instead of mapping, manual data entry should be considered, especially when dealing only with 2 books. In any case, new "eSciDoc VIRR profile" might be needed, as genre types and current PubMan Metadata won't cover the VIrr material. ''
''Already some input from Inga: Generic Mapping MAB=> eSciDoc is not of great help, as MAB is poor in bibliographic information, in addition, each MAB user uses his own adapted MAB and using MAB means running into severe character set problems. If a mapping is needed, mapping to DC might be sufficient. In addition, instead of mapping, manual data entry should be considered, especially when dealing only with 2 books. In any case, new "eSciDoc VIRR profile" might be needed, as genre types and current PubMan Metadata won't cover the VIrr material. ''
* improve quality of image files (based on TIFFs) => for improved thumbnails + additional resolution for web presentation => check concrete requs with Institute ("schwarze Ränder" on TIFFs would have to be done by institute). Check requirements for resolution needed by digilib
* improve quality of image files (based on TIFFs) => for improved thumbnails + additional resolution for web presentation => check concrete requs with Institute ("schwarze Ränder" on TIFFs would have to be done by institute). Check requirements for resolution needed by digilib
* functional prototype for Display and browsing
* functional prototype for Display and browsing
Line 32: Line 32:
#* editing via simple edit mask or already with METS editor (selection of Editor depends on eSciDoc METS profile)
#* editing via simple edit mask or already with METS editor (selection of Editor depends on eSciDoc METS profile)


'''TO DO:'''  
'''ToDo:'''  
* prepare first draft eSciDoc METS profile (based on bibliografic data needed, descriptive data needed)
* prepare first draft eSciDoc METS profile (based on bibliographic data needed, descriptive data needed)
* decide on recommended METS editor
* decide on recommended METS editor
* prepare requirements for FIZ for the METS integration
* prepare requirements for FIZ for the METS integration
Line 39: Line 39:
=== Release three ===
=== Release three ===


# Display (detailled)
# Display (detailed)
#* integration of digilib functionalities (minimum: zoom in, zoom out)
#* integration of digilib functionalities (minimum: zoom in, zoom out)
#* dynamic generation and integration of "identification stamp" ("Herkunftsnachweis") on the images (whole image, selected part of image) --> new Digilib requirement
#* dynamic generation and integration of "identification stamp" ("Herkunftsnachweis") on the images (whole image, selected part of image) --> new Digilib requirement
# Browsing (detailled)
# Browsing (detailed)
#* extension of the alphabetical browsing tree (chapters)
#* extension of the alphabetical browsing tree (chapters)
#* chronological navigation  on book and/or chapter level?(depends on descriptive Metadata! )
#* chronological navigation  on book and/or chapter level?(depends on descriptive Metadata! )
Line 63: Line 63:
# Display keywords as list (cf. Index in a book)
# Display keywords as list (cf. Index in a book)
# Persistent Identifier (PID)
# Persistent Identifier (PID)


== SECOND PHASE - Virtual research environment ==  
== SECOND PHASE - Virtual research environment ==  
Following is a list of requirements to be met...detailled release planning at a later stage.
 
Following is a list of requirements to be met...detailed release planning at a later stage.


* Workflow for edition process of collection, incl. metadata, images, annotations, external sources (upload, editing, annotating, scientific review etc.)
* Workflow for edition process of collection, incl. metadata, images, annotations, external sources (upload, editing, annotating, scientific review etc.)
* User Management to support workflow
* User Management to support workflow
* Fulltext transcription online (offline client at later stage) - in METS
* Fulltext transcription online (offline client at later stage) - in METS
* Ingestion/Upload of additional books (digital images + bibliographic metadata) - local ressources, BBAW-DTA
* Ingestion/Upload of additional books (digital images + bibliographic metadata) - local resources, BBAW-DTA
* Adding and editing of bibliografic and descriptive metadata  
* Adding and editing of bibliographic and descriptive metadata  
* Adding annotations
* Adding annotations
* Adding relations
* Adding relations
* Adding comments
* Adding comments
* Integration of external ressources (Deutsches Rechtswoerterbuch/Heidelberg)
* Integration of external resources (Deutsches Rechtswoerterbuch/Heidelberg)
* Creation and maintenance of synonyms  
* Creation and maintenance of synonyms  
* Offering metadata to the ZVDD and other virtual libraries - OAI interface
* Offering metadata to the ZVDD and other virtual libraries - OAI interface
* Sitemap protocol for crawlers
* Sitemap protocol for crawlers
* Integration of research literature for download (bibliografic lists? articles?)
* Integration of research literature for download (bibliographic lists? articles?)
* Linking to other digital archives / OPACs /research projects
* Linking to other digital archives / OPACs /research projects


 
'''ToDo:'''
'''TO DO:'''
* Structural analyzes of the data of the Deutsche Rechtswörterbuch  
* Structural analyzes of the data of the Deutsche Rechtswörterbuch  
* Analyzes of the requirements of the ZVDD
* Analyzes of the requirements of the ZVDD
* Text editor for the creation of transcriptions is needed
* Text editor for the creation of transcriptions is needed


== THIRD PHASE - Productive environment ==
== THIRD PHASE - Productive environment ==
* Preparation of productive environment (hardware, support, policies)
* Preparation of productive environment (hardware, support, policies)
* Offline tool for image processing to improve image quality
* Offline tool for image processing to improve image quality

Revision as of 15:48, 30 January 2008

ToDo's, comments for each Release:

FIRST PHASE - Publication of the digital collection[edit]

Release one[edit]

  1. Ingestion
    • scans --> derive from file structure a first skeleton of toc (name of book, sequence of pages)
    • bibliographic metadata (currently in MAB) - either entered manually or ingested
    • derive basic keywords from title of book (to be checked with institute)
  2. Display (basic)
    • thumbnail lists
    • basic bibliographic metadata (name of book, page)
    • scans
  3. Browsing (basic)
    • browsing tree (books and pages), sorted alphabetically by title

ToDo:

  • ingestion of bibliografic data: either mapping MAB to eSciDoc XML or to Dublin Core, or enter data manually (evaluation by inga?)
  • relation to eSciDoc METS profile (first draft based on Ingas mapping ebinds<=>METS)?

Already some input from Inga: Generic Mapping MAB=> eSciDoc is not of great help, as MAB is poor in bibliographic information, in addition, each MAB user uses his own adapted MAB and using MAB means running into severe character set problems. If a mapping is needed, mapping to DC might be sufficient. In addition, instead of mapping, manual data entry should be considered, especially when dealing only with 2 books. In any case, new "eSciDoc VIRR profile" might be needed, as genre types and current PubMan Metadata won't cover the VIrr material.

  • improve quality of image files (based on TIFFs) => for improved thumbnails + additional resolution for web presentation => check concrete requs with Institute ("schwarze Ränder" on TIFFs would have to be done by institute). Check requirements for resolution needed by digilib
  • functional prototype for Display and browsing
  • start collecting requirements for the viewing environment DigiLib and set up meeting with user group (Contact@FIZ: Frank Schwichtenberg) (Kristina, Tobias)

Release two[edit]

  1. Editing
    • enrich toc sceleton with information on chapters (i.e. bundles)(e.g. page 1-5 = chapter 1)
    • add metadata about the chapters, e.g. keywords
    • editing via simple edit mask or already with METS editor (selection of Editor depends on eSciDoc METS profile)

ToDo:

  • prepare first draft eSciDoc METS profile (based on bibliographic data needed, descriptive data needed)
  • decide on recommended METS editor
  • prepare requirements for FIZ for the METS integration

Release three[edit]

  1. Display (detailed)
    • integration of digilib functionalities (minimum: zoom in, zoom out)
    • dynamic generation and integration of "identification stamp" ("Herkunftsnachweis") on the images (whole image, selected part of image) --> new Digilib requirement
  2. Browsing (detailed)
    • extension of the alphabetical browsing tree (chapters)
    • chronological navigation on book and/or chapter level?(depends on descriptive Metadata! )
    • paginator (for lists)
    • paging for images (i.e. "im Buch blaettern")
  3. Search
    • simple search (one search field "any field")
    • advanced search (several special search fields, e.g. one for title, one for author)

Release four[edit]

  1. Functional definition of eSciDoc METS profile
    • needed for import / export
  2. Export
    • image selection
    • downloading/printing of selected images(in separate jpgs)
    • downloading/printing of selected images(in one pdf with a cover page)
    • downloading/printing selected part of an image
    • downloading of METS-xml
  3. Display keywords as list (cf. Index in a book)
  4. Persistent Identifier (PID)


SECOND PHASE - Virtual research environment[edit]

Following is a list of requirements to be met...detailed release planning at a later stage.

  • Workflow for edition process of collection, incl. metadata, images, annotations, external sources (upload, editing, annotating, scientific review etc.)
  • User Management to support workflow
  • Fulltext transcription online (offline client at later stage) - in METS
  • Ingestion/Upload of additional books (digital images + bibliographic metadata) - local resources, BBAW-DTA
  • Adding and editing of bibliographic and descriptive metadata
  • Adding annotations
  • Adding relations
  • Adding comments
  • Integration of external resources (Deutsches Rechtswoerterbuch/Heidelberg)
  • Creation and maintenance of synonyms
  • Offering metadata to the ZVDD and other virtual libraries - OAI interface
  • Sitemap protocol for crawlers
  • Integration of research literature for download (bibliographic lists? articles?)
  • Linking to other digital archives / OPACs /research projects

ToDo:

  • Structural analyzes of the data of the Deutsche Rechtswörterbuch
  • Analyzes of the requirements of the ZVDD
  • Text editor for the creation of transcriptions is needed


THIRD PHASE - Productive environment[edit]

  • Preparation of productive environment (hardware, support, policies)
  • Offline tool for image processing to improve image quality
  • Fulltext transcription in TEI?
  • Additional functionality for historisch-kritische Editionsarbeit?
  • Concept ViRR for other local/MPG projects (e.g. Policey-Ordnung)