FAQs

What is the plone?

Plone is a content management system built on Python, with its first release in 2001. Plone has features that appeal to developers and users alike, such as customizable content types, hierarchical URL object traversing, and a sophisticated content workflow powered by a granular permissions model. This allows you to build anything from simple websites to enterprise-grade intranets.

How do I upload and download my data?

To upload new data or download detection extracts, log in to your account and click through the folders. Specific step-by-step guides for extracts can be found here or to upload data can be found here

I submitted my data, when will I get my detection matches?

OTN undergoes three "data pushes" each year where all tag metadata is cross-referenced across all receiver detection data for contributing nodes. These occur usually in the months of February, June and October. Once the OTN push starts, new data can no longer be ingested so as not to disrupt the database. Users can expect their detection extracts ~6 weeks after the push starts.

When and often can I submit new data?

You can submit new data at any point to your node manager directly via email or through this site after logging into your account.

Who has access to the data that I submit to N-PAcT?

Your detection data, tag metadata, receiver locations, etc. are ONLY immediately visible to those who are 1) members of your project, and 2) members of N-PAcT. No one can just visit the N-PAcT website and start perusing other peoples’ datasets at will (except the data managers, but we really need this access in order to get your data loaded.). When cross-over between projects occur (i.e. tags from one project detected on another project’s receivers), then there is some exchange of more specific information about tags and receivers, such as receiver coordinates and the species tagged. Various rules to prevent/discourage misuse, and encourage fair attribution of these data, are baked into the database structure and our User Agreement and Data Policy.

What do each of the columns in my extracts mean?

OTN glossary of terms can be found here.

What do "unqualified detections" mean?

These are detections made by your project’s receivers that have not been matched to any tag, in any cooperating data node. There may be several reasons for this.

One: It is a test or sentinel tag that was not reported to the data node.

Two: It is an ambiguous tag which means we have more than one set of tag metadata which the detection could belong to.

Three: We have not received any release metadata for the tag.

Four: It is an old-style sensor tag and we have not been able to determine the associated pinger ID.

We recommend working with your node manager and the tag manufacturer to help find these mystery tags.

Feedback

Please email us at npact@aoos.org for features and tutorials that you would like to see!