search

EpiDoc / EFES

EFES (EpiDoc Front End Services) is a custom and readily customizable platform for publication and search/indexing of EpiDoc files, based on the Kiln platform
Apache License 2.0
31 stars 38 forks source link

Indexes - Visualisation after harvesting #52

Open SigiDoc opened 5 years ago

SigiDoc commented 5 years ago

Troubles with visualisation (http://localhost....) randomly changing after each harvesting, apparently there is no ratio in this behaviour.

IreneVagionakis commented 2 years ago

It happened to me too, in indices and facets. It would be good to provide some screenshots here to document this.

filosam commented 2 years ago

Hi all -- here's an example of this seemingly random behaviour: (see: [1] Ἰουστινιανός, [2] Λέων, and [3] Βουλκασιότης Παγκράτιος)

Bild1 Bild3

...after re-indexing and re-harvesting...

Bild5 Bild4

...but...

Bild6

ajenhl commented 2 years ago

It is not clear to me why this is happening. The display of the index entry requires that the reference in the Epidoc XML corresponds to an entry in the referenced index XML, and that the indexed has been successfully harvested into the RDF store. When you see an index entry of the form "http://localhost...." rather than the expected name, that indicates that the RDF data does not have a mapping of that reference to a particular name harvested from the index.

Why that data may not be harvested is unknown to me from the above.

filosam commented 2 years ago

@gabrielbodard : could be a memory issue? Do we have a way of enlarging the memory for RDF harvesting?

ajenhl commented 2 years ago

Do we have a way of enlarging the memory for RDF harvesting?

When running locally via the build script, you can specify the amount of memory available to EFES via the -Xmx parameter in build.sh or build.bat. For example, "-Xmx8192m" is 8GB of memory.