arkflow VS colibri

Incidentally arkflow implements VRL https://github.com/arkflow-rs/arkflow/pull/273

# Clone the repository git clone https://github.com/chenquan/arkflow.git cd arkflow # Build the project cargo build --release # Run tests cargo test

I'm working on a self-hostable ebook library (https://github.com/colibri-hq/colibri), and currently tinkering with searching over book content. Have you written about your approach to search somewhere, perhaps? Would be very interested in learning how others go about this. Kudos for DocGlobin, looks great :-)

Im working on a similar project, Colibri (https://github.com/colibri-hq/colibri), an app to manage your ebook collection. Librari is looking really slick! Also, It’s always interesting to see how others approach schema selection and customization.

If I may, I would suggest adding support for ingesting data from open sources, for example OpenLibrary, WikiData, the LoC API, and a bunch of others. Since you’re building a for-profit project, you can probably also tap the billed services to get high-quality metadata. But even with OpenLibrary alone, you have access to a treasure trove of information that spares users from having to type off things from their books. That allows for bulk import, high-res covers, and so on.

I’m currently working on the metadata reconciliation engine in Colibri, so feel free to check out the source every once in a while.

Funny thing. I have built something similar recently, that is a 2.1-compliant authorisation server in TypeScript[0]. I did it by hand, with some LLM help on the documentation. I think it took me about two weeks full time, give or take, and there’s still work to do, especially on the testing side of things, so I would agree with you.

I’m going to take a very close look at your code base :)

[0] https://github.com/colibri-hq/colibri/blob/next/packages/oau...

Semantic search is planned as part of book content search, look here: https://github.com/colibri-hq/colibri/issues/45

LLMs might make sense to interact with your collection, so that could find its way into the app at some point. Plus, I've been experimenting with generating llms.txt for all routes to point your own LLM to.

On the other hand, I'm concerned with LLMs quite intensely at work, so it's nice to spend some time with plain, honest-to-god SQL for now!

But currently it's from openlibrary.org right? https://github.com/colibri-hq/colibri/blob/next/apps/app/src...

Oh my! This looks very neat, and I’ve been working on something similar to Storyteller (i think): https://github.com/project-kiosk/kiosk

I don’t get around working on it right now, but maybe there’s something useful there for you.

I'm actually working on something like this:

https://github.com/project-kiosk/kiosk/tree/v3

I'm still deep in the trenches, though. That project is like my personal zen garden of deadline-free software development, so don't expect a release soon. Happy if someone would be interested in contributing, though :)

Interesting! For a while now, I’ve started working on a similar project with the same general idea, although I settled for SvelteKit and browsers instead of native apps:

https://github.com/project-kiosk/kiosk

I just can’t keep motivation up long enough to finish it…