semvec/pypi-packages huggingface dataset:
jsonable-llm 0.0.1.dev0
Make 7B/13B LLM output JSON more stable
Requires Python: >=3.9

<div align="center">
  <h1>jsonable-llm</h1>
  <strong>Make 7B/13B LLM output JSON more stable</strong>
  <p>by converting your JSON schema to Markdown</p>
  <p>
    <img src="https://img.shields.io/badge/python->=3.9.11-blue">
    <a href="https://pypi.org/project/jsonable-llm/">
      <img src="https://img.shields.io/pypi/v/jsonable-llm.svg">
    </a>
  </p>
</div>
simpler-cli 0.2.0
CLI for the simple ER package collection
Requires Python: >=3.12
Keywords: entity-relationship-model, ER, extraction, model, cli, simpler

# Simple ER CLI

This is the CLI for the Simple ER Extraction [Framework](https://github.com/Cpprentice/FAIRlead-model-extraction).

## Usage

The CLI provides several commands.
You can get the help for each command by using the following:

```bash
python -m simpler_cli <command> --help
```

And replacing the command placeholder with the respective command of interest.

### extract

This command extracts an entity-relationship model from the specified data set.
It supports various output formats.
The most common ones are the Graphviz DOT format and YAML to represent the frameworks own ER model serialization.

### schema

This command takes a full YAML ER model specification and an extension file as input.
It prints the combined model to stdout.

### dot

This command converts from YAML serialization to a graphviz Dot format.
fhirsnake 1.1.0
A minimalistic FHIR server for resources as files
Requires Python: <4.0,>=3.11

<img src="https://github.com/beda-software/fhirsnake/raw/main/coral%20snake.webp" alt="fhirsnake Image" height="200">

# fhirsnake: turn static files to a FHIR server

![image](https://img.shields.io/badge/fastapi-109989?style=for-the-badge&logo=FASTAPI&logoColor=white)

## What is it?
**fhirsnake** is a minimalistic FHIR server that serve yaml and json files as FHIR resources

## How it works?
The server reads all `yaml` and `json` files from `resources` directory.
Rsources directory should have subdirectories with names equal resource types:
```markdown
resources/
├── Patient/
│   ├── example.yaml
│   ├── john-doe.json
│   └── patient3.yaml
├── Questionnaire/
│   ├── questionnaire1.yaml
│   ├── questionnaire2.yaml
│   └── questionnaire3.yaml
```

## Supported operations
> [!IMPORTANT]
> All created and updated resources persist in runtime only. All changes are vanished after service restart

- **read**, **create** and **update** operations are supported
- **search** - limied support without any search params
- `GET /$index` operation returns a map of all resources in format `<resource_type>:<id>`


## How to use?
1. Organize resources in a directory
2. Adjust source destination in `Dockerfile.resources` if required
3. Option A: Run a container
    ```bash
    docker run -p 8002:8000 -v ./resources:/app/resources  bedasoftware/fhirsnake
    ```
3. Option B: Build an image using the base image
    ```bash
    docker build -t fhirsnake-resources:latest -f Dockerfile.resources .
    docker run -p 8000:8000 fhirsnake-resources 
    ```
   
## Contribution and feedback
Please, use [Issues](https://github.com/beda-software/fhirsnake/issues)


## Development

### Format and fix with ruff
   ```sh
   ruff format
   ruff check . --fix
   ```

### Issue new version - run [semantic release](https://semantic-release.gitbook.io/semantic-release/usage/installation) locally
   ```sh
   npx semantic-release --no-ci
   ```

### Publish to pypi
   ```sh
   poetry build
   poetry publish
   ```