This page documents the process for archiving the ATN observations at NCEI.
Edit me
Archive SOP
This page documents the Standard Operating Procedures for archiving the ATN observations.
The observations have been split into trajectory and profile observation types.
Each section below documents the decisions made for the archival of the data at NCEI.
Data flow
%%{
init: {
'theme': 'base',
'themeVariables': {
'primaryColor': '#007396',
'primaryTextColor': '#fff',
'primaryBorderColor': '#003087',
'lineColor': '#003087',
'secondaryColor': '#007396',
'tertiaryColor': '#CCD1D1'
},
'flowchart': { 'curve': 'basis' }
}
}%%
flowchart TD
A([Satellite Tag Deployment])
B([ATN])
D([NCEI])
E([Darwin Core Alignment])
F([IPT OBIS-USA])
G([ATN Portal])
H([NDBC])
I([GTS])
J[(NOAA OneStop)]
K[(data.gov)]
L[("Commerce
Data Hub")]
M[("IOOS Data Catalog
(data.ioos.us)")]
A --> B
B -- Data released from embargo --> D
D .-> E
D --> FC
E .-> F
B --> G
B -- BUFR msgs from Profiling Tags --> H
B .->|Data released from embargo| M
M --> FC
H --> I
F --collection--> D
subgraph FC [U.S. Federal Catalogs]
J
K
L
end
ATN WAF structure for NCEI pickup
%%{
init: {
'theme': 'base',
'themeVariables': {
'primaryColor': '#007396',
'primaryTextColor': '#fff',
'primaryBorderColor': '#003087',
'lineColor': '#003087',
'secondaryColor': '#007396',
'tertiaryColor': '#CCD1D1'
},
'flowchart': { 'curve': 'basis' }
}
}%%
flowchart TD
%% Nodes
A("Deployment")
B("Trajectory")
C("Profile")
D("Derived SSM\n(eg. Foie-gras)")
E("NCEI Archival Information Package")
%% build the graph
A --> B
A --> C
A --> D
B --> E
C --> E
D --> E
Trajectory
Package generation at ATN
Archival procedure
- Each Archival Information Package (AIP) will consist of a single tag deployment.
- Describe how the packages will be organized on ATNs server for pickup from NCEI.
- The packages will be updated when they become available as deemed appropriate by the scientist or when changes are made to the ATN DAC.
- Packages will be made available on the web accessible folder (WAF) https://ncei.axiomdatascience.com/atn/prod/
- NCEI will check for new packages once daily.
- Packages will be validated using a single manifest file which contains the md4 checksum for each file to be picked up by NCEI. The file is named
md5.txt
and will be available on the ATN WAF.
- For new submissions (ones that NCEI hasn’t made an AIP for yet)
- The package will be tranferred to NCEI.
- Once the package has been verified, the manifest files will be discarded as they are artifacts from the transfer.
- NCEI will extract the metadata from the data and metadata files to populate the AIP metadata record.
- NCEI will check metadata to ensure compliance with the agreed upon transfer agreement.
- Updates to already archived packages:
- Update the entire package?
- How will NCEI know there is a new version?
- File checksums don’t match.
- NCEI will replace files which have the same filename but differing checksum values.
- The AIP metadata record will be updated to reflect the change in the AIP contents.
- The data will be served according to Tier 1 stewardship (basic access), and Tier 2 (enhanced access) by providing access to the netCDF files via THREDDS.
NCEI checks on the package
- Package structure follows the identified structure below.
- Checksums match.
- File names match the identified convention described in File naming convention.
- Validate sea names against NCEI authority table.
- Validate variable names against NCEI authority table.
- Check people against ORCID
- Lat/Lon points are valid according to units.
- Times are valid according to units.
File naming convention
Template |
Example |
atn_ [ptt id]_ [animal common name]_trajectory_ [deployment start date]-[deployment end date].nc |
atn_38553_bearded-seal_trajectory_20110617-20120313.nc |
Variable |
Description |
Example |
ptt id |
Platform Transmitter Tag code. PTT codes may be used on multiple deployments, but not concurrently. When combined with deployment dates, PTTs can uniquely identify a deployment. |
38553 |
animal common name |
Common name of the species being tracked with spaces removed. |
bearded_seal |
deployment start date |
Start of the deployment. Following format YYYYMMDDTHHmmssZ |
20110617 |
deployment end date |
End of the deployment. Following format YYYYMMDDTHHmmssZ |
20120313 |
This sections contains an example of what the intended submission package will look like on the ATN Web Accessible Folder (WAF). Each deployment is a separate file and will be archived as an independent Archival Information Package (NCEI Accession).
Index of /atn/prod/
atn_38553_bearded-seal_trajectory_20110617-2012..> 30-Apr-2024 18:29 2515242
atn_39489_bearded-seal_trajectory_20110616-2012..> 30-Apr-2024 18:29 2425934
atn_64459_bearded-seal_trajectory_20090625-2012..> 30-Apr-2024 18:29 136505
atn_64462_bearded-seal_trajectory_20090622-2012..> 30-Apr-2024 18:29 151849
atn_66971_bearded-seal_trajectory_20110616-2012..> 30-Apr-2024 18:29 1936257
atn_66983_bearded-seal_trajectory_20110617-2014..> 30-Apr-2024 18:29 158410
atn_67004_bearded-seal_trajectory_20120703-2013..> 30-Apr-2024 18:29 148087
atn_67007_bearded-seal_trajectory_20110616-2012..> 30-Apr-2024 18:29 147924
atn_74626_bearded-seal_trajectory_20090624-2010..> 30-Apr-2024 18:29 1479689
atn_74627_bearded-seal_trajectory_20090622-2010..> 30-Apr-2024 18:29 1691372
atn_74630_bearded-seal_trajectory_20090625-2010..> 30-Apr-2024 18:29 1304864
atn_83904_bearded-seal_trajectory_20090624-2012..> 30-Apr-2024 18:29 147551
atn_99287_bearded-seal_trajectory_20120703-2013..> 30-Apr-2024 18:29 2455893
atn_99310_bearded-seal_trajectory_20110616-2012..> 30-Apr-2024 18:29 159061
md5.txt 30-Apr-2024 18:29 1246
Package sizes
These are approximate sizes of an entire SIP.
Package |
SIP Size (B) |
atn_38553_bearded-seal_trajectory_20110617-20120313.nc |
2515242 |
atn_39489_bearded-seal_trajectory_20110616-20120401.nc |
2425934 |
atn_64459_bearded-seal_trajectory_20090625-20120517.nc |
136505 |
atn_64462_bearded-seal_trajectory_20090622-20120611.nc |
151849 |
atn_66983_bearded-seal_trajectory_20110617-20140625.nc |
1936257 |
Profile
Archival procedure
NCEI checks on the package
File naming convention
Variable |
Description |
Example |
|
|
|
Tags: