-
Important preliminary questions
-
Existing implementations, resources for new development
-
Prerequisites
❓ Can I host the endpoint myself?
❗ No → HelpDesk: CLARIN, Text+
❓ What type of data do I have?
❗ Raw text, Vertical/CONLL, TEI, …
❓ Which search engine do I use / can I use?
❗ KorAP, Korp/CWB, Lucene/Solr/ElasticSearch, BlackLab, (No)SketchEngine, …
❓ Customization or new development?
❗ List of existing endpoint implementations (Awesome List)
❓ Programming language?
❗ Java, Python, (PHP, XQuery)
❓ In-house development: Use of the reference libraries (Java, Python)
❗ Maven Archetype, Korp
❗ SRU + FCS specifications …
-
Korp FCS 2.0 - reference implementation, Korp corpus search
-
CQP/SRU bridge - Corpus Workbench (CWB)
-
KonText, fcs-noske-endpoint - (No)SketchEngine (CONLL/Vertical)
-
oclcsrw - SRW/SRU server for DSpace, Lucene and/or Pears/Newton
-
corpus_shell, SADE - MySQL PHP/DDC Perl, eXist/XQuery
-
arche-fcs - ARCHE Suite, php
-
Blacklab / MTAS - corpus search engines using Lucene/Solr
-
KorapSRU - KorAP (IDS)
Sources: clarin, awesome-fcs
-
Customization of reference implementation (Korp)
-
Development using CLARIN SRU/FCS libraries
-
Docs:
-
“New” development specifications (for other languages)
-
FCS: github.com/clarin-eric/fcs-misc → “FCS Core 2.0”
-
Awesome List: github.com/clarin-eric/awesome-fcs