| 1 |
What don't we know from the filenames: |
| 2 |
|
| 3 |
- product: ? More logic needed |
| 4 |
- realm: from the MIP table |
| 5 |
- version: Must be deduced form datanode? |
| 6 |
- institute: Configured on ingest |
| 7 |
- frequency: From MIP table |
| 8 |
- activity: Configured on ingest |
| 9 |
|
| 10 |
|
| 11 |
Versioning |
| 12 |
========== |
| 13 |
|
| 14 |
isenes.drslib is going to be where the version directory structure |
| 15 |
tool lives. |
| 16 |
|
| 17 |
Definitions |
| 18 |
----------- |
| 19 |
|
| 20 |
DRSTree: A DRS filesystem hierarchy rooted at a given path. Each DRS |
| 21 |
tree is associated with a set of PublisherTree. |
| 22 |
|
| 23 |
PublisherTree: A directory containing multiple versions of a |
| 24 |
publication-level dataset. A PublisherTree can be in one of several states: |
| 25 |
|
| 26 |
1. InitialCMOR |
| 27 |
2. VersionedPrepublished |
| 28 |
3. VersionedPublished |
| 29 |
4. VersionedTransition |
| 30 |
|
| 31 |
|
| 32 |
gridspec support |
| 33 |
---------------- |
| 34 |
|
| 35 |
Gridspec files have a different syntax to DRS data files. They are of |
| 36 |
the form: |
| 37 |
|
| 38 |
gridspec_<realm>_fx_<model>_<experiment>_r0i0p0.nc' |
| 39 |
|
| 40 |
drslib has not been designed to deal with this syntax therefore a work-around is in place to map these files to the following DRS components: |
| 41 |
|
| 42 |
- activity, product, institute: as configured |
| 43 |
- model, experiment, realm: as above |
| 44 |
- frequency: "fx" |
| 45 |
- mip_table: "fx" |
| 46 |
- variable: "gridspec" |