File size: 1,787 Bytes
3967721
 
 
 
580f513
 
 
3967721
04e4882
3967721
580f513
3967721
95cc939
46e0be6
3967721
580f513
 
 
3967721
 
 
 
 
 
 
580f513
 
 
3967721
 
 
580f513
 
 
3967721
 
580f513
 
 
 
 
 
 
 
 
95cc939
46e0be6
580f513
 
 
 
 
3967721
 
 
580f513
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
# Dataset Viewer Migration

## Goal

Expose canonical and Pre-Standard recordings as separate Hub configurations so
users do not mistake different acquisition/documentation eras for an official
machine-learning split.

## Current configuration

The release candidate defines:

- `canonical/archive` — default; 360 direct Standard MP4 files
- `pre_standard/archive` — 128 direct Pre-Standard MP4 files

Both configurations use explicit direct-file globs. The canonical glob does
not recurse into `Standard_Time_Lapses/Provenance/`, so supporting historical
videos cannot enter the canonical Viewer accidentally.

```yaml
configs:
- config_name: canonical
  default: true
  data_files:
  - split: archive
    path:
    - metadata.csv
    - Standard_Time_Lapses/*.mp4
- config_name: pre_standard
  data_files:
  - split: archive
    path:
    - Pre_Standard_Time_Lapses/metadata.csv
    - Pre_Standard_Time_Lapses/*.mp4
```

The two configurations share the same declared 29-field schema. Both tiers now
have complete core encoded-video metadata, stable IDs, content hashes, and byte
sizes. Historical descriptive and provenance uncertainty remains explicit in
the Pre-Standard tier.

## Merge criteria

Merge only after the pull-request preview confirms:

1. `canonical/archive` contains exactly 360 rows.
2. `pre_standard/archive` contains exactly 128 rows.
3. No provenance video is present in either configuration.
4. Every expected row contains its metadata.
5. Stored dimensions and byte sizes load as integers.
6. `has_audio` loads as a boolean.
7. Generated Parquet artifacts succeed for both configurations.

## Split terminology

`archive` describes repository membership. It is not a training or evaluation
recommendation. No official train/validation/test partition exists.