Results for concision-data

this crate provides additional tools for working with datasets

cddlc implements converters and miscellaneous tools for CDDL, RFC 8610

Filter arbitrary data trees with a concise query language.

A concise data definition language and generator for active record with the ability to properly map model associations

An extensible, concise and light weight DSL on Rake to automate data processing tasks

Advance allows you to concisely script your data transformation process and to incrementally build and easily debug that process. Each data transformation is a step and the results of each step become the input to the next step.

Provides a concise DSL to map, validate and import data from an excel sheet into your ruby app

ConfigReader provides an easy way to load up your configuration YAML files into Ruby objects, providing a more concise API to access your configuration data, by accessing methods instead of Hash keys. It also allows you to configure environment aware configuration objects, and by so inverting the logic of environment specific configuration into the ConfigReader.

TraitEngine replaces nested if/else logic with a concise DSL that maps data sources to derived attributes using reusable traits, transformations, and decision tables.

The app provides a command-line interface (CLI) to an Ollama AI model, allowing users to engage in text-based conversations and generate human-like responses. Users can import data from local files or web pages, which are then processed through three different modes: fully importing the content into the conversation context, summarizing the information for concise reference, or storing it in an embedding vector database for later retrieval based on the conversation.

The Concise Binary Object Representation (CBOR) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation (RFC8949). It is used in different protocols like the Client to Authenticator Protocol CTAP2 which is a essential part of FIDO2 authenticators/ Passkeys.

MurmuringSpider is a concise Twitter crawler. When we write a data-mining / text-mining application based on twitter timeline, we have to collect and store tweets first. I am irritated with writing such crawler repeatedly, so I wrote this. What you have to do is only to add query and to run them periodically. Thanks to consistent Twitter API and twitter gem (http://twitter.rubyforge.org/), it is quite easy to track various types of timelines (such as user_timeline, home_timeline, search...)

Lazy As Json A simple and concise way to use as_json with “only”, “except” and other options without using them literally. Instead of using this - `User.as_json(only: [:id, :first_name, profiles: [:company, :location]])` You can perhaps use this - `User.as_json(only_keys: ‘_,first_name,profiles(p),p.company,p.location’)` As simple as this. You can control what your API response should include through a flexible parameter string. i.e. - “/api/v1/users/me?_keys=_,last_name,profiles(p),p.company,p.location” This parameter string could dig through the nested objects and their nesting too. Just to reduce the API response size significantly, you can use this parameter control over wherever it is used. However it might seems quite trivial but frankly speaking it saves lot in response data hence faster loading time at client side. Moreover as it uses Hash.new and constructs attribute on runtime, you can throttle calling from the expensive method by using this parameter string.