mirror of
https://gitlab.ub.uni-bielefeld.de/sfb1288inf/nopaque.git
synced 2024-11-16 01:35:41 +00:00
53 lines
2.3 KiB
Plaintext
53 lines
2.3 KiB
Plaintext
|
<h2>Services</h2>
|
||
|
|
<div class="row">
|
||
|
|
<div class="col s12 m4">
|
||
|
|
<img alt="Services" class="materialboxed responsive-img" src="{{ url_for('static', filename='images/manual/services.png') }}">
|
||
|
|
</div>
|
||
|
|
<div class="col s12 m8">
|
||
|
|
<p>
|
||
|
|
nopaque was designed from the ground up to be modular. This modularity
|
||
|
|
means that the offered workflow provides variable entry and exit points,
|
||
|
|
so that different starting points and goals can be flexibly addressed.
|
||
|
|
Each of these modules are implemented in a self-contained service, each of
|
||
|
|
which represents a step in the workflow. The services are coordinated in
|
||
|
|
such a way that they can be used consecutively. The order can either be
|
||
|
|
taken from the listing of the services in the left sidebar or from the
|
||
|
|
roadmap (accessible via the pink compass in the upper right corner). All
|
||
|
|
services are versioned, so the data generated with nopaque is always
|
||
|
|
reproducible.
|
||
|
|
</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<h3>File Setup</h3>
|
||
|
|
<p>
|
||
|
|
The <a href="{{ url_for('services.file_setup_pipeline') }}">File Setup Service</a> bundles image data, such as scans and photos,
|
||
|
|
together in a handy PDF file. To use this service, use the job form to
|
||
|
|
select the images to be bundled, choose the desired service version, and
|
||
|
|
specify a title and description. Please note that the service sorts the
|
||
|
|
images into the resulting PDF file based on the file names. So naming the
|
||
|
|
images correctly is of great importance. It has proven to be a good practice
|
||
|
|
to name the files according to the following scheme:
|
||
|
|
page-01.png, page-02.jpg, page-03.tiff, etc. In general, you can assume
|
||
|
|
that the images will be sorted in the order in which the file explorer of
|
||
|
|
your operating system lists them when you view the files in a folder
|
||
|
|
sorted in ascending order by file name.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<h3>Optical Character Recognition (OCR)</h3>
|
||
|
|
<p>Comming soon...</p>
|
||
|
|
|
||
|
|
<h3>Handwritten Text Recognition (HTR)</h3>
|
||
|
|
<p>Comming soon...</p>
|
||
|
|
|
||
|
|
<h3>Natural Language Processing (NLP)</h3>
|
||
|
|
<p>Comming soon...</p>
|
||
|
|
|
||
|
|
<h3>Corpus Analysis</h3>
|
||
|
|
<p>
|
||
|
|
With the corpus analysis service, it is possible to create a text corpus
|
||
|
|
and then explore it in an analysis session. The analysis session is realized
|
||
|
|
on the server side by the Open Corpus Workbench software, which enables
|
||
|
|
efficient and complex searches with the help of the CQP Query Language.
|
||
|
|
</p>
|