Newly uploaded KGE File Sets are not generally visible right away?

[RichardBruskiewich]

Due to the latency in post-processing of file sets, they don't automatically show up right away in the /home catalog (bug or feature??). Once those filesets are ready for downloading, user manual refreshing of the catalog display results in display of the new file set (looking under the good, this happens once the fileset status gets set to KgeFileSetStatusCode.VALIDATED).

It would be more satisfying to have some kind of automatic refreshing of the /home browser-hosted catalog accessed by the Javascript. This may be achieve with some clever html form signalling triggering a Javascript polling activity on the /home page which could call a new KGE Archive backend web services endpoint /<kg_id>/<fileset_version>/status endpoint on the server, which would simply return the status. The /home Javascript could then update its local browser catalog.

Extending this further, the exact status could be returned, which could include any of the following KgeFileSetStatusCode status codes:

    CREATED = "Created"
    LOADED = "Loaded"
    PROCESSING = "Processing"
    VALIDATED = "Validated"
    ERROR = "Error"

For "errors', another link could be provided to report these (at least, for the client who uploaded the fileset).