# OpenAleph new features: Audio/Video extraction, Geocoding & Distance lookups, Peoples faces **URL:** \ **Category:** Community Projects\ **Created:** [May 26, 2025, 11:13am UTC](https://aleph.discourse.group/t/openaleph-new-features-audio-video-extraction-geocoding-distance-lookups-peoples-faces/268 "2025-05-26T11:13:06Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![simon](https://yyz2.discourse-cdn.com/free1/user_avatar/aleph.discourse.group/simon/32/10_2.png) [@simon](https://aleph.discourse.group/u/simon)\ **Post date:** [May 26, 2025, 11:13am UTC](https://aleph.discourse.group/t/openaleph-new-features-audio-video-extraction-geocoding-distance-lookups-peoples-faces/268/1 "2025-05-26T11:13:06Z")
Hey all 👋 as already shown at this years [DataHarvest](https://dataharvest.eu) conference, we introduced a set of a few nice & new features into our soft fork of Aleph, called [OpenAleph](https://openaleph.org): - [Making audio & video searchable with ✨ AI ✨](https://darc.social/t/making-audio-video-searchable-with-ai/33) - [Example dataset](https://search.openaleph.org/datasets/618) - [Search example](https://search.openaleph.org/datasets/618?cslimit=30&csq=physics#mode=search) - Geocode Address entities via [`ftm-geocode`](https://github.com/dataresearchcenter/ftm-geocode) and show geographical distance to other entities - [Example dataset](https://search.openaleph.org/datasets/615) - [See the distance between DARC and OpenStreetMap Foundation](https://search.openaleph.org/entities/addr-osm-146395129.4955f6cddc5491ff0a3133cc17a329fcc0e8d642#mode=nearby) - Show profile pictures for Person entities with a `wikidataId` property (via [`ftm-assets`](https://github.com/dataresearchcenter/ftm-assets)) - [Example dataset](https://search.openaleph.org/datasets/614) These features are a sneak preview of what we are currently working on in the open. Consider them “work in progress” and follow our [discourse](https://darc.social) for more updates. Of course we will update you here, too. [As announced previously](https://aleph.discourse.group/t/introducing-openaleph-and-the-data-and-research-center-darc/214), **OpenAleph** is a project by [DARC](https://darc.li) and a range of other contributors and will always stay open source. Feel free to comment for any questions or suggestions! Cheers, Simon ---
**Author:** ![simon](https://yyz2.discourse-cdn.com/free1/user_avatar/aleph.discourse.group/simon/32/10_2.png) [@simon](https://aleph.discourse.group/u/simon)\ **Post date:** [May 26, 2025, 11:17am UTC](https://aleph.discourse.group/t/openaleph-new-features-audio-video-extraction-geocoding-distance-lookups-peoples-faces/268/2 "2025-05-26T11:17:29Z")
We also have blogposts about the audio extraction feature: - Feature intro: [Making Audio and Video Files Searchable](https://openaleph.org/blog/2025/05/Making-Audio-and-Video-Files-Searchable/999f0117-7cf3-4099-bcd9-f60f5492c897) - Technical background: [AI Transcriptions in OpenAleph: the First Steps](https://openaleph.org/blog/2025/05/AI-Transcriptions-in-OpenAleph:-the-First-Steps/68450c9c-78e7-4e3f-8743-40ad6ba7b4f9/) ---
**Author:** ![pudo](https://yyz2.discourse-cdn.com/free1/user_avatar/aleph.discourse.group/pudo/32/41_2.png) [@pudo](https://aleph.discourse.group/u/pudo)\ **Post date:** [May 26, 2025, 11:18am UTC](https://aleph.discourse.group/t/openaleph-new-features-audio-video-extraction-geocoding-distance-lookups-peoples-faces/268/3 "2025-05-26T11:18:14Z")
The distance tables and the audio transcript are absolutely nuts! Are you running `ftm-geocode` before sending the entities to the API, or did you end up doing it as an analyzer in the ingest framework? ---
**Author:** ![simon](https://yyz2.discourse-cdn.com/free1/user_avatar/aleph.discourse.group/simon/32/10_2.png) [@simon](https://aleph.discourse.group/u/simon)\ **Post date:** [May 26, 2025, 11:21am UTC](https://aleph.discourse.group/t/openaleph-new-features-audio-video-extraction-geocoding-distance-lookups-peoples-faces/268/4 "2025-05-26T11:21:05Z")
Currently, we would preprocess them before sending to the api. But we are actively working on making it part of the ingestion process. For this, we are currently considering if it should be part of `ingest-file` which would blow up the already huge docker image because of libpostal dependencies, or if this now (together with whisper) is a great time to split up `ingest-file` in smaller parts (which would introduce a rework of the task queuing, again… 😂 ) Just thinking out loud here. ---
**Author:** ![pudo](https://yyz2.discourse-cdn.com/free1/user_avatar/aleph.discourse.group/pudo/32/41_2.png) [@pudo](https://aleph.discourse.group/u/pudo)\ **Post date:** [May 26, 2025, 11:24am UTC](https://aleph.discourse.group/t/openaleph-new-features-audio-video-extraction-geocoding-distance-lookups-peoples-faces/268/5 "2025-05-26T11:24:01Z")
Ah nice, so `ingest-file` and `analyze-entity` in essence? We played with this before and it seemed like a nice pattern to me: [GitHub - alephdata/translate-service: Demo: document processing service for automated translation](https://github.com/alephdata/translate-service) ---
**Author:** ![simon](https://yyz2.discourse-cdn.com/free1/user_avatar/aleph.discourse.group/simon/32/10_2.png) [@simon](https://aleph.discourse.group/u/simon)\ **Post date:** [May 26, 2025, 11:26am UTC](https://aleph.discourse.group/t/openaleph-new-features-audio-video-extraction-geocoding-distance-lookups-peoples-faces/268/6 "2025-05-26T11:26:19Z")
Yes, something like this. As more advanced analyzing features would come in (looking at ✨ AI ✨ ) you might want to run different ingestion services on different infrastructure, ideally without docker or any other virtualization, for specific tasks. ---
**Author:** ![alex](https://yyz2.discourse-cdn.com/free1/user_avatar/aleph.discourse.group/alex/32/8_2.png) [@alex](https://aleph.discourse.group/u/alex)\ **Post date:** [May 29, 2025, 9:12am UTC](https://aleph.discourse.group/t/openaleph-new-features-audio-video-extraction-geocoding-distance-lookups-peoples-faces/268/7 "2025-05-29T09:12:32Z")
We published [a blog post](https://openaleph.org/blog/2025/05/Putting-a-Face-to-the-Name/c003a3a8-ce3d-4745-b61c-ed52e3898525/) about the feature that displays an image next to every FTM entity that has the `wikidataId` property set. We also published [a tutorial](https://github.com/dataresearchcenter/tutorials/tree/main/Tutorial%3A%20Display%20Images%20for%20Vessels) that walks folx, step by step, through scraping data, creating FTM entities, uploading them and enjoying the little image thumbnails in their own instance. We’re planning to release more of these little tutorials, as Jupyter notebooks, because it feels like they’re excellent ways to explore the entire ecosystem of open-source tools that has emerged around Aleph. 🙂 And, who knows, maybe one they these can serve as the basis of a curricula!