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

Check whether we get the correct format of the ontology and it can be parsed correctly #8

Open
kuefmz opened this issue Jun 10, 2024 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@kuefmz
Copy link
Collaborator

kuefmz commented Jun 10, 2024

ideas here are to improve the failover mode

  • inspect first lines only to get whether indicator for format (see. e.g. rdf detector)
  • parse entire file first (needs performance optimizations e.g. bytesize limit)
  • think about caching parse and content type information based on etag or (modified, byte-size, content-type) combo

NOTE: in general this could be also outsourced to archivo itelf for performance reasons since it check this in the crawls anyhow. the report of archivo could be improved such that information would only be fetched from archivo, however this would not be "live" but probably good tradeoff between reliability and speed for full file validity => new mode originalFailoverArchivoMonitor
if these reports are cached in the timemachine and kept in sync then there would be almost no performance effects

@kuefmz kuefmz changed the title Extend the tests to check whether we get the right triples Check whether we get the correct format of the ontology and it can be parsed correctly Sep 27, 2024
@kuefmz kuefmz added this to the Future work milestone Sep 27, 2024
@JJ-Author JJ-Author added enhancement New feature or request and removed development labels Oct 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants