Jan Niestadt

Here's a few test queries we can use: http://172.16.4.23/mediawiki/index.php/SRU_application_(Corpus_Search)#Testing

We should decide whether keeping everything in CQL on the frontend side is worth the effort, or if we should opt for a different URL scheme that's easier to develop...

If we move as much corpus-frontend functionality as possible to JS, which we eventually want to do anyway, this issue will go away, as BLS will be accessed from the...

To fix this, BLS should also 404 if you request information about a corpus you're not authorized to see. Currently it only restricts searches and documents, not corpus information.

About 'publish corpus': unclear if we can do this without inviting legal troubles. About 'edit corpus metadata': you can put corpus metadata in the input format file, but that's only...

This is currently not yet possible, unfortunately. If you want to take a stab at implementing this, here's a way to go about it: - documents that differ from the...

Have a look at [HitsTable.vue](https://github.com/INL/corpus-frontend/blob/dev/src/frontend/src/pages/search/results/table/HitsTable.vue). For the table headings, you can customize the text via custom locale files, see [here](https://github.com/INL/corpus-frontend/tree/dev?tab=readme-ov-file#internationalization). Create a file e.g. `$corporaInterfaceDataDir/MyCorpus/static/locales/en-us.json` containing: ```json { "results": {...

It's difficult for me to help without knowing your data, .blf.yaml and changes to corpus-frontend. If you have your own clone of BlackLab on GitHub, you can easily create a...

I've updated corpus-frontend as I suggested above and it looks like it's working with your corpus (latest dev BlackLab and frontend). Let us know if it looks okay. `~/.blacklab` applies...

Sorry for the late reply. I just tried it with your sample from last year, and it seems to display hits correctly with v4.0.0 of the frontend. I'm running a...