• Data Team Reference Guide
  • About
  • Miscellaneous
    • Code Snippets
    • File paths
      • Remote files vs. local files
      • File path shortcuts
    • Metacat version
    • Resources for R
      • Learning
      • Packages
  • Edit data packages
    • datapack Background
      • Navigating data packages
      • Data Objects
      • Provenance
    • Create a new data package
      • Upload new data files
      • Upload the package
    • Update packages with datapack
      • Get the package
      • Update the metadata
      • Modify the data files
      • Publish update
    • Add a pre-generated identifier to the EML
    • Edit sysmeta
      • Identifiers and sysmeta
      • Additional resources
    • Obsolescence chain
    • Set DataONE nodes
      • Staging (Test) nodes
      • Production nodes
    • Set rights and access
      • My profile
    • Show indexing status
    • Preserve folder structures
      • Download the zip file to datateam
      • Re-upload the contents to the Arctic Data Center
      • Summary
      • Example with multiple ZIP files
    • Update a package with a new data object
      • Publish update
    • Update an object
  • Explore EML
    • Access specific elements
    • Navigate through EML
    • Understand the EML schema
  • Edit EML
    • Edit an EML element
      • Edit EML with strings
      • Edit EML with the “EML” package
      • Edit EML with objects
    • Edit attributeLists
      • Edit attributes
      • Edit custom units
      • Edit factors
      • Finalize attributeList
    • Edit custom units
    • Edit dataTables
    • Edit otherEntities
      • Remove otherEntities
      • Create otherEntities
    • Semantic annotations
      • How annotations are used
      • How to add an annotation
      • Dataset Annotations
    • Edit spatial data
      • Reading Spatial Files
      • spatialVector
      • spatialRasters
    • Format text in EML
      • Type-setting
      • Links
      • Lists
    • Series Identifier (SID)
      • Adding a SID to a package
      • Updating the child packages of a parent package with a SID
      • Updating the metadata of a package with a SID
    • Set coverages
      • Set multiple coverages
      • Special coverages
    • Set methods
      • Adding sampling info to methods section
    • Set parties
    • Set physical
    • Set the project section
    • Use references
      • Example with parties
      • Example with attributes
  • PI correspondence
    • Email templates
      • Initial email template
      • Comment templates based on what is missing
      • Final email templates
      • Additional email templates
    • PI FAQ email templates
      • Data
      • Access
      • Scope
    • Good Examples of data packages
    • Final Checklist
      • Special Datasets
      • System Metadata
      • General EML
      • Title
      • Abstract
      • DataTable / OtherEntity / SpatialVectors
      • People
      • Geographic region
      • Project
      • Methods
      • Check EML Version
      • Access
      • SFTP Files
      • Updated datasets
    • Initial review checklist
    • Large file transfer
      • sFTP
      • Globus Endpoint
    • Navigate RT
      • Front page
      • All tickets
      • Example ticket
      • New data submission
    • Replicate Datasets
      • Cloning the packages
  • Miscellaneous file types
    • Convert Excel file to CSV
    • Datalogger files
    • NetCDFs
    • Reorganize files on the server
      • Basics
      • Rename file based on file path
      • Unzip files
      • Zip shapefiles
    • Scan rar files
    • Spatial data
  • Wrangle data
    • Clean column names
    • Fix Excel dates
  • Solr queries
    • Construct a query
    • Query Solr via a browser
    • Query Solr via R
    • Use facets
    • Use stats
    • Example Solr queries
      • Find everything
      • Query a wildcard expression
      • Query multiple fields
      • Query by formatType
      • Query pids by a specific submitter
      • Query pids with special characters
      • Query multiple conditions within one field
      • Query for latest versions only
      • Use NOT in a query
      • Query a coordinating node
      • Query for EMLs that document a specific data pid
      • Query for files uploaded during a specific time
      • Use facets
    • More resources
  • ADC web submissions
    • Add physicals to submissions
    • Assess attributes
    • List submissions to the Arctic Data Center
    • Recover failed submissions
  • Data Portals
    • Customizing Data Portals
      • My portals
      • Creating Data Filters
      • Set Access Permissions
      • Advanced portal customizations
      • Updating portals
    • Distributed Biological Observatory (DBO) submissions
    • MOSAiC
      • Dataset Level Annotations
      • Portal updates
  • Using arcticdatautils
    • Create a resource map using arcticdatautils
    • Get package and EML
    • Publish an object
    • Reorder entities
  • Nesting Data
    • Nesting a data package
    • Add children to an existing parent
    • Create a new parent package
    • Example
  • Large Dataset Method
    • Example Dataset
    • Uploading files to datateam
      • Instructions for uploading files to datateam
      • Moving files within datateam
    • Processing
      • Understanding the contents of a large data submission
      • Creating representative entities
      • Moving files to web-accessible location
      • Adding Markdown link to abstract in EML
  • Training

NCEAS Data Team Reference Guide

Navigate RT

The RT ticketing system is how we communicate with folks interacting with the Arctic Data Center.
We use it for managing submissions, accessing issues, etc. It consists of three separate interfaces:
Front Page
All Tickets
Ticket Page

Front page

This is what you see first

  1. Home - brings you to this homepage
  2. Tickets - to search for tickets (also see number 5)
  3. Tools - not needed
  4. New Ticket - create a new ticket
  5. Search - Type in the ticket number to quickly navigate to a ticket
  6. Queue - Lists all of the tickets currently in a particular queue (such as ‘arcticdata’) and their statuses
  • New = unopened tickets that require attention
  • Open = tickets currently open and under investigation and/or being processed by a support team member
  • Stalled = tickets awaiting responses from the PI/ submitter
  1. Tickets I Own - These are the current open tickets that are claimed by me
  2. Unowned Tickets - Newest tickets awaiting claim
  3. Ticket Status - Status and how long ago it was created
  4. Take - claim the ticket as yours

All tickets

This is the queue interface from number 6 of the Front page
1. Ticket number and title
2. Ticket status
3. Owner - who has claimed the ticket

Example ticket

  1. Title - Include the PI’s name for reference
  2. Display - homepage of the ticket
  3. History - Comment/Email history, see bottom of Display page
  4. Basics - edit the title, status, and ownership here
  5. People - option to add more people to the watch list for a given ticket conversation. Note that user/ PI/ submitter email addresses should be listed as “Requestors”. Requestors are only emailed on “Replys”, not “Comments”. Ensure your ticket has a Requestor before attempting to contact users/ PIs/ submitters
  6. Links - option to “Merge into” another ticket number if this is part of a larger conversation. Also option to add a reference to another ticket number

Verify that this is indeed the two tickets you want to merge. It is non-reversible.

  1. Actions
  • Reply - message the submitter/ PI/ all watchers
  • Comment - attach internal message (no submitters, only Data Teamers)
  • Open It - Open the ticket
  • Stall - submitter has not responded in greater than 1 month
  • Resolve - ticket completed
  1. History - message history and option to reply (to submitter and beyond) or comment (internal message)

New data submission

When notified by Arcticbot about a new data submission, here are the typical steps:

  1. Update the Requestor under the People section based on the email given in the submission (usually the user/ PI/ submitter). You may have to google for the e-mail address if the PI did not include it in the metadata record.
  2. Take the ticket (Actions > Take)
  3. Review the submission based on the checklist
  4. Draft an email using the template and let others review it via Slack
  5. Send your reply via Actions