NatLabRockies / NatLabRockies/COMPASS

Allow multiple schemas for one shot

Open
#393 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
17
Forks
4
Avg merge
2d 7h
Merged PRs (30d)
17

Description

It might be good to allow users to provide multiple schemas, which would set up multiple parsers for the one shot extraction.

Key considerations:

  • Auto generating queries, heuristic keywords, and keywork scores will become tricker. Might be able to get around this by only merging the "features" and "$descriptions" into a "main" schema and using that as the template
  • Allowing custom prompts for text collection and text extraction will have to support a per-schema approach. Likely the safest way to do this is to use a dict keyed by the schema filename (no extension?), but it's kind of ugly. Could also disable custom prompts for a multi-schema input but this seems unnecessarily restrictive. Maybe instead the schema input itself is a dict and then keys can match between those? No matter what, this is kind of a bookkeeping nightmare
  • The auto generated collection/text extraction prompts as well as the parsers should be on a 1-per-input schema basis, with the data getting concatenated at the very end like we do for wind/solar

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the existing one-schema extraction flow and the wind/solar handling referenced in the issue. Identify how schemas, generated collection and extraction prompts, parsers, and final concatenation currently work. Done would mean multiple schemas can run independently while supporting the required prompt behavior and combining their results.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
ai
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.