node-manager-training
Curriculum for training node managers in how to operate an OTN Database Node system
https://github.com/ocean-tracking-network/node-manager-training
Science Score: 67.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
✓CITATION.cff file
Found CITATION.cff file -
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
✓DOI references
Found 2 DOI reference(s) in README -
✓Academic publication links
Links to: zenodo.org -
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (9.4%) to scientific vocabulary
Repository
Curriculum for training node managers in how to operate an OTN Database Node system
Basic Info
- Host: GitHub
- Owner: ocean-tracking-network
- License: other
- Language: HTML
- Default Branch: gh-pages
- Homepage: https://ocean-tracking-network.github.io/node-manager-training/
- Size: 102 MB
Statistics
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 12
- Releases: 2
Metadata Files
README.md
Welcome to OTN's Node Manager Training Curriculum.
This OTN-hosted training will provide OTN-style Node Managers with an overview of the processes and tools to use to 1) ensure data is formatted correctly and free form errors, 2) ingest data into the Database Node and 3) create any relevant data products for members of their Node.
Attendees should be detail oriented, in-tune with their local telemetry communities, and not afraid to ask questions!
The website rendering is available here https://ocean-tracking-network.github.io/node-manager-training/index.html
General Node Manager Training Agenda
The next scheduled training is December 2nd - 6th, 2024 in Halifax, NS, at the Steele Ocean Sciences Building (OTN Headquarters). Invitees from new and existing nodes will explore the OTN Node curriculum with the OTNDC team. A draft agenda (subject to update or amendment) for the week's proceedings:
Day 1
Welcome
- Presentation: Introduction to Nodes (virtual connections available)
- The Ocean Tracking Network's Data Centre, the Care of Animal Tracking Data, and the Database Node concept - Jon Pye
- Data Policies and User Agreements
- What your user agreement or data policy says you can and can't do w/ other folks' data in your Node
- The common rules across our Agreements that allow Nodes to interoperate
Lightning Introductions for attendees: Maximum of Three (3) slides describing each Node Manager's background, the community the Node serves, and how you're hosted/funded.
- FACT - Danielle Morley (Florida FWC)
- ACT - Kim Richie & Beth Bowers (Smithsonian)
- PIRAT - Tom TinHan (UH)
- PATH - Jon Walter (UC Davis)
- MigraMar - Marta Cambra (U Costa Rica)
- iTag - Claudia Friess & Hannah Gottesman (UFl + TAMU)
- NPACT - Ryan Freedman & Ryan Logan (NOAA)
- RAFT - Matt Walker (USGS)
- ETN - Claudia Meneses (VLIZ)
- ATN - Megan McKinzie (MBARI)
AM Break * Lightning Introductions cont? * OTN System, Structure, and Outputs * Schema structure and data workflows
- Software Setup and Installation
- Python
- Git
- Nodebooks
Lunch
The Data Loading Workflow
- How data is received
- Documenting data loading tasks
- Accessing and querying your database
Data Loading - Project Metadata
- Practical - register metadata about new projects to the Node
Day 2
- Data Loading - Tagging Metadata
- Practical - load records of deployed tags to a project in the Node
- Validation - internally consistent data
- Verification - data consistent across the database
AM Break
- Data Loading - Deployment Metadata
- Practical - load records of deployed listening equipment to a project in the Node
- Validation - internally consistent data
- Verification - data consistent across the database
Lunch
- Detection Loading
- Practical - load detection files from the listening instruments to a project in the Node
- Validation - unedited files created by the instrument or client software for the instrument
- Verification - proper formatting of serials, models, dates
- Recorded Events data loaded from instrument
- tilt, temperature, etc.
PM Break
- Detection Loading cont.
- Verification - detections not previously loaded
- Correction - time drift calculations
- Verification - no missing metadata
- Events - create receiver configuration record from Event data
- listening scheme (OP, NexTrak, MAP-114, etc.)
- Match detections to animal tags registered to any project within the Database Node
Day 3
- Moving Platforms
- Loading Detections and Mobile Receiver Deployments
AM Break * Moving Platforms cont. * Gliders
Lunch * Moving Platforms cont. * Satellite-tagged animals * Manual Sampling
PM Break * Visualization Notebooks * Node summaries of counting statistics * Project-by-project reporting * Other
- Evening: Dinner - venue TBD
Day 4
- Fixing Data Errors
- The DB-Fix Notebooks
AM Break
- Fixing Data Errors cont.
Lunch
- The Data Push
- Rationale, Process, Schedule
- Creating detection extracts for researchers
PM Break
- OTN All-Hands meeting
Day 5
Supplementary Notebooks
- scientificnamecheck
- Registering new instrument models
- vendor tag and sales sheets
- Health reporting
- Contacts updates
Nodebook Development and Improvements
Lunch * Tandem real data loading w/ OTNDC or DB-Fix notebooks
Owner
- Name: Ocean Tracking Network
- Login: ocean-tracking-network
- Kind: organization
- Email: otndc@dal.ca
- Location: Halifax, NS
- Website: https://oceantrackingnetwork.org
- Twitter: OceanTracking
- Repositories: 22
- Profile: https://github.com/ocean-tracking-network
Citation (CITATION)
Please cite as: Greg Wilson (ed.): "Software Carpentry: Lesson Example." Version 2016.06, June 2016, https://github.com/carpentries/lesson-example, 10.5281/zenodo.58153.
GitHub Events
Total
- Create event: 25
- Release event: 2
- Issues event: 43
- Watch event: 1
- Delete event: 1
- Issue comment event: 76
- Push event: 103
- Pull request review event: 36
- Pull request review comment event: 26
- Pull request event: 52
Last Year
- Create event: 25
- Release event: 2
- Issues event: 43
- Watch event: 1
- Delete event: 1
- Issue comment event: 76
- Push event: 103
- Pull request review event: 36
- Pull request review comment event: 26
- Pull request event: 52
Issues and Pull Requests
Last synced: 10 months ago
All Time
- Total issues: 5
- Total pull requests: 3
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Total issue authors: 4
- Total pull request authors: 3
- Average comments per issue: 0.0
- Average comments per pull request: 0.0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 5
- Pull requests: 3
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Issue authors: 4
- Pull request authors: 3
- Average comments per issue: 0.0
- Average comments per pull request: 0.0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
- CaitlinBate (9)
- jackVanish (7)
- yingniu (5)
- jdpye (5)
- diniangela (2)
- joyliujoyliu (1)
- naomitress (1)
Pull Request Authors
- jackVanish (14)
- jdpye (7)
- CaitlinBate (3)
- diniangela (2)
- yingniu (2)
- slandovs (2)
- brian-lorenzo-jones (1)
- PatrickWMartin (1)
- bmanjones (1)
Top Labels
Issue Labels
Pull Request Labels
Dependencies
- coveralls > 0.7 development
- launchy ~> 2.4, >= 2.4.3 development
- memory_profiler >= 0 development
- rake >= 12.3.3 development
- redcarpet >= 0 development
- rspec ~> 3.8 development
- rspec-its ~> 1.3 development
- simplecov >= 0 development
- yard >= 0 development
- idn-ruby >= 0
- luna-rspec-formatters >= 0 development
- rspec-helpers >= 0 development
- rake >= 0
- rspec ~> 3.1 development
- awesome_print >= 0 development
- bundler ~> 1.2 development
- json ~> 1.8.1 development
- minitest ~> 5.6 development
- rake-compiler ~> 0.9 development
- rdoc ~> 5.1 development
- ruby-enum ~> 0.5
- pry ~> 0.11 development
- rake-compiler ~> 1.0, >= 1.0.7 development
- rake-compiler-dock ~> 1.0 development
- rspec ~> 3.7 development
- sigdump >= 0 development
- timecop ~> 0.7.4 development
- bench9000 >= 0
- benchmark-ips ~> 2.7
- coveralls ~> 0.8.2
- md-ruby-eval ~> 0.6
- redcarpet ~> 3.0
- simplecov ~> 0.16.0
- yard ~> 0.9.0
- coveralls ~> 0.7 development
- minitest ~> 5.14.4 development
- minitest-display >= 0.3.1 development
- nio4r ~> 2.0 development
- rake >= 13.0.6 development
- rubydns ~> 2.0.1 development
- yard ~> 0.9 development
- simpleidn ~> 0.1
- em-http-request ~> 1.1.1
- em-spec ~> 0.2.6
- em-websocket-client >= 0
- rake >= 0
- rspec ~> 3.5.0
- benchmark-ips >= 0 development
- curb >= 0 development
- json < 2 development
- json >= 0 development
- mime-types ~> 1.18 development
- mustermann = 0.4.0 development
- mustermann = 0.3.1 development
- mustermann >= 0 development
- patron >= 0 development
- rspec ~> 3.4 development
- sinatra >= 0 development
- webrick >= 0 development
- rake >= 0
- rake < 11
- ffi >= 1.15.0
- bundler >= 1.16, < 3 development
- kramdown >= 0 development
- rake ~> 13.0 development
- rake-compiler ~> 1.0.3 development
- rake-compiler-dock ~> 1.0 development
- rspec ~> 3.0 development
- yard ~> 0.9 development
- rake ~> 13.0 development
- rake-compiler ~> 1.0 development
- rake-compiler-dock ~> 1.0 development
- rspec ~> 2.14.1 development
- codeclimate-test-reporter >= 0 development
- luna-rspec-formatters >= 0 development
- luna-rubocop-formatters >= 0 development
- rspec >= 0 development
- rspec-helpers >= 0 development
- rubocop >= 0 development
- rake >= 0
- dotenv ~> 2.7 development
- gem-release ~> 2.1 development
- pry ~> 0.10 development
- pry-byebug >= 0 development
- rspec ~> 3.0 development
- rubocop ~> 0.52 development
- webmock ~> 3.8 development
- addressable ~> 2.3
- dnsruby ~> 1.60
- octokit ~> 4.0
- public_suffix >= 3.0, < 5.0
- typhoeus ~> 1.3
- RedCloth ~> 4.2.9 development
- appraisal >= 0 development
- bundler >= 0 development
- commonmarker ~> 0.16 development
- email_reply_parser ~> 0.5 development
- escape_utils ~> 1.0 development
- gemoji ~> 2.0 development
- minitest >= 0 development
- minitest-focus ~> 1.1 development
- rake >= 0 development
- rinku ~> 1.7 development
- rouge ~> 3.1 development
- sanitize ~> 4.6 development
- activesupport >= 2
- nokogiri >= 1.4
- benchmark_suite ~> 1.0 development
- ffi ~> 1.9 development
- jruby-openssl >= 0 development
- json ~> 2.1 development
- rake-compiler ~> 1.0 development
- rspec ~> 3 development
- yajl-ruby ~> 1.3 development
- yajl-ruby = 1.2.1 development
- bundler > 1.0, < 3.0 development
- rake ~> 12.3 development
- rspec ~> 3.0 development
- rspec-html-matchers ~> 0.9 development
- rubocop-jekyll ~> 0.10.0 development
- jekyll >= 3.0, < 5.0
- bundler >= 0 development
- rake ~> 12.0 development
- rspec ~> 3.0 development
- rubocop-jekyll ~> 0.5 development
- commonmarker ~> 0.14
- jekyll >= 3.7, < 5.0
- rake >= 0 development
- rspec ~> 3.0 development
- commonmarker ~> 0.17.6
- jekyll-commonmark ~> 1.2
- rouge >= 2.0, < 4.0
- github-pages >= 0
- bundler ~> 1.6 development
- jekyll >= 3.0 development
- rake >= 0 development
- rspec >= 0 development
- rubocop ~> 0.51 development
- webmock >= 0 development
- octokit ~> 4.2
- bundler ~> 1.5 development
- jekyll ~> 2.0 development
- rake >= 0 development
- rspec ~> 3.0 development
- bundler >= 0 development
- jekyll-sitemap ~> 1.0 development
- rake ~> 12.0 development
- rspec ~> 3.5 development
- rubocop-jekyll ~> 0.10 development
- jekyll >= 3.3, < 5.0
- bundler >= 1.15 development
- html-proofer ~> 3.7 development
- rspec ~> 3.5 development
- rubocop-jekyll ~> 0.11 development
- jekyll >= 3.8, < 5.0
- bundler >= 0 development
- rake >= 0 development
- rspec ~> 3.0 development
- rubocop-jekyll ~> 0.4 development
- jekyll >= 3.7, < 5.0
- bundler ~> 1.3 development
- rake >= 0 development
- rspec ~> 3.0 development
- rake >= 0 development
- bundler >= 1.3, < 3 development
- rake >= 0 development
- rspec ~> 3.4 development
- bundler >= 1, < 3 development
- faraday >= 0.9
- sawyer >= 0.5.3, ~> 0.8.0
- benchmark-ips >= 0 development
- luna-rspec-formatters >= 0 development
- pry >= 0 development
- rspec >= 0 development
- rspec-helpers >= 0 development
- rubocop >= 0 development
- safe_yaml >= 0 development
- simple-ansi >= 0 development
- simplecov >= 0 development
- rake >= 0
- codecov >= 0
- memory_profiler >= 0
- minitest >= 0
- minitest-reporters >= 0
- mocha >= 0
- rake >= 0
- rubocop ~> 0.90
- yard >= 0
- ruby $RUBY_VERSION-slim build
- PyYAML *
- update-copyright *
- guard-rspec ~> 4.2 development
- rake ~> 12.0 development
- rspec ~> 3.6 development
- coveralls >= 0 development
- pry >= 0 development
- pry-coolline >= 0 development
- simplecov >= 0 development
- tty-prompt >= 0 development
- bundler >= 0 development
- concurrent-ruby >= 0 development
- rake >= 0 development
- rspec ~> 3.6 development
- ffi ~> 1.0
- github-markup >= 0 development
- pry >= 0 development
- shotgun >= 0 development
- sinatra >= 0 development
- sinatra ~> 1.4.8 development
- git >= 0
- memory_profiler >= 0
- minitest >= 5.0
- minitest-power_assert >= 0
- rake >= 0
- redcarpet >= 0
- rubocop ~> 0.49.1
- yard >= 0
- danger >= 0 development
- danger-changelog = 0.6.1 development
- danger-toc = 0.2.0 development
- rspec ~> 3.0 development
- rubocop = 0.80.1 development
- simplecov >= 0 development
- rake >= 0
- activesupport 6.1.0
- addressable 2.7.0
- ast 2.4.2
- bundler 2.1.4
- claide 1.0.3
- claide-plugins 0.9.2
- colored2 3.1.2
- concurrent-ruby 1.1.7
- cork 0.3.0
- danger 8.2.1
- danger-changelog 0.6.1
- danger-plugin-api 1.0.0
- danger-toc 0.2.0
- diff-lcs 1.3
- docile 1.3.5
- faraday 1.3.0
- faraday-http-cache 2.2.0
- faraday-net_http 1.0.0
- git 1.8.1
- i18n 1.8.7
- jaro_winkler 1.5.4
- kramdown 2.3.0
- kramdown-parser-gfm 1.1.0
- minitest 5.14.3
- multipart-post 2.1.1
- nap 1.1.0
- no_proxy_fix 0.1.2
- octokit 4.20.0
- open4 1.3.4
- parallel 1.20.1
- parser 3.0.0.0
- public_suffix 4.0.6
- rainbow 3.0.0
- rake 13.0.1
- rchardet 1.8.0
- rexml 3.2.4
- rspec 3.9.0
- rspec-core 3.9.1
- rspec-expectations 3.9.1
- rspec-mocks 3.9.1
- rspec-support 3.9.2
- rubocop 0.80.1
- ruby-enum 0.9.0
- ruby-progressbar 1.11.0
- ruby2_keywords 0.0.2
- sawyer 0.8.2
- simplecov 0.21.2
- simplecov-html 0.12.3
- simplecov_json_formatter 0.1.2
- terminal-table 1.8.0
- tzinfo 2.0.4
- unicode-display_width 1.6.1
- zeitwerk 2.4.2
- i18n >= 0
- hashie >= 0 development
- heredoc_unindent >= 0 development
- rake >= 0 development
- rspec >= 0 development
- travis-lint >= 0 development
- minitest >= 0 development
- rake >= 0
- addressable >= 2.3.5
- faraday > 0.8, < 2.0
- codecov >= 0 development
- rspec >= 0 development
- simplecov >= 0 development
- bundler ~> 1.11 development
- rake ~> 10.0 development
- rspec ~> 3.0 development
- unf ~> 0.1.4
- tins ~> 1.0.0
- bundler ~> 1.10 development
- pry >= 0 development
- rake ~> 10.0 development
- rspec >= 3.0 development
- term-ansicolor >= 0 development
- unicode-display_width ~> 1.1, >= 1.1.1
- countloc ~> 0.4.0 development
- coveralls ~> 0.7.11 development
- inch ~> 0.5.10 development
- redcarpet ~> 3.2.2 development
- rspec ~> 3.2.0 development
- simplecov ~> 0.9.2 development
- term-ansicolor ~> 1.3.2 development
- tins ~> 1.6.0 development
- yard ~> 0.8.7.6 development
- atomic = 1.1.16 development
- rake < 12.0 development
- rspec ~> 3.2 development
- dalli ~> 2.0 development
- faraday >= 0.9 development
- guard-rspec ~> 0.7 development
- rb-fsevent ~> 0.9.1 development
- redis ~> 3.0 development
- rspec ~> 3.0 development
- sinatra ~> 1.3 development
- spoon >= 0 development
- json < 2
- json >= 0
- rake >= 0
- rake < 11
- ethon >= 0.9.0
- thread_safe ~> 0.1
- activesupport < 4.0 development
- bundler >= 1.2.0 development
- rake >= 0.9.2.2 development
- rdoc > 2.4.2 development
- bundler >= 1.2 development
- rake >= 0.9.2.2 development
- rake-compiler >= 1.1.1 development
- rake-compiler-dock >= 1.1.0 development
- rdoc > 2.4.2 development
- test-unit >= 0 development