Skip to content

Commit 2d232db

Browse files
committed
[chore] Update TODO list with completed tasks and new considerations
1 parent 8023f6e commit 2d232db

1 file changed

Lines changed: 8 additions & 13 deletions

File tree

TODO.md

Lines changed: 8 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -9,10 +9,10 @@ TODO.md
99
- [ ] Datasets Package
1010
- [x] Documents dataset (mabye rename to DocumentDataset)
1111
- [ ] Chunks Package (or part of DocumentDataset?)
12-
- [ ] Move Model repository to datasets package.
13-
- [ ] Chunks and nodes are not always the same.
14-
- [ ] And we may need to save the chunk's node path. Or paths? or document range? Standard metadata?
15-
- [ ] Instead of passing doc_id around, pass a document key that is unknonwn (string or object)
12+
- [x] Move Model repository to datasets package.
13+
- [x] Chunks and nodes are not always the same.
14+
- [x] And we may need to save the chunk's node path. Or paths? or document range? Standard metadata?
15+
- [ ] Instead of passing doc_id around, pass a document key that is of type unknonwn (string or object)
1616

1717
- [ ] Get a better model for question answering.
1818
- [ ] Get a better model for named entity recognition, the current one recognized everything as a token, not helpful.
@@ -25,16 +25,11 @@ TODO.md
2525
- [ ] rename the registration stuff to not look ugly: registerHuggingfaceTransformers() and registerHuggingfaceTransformersUsingWorkers() and registerHuggingfaceTransformersInsideWorker()
2626
- [ ] fix image transferables
2727

28-
onnx-community/ModernBERT-finetuned-squad-ONNX - summarization
28+
- [ ] Consider different ways to connect tasks to queues. What is a task? What is a job?
29+
30+
- [ ] Input and outputs are all scalar, arrays, or unions. But what about streams? Stream of items in an array, stream of content for a scalar like a string, etc.
2931

30-
- [x] Auto-generated primary keys for TabularStorage
31-
- [x] Schema annotation with `x-auto-generated: true`
32-
- [x] Type system with `InsertEntity` for optional auto-generated keys
33-
- [x] Support for autoincrement (integer) and UUID (string) strategies
34-
- [x] Configurable client-provided keys: "never", "if-missing", "always"
35-
- [x] Implementations: InMemory, SQLite, Postgres, Supabase, IndexedDB, FsFolder
36-
- [x] Comprehensive test suite (342 tests pass)
37-
- [x] Documentation updated
32+
onnx-community/ModernBERT-finetuned-squad-ONNX - summarization
3833

3934
Rework the Document Dataset. Currently there is a Document storage of tabular storage type, and that should be registered as a "dataset:document:source" meaning the source material in node format. And there is already a "dataset:document-chunk" for the chunk/vector storage which should be registered as a "dataset:document:chunk" with a well defined metadata schema. The two combined should be registered as a "dataset:document" which is the complete document with its source and all its chunks and metadata. This is for convenience but not used by tasks or ai tasks.
4035

0 commit comments

Comments
 (0)