Home / tools / 3.0.3
Name Modified Size Downloads / Week Status
Parent folder
Totals: 4 Items   6.8 MB 4
README.txt 2012-10-02 3.2 kB 11 weekly downloads
dnb-conversion-env-3.0.3-xmab2utf8.jar 2012-10-02 466.3 kB 11 weekly downloads
dnb-conversion-env-3.0.3-mabxml2mab.jar 2012-10-02 3.2 MB 11 weekly downloads
dnb-conversion-env-3.0.3-mab2mabxml.jar 2012-10-02 3.2 MB 11 weekly downloads
Welcome to conversion tools of German National Library (Deutsche Nationalbibliothek). This Java Code Library offers two ways of using the implemented conversion mechanisms: 1. Command line tools (meant to be) 2. Generated Sources 3. Using the provided conversion context 1. Command Line There are three command line tools to choose from. - XMab2Utf8 - Mabxml2Mab - Mab2Mabxml To invoke any of these you have to type the following command (the part in brackets needs to be replaced appropriate): java -jar [jar file] -help This will print an overview of the mandatory/possible parameters to start any conversion. To start a conversion simple type this: java -jar [jar file] -i [input file] -o [output file] 2. Generated Sources To code against the sources generated by xmlbeans you first need to run the maven goal generate-sources. XmlBeans does generate source files and additional class files which have to be packaged with the project. If you chose eclipse as your IDE and the generated sources are not on the classpath run Maven -> Update Project Configuration from the projects context menu. 3. Conversion Context The conversion context can be found in de.dNb.conversion.context package. This is a facility to obtain a converter by passing appropriate parameters. The conversion context returns a converter specific to the passed parameters. The parameters that define a conversion pattern are: - input format - input encoding - output format - output encoding A converter can be placed in the conversion context by specifying these four parameters and can be retrieved by querying the conversion context and specifying this information again. The basic classes are in the package de.dNb.conversion and de.dNb.conversion.context. A converter is declared by the interface de.dNb.conversion.Converter. An abstract implementation derived from that interface has to be used by any implementing converter. Further there are three specialized child classes to server three basic purposes: 1. BinaryConverter 2. CharstreamConverter 3. PipedConverter The first one is used to handle binary streams coming from a OCLC server side Format Conversion (FCV). (No subclassing expected) The second is used to handle character streams. And the third wires two converters together by passing the output of the first as input to the second. The class hierarchy is this: - Converter | - GenericConverter | - BinaryConverter - CharstreamConverter - PipedConverter Any Converter implementation should be derived from GenericConverter (or CharstreamConverter if needed). The conversion context is currently initialized by an xml based configuration file. The according schema can be found under de.dNb.conversion.context.resource. Dependencies PicaToRdfBasisConverter and RdfEnricher following additional files are required: - arq-2.8.5.jar - iri-0.8.jar - jena-2.6.3.jar - picaToRdfBasisConverter-0.0.2.jar - rdfEnricher-0.0.2.jar - slf4j-api-1.5.8.jar - slf4j-log4j12-1.5.8.jar - de.dNb.conversion.rdf.ressources.ddc2sgMap.txt - commons-httpclient-3.0.jar
Source: README.txt, updated 2012-10-02