Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Indexes - Visualisation after harvesting #52

Open
SigiDoc opened this issue Jun 22, 2019 · 5 comments
Open

Indexes - Visualisation after harvesting #52

SigiDoc opened this issue Jun 22, 2019 · 5 comments
Assignees
Labels

Comments

@SigiDoc
Copy link

SigiDoc commented Jun 22, 2019

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

@IreneVagionakis
Copy link
Member

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

@filosam
Copy link

filosam commented May 2, 2022

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
Copy link

ajenhl commented May 5, 2022

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
Copy link

filosam commented Jun 14, 2022

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

@ajenhl
Copy link

ajenhl commented Jun 14, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants