Onkopedia ist ein medizinische Fachportal mit Leitlinien zur Behandlung von u.a. Krebserkrankungen. Der Vortrag dokumentiert die Umstellung des Publishing Workflows (DOCX -> HTML + PDF) auf Basis von XML.
The document provides suggestions for improving PyPI:
1) Always upload packages to PyPI to ensure availability and allow for mirroring by other sites.
2) Never remove released packages from PyPI to avoid breaking installations that depend on pinned versions.
3) Do proper releases by including metadata, descriptions, source distributions, and eggs for Windows, and consider PyPI an ecosystem rather than a personal package storage.
The document summarizes the past, present, and future of the Zope project. It discusses how Zope was initially successful competing with other web frameworks but then lost popularity with the rise of Ruby on Rails and other Python frameworks. This led to an identity crisis within the Zope community. The vision going forward is to phase out the term "Zope 3", support Zope 2 as the application server, and promote GROK and Zope components as lower barrier ways to build with Zope.
The document discusses best practices for completing pragmatic Plone projects based on lessons learned from a large Plone project for Weishaupt, a major heating systems company. It covers common customizations required in projects and recommends patching Python code and resources through forks, branches, and overrides rather than directly modifying third-party packages. The talk also provides tips for working within constraints of limited budgets, resources, and timeframes and keeping designers happy through sample content.
Pyfilesystem provides a unified Python API for accessing various storage systems and file services. It abstracts away differences between storage APIs so that code works across systems without changes. Drivers exist for many systems including WebDAV, SFTP, S3, and local filesystems. The goal is for code to be unaware of the underlying storage type being used.
Producing high-quality documents with PloneAndreas Jung
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive function. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms for those who already suffer from conditions like anxiety and depression.
This document discusses best practices for completing pragmatic Plone projects based on lessons learned from a large Plone project for Weishaupt, a major heating systems company. It addresses common project constraints like limited budgets, resources and time. It provides tips for getting work done on schedule and budget through customizations, patching, overriding and extending existing Plone and third-party packages. Sample content and pre-defined site structures are also recommended to help designers. The key lessons are to contribute fixes and enhancements back to packages when possible and always keep custom code separate from third-party packages.
Universities and institutes often use Plone for their websites but have similar needs and develop their own incomplete solutions. Migrating Plone 2.0 sites to 3.0 is difficult. The German Zope User Group wants to create a dedicated website for universities using Plone to share information, best practices, references, and software in a collaborative way by first focusing on individual departments instead of entire institutions.
Frequently asked questions answered frequently - but now for the last timeAndreas Jung
This document contains a transcript of a talk given by Andreas Jung about frequently asked questions (FAQs) on IRC and mailing lists regarding Plone. The talk provides answers to common Plone questions around topics like installing themes, changing logos, system requirements, debugging issues, and more. It emphasizes best practices for asking questions like providing context and version details. The speaker has extensive experience with Python, Zope, and Plone development.
The document summarizes Andreas Jung's presentation on using MongoDB as the database for BRAINREPUBLIC. Some key points include:
- Andreas evaluated different "no-SQL" database options for BRAINREPUBLIC including key-value stores, MongoDB, and CouchDB.
- MongoDB was chosen because it offered the best performance compared to CouchDB, and its rich query API was preferable to map-reduce alone.
- The proposed architecture for BRAINREPUBLIC involved using MongoDB for the database, RabbitMQ for messaging, and SOLR for search, behind a load balancing layer.
Plone Integration with eXist-db - Structured Content rocksAndreas Jung
This document discusses integrating the eXist-db XML database with Plone. It presents an XML-based workflow for publishing medical guidelines, including converting documents to XML, storing them in eXist-db with a structured folder structure, and mapping that structure to Plone using a custom content type. This allows managing XML documents and assets in eXist-db while surfacing them through Plone. The integration provides benefits like improved production safety, validation, and a smaller codebase compared to the original HTML-based system.
This document summarizes a presentation about pragmatic approaches for Plone projects. It discusses customizing Plone and third party packages through various methods like monkey patching, overrides, and extending schemas. It also provides an example of a large company portal project built on Plone 4.2 for Weishaupt, a major heating systems vendor.
Produce & Publish Authoring Environment V 2.0 (english version)Andreas Jung
The document discusses single-source multi-channel publishing using Plone and Produce & Publish. It describes how content can be authored in Plone and transformed into multiple formats like PDF, EPUB, and office formats. The Produce & Publish system aggregates content from Plone, applies transformations, and converts it using various engines. The talk demonstrates the Produce & Publish workflow and discusses related Plone extensions.
Building bridges - Plone Conference 2015 BucharestAndreas Jung
This document discusses integrative publishing solutions using Plone and external storage systems and document formats. It introduces the XML Director toolkit which provides unified access to external storages like S3, WebDAV, FTP through a common API. It allows mounting these storages in Plone and integrating them with Dexterity content. The document also discusses various document formats like DOCX, DITA, HTML, PDF, EPUB and tools for converting between these formats to support an XML-based publishing workflow in Plone.
This document provides an overview of using Python and MongoDB together. It discusses MongoDB concepts and architecture, how to get started with MongoDB using the interactive console, and basic CRUD operations. It then covers installing and using PyMongo, the main Python driver for MongoDB, and some popular high-level Python frameworks built on top of PyMongo like MongoEngine and MongoAlchemy.
This document discusses reasons why the author believes Plone may decline or become a "CMS zombie" unless changes are made. Key points include:
- Growing developer and integrator frustration due to legacy code, complexities, lack of documentation and APIs.
- Difficult and unpredictable migrations between major Plone versions that introduce issues and costs.
- Stagnating community and market as Plone relies on aging technologies like Zope and ZODB.
The author argues Plone needs to remove legacy code, simplify architectures, introduce explicit APIs, support new databases and Python 3 to thrive in the future. A potential approach is starting from scratch with Pyramid and new components rather than continuing to build on aging foundations.
The document provides suggestions for improving PyPI:
1) Always upload packages to PyPI to ensure availability and allow for mirroring by other sites.
2) Never remove released packages from PyPI to avoid breaking installations that depend on pinned versions.
3) Do proper releases by including metadata, descriptions, source distributions, and eggs for Windows, and consider PyPI an ecosystem rather than a personal package storage.
The document summarizes the past, present, and future of the Zope project. It discusses how Zope was initially successful competing with other web frameworks but then lost popularity with the rise of Ruby on Rails and other Python frameworks. This led to an identity crisis within the Zope community. The vision going forward is to phase out the term "Zope 3", support Zope 2 as the application server, and promote GROK and Zope components as lower barrier ways to build with Zope.
The document discusses best practices for completing pragmatic Plone projects based on lessons learned from a large Plone project for Weishaupt, a major heating systems company. It covers common customizations required in projects and recommends patching Python code and resources through forks, branches, and overrides rather than directly modifying third-party packages. The talk also provides tips for working within constraints of limited budgets, resources, and timeframes and keeping designers happy through sample content.
Pyfilesystem provides a unified Python API for accessing various storage systems and file services. It abstracts away differences between storage APIs so that code works across systems without changes. Drivers exist for many systems including WebDAV, SFTP, S3, and local filesystems. The goal is for code to be unaware of the underlying storage type being used.
Producing high-quality documents with PloneAndreas Jung
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive function. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms for those who already suffer from conditions like anxiety and depression.
This document discusses best practices for completing pragmatic Plone projects based on lessons learned from a large Plone project for Weishaupt, a major heating systems company. It addresses common project constraints like limited budgets, resources and time. It provides tips for getting work done on schedule and budget through customizations, patching, overriding and extending existing Plone and third-party packages. Sample content and pre-defined site structures are also recommended to help designers. The key lessons are to contribute fixes and enhancements back to packages when possible and always keep custom code separate from third-party packages.
Universities and institutes often use Plone for their websites but have similar needs and develop their own incomplete solutions. Migrating Plone 2.0 sites to 3.0 is difficult. The German Zope User Group wants to create a dedicated website for universities using Plone to share information, best practices, references, and software in a collaborative way by first focusing on individual departments instead of entire institutions.
Frequently asked questions answered frequently - but now for the last timeAndreas Jung
This document contains a transcript of a talk given by Andreas Jung about frequently asked questions (FAQs) on IRC and mailing lists regarding Plone. The talk provides answers to common Plone questions around topics like installing themes, changing logos, system requirements, debugging issues, and more. It emphasizes best practices for asking questions like providing context and version details. The speaker has extensive experience with Python, Zope, and Plone development.
The document summarizes Andreas Jung's presentation on using MongoDB as the database for BRAINREPUBLIC. Some key points include:
- Andreas evaluated different "no-SQL" database options for BRAINREPUBLIC including key-value stores, MongoDB, and CouchDB.
- MongoDB was chosen because it offered the best performance compared to CouchDB, and its rich query API was preferable to map-reduce alone.
- The proposed architecture for BRAINREPUBLIC involved using MongoDB for the database, RabbitMQ for messaging, and SOLR for search, behind a load balancing layer.
Plone Integration with eXist-db - Structured Content rocksAndreas Jung
This document discusses integrating the eXist-db XML database with Plone. It presents an XML-based workflow for publishing medical guidelines, including converting documents to XML, storing them in eXist-db with a structured folder structure, and mapping that structure to Plone using a custom content type. This allows managing XML documents and assets in eXist-db while surfacing them through Plone. The integration provides benefits like improved production safety, validation, and a smaller codebase compared to the original HTML-based system.
This document summarizes a presentation about pragmatic approaches for Plone projects. It discusses customizing Plone and third party packages through various methods like monkey patching, overrides, and extending schemas. It also provides an example of a large company portal project built on Plone 4.2 for Weishaupt, a major heating systems vendor.
Produce & Publish Authoring Environment V 2.0 (english version)Andreas Jung
The document discusses single-source multi-channel publishing using Plone and Produce & Publish. It describes how content can be authored in Plone and transformed into multiple formats like PDF, EPUB, and office formats. The Produce & Publish system aggregates content from Plone, applies transformations, and converts it using various engines. The talk demonstrates the Produce & Publish workflow and discusses related Plone extensions.
Building bridges - Plone Conference 2015 BucharestAndreas Jung
This document discusses integrative publishing solutions using Plone and external storage systems and document formats. It introduces the XML Director toolkit which provides unified access to external storages like S3, WebDAV, FTP through a common API. It allows mounting these storages in Plone and integrating them with Dexterity content. The document also discusses various document formats like DOCX, DITA, HTML, PDF, EPUB and tools for converting between these formats to support an XML-based publishing workflow in Plone.
This document provides an overview of using Python and MongoDB together. It discusses MongoDB concepts and architecture, how to get started with MongoDB using the interactive console, and basic CRUD operations. It then covers installing and using PyMongo, the main Python driver for MongoDB, and some popular high-level Python frameworks built on top of PyMongo like MongoEngine and MongoAlchemy.
This document discusses reasons why the author believes Plone may decline or become a "CMS zombie" unless changes are made. Key points include:
- Growing developer and integrator frustration due to legacy code, complexities, lack of documentation and APIs.
- Difficult and unpredictable migrations between major Plone versions that introduce issues and costs.
- Stagnating community and market as Plone relies on aging technologies like Zope and ZODB.
The author argues Plone needs to remove legacy code, simplify architectures, introduce explicit APIs, support new databases and Python 3 to thrive in the future. A potential approach is starting from scratch with Pyramid and new components rather than continuing to build on aging foundations.
Anwendungsmodernisierung mit Oracle Application Express (APEX)Niels de Bruijn
Lernen Sie warum man für legacy Anwendungen basierend auf Oracle Forms oder MS Access überlegen sollte, warum eine Migration auf eine neue Technologie sinnvoll ist.
Ein Blick in die Kristallkugel mit dem Ziel spannende und relevante Online-Trends für das Jahr 2007 hervorzusagen. Auf der Liste sind:
- Enterprise Wikis
- Software as a Service (SES)
- OpenID
- WPF/E (=Windows Presentation Foundation / Everywhere) Neu: Microsoft Silverlight
- SIP/IMS
- Online TV
- Wireless Commons / OLSR
- Live Clipboard
- Scrum
- Geo tagging
Ein Blick in die Kristallkugel mit dem Ziel spannende und relevante Online-Trends für das Jahr 2006 hervorzusagen. Auf der Liste sind:
- Desktop Widgets
- 2D Barcoding
- JSR-170/286
- REST
- Lightweight APIs und JSON
- Presence und Instant Messaging
- Home Networking
- Microformats/Structured Blogging
- Online Identity
- Antiphishing
Einführung aus den Perspektiven Site Builder, Developer, Themer & Community
http://www.drupal-austria.at/veranstaltungen/drupal-roadshow-klagenfurt
Christian Ziegler
Wolfgang Ziegler
Nico Grienauer
Josef Dabernig
MT AG Rapid Application Development mit APEX 5 (Important: latest version on ...Niels de Bruijn
As Slideshare won't let me update the content without breaking the URL, I was forced to use a new platform for my documents. Please use the following link to get the latest version:
https://www.edocr.com/v/ldmkqo7v/nielsdebruijn/20180529_Einfuehrung_APEX
Hier erfährt ihr warum internationales SEO kein "normales" SEO ist. Welche Besonderheiten gibt es, was man bei der Internationalisierung eigener Website beachten muss: Strategie, Prozesse, Beispiele, FAQs, usw.
Datensicherheit in der Cloud und ausserhalb - SharePoint Konferenz Wien 2013Michael Kirst-Neshva
In diesem Vortrag gebe ich einen Überblick über die vermeintliche Cloud Bedrohung von ausländischen Behörden und wie man generell mit einfachen Mitteln sein Netzwerk und vor allem die Dateninhalte schützen kann.
Anhand von recherchierten Zahlen konnte ich darstellen, dass nicht alleine ausländische Behörden erhebliche Mengen an Daten bei Cloud Providern anfragen.
Die in diesem Vortrag gezeigten Vorschläge sind nur als Teil einer Gesamtlösung zu sehen.
amsl - Ergebnispräsentation der EFRE-FörderphaseBjörn Muschall
Am 26.09.2014 fand in der SLUB Dresden ein 2. amsl Workshop statt. Neben der Ergebnispräsentation der EFRE-Förderphase hatten die Teilnehmer Gelegenheit, die Anwendung zu nutzen.
This document summarizes Andreas Jung's presentation on the state of PrintCSS in 2023. It discusses the basics of PrintCSS, challenges in comparing different PrintCSS tools, an overview of free and commercial PrintCSS renderers, the role of JavaScript, common pain points, and decision criteria for choosing a PrintCSS renderer. The presentation provides an in-depth look at PrintCSS standards, tools, features, use cases, and recommendations.
PrintCSS W3C workshop at XMLPrague 2020Andreas Jung
1. Andreas Jung is a freelance consultant and developer who founded the print-css.rocks project in 2016 to provide vendor-neutral information about PrintCSS.
2. There are many incomplete and missing parts of the PrintCSS standard including issues with table splitting, floating, images, and support for JavaScript and multi-column layouts.
3. Key missing features from the standard include CSS exclusions, named page floating, hyphenation dictionaries, auto-sizing text to containers, consistent sidenote positioning, and tests to ensure consistent rendering behavior across tools.
Andreas Jung gives a presentation on PrintCSS, which uses CSS to control pagination and layout when converting XML or HTML to PDF. He discusses various PrintCSS tools and their features, provides examples of how PrintCSS is used, and highlights areas that still need improvement, such as standardization, JavaScript support, image positioning, and hyphenation. The ecosystem of PrintCSS tools is still limited with few free and open source options.
Plone 5.2 migration at University Ghent, BelgiumAndreas Jung
This talk summarizes our #Plone migration approach of the Plone installation at ugent.be. The migration process consists of the export of the original site to JSON using collective.jsonify, import of the data to ArangoDB and then back into a fresh Plone site through plone.restapi
This document discusses migrating 10 Plone sites from Plone 4.1/4.3 to Plone 5.1 using plone.restapi. The goals were a consistent look and feel, common code base with fewer dependencies, and consistent deployment. A custom provisioning API was built to handle site creation, content migration, and other tasks. The migration process extracted content from source sites and recreated it in the target Plone 5 sites using plone.api calls over HTTP. Most structures and content migrated automatically, with some manual work needed for default pages, collections, and other content. Lessons learned were that the approach was stable, reasonably fast, and could be adopted for other migrations.
Creating Content Together - Plone Integration with SMASHDOCsAndreas Jung
Plone Conference 2017 in Barcelona. Lightning talk .
Collaborative Content Creation solutions for content management systems or arbitrary web applications,
Creating Content Together - Plone Integration with SMASHDOCsAndreas Jung
Plone Conference 2017 in Barcelona. Lightning talk .
Collaborative Content Creation solutions for content management systems or arbitrary web applications,
3. www.produce-and-publish.de Professional XML Publishing
Was ist Onkopedia?
‣ www.dgho-onkopedia.de • www.onkopedia-guidelines.info
‣ Medizinisches Fachportal mit Behandlungs- und
Diagnoseleitlinien zur Erkennung und Behandlung von
Krebs- und Bluterkrankungen in DACH
‣ Mittel der Qualitätssicherung im Bereich der
Evidenz-basierten Medizin
‣ reflektiert den aktuellen Wissensstand der Medizin
‣ Betreiber: Deutsche Gesellschaft für Hämatologie und
Medizinische Onkologie (DGHO) und weitere DACH
Fachgesellschaften
4. www.produce-and-publish.de Professional XML Publishing
Onkopedia Inhaltsbereiche
‣ Onkopedia
‣ Zielgruppe: behandelnde Mediziner
‣ verbindliche Diagnose- und Behandlungsleitlinien
‣ Mein Onkopedia
‣ Zielgruppe: Patienten und deren Umfeld
‣ Patientengerechte Ansprache und Erklärung der Krankheitsbilder
‣ Onkopedia Pflege
‣ Zielgruppe: Pflegepersonal
‣ Pflegeanweisungen und Pflegediagnosen
‣ Wissensdatenbank
‣ Informationen und Vorträgen von Kongressen etc.
‣ Onkopedia EN (im Aufbau)
5. www.produce-and-publish.de Professional XML Publishing
Diagnose- und Behandlungsleitlinien
‣ Autoren sind führende Ärzte und Professoren
‣ Dokumententypen:
‣ Leitlinien
‣ Zulassungsprotokolle
‣ Studienergebnisse
‣ Therapieprotokolle
‣ Leitlinien haben verbindlichen
‣ Aktualisierungszyklus zwischen 1 und 4 Jahren
6.
7.
8.
9.
10.
11. www.produce-and-publish.de Professional XML Publishing
‣ Autoren (Mediziner)
verfassen Manuskripte in
Word/DOCX
‣ Übergabe Word-Dokumente
an interne Redaktion
‣ Import Manuskripte in CMS
‣ interne Überprüfung und
Korrekturläufe
‣ Generierung druckfertiger PDF
Dokumente gemäß
vorkonfiguriertem Layout
Word-Manuskripte ➝ PDF
12. www.produce-and-publish.de Professional XML Publishing
2010-2014: Bearbeitungsworkflow
Word -> XHTML
über externen Webservice
(OpenOffice)
Grafiken nachbearbeiten
(Imagemaps, Skalierung)
Konvertierung über externe
Konverter nach PDF und
EPUB
Freigabe und Publikation
13. www.produce-and-publish.de Professional XML Publishing
‣ Gründe für die Umstellung auf XML
‣ fragile Konvertierung
‣ Drittverwertung der Inhalte durch externe Anbieter
(z.B. für Sondereditionen)
‣ Vereinheitlichung der Dokumentenstruktur
‣ Wunsch nach besserer Automatisierung
des Publikationsworkflows
‣ Überarbeitung und Refaktorierung der Softwarebasis
notwendig
‣ unzureichende Metadaten
2014: Umstellung auf XML
14. www.produce-and-publish.de Professional XML Publishing
‣ HTML als internes Format
‣ fehlende Semantik der Elemente
‣ unzureichende Validierungsmöglichkeiten
‣ zu web-zentriert
‣ zu viele Freiheitsgrade
‣ unstrukturiert
‣ nicht zukunftssicher
‣ Anbindung an externe Dienstleister (XML Anforderung)
Gründe für Umstellung auf XML/Details
15. www.produce-and-publish.de Professional XML Publishing
‣ Word als Autorenwerkzeug
‣ DOCX als Quellformat
‣ Entwicklung einer spezifischen Word Formatvorlage
‣ Abbildung der Dokumentstrukturen
‣ semantische Auszeichnung von Textelementen und Absätzen
‣ DOCX ➝ XML Konvertierung als Webservice
‣ generiert XML und HTML (Web)
‣ Extrahiert Grafiken etc.
‣ automatischer Erkennung von Links etc.
‣ Speicherung XML in XML Datenbank (eXist-db)
Umstellung redaktioneller Workflow auf XML
17. www.produce-and-publish.de Professional XML Publishing
‣ Bereitstellung HTML fürs Web
‣ Konvertierung XML nach PDF
‣ via „CSS Paged Media“
‣ HTML/XML als Eingabeformat
‣ CSS Stylesheets für Layout und Styling
‣ Konvertierung über kommerzielle PDF Konverter
(PrinceXML oder PDFreactor)
‣ Bereitstellung PDF im Web zum Download
XML Publikationsworkflow
18. www.produce-and-publish.de Professional XML Publishing
Web-to-Print Automatischer Satz
• Layout-orientierte Dokumente
• Zusammenführung von Daten und
Templates
• Alternative zu teuren Web-to-Print
Lösungen für einfache bis
mittelkomplexen Layouts
• vergleichbar mit TeX
• Fussnoten, Randziffern
• Mehrsprachigkeit/Unicode
• Spaltensatz
• Trenntabellen (mehrsprachig)
• LTR/RTL Unterstützung
• Tabellen (über mehrere Seiten)
• Bilder, Bildunterschriften
• Tabellen-, Grafikverzeichnisse
• Index-Generierung
• automatisches Inhaltsverzeichnis
• Deckseiten
• PDF Bookmarks
• sehr hohe PDF Qualität
Features
19. www.produce-and-publish.de Professional XML Publishing
Produce & Publish
XML to PDF
Query Server
Word2XML
Plone
CMS
DGHO
Member Database
Authentication
DOCX
XML, Assets
Authorization
PDF, EPUB
HTML, XML + CSS
XQuery
XML, HTML, JSON
Mac
XM
LEditing,AssetsEditing
XM
LEditing,AssetsEditing
W
ebDAV
W
ebDAV
Windows
JSON
HTML
XMLXQuery
WebDAV
Onkopedia Onkopedia Editor (Intern)
OnkopediaEditor(Intern)
OnkopediaSiteVisitor
OnkopediaSiteVisitor
OnkopediaEditor(Intern)
External Systems
Clinical systems
Medical applications
Medical databases
HTTP
REST API
Guidelines (XML)
Addendums (XML)
Assets (Images, Styles)
PDF
DOCX
eXist-db
XML database
Architektur
20. Produce & Publish
XML to PDFWord2XML
Plone
CMS
ntication
DOCX
XML, Assets
Authorization
PDF, EPUB
HTML, XML + CSS
JSON
HTML
XMLXQuery
WebDAV
Onkopedia Onkopedia Editor (Intern)
OnkopediaEditor(Intern)
OnkopediaSiteVisitor
OnkopediaSiteVisitor
OnkopediaEditor(Intern)
21. Produce & Publish
XML to PDF
Query Server
Word2XML
Plone
CMS
DGHO
Member Database
Authentication
DOCX
XML, Assets
Authorization
PDF, EPUB
HTML, XML + CSS
XQuery
XML, HTML, JSON
Mac
XM
LEditing,AssetsEditing
XM
LEditing,AssetsEditing
W
ebDAV
W
ebDAV
Windows
JSON
HTML
XMLXQuery
WebDAV
Onkopedia
diaSiteVisitor
SiteVisitor
OnkopediaEd
HTTP
REST A
Guidelines (XML)
Addendums (XML)
Assets (Images, Styles)
PDF
DOCX
eXist-db
XML database
22. Produce & Publish
XML to PDF
Query Server
Plone
CMS
XML, Assets
Authorization
PDF, EPUB
HTML, XML + CSS
XQuery
XML, HTML, JSON
Mac
LEditing,AssetsEditing
XM
LEditing,AssetsEditing
W
ebDAV
W
ebDAV
JSON
HTML
XMLXQuery
WebDAV
OnkopediaEd
opediaSiteVisitor
diaSiteVisitor
OnkopediaEdito
External Systems
Clinical systems
Medical applications
Medical databases
HTTP
REST API
Guidelines (XML)
Addendums (XML)
Assets (Images, Styles)
PDF
DOCX
eXist-db
XML database
23. www.produce-and-publish.de Professional XML Publishing
Produce & Publish
XML to PDF
Query Server
Word2XML
Plone
CMS
DGHO
Member Database
Authentication
DOCX
XML, Assets
Authorization
PDF, EPUB
HTML, XML + CSS
XQuery
XML, HTML, JSON
Mac
XM
LEditing,AssetsEditing
XM
LEditing,AssetsEditing
W
ebDAV
W
ebDAV
Windows
JSON
HTML
XMLXQuery
WebDAV
Onkopedia Onkopedia Editor (Intern)
OnkopediaEditor(Intern)
OnkopediaSiteVisitor
OnkopediaSiteVisitor
OnkopediaEditor(Intern)
External Systems
Clinical systems
Medical applications
Medical databases
HTTP
REST API
Guidelines (XML)
Addendums (XML)
Assets (Images, Styles)
PDF
DOCX
eXist-db
XML database
Architektur
24. www.produce-and-publish.de Professional XML Publishing
‣ Plone
‣ Open-Source Enterprise Content Management System
‣ eXist-db
‣ XML Datenbank
‣ Open-Source
‣ PDFreactor
‣ XML/HTML ➝ PDF Konverter
‣ kommerziell
➝ offene und kostengünstige Lösung dank Open-Source
➝ Kein Vendor-Lockin
Eingesetzte Software
25. www.produce-and-publish.de Professional XML Publishing
‣ Strukturierter Content (XML) im professionellen Publishing
Umfeld unerlässlich:
‣ Validierbarkeit, bessere Automatismen
‣ verbesserte Produktionssicherheit und Automatisierung
‣ Metadaten erlauben Klassifizierung und
Verknüpfung von Inhalten ➝ bessere Navigation
‣ Kunde behält die Hoheit über den eigenen Content
‣ Schnittstellen für den Zugriff von externen Applikationen/
Anbietern
Zusammenfassung