Thinh Nguyen

add mechanism to check for processing progress at schema level

6

Add new method `progress` for the schema object, returning the populate progress for all imported/computed tables for a given schema (also accounts for `reserved`, `error`, `ignore` jobs)

Dataset transfer

1

Related to Issue #560 DataJoint needs a feature to select a subset of data to be transferred to another database (with identical scheme/pipeline design) For instance, users would select particular...

schema name should not allow "upper-case"

1

A schema name with upper-case letter in it will result in incorrect behavior when referenced by another schema. Note: no error thrown Quick example: ```python schema = dj.schema('Schema_A') @schema class...

`context` required for parent tables having `AttributeAdapter` type

1

For parent tables with attributes of adapted type, the context is required to find the adapter object. But when declare tables with `dj.FreeTable`, context was not provided. This bug prevents...

Support meta information for `filepath` attributes.

13

An example use-case is to work with NWB files more elegantly. For a particular NWB object, we need to store 2 things: `object_id` - varchar(36) and `nwb_file` - filepath@store Currently...

Strain on MySQL resource with "expensive" key-source

5

For tables with complicated/expensive key-source to be computed. When multiple workers calling `populate()` on this table at the same time, the initial `key-source` calculation by all of these workers creates...

Introduce a new argument `return_success_count` to the `.populate()` routine, that would return the count of successful `make()` calls in one `.populate()` call. This functionality allows for us to answer the...