ivan-cukic/litef-conductor

litef-conductor's Issues

Fix encoding of NERD Uris

Check where encoding of files (and if) becomes broken.
On download it JSON file shows ISO-8859 character set, and it is further treated as such.
This produces very strange URIs and values afterwards in NERD.

https://int2.cendari.dariah.eu/ckan/dataset/9200316-bibliographicresource_3000092750591/resource/4a24a665-1bed-4a8c-bd97-77b67d8ac351

the RDF version of this resource is in UTF encoding, see
https://int2.cendari.dariah.eu/ckan/dataset/9200316-bibliographicresource_3000092750591/resource/f22c70aa-c640-4773-884d-076ac2f536c4

on download UTF-8 file, somewhere during processing (i could track to NERD2RDF processing) the encoding goes into ascii

nbulatovic@int2:/var/lib/litef/default/resources/f22/c70/aa-c640-4773-884d-076ac2f536c4$ file application:rdf+xml
application:rdf+xml: UTF-8 Unicode text, with very long lines

nbulatovic@int2:/var/lib/litef/default/resources/f22/c70/aa-c640-4773-884d-076ac2f536c4$ file application:x-nerd-output
application:x-nerd-output: UTF-8 Unicode text, with very long lines, with no line terminators

nbulatovic@int2:/var/lib/litef/default/resources/f22/c70/aa-c640-4773-884d-076ac2f536c4$ file "application:x-nerd-output -> application:rdf+xml"
application:x-nerd-output -> application:rdf+xml: ASCII text

Add resource processing status to the data API

Create the elastic-indexer plugins

The text extraction using modified Tika is done.

The rest depends on: CENDARI/elastic-indexer#2