Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Handle incoming file lists from NABat

Open
#536 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
graphql, python

Research direction

Start by tracing how incoming NABat data and the GraphQL acousticFileListById structure are handled; the issue names no files or tests. Investigate the three listed questions about batch metadata, combined queries, and pre-signed URL expiry. Done requires an agreed implementation scope for file lists, metadata and annotations, spectrogram generation, and file-list browsing.

Written by the indexing model from the issue text.

Description

NABat could send a list of files (or an ID referencing a list of files)

BatAI could then preemptively generate spectrograms for smoother front-end experience, mirror the data model for file lists, and provide a specialized browser for jumping around in the files in a list.

See the GraphQL structure for file lists:

acousticFileListById(id: 1) {
    name
    projectId
    createdBy
    acousticFileAcousticFileListsByListId {
      nodes {
        fileId
        acousticFileByFileId {
          id
        }
      }
    }
  }

Questions:

  1. Is there a way to get many file metadata responses at once? (single GraphQL endpoint for a batch of files)
  2. Can we use a single GraphQL query to get all information (file IDs, existing annotations, etc)
  3. How can we use the pre-signed URLs before they expire/refresh them when they do?
Dominant language
Python
Stars
10
Forks
3
Avg merge
5d 13h
Merged PRs (30d)
2

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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.

More from Kitware/batai

All issues in Kitware/batai

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.