Skip to end of metadata
Go to start of metadata

Questions and answers about OOIN Release 2 are included below, grouped by category.

Contents by Subject

Contents by Question


General System and User Documentation


User Documentation for OOIN
What is the longer term plan for the User Documentation?

The OOIN User Documentation will be in Confluence through Release 2 (R2). Further development beyond R2 will be determined by the scope of features for future releases. Tentatively, an interactive online help system is scheduled to be provided in Release 3. Added Feb 28, 2013


System Requirements (OOIN Release 2)
What browsers are supported in Release 2?

In Release 2, the following browser list will be supported:

  • IE 10 on Windows 7
  • Firefox 13 & 14 on Windows 7, Mac OS 10.6 & 10.7, and Linux (Ubuntu)
  • Chrome 19 & 20 on Windows 7, Mac OS 10.6 & 10.7, and Linux (Ubuntu)
  • Safari 5.x on Mac OS 10.6 & 10.7
Firefox issue
Some performance issues have been observed using Firefox to display the data with the HighCharts javescript library.  This appears to be due to an unoptimized javascript environment within the Firefox browser as well as potentially unoptimized javascript code within the HighCharts library running on Firefox.  This issue has not been seen on any other browser.

More recent versions may also be supported as they are released, if they do not require significant software modifications. CI intends to support all the common operating system/browser/browser version combinations, consistent with available resources. For further details see, Product Description - Release 2 Browser Support. Edited Aug 07, 2013

What is the optimal screen resolution?

The system was designed for 1440x900; note that below the minimum supported screen resolution of 1024x768, formatting of pages may not display appropriately. Added Aug 20, 2013



Data


Data Refresh and Update
What does Historic Data mean in the context of a data graph?
Is the data being updated as new data is received by the system?

The term historic was used as a placeholder in early development to distinguish between older and incoming real-time data. That terminology is no longer utilized as there is now only one data graph with older data that is updated with new data as it is received. The update should occur automatically but a refresh of the current screen will also enable the user to activate the update, see the User Documentation for further details on Interacting with Data . Added Apr 04, 2013


Data Product Types
What does parsed canonical mean?

It's an easy way to view and choose variables, raw data is parsed into a canonical format. This allows for no loss of precision and is akin to L0 data in that it is unprocessed. For a given instrument, multiple parsed components may be available that represent the various data streams coming off the device. Edited Apr 04, 2013

What are the various data products and how does the process of getting from one type to another work?

The data available through OOI can be as raw, parsed, L0, L1, or L2. For further definitions and to understand the process of getting from one type to another see the User Documentation Data Products page. Added Apr 04, 2013


Graphic Overlays of Data
Are there ways to plot data from more than one instrument on the same graph?

(For example, 2 sensors on one platform, or 2 nearby sensors)

This is anticipated to be available in a later version. The intent is to have the ability to overlay data from different data products, for instance, data from two different sensors on a single platform or from two different instruments. Edited Apr 02, 2013


Images of the Data Graph
Can an image of the data graph be created directly in OOIN?

Yes, from the Data tab section of any Data Product, the user can print directly or export the graphic image via two icons. In the far upper right of the data block, the graphic image can be printed directly or exported as png, jpeg, pdf or svg. For further details, see the User Documentation Interacting with the Data View.

Additionally, more options of image downloading are available after downloading the data and utilizing the ERDDAP page options. For further details, see User Documentation on Downloading an Image. Added Aug 06, 2013



Functionality


Common and Instrument Specific Commands
Will there be one unified list of commands that is found for all instruments or will they be instrument specific?

Answer is actually both, there is a set of common commands and there can be additional commands specific to an instrument. For a list and description of the common commands see the User Documentation Command a Resource page. See the individual Instrument Operational Specification (IOS) page for details on instrument specific commands. The IOS pages can be accessed from the full instrument list at https://confluence.oceanobservatories.org/display/instruments/OOI+Instruments. Added Apr 04, 2013


Events - Auto-Generated & User Added Notes
What are the available events in OOIN?
Can specific types of events be subscribed by an user?

Currently produced events and their descriptions are included in the User Documentation Events page. Any Facility Members can subscribe to specific events for a given resource, see Subscribe or Unsubscribe to a Resource page for more details. Added Aug 15, 2013

Is there a way for users to add notes and comments for data products and instruments, to annotate them?

Yes, Facility Operators and above can create manual events for a resource, that will show up in the Recent Events tab, see the User Documentation Manual Entry to Event Log page for details on functionality. Edited Aug 15, 2013

Is there the ability in the system to expand events to include detection and notifications for science events.

Yes, the system is setup to allow new types of events to be added in the future, such as program specific science events. Though, this functionality is not fully implemented yet. Added Aug 15, 2013


Status Information and Displays
How is status depicted currently?*

Currently status for a marine resource is shown in the upper right of its title bar. For more details see the User Documentation Status Flag Details page. Added Aug 12, 2013

When a user zooms into Google map view, can it break down to a level that shows all the sensors?
Can a user see all sensors with green if working and then click to bring up info about a sensor?

Actual plans for future scope are being determined but below are initial design plan depictions.

In the later view, the evolution of "status" into the "Power history," "Communications flow," "Data flow," and "Location history" indicators can be seen that came out of discussions with users.

These mockups and others are posted at https://userexperience.oceanobservatories.org/. Edited Aug 12, 2013

Click here for further discussion of initial status page design details.

OOIN Dashboard Views versus the OOI Homepage
How is the Dashboard different from the OOI homepage?

The Dashboard or landing page for OOIN consists of a Map view or Resources view and is the jumping off point for exploring or navigating resources, and is accessible for the beta version at http://ion-beta.oceanobservatories.org/. For more details about the Dashboard views, take the User Documentation initial Tour of the OOIN Interface.

The OOI homepage is the starting point for OOI programmatic information and details, and is accessible at http://www.oceanobservatories.org/. Added Aug 06, 2013



Terminology


Lifecycle State versus Resource Status
Is there a difference between State and Status?
How do I find out what the Lifecycle States mean?

The lifecycle states show the current state of the resource in a broad way, similar to stages that the resource would go through. Some of the current lifecycle states are developed, integrated, and deployed. See the User Documentation for the available lifecycle states and their current definitions.

The status shows a more immediate and up to date condition of the resource, for more details, see the User Documentation Status Flag Details page.

Note that not all resources within OOIN will display a status nor are all the lifecycle state options pertinent, for example Data Products have a lesser number of Lifecycle States available and do not display a status. Added Aug 06, 2013


Temporal Bounds / Timeframe Component of Resources
How are ‘temporal bounds’ factored into OOIN?
How is the timeframe a particular resource is deployed at a particular location conveyed?

The deployment block on a resources Facepage conveys the timeframe/temporal bounds for the deployment and that particular association. Note that the OOIN system allows for the tracking of a specific instrument being deployed or associated with varying platforms or stations over the course of its lifetime. The deployment functionality is a key part of that temporal tracking of resources and their associations over time. See the User Documentation for more details about Deployments and Associations.

Additionally, the advanced search function allows the user to search over specific temporal bounds for data products and other resources within OOIN. The User Documentation outlines the advanced searching functionality available. Added Aug 14, 2013



Resources


Preloaded Resources (SAF Import)
How does the information represented in the OOIN application connect to information in the SAF application?

The Integrated Observatory Network (OOIN) application will be preconfigured with information from several sources:

  • The SAF database
  • A spreadsheet augmenting the mapping between SAF and OOIN (created by Ed Chapman, Sheri White, Mike Mulvihill, and Matthew Arrott)
  • A spreadsheet of all DPSs (for Data Product attributes and variables)
  • A spreadsheet of all IOSs (for Instrument attributes)

As we refine the preload process and information is gathered, more sources may be added. Edited Apr 02, 2013


Platform within a Platform
Why is there a ‘Platform’ tab when viewing a Platform? What type of data is expected there?

The platform tab within a platform Facepage, allows for the case where there is a sub-platform on a platform. There is currently not a good example of this functionality but the need for this type of association is anticipated. The platform tab within a platform Facepage will list the associated sub-platform, description, and link to its Facepage. The User Documentation page Introduction to OOIN and its definition of terms is an available reference. Added Aug 13, 2013



Security, Roles, and Access Permissions


Allowable Activities by User Role
Is there a spreadsheet outlining the read/write capabilities available?

Yes, there is a grid showing the Allowable Activities by User Role in the User Documentation.

The roles give general capabilities, currently there is no way to restrict which attributes of a resource can be modified by which role. If the user has editing for a resource, they can change each and every attribute associated with that resource. There is the ability to enhance the granularity of access control in future scope based on MIO feedback. Added Aug 15, 2013


Security Management - Policies and Roles
Are the user roles mutually exclusive?

That is for example, can the observatory manager also perform the functions of the operator and data operator with higher level roles inclusive of the lower level roles- nested?

What process for approval will be followed when an individual is to be added or deleted as a marine user?

I expected a list of user names to be presented (e.g., RSN administrator, RSN Operator, RSN engineer).

I expected a list of permissions (policies) to be more detailed for each user name.

Here is a list of the OOIN concepts defined:

  • A User Account represents an individual human user and stores their preferences and settings. One of these settings is their Name, which is they can edit themselves and is primarily used for human to human communications, e.g., if one operator needs to call another. OOIN users do not need a special OOIN User ID (login name) or password, since the login process is handled through the institution of their choice.
  • A Policy is a set of rules defining what actions someone is allowed to perform on a particular Resource.
  • A Role is a name for a set of Policies. This is a convenience that takes advantage of common patterns of use to make Policy assignments and management easier. Roles are merely definitions of sets of access permissions, and can be assigned to any number of users.
  • Access permissions are either requested by a user or offered/denied for a particular role by an Administrator.

Further details are outlined in the User Documentation User Roles and Request Access Permission pages.

Or click here to see the full discussion of Roles, Policies and Permissions.

Facility Operator Access Permissions to Instruments & Platforms
Would a Facility Operator have permissions for all of instruments/platforms within the Facility?
Who gets to assign/check permissions?

A Facility Administrator (there can be more than one) grants permission to roles and access to devices, can offer roles, and has the ability to review who has what roles within a Facility. A Facility member can request or be offered the Facility Operator role. With the Facility Operator role, some general functions are available but access to and the ability to command specific instruments and platforms must be requested and granted separately for each device. General information about the User Roles is available in the User Documentation, it also outlines for a user how to Establish User Role & Access Permissions and gives details on how to Manage Roles & Access for the administrator. Added Aug 14, 2013



CIPROD:Back to Top of Page

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.