ViRR Meetings

MPDL

Meeting, Release 3
Outcome of prototype handover meeting (5th. Feb. 2010). Malte, Ulla, Rupert, Willy, Markus M., Markus H., Bastien, Rike

Decisions:
 * Runmaster: Rupert
 * Runteam: Markus H., Markus M., Rike
 * Schedule: End of March 2010

Prototype Discussion: Action Menu:
 * Description / Beschreibung
 * ISBD / ISBD
 * List / Liste (default)


 * Browse / Ansehen (only for monographs and volumes) - Alternative: Document / Dokument
 * Image / Bild
 * Outline / Gliederung
 * Image & Outline / Bild & Gliederung (default)
 * Details / Details


 * Export / Export (only for monographs and volumes)
 * DFG Viewer / DFG Viewer
 * METS/MODS / METS/MODS - Alternative: XML / XML


 * Edit Structure / Struktur Bearbeiten (only for logged in users, only for monographs and volumes)
 * Pagination / Paginierung (default)
 * Outline / Gliederung
 * Details / Details
 * Assign Pages / Seiten zuweisen
 * Publish / Veröffentlichen (only enabled when a pending version exists)


 * Edit Details/ Details Bearbeiten (only for logged in users, only for multivolumes and monographs) = > Edit bibliographic metadata

Page Discussion:
 * General: Only existing functionality will come in the new GUI release, therefore all not yet existing func in the prototype can be ignored (e.g. search, sort...).
 * Collection Systematically: Page not needed
 * Browse Collection:
 * It should be possible to expand and collapse the volumes under a multivolume
 * When clicking on a volume or a monograph one comes directly to Browse, when clicking on a multivolume one comes to Description.
 * The status of the last TOC version, last modification date and last published date must be visible for logged in users.
 * View Structure + View options:
 * No 'veröffentlichen' Button here
 * When clicking on 'Image' one comes to the full view of a scan (single column). When clicking on 'Outline' one comes to the full view of a TOC. TODO: enhance prototype with this pages
 * No notation
 * Edit Volume 2.:
 * Show options are missing (pages, title, structural element)
 * Edit Volume 3.:
 * Possibility is missing to delete all pages of a structural element
 * Confirmation page:
 * TODO: Enhance prototype
 * Homepage:
 * Left side: startpage text (like current ViRR version).
 * Right side: Random picture which switches on every side call (all title pages within the collection). For more details ask Rike. Example: http://www.archive.org/details/millionbooks
 * View Details (Volume + Monograph) Page
 * Include thumbnail picture

Meeting, Plan for 2010 - 12.01.2010
Participants: Malte, Natasa, Ulla, Rupert, Willy, Rike

Aim: What are the next steps in the ViRR development


 * Ingest on live server - Estimated start: KW3
 * GUI: Define fixed scan 'stage'. (First step, KW2)
 * Ingest: Generate web res. depending on this stage size (make sure to keep aspect ratio).


 * Ingest on demo server
 * To be started after ingest on live is finished.


 * Bugfix Release (2.7) - Estimated end of January
 * Display of wrong TOC - done
 * Role and Rights problem (only user who ingested a book may edit it) - done
 * Some GUI issues (Rupert and Rike check)
 * Implementation of the stage (especially resizing of the image)
 * Image should not be scaled, just placed in the stage (like dfg viewer)
 * Define background of stage
 * Test of Bugfix Release by Rike, KW4


 * Schedule of ViRR Gui V2 Release - Estimated April
 * Dev start in March, optimistic end of feb. as Markus M. should not be too involved in Pubman6.1.
 * Runmaster: To be decided by end of February (Rupert or Markus M.)
 * April: Test by Rike


 * Discussion of the Project plan from the institute
 * The decision of the extend of a next functional release can not be done before May and will be in the scope of the digilifecycle project.

Meeting, Shape future Releases - 21.07.2009
Participants: Willy, Markus H., Markus M.,Rike i: Requirement from institute p: Needed for productive use

R2.6 (Ingest Release)
Roughly planned for Oct.


 * p Help (context-sensitive), text is ready.
 * No big issue, probably a day


 * p Integration of  Disclaimer/Copyright
 * i Display Metadata in  ISBD style
 *  Spec will be checked by Willy


 * Tool for automated jpeg creation
 * To be checked by Willy


 * p Ingest of all books (new metadata profile)
 * R2.5 Leftovers and Testresults

R3.0 (Technical Release)
Roughly planned end of Year


 * p Bookmarkable pages/nice URLs
 * For this we would need to implement JSF2 with PrettyFaces, this would approx. take 3 weeks for one person. Further tests needed.


 * i Google-enabling
 * For start we can implement a sitemap, would probably only take a few days


 * p GUI V2
 * Rupert has to provide functional prototype. Implementation approx. 2 weeks


 * p Tooltips
 * Will be addressed by Markus H. and Rike, probably a day


 * i GUI Leftovers
 * p Integration of Copyright in Metadata (machine readable)?
 * On book (container) level, to be discussed with Julia.


 * i OAI-PMH Interface integration?
 * Will be addressed by Willy


 * i  Persistent Identifier
 * Blocked by PrettyUrls

Other

 * Status of Metadata change (possible to release on demo and live end of July)?
 * Can not be estimated so far, will not happen end of July


 * Check on readiness for journal project
 * Nice: Functional prototype ready for project meeting in September

Telko 15.05.2009
PARTICIPANTS: Rupert, Rike, Frau Amedick, Frau Fritz

Discussion of the Browse entry page (Remarks document from the Institute).


 * Changes in R2.5
 * Label 'Mehrbandwerk' on the left side not needed anymore, instead different icons in front of the title (3 icons for Mehrbandwerk, Band, Monograf)
 * The two sections (Thumbnail + Bibl. MD and TOC) should be hidable/unhideable
 * New Icons for functionality open/close all levels (TOC)
 * TOC functionality bar should be separated from the TOC that it does not disappear when scrolling
 * Change label: Metadaten to Details (in whole solution)


 * Changes in  R3
 * Eigene Textinhalte: Fixed size of 5 lines, only displayed when filled
 * New link to open Metadata in ISBD Format (see details here)
 * New button for a Volume: Show multivolume

Meeting in München, 07.05.2009
PARTICIPANTS: Malte, Ulla, Willy, Markus H., Natasa, Rike, Frau Amedick, Frau Fritz, Frau Flitner, Frau Dr. Anette Creutzburg, Frau Engelhardt


 * Presentation and collective workthrough (Modell structure of Oertel Band 1 und 2)


 * Organizational Issues:
 * 1) User Management
 * 2) * The MPDL will create the users.
 * 3) Which persons (librarian, hiwies, scientists) will work with the editing interface?
 * 4) Are different editing roles needed?
 * 5) * Only one editing role is needed.
 * 6) Requirements and timeline for productive readiness (usage by external service providers for DFG application)
 * 7) * Everything that is in the new scope for R3.0 (see ViRR Scope: Release 3.0.
 * 8) PIDs needed? For what (scan, book, ...)?
 * 9) * Not needed by the institute.


 * Release 3:
 * 1)  Crosscheck former shaped scope
 * 2) Enrichment of the controlled vocabulary for the metadata "Law Type" of a structural element?
 * 3) METS Import (Is this still needed?): example data needed for specifing the mapping


 * Other:
 * 1) Additional User Interface Evaluation desired?
 * 2) Integration of a "Zeichenzähler" to calculate the payment for external service providers
 * 3) Enrichment of TOC-Editor with structural elements for Journals (Zeitschriften-Format) => DFG application

Outcome
Changes for R2.5 & R3.0:
 * Rework of entrance page for browse volume (suggestions from rupert)
 * Browse: Only logical page number should be displayed for pages
 * Browse: Show start page of structural element after title in brackets
 * Browse: Level action elements like in the edit tree should be integrated
 * Browse: As default, MD section is hidden
 * Structural element type, add: 'Rechtssprechung', 'Vorsatz'
 * Browse: Structural element type should be displayed differently to title (other colour, italic etc.)
 * Browse: Pages should be hidden as default
 * Edit: When I create a new structural element, this element should be selected
 * Numbering of structural element should be displayed after the name of a structural element in the toc
 * Ingest of TIFFs to eSciDoc


 * Rework of homepage content (by the institute)
 * Disclaimer (by the institute)
 * Copyright information (by the institute)

Changes in Project Phase:
 * see ViRR Scope: Project Phase

General Improvements (not yet scheduled):
 * New selection opportunity: Select interval --> already implemented
 * Unselect all checkboxes after pagination (to be checked in user test) --> in work
 * New action: download METS/MODS xml (together with export func in project phase)
 * Nice Urls

Telephone Conference, 30.09.08
PARTICIPANTS: Frau Fritz, Rupert, Rike, Kristina Agenda: Results:
 * Discussion of the current state of the GUI prototype for the editing interface
 * Changes in the GUI
 * See ViRR GUI


 * Frau Fritz will deliver Feedback to following questions (till the end of October):
 * Display in the TOC tree: Shall there be always displayed the type of the structural element, the name of it (if available) or both? If only the name will be displayed, the type can be displayed via an mouse over.
 * Drop down menu "List of structural elements": all elements built a list much too long. Therefore, some main elements are needed. The other elements will be displayed either via a second drop down list (after selection "Andere") or only via a free text field.

Telephone Conference, 19.08.08
PARTICIPANTS: Frau Fritz, Rupert, Rike, Kristina
 * Discussion of possible Editing Szenarios

Telephone Conference, 24.06.08
PARTICIPANTS: Frau Amedick, Rupert, Kristina
 * Presentation of the functional prototype for R1

Meeting in München, 15.04.2008
PARTICIPANTS: Frau Amedick, Malte, Ulla, Inga, Wilhelm, Kristina
 * R1: Presentation
 * 1) * Feedback is collected on the GUI page
 * R2: Editing
 * 1) * Definition of structural units
 * 2) * Editing interface
 * 3) * Output can be found on Editing
 * 4) Miscellaneous
 * 5) * Can R1 be shown to the colleagues in Florenz?
 * Yes!
 * 1) * Contact DTA/BBAW
 * The DTA focuses on books after 1780. The books relevant for ViRR are earlier. So its not interesting for the DTA to cooperate with the ViRR project.
 * 1) * Project Proposal
 * The project proposal could be based on a cooperation with more than one institute. Therefore Frau Amedick will contact interested potential partners at the BT Jena to get an overview via the (different) interests in ViRR.

Telephone Conference, 28.02.08
PARTICIPANTS: Frau Amedick, Malte, Ulla, Kristina

Agenda:
 * 1) Release plan
 * 2) Functional prototype - basic browse/display
 * 3) Time schedule
 * 4) Kooperationsvertrag

Output:
 * The institute will send us the original tiffs of the two starting books (and if possible already some more pictures).
 * The KHI Florenz is interested in the first phase of ViRR (contact Dr. Simane). For both sides (the MPI and the MPDL) its fine to invite them for our next meetings.
 * The MPDL will create a proposal for a "Kooperationsvertrag" between the MPI and the MPDL, which can be used as basis for a project application.
 * Our next meeting will be in KW 15(07.-11.04.08), where R1 should be implemented and presented.

Meeting in Frankfurt, 22.10.07
PARTICIPANTS: Prof. Stolleis, Frau Amedick, Frau Fritz, Herr Haerter, Herr Novak, Malte, Ulla, Inga, Andreas, Kristina
 * 1) Vorstellungsrunde: Rolle der Anwesenden im Projekt ViRR
 * 2) DFG Praxisregeln und ViRR
 * 3) Diskussion des aktuellen Scope Dokumentes
 * 4) Diskussion von METS
 * 5) Nachhaltigkeit und Nachnutzung
 * 6) Projekt-Kommunikation (inkl. colab-wiki)
 * 7) Personelle und sachliche Ressourcen
 * 8) Zeitplan
 * 9) Sonstiges (Klärung offener Fragen)
 * 10) ViRR auf der Herbsttagung
 * 11) Nächste Schritte

Meeting in Frankfurt, 18.06.07
PARTICIPANTS: Frau Amedick, Frau Fritz, Herr Haerter, Herr Novak, Malte, Ulla, Inga, Natasa, Kristina
 * 1) Aim of project (research question, in short)
 * 2) * Overall picture
 * 3) Needs - what is lacking? (usage scenarios)
 * 4) * Essential
 * 5) * Short-term
 * 6) * Long-term
 * 7) Current status
 * 8) * Data formats
 * 9) * Metadata
 * 10) * Users Software, functionalities, tools in use
 * 11) Next steps, project title, communication medium