Artifacts using JCoRe Utilities (52)

Sort by:Popular▼

✓Popular✓Newest

Parses CAS data in XMI format in order to select specified annotations (XmiSplitter) or or builds a single XMI representation out of the base document and the selected annotations (XmiBuilder). These tools are used by the JCoRe CAS to/from DB Reader/Consumer to store or read portions of XMI files from a PostgrSQL database.

A Collection Reader that converts XML, stored in a database, to CAS objects. The conversion is the same employed by the jcore-xml-reader, making use of the jcore-xml-mapper. The reader requires a configuration file which determines the database connection, the table schema and the PostgreSQL schema (namespace) to use.

This is a JeDIS component. It can be used to set the 'last component' column in a subset table. This help to keep track of the pipeline status.

Reads CAS XMI data from a relational database (Postgres). Thus, the stored CASes may then be processed further.

Abstract database reader for database driven processing

UIMA Wrapper for the JULIE Token Boundary Detector.

UIMA Wrapper for the JULIE Sentence Boundary Detector.

Uses the Linnaeus software (http://linnaeus.sourceforge.net/) to detect species mentions and map them to NCBI taxonomy IDs. This project contains the UIMA wrapper around the original Linnaeus software but does not include any dictionaries. Since Linnaeus works with different dictionaries (e.g. concrete species name mention recognition, species proxy/clue recognition, ...) each of the different resource has been stored in a project of its own in jcore-projects. The ...

Basically used as NE tagger based on Lingpipe's dictionary-lookup tagger.

Writes CAS documents into the BioC XML format used by the gene tagger and normalizer GNormPlus.