Changes between Version 1 and Version 2 of SIS/UI/Tutorial-v1.0/StationSummary


Ignore:
Timestamp:
06/18/12 16:14:14 (5 years ago)
Author:
skientz
Comment:

Added images

Legend:

Unmodified
Added
Removed
Modified
  • SIS/UI/Tutorial-v1.0/StationSummary

    v1 v2  
    8989Select the netcode from the Network drop-down menu, and enter the station code in the Station code text box (your entry for the station code) is converted to uppercase before being processed by the database). Click the button to submit the form.   
    9090 
    91  
     91[[Image(JumptoStation.PNG)]] 
    9292 
    9393Figure 1: Jump to Station form 
     
    9898If the submitted netcode and stationcode matches a station in the database, you are re-directed to the station’s summary page, else you are re-directed to the Station Form: 
    9999 
     100[[Image(StationHeaderForm.PNG)]] 
     101 
    100102Figure 2. Station Form 
    101103 
     
    113115 
    114116 
    115 The station header module displays the fields of the station header,  along with a mini JumptoStation form to navigate to another station: 
     117The station header module displays the fields of the station header, along with a mini !JumptoStation form to navigate to another station: 
     118 
     119[[Image(StationHeader.PNG)]] 
    116120 
    117121Figure 3. Station Header module in the Summary page (example for station CI.XX1) 
     
    136140The last instrument activity shows the latest epoch on/offdate and the reason. (See the Channel Manager for more information about the channels epochs and reason). 
    137141 
    138 For stations whose metadata is imported (i.e. SCSN is not the authoritative source): 
     142For stations whose metadata is imported (i.e., SCSN is not the authoritative source): 
    139143 
    140144 - The imported station’s channel responses are not linked with any instruments from the SIS inventory. 
     
    149153 
    150154 
    151 === Telemetry Devices 
     155=== Telemetry Devices === 
    152156 
    153157The current power devices are displayed. Click on the device link to get to its summary page. 
     
    166170 
    167171 
    168 == [=#LinksAndFeeds Links and Feeds] == 
     172=== [=#LinksAndFeeds Links and Feeds] === 
    169173 
    170174This section contains links, and depending on the station, some feed displays from web services. 
    171175 
    172176 
    173 == [=#StationLinks Station Links] == 
    174  
    175 ==== !Channel/Response ==== 
     177==== [=#StationLinks Station Links] ==== 
     178 
     179===== !Channel/Response ===== 
    176180 
    1771811. Instrument history by date: report of the logger and sensor installation history at this station. 
     
    181185 
    182186 
    183 ==== !Installations/Logs ==== 
     187===== !Installations/Logs ===== 
    184188 
    1851891. Station Logs: shows all the log entries for the station. Click on the subject to see the full entry. For authenticated users, there is a link to create a new log entry. (See User Actions for instructions). 
     
    188192 
    189193 
    190 ==== External Links ==== 
     194===== External Links ===== 
    191195 
    1921961. SCSN Operators list email archive for the station 
     
    194198 
    195199 
    196 == [=#UserLinks User Links] == 
     200==== [=#UserLinks User Links] ==== 
    197201 
    198202Links for authenticated users. See the  
     
    200204 
    201205 
    202 == [=#FeedRecentEmailUpdates Feed: Recent Email Updates] == 
     206==== [=#FeedRecentEmailUpdates Feed: Recent Email Updates] ==== 
    203207 
    204208This is an SCSN-specific module that relies on a web service from the SCSN Email updates archive.  The service provides the subject, date, and sender-email of the last 5 email updates for this station. Click on the subject link to see its entry in the email archive. 
     
    206210 
    207211 
    208 == [=#FeedTaskzillaOpenTickets Feed: Taskzilla Open Tickets ==== 
     212==== [=#FeedTaskzillaOpenTickets Feed: Taskzilla Open Tickets] ==== 
    209213 
    210214This is an SCSN-specific module that relies on a web service from the SCSN Taskzilla (Bugzilla) software.  The service provides the description, product and last-modified fields of the open issues in Taskzilla for this station.  Click on the description to see its Taskzilla entry. 
     
    219223This module contains links for authenticated users. 
    220224 
    221 == [=#SendEmail Send Email === 
     225=== [=#SendEmail Send Email] === 
    222226 
    223227This form is to send an email concerning the station. It can be used to report any actions that have been recorded for this station in SIS. 
    224228 
     229[[Image(StationEmailForm.PNG)]] 
     230 
    225231Figure 4. Station Email Form 
    226232 
     
    228234 
    229235{{{ 
    230 why are the following fields numbered the way they are? Always restarting back to "1". 
     236Check the numbering here and fix 
    231237}}} 
    232238 
     
    248254 
    249255 
    250 == [=#UpdateStationInstruments Update Station Instruments] == 
     256=== [=#UpdateStationInstruments Update Station Instruments] === 
    251257 
    252258 
     
    266272 
    267273Click on the drop-down menu for ‘Station actions’ in the form: 
     274 
     275[[Image(UpdateStaInstrum_select_stationaction.PNG)]] 
    268276 
    269277Figure 5. Update Station Instruments Form: select Station action 
     
    284292The next step is to select the logger and sensor(s) from the inventory: 
    285293 
     294[[Image(UpdateStaInstrum_install_newlogger.PNG)]] 
     295 
    286296Figure 6. Install new logger and sensor(s) form 
    287297 
     
    292302 
    293303 1. Loggertype: Select the logger model of the logger to be installed from the loggertype dropdown. 
    294  2. Logger S/N: The S/N dropdown is then populated with the available loggers of the selected loggertype. 
     304 2. Logger !S/N: The !S/N dropdown is then populated with the available loggers of the selected loggertype. 
    295305 
    296306 1. ONLY loggers having inventory status=INVENTORY are displayed in the dropdown. 
     
    299309 1. Configuration: The Channel configuration dropdown is populated with the available channelset(s) for the selected loggertype.  The default selection is the most common use for SCSN stations. 
    300310 2. Sensortype: select the sensor model of the first sensor from the sensortype dropdown. 
    301  3. Sensor S/N: The S/N dropdown is then populated with the available sensors of the selected sensortype. 
     311 3. Sensor !S/N: The !S/N dropdown is then populated with the available sensors of the selected sensortype. 
    302312 
    303313 1. ONLY sensors have inventory status=INVENTORY are displayed in the dropdown. 
     
    339349The form now displays the currently installed loggers and sensors with an Action dropdown menu next to each instrument: 
    340350 
     351 
     352[[Image(UpdateStaInstrum_select_addsensor.PNG)]] 
     353 
    341354Figure 7. Update Station Instruments: select action for existing instrument 
    342355 
     
    345358Enter the GMT datetime of the action and click Continue. 
    346359The next step is to select the sensor from the inventory: 
     360 
     361 
     362[[Image(UpdateStaInstrum_addsensor.PNG)]] 
    347363 
    348364Figure 8. Update Station Instruments: Add a sensor to an existing logger 
     
    365381 
    366382 
    367 3. Sensor/Logger swap 
     3833. !Sensor/Logger swap 
    368384 
    369385 
     
    375391 
    376392From the Station Summary page, Click on the ‘Update Station Instruments’ link in the User links module. 
     393 
    3773941. From the Action menu of the instrument to be replaced, select the ‘Swap’ option.  Enter the GMT datetime of the swap action and click Continue. 
    3783952. The next step is to select the new instrument from the inventory.  Select the model and serialnumber of the new instrument and submit the form to update the database.   
     
    388405 
    389406 
    390 4. Sensor/Logger temporary removal 
     4074. !Sensor/Logger temporary removal 
    391408 
    392409 
     
    394411From the Station Summary page, Click on the ‘Update Station Instruments’ link in the User links module. 
    395412From the Action menu of the instrument to be temporarily removed, select the ‘Remove to reinstall later’ option. 
     413 
    396414Enter the GMT datetime of the removal and submit the form. At this time, the following database changes are made: 
     415 
    3974161. The current active channel epochs belonging to the removed instrument are ended (their offdate is set to the removal date). 
    3984172. New active channel epochs are created whose ondate is the removal date, with a flag indicating that they have no instrument gain for this epoch. 
     
    404423The removed instrument appears in the Instruments module with the words ‘Not currently installed’ next to it. 
    405424The channels belonging to the removed instrument appear in the Current Channels module, but with no gain for their current epoch.   
    406 5. Sensor/Logger reinstall 
    407  
    408  
    409 This is the reverse action of the ‘Sensor/Logger temporary removal’ action.   
     425 
     4265. !Sensor/Logger reinstall 
     427 
     428 
     429This is the reverse action of the ‘!Sensor/Logger temporary removal’ action.   
     430 
    410431Note: this action is to re-install the SAME instrument at the station;  if the same instrument is not re-installed, you need to use the Swap action to install a different instrument. 
     432 
    411433From the Station Summary page, Click on the ‘Update Station Instruments’ link in the User links module. 
    412434From the Action menu of the instrument that is temporarily removed, select the ‘Reinstall’ option: 
    413435 
     436 
     437[[Image(UpdateStaInstrum_select_reinstall.PNG)]] 
     438 
    414439Figure 9. Update Station Instruments - select reinstall option 
    415440 
    416441 
    417442Enter the GMT datetime of the re-install and submit the form. At this time, the following database changes are made: 
     443 
    4184441. The current active channel epochs belonging to the instrument are ended (their offdate is set to the reinstall date).  Reminder: these channel epochs have no instrument gain. 
    4194452. New active channel epochs are created whose ondate is the reinstall date and their simplereponse is calculated. 
     
    426452 
    4274536. Sensor removal to end channels 
     454 
    428455This action is used to permanently remove a sensor and set the offdate of the channels belonging to the sensor. 
    429456From the Station Summary page, Click on the ‘Update Station Instruments’ link in the User links module. 
    430457From the Action menu of the sensor to be permanently removed, select the ‘Terminate (remove + end its channels)’ option.   
     458 
    431459Enter the GMT datetime of the action and submit the form. At this time, the following database changes are made: 
     460 
    4324611. The current active channel epochs belonging to the offlined sensor are ended (their offdate is set to the remove date). 
    4334622. The channel header offdate for each of those channels is ended (their offdate is set to the remove date) to indicate there will be no further epochs for this channel. 
     
    436465If there are no errors in the above steps, you are re-directed back to the station summary page.  
    437466The Current Channels module should no longer display the ended channels of the offlined sensor. However, the channel headers and their epochs still exist in the database, and can be modified via the Channel Manager. 
     467 
    4384687. Terminate Station 
    439469From the Station Summary page, Click on the ‘Update Station Instruments’ link. 
     
    450480To edit the channel and channel epoch offdates, use the Channel Manager. 
    451481 
    452  
    453 Create new Station Log 
     482=== [=#CreateNewStationLog Create New Station Log] === 
    454483 
    455484 
    456485This form is for creating a new station log entry.  It is used to record notes about the station. 
    457486 
    458 Figure 10. Station/Location  Log entry form 
     487 
     488[[Image(StationLogForm.PNG)]] 
     489 
     490Figure 10. !Station/Location  Log entry form 
    459491 
    460492 
     
    465497 
    466498The Station Summary Page displays the most recent log entry, if one exists, in the Last Log Entry module.  The complete list of the station’s logs is accessible by the ‘Station logs’ action in the Station links module.  
    467 Update Power devices 
     499  
     500=== [=#UpdatePowerDevices Update Power Devices] === 
    468501 
    469502 
     
    489522Select the desired devicemodel from the second dropdown. 
    490523 
     524 
     525 
     526[[Image(UpdateStaDevice_select_installnew.PNG)]] 
     527 
    491528Figure 11. Update current Power Devices: select action 
    492529 
     
    496533The next step is to specify the attributes of the device to be installed (a Charger in this example): 
    497534 
     535 
     536[[Image(UpdateStaDevice_install_charger.PNG)]] 
     537 
    498538Figure 12. Update current Power Devices: install new device (charger) 
    499539 
     
    501541Enter the values and submit the form. At this time, the following database changes are made: 
    502542 1. If the selected devicetype is: 
    503   a.  inventoryable (devices tracked by unique serialnumber): 
     543  a.  inventoriable (devices tracked by unique serialnumber): 
    504544    * The device serialnumber selected by the user is identified in the inventory pool and its inventory status is set to INSTALLED. 
    505   b. non-inventoryable (devices are not tracked by unique serialnumber): 
     545  b. non-inventoriable (devices are not tracked by unique serialnumber): 
    506546   * A new device is automatically created in the database 
    507547   * A new active installation epoch is created that links the device to the location.  The epoch’s ondate is the submitted install date.  
     
    516556This is to swap a current power device with another of the same devicetype (e.g. one Charger for another). 
    517557From the action menu of the device to be swapped, select the ‘Swap’ action. In this example, we select swap on the Charger installed in Part 1 above: 
     558 
     559[[Image(UpdateStaDevice_select_swap.PNG)]] 
    518560 
    519561Figure 13. Update current Power Devices: select Swap action 
     
    5265681. The installation epoch belonging to the old device is ended (its offdate is set to the swap date). 
    5275692. If the devicetype is: 
    528 1. inventoryable:  
     5701. inventoriable:  
    5295711. The inventory status of the old device is set to INVENTORY. 
    5305722. The new device serialnumber is selected by the user and its inventory status is set to INSTALLED. 
    531 1. Non-inventoryable: 
     5731. Non-inventoriable: 
    5325741. A new device is automatically created 
    5335751. A new active installation epoch is created that links the device to the location. The epoch’s ondate is the submitted swap date. 
    534 If there are no errors in the above steps, you are re-directed back to the Summary page where you should see the new device in the Power devices module.  To swap another device, click the Update Power devices link and repeat the procedure. To view and correct the power installation epochs, refer to the  
    535 [#PowerInstallations Power Installations] section in this document. 
     576If there are no errors in the above steps, you are re-directed back to the Summary page where you should see the new device in the Power devices module.  To swap another device, click the Update Power devices link and repeat the procedure. To view and correct the power installation epochs, refer to the [#PowerInstallations Power Installations] section in this document. 
    536577 
    537578 
     
    546587 
    547588 1. The installation epoch belonging to the device is ended (its offdate is set to the remove date). 
    548  2. If the devicetype is inventoryable: the removed device’s inventory status is set to INVENTORY. 
     589 2. If the devicetype is inventoriable: the removed device’s inventory status is set to INVENTORY. 
    549590 
    550591If there are no errors in the above steps, you are re-directed back to the Summary page. 
     
    554595 
    555596 
    556 == [=#Update Telemetry devices] == 
     597=== [=#UpdateTelemetryDevices Update Telemetry Devices] === 
    557598 
    558599 
    559600This form is to update the current telemetry devices at the location. 
    560601It allows the user to install a new telemetry device at the location, and to swap or un-install the current existing telemetry devices at the location. 
    561 Note: Devicetypes can be inventoryable (its devices are tracked by unique serialnumber) or non-inventoryable (its devices are not tracked by a unique serialnumber).  Since most Telemetry devicetypes are inventoryable, the examples shown here are for inventoryable telemetry devices. 
     602Note: Devicetypes can be inventoriable (its devices are tracked by unique serialnumber) or non-inventoriable (its devices are not tracked by a unique serialnumber).  Since most Telemetry devicetypes are inventoriable, the examples shown here are for inventoriable telemetry devices. 
     603 
    5626041. Install a new device 
    563605 
     
    568610In this example, we select the DIGITAL-RECORDER devicetype. 
    569611 
     612[[Image(UpdateStaTelemDevice_select_installnew.PNG)]] 
     613 
    570614Figure 14. Update current Telemetry Devices: Select Install new 
    571615 
     
    574618The next step is to select the device to be installed (a Kinemetrics BalerPB44 in this example): 
    575619 
     620[[Image(UpdateStaTelemDevice_install_baler.PNG)]] 
     621 
    576622Figure 15. Update Telemetry Devices: install new device 
    577623 
    578624 
    579 Since the DIGITAL-RECORDER devicetype is inventoryable: 
     625Since the DIGITAL-RECORDER devicetype is inventoriable: 
    5806261. The available devices whose inventory status=INVENTORY of the selected devicemodel are displayed in the Serialnumber dropdown menu.   
    5816272. Select the serialnumber of the device to install from the Serialnumber dropdown menu 
     
    590636From the action menu of the device to be swapped, select the ‘Swap’ action. In this example, we select swap on the Baler-PB44 digital recorder installed in Part 1: 
    591637 
     638[[Image(UpdateStaTelemDevice_select_swap.PNG)]] 
     639 
    592640Figure 16. Update current Telemetry Devices: select Swap action 
    593641 
     
    595643Enter the GMT datetime of the swap (the swap date must be posterior to the device’s install date), and click Continue. The next step is to select the new device to be installed.  
    596644Note: the Swap action preserves the devicetype across the swap, but you can select another devicemodel for the new device. 
    597 Since the DIGITAL-RECORDER devicetype is inventoryable: 
     645Since the DIGITAL-RECORDER devicetype is inventoriable: 
    5986461. The available devices whose inventory status=INVENTORY of the selected devicemodel are displayed in the Serialnumber dropdown menu.   
    5996472. Select the serialnumber of the device to install from the Serialnumber dropdown menu 
     
    608656Enter the GMT datetime of the removal (the removal date must be posterior to the device’s install date), and submit the form.  At this time, the following database changes are made: 
    6096571. The installation epoch belonging to the device is ended (its offdate is set to the remove date). 
    610 2. If the devicetype is inventoryable: the removed device’s inventory status is set to INVENTORY. 
     6582. If the devicetype is inventoriable: the removed device’s inventory status is set to INVENTORY. 
    611659If there are no errors in the above steps, you are re-directed back to the Summary page. 
    612660 
     
    615663 
    616664 
    617 Power Installations 
     665== [=#PowerInstallations Power Installations] == 
     666 
    618667From the Summary page, click the ‘Power installations’ link in the Links module. 
    619 It displays the existing power installation epochs at the location, and enables authenticated users to create historic installation epochs and correct existing ones. 
    620 Create historic power installation epoch 
    621 Click the ‘Create historic installation epoch’ link which takes you to a form: 
     668It displays the existing power installation epochs at the location, and enables authenticated users to create historical installation epochs and correct existing ones. 
     669 
     670=== [=#CreateHistoricalPowerInstallationEpoch Create Historical Power Installation Epoch] === 
     671 
     672Click the ‘Create historical installation epoch’ link which takes you to a form: 
     673 
     674[[Image(CreateHistoricalPowerEpoch.PNG)]] 
    622675 
    623676Figure 17. Create Power Installation epoch 
     
    632685The next step is to specify the device for the installation epoch: 
    633686 
    634 Figure 18. Create Power Installation epoch - install Battery 
    635  
    636  
    637 Since the Battery devicetype is non-inventoryable in SIS, the device serialnumber is optional. 
     687[[Image(CreateHistoricalPowerEpoch_installbattery.PNG)]] 
     688 
     689Figure 18. Create Power Installation Epoch - Install Battery 
     690 
     691 
     692Since the Battery devicetype is non-inventoriable in SIS, the device serialnumber is optional. 
    638693Enter the values for the device and submit the form.  
    639 At this time, a new installation epoch is created hat links the device to the location for the given ondate and offdate. 
     694At this time, a new installation epoch is created that links the device to the location for the given ondate and offdate. 
    640695If there are no errors in the above steps, you are re-directed to the detail page of the newly created epoch. 
    641696 
     
    644699 
    645700 
    646 Note: Editing an epoch is intended for correcting typos/errors, not to overwrite accurate historic data. 
     701Note: Editing an epoch is intended for correcting !typos/errors, not to overwrite accurate historical data. 
    647702 
    648703 
    649704Click on the ‘Epoch’ link of the installation epoch that needs to be corrected. This takes you to the detail page of the epoch. In this example, we click on the epoch that was created above: 
    650705 
    651 Figure 19. Power installation epoch detail 
     706[[Image(PowerEpoch_detail.PNG)]] 
     707 
     708Figure 19. Power Installation Epoch detail 
    652709 
    653710 
     
    660717From the Summary page, click the ‘Telemetry installations’ link in the Links module. 
    661718 
    662 It displays the existing telemetry installation epochs at the location, and enables authenticated users to create historic installation epochs and correct existing ones. 
    663  
    664 === [=#CreateHistoricalTelemetryInstallationEpoch Create Historic Telemetry Installation Epoch] === 
    665  
    666 Click the ‘Create historic installation epoch’ link which takes you to a form: 
     719It displays the existing telemetry installation epochs at the location, and enables authenticated users to create historical installation epochs and correct existing ones. 
     720 
     721=== [=#CreateHistoricalTelemetryInstallationEpoch Create Historical Telemetry Installation Epoch] === 
     722 
     723Click the ‘Create historical installation epoch’ link which takes you to a form: 
    667724Submit the form. 
    668725 
     
    671728 
    672729Click on the ‘Epoch’ link of the installation epoch that needs to be corrected. 
    673 Note: Editing the epoch is intended for correcting typos/errors, not to overwrite accurate historic data. 
     730Note: Editing the epoch is intended for correcting !typos/errors, not to overwrite accurate historical data. 
    674731 
    675732