wiki:SIS/UI/faq
Last modified 5 weeks ago Last modified on 07/20/17 14:37:13

SIS UI: Frequently Asked Questions

  1. SIS UI: Frequently Asked Questions
    1. SIS Accounts
      1. Q. How do I get a SIS account?
      2. Q. I need to work with equipment from another network, so I need SIS …
    2. Equipment
      1. Q. Why don't I see my logger for install?
      2. Q. My network has started using a new equipment model. How can I tell if …
      3. Q. I want to create some record to track equipment location for some spare …
      4. Q. How can I associate an existing FIR cascade with a new model?
      5. Q. How does SIS calculate sensitivity/gain?
      6. Q. Can I associate the NRL response of a similar episensor, to a new type …
      7. Q. How can I track equipment that consist of two parts of a "package"?
      8. Q. I've noticed that we had swapped a Basalt with internal SM Deck sensor. …
      9. Q. Does recalibrating a seismic instrument automatically change …
      10. Q. Must I make separate templates for hardware whose only difference is …
      11. Q. How do I indicate mis-wiring in SIS?
    3. Metadata Loading
      1. Q. What's the best way to move metadata from SIS to AQMS?
      2. Q. When I uploaded, SIS rejected one of my sensor model names. Must I map …
      3. Q. How is pre-digital metadata handled in SIS?
      4. Q. How could I get two "adopted" stations into SIS with the least pain?
      5. Q. How do we determine how many logger boards are in a Logger when writing …
      6. Q. Will my metadata have to change now that the SIS website uses HTTPS?
    4. SIS UI - How To
      1. Q. What date format does SIS require?
      2. Q. Do you currently have any CI site in SIS that has more than one site …
      3. Q. Does a break in a station history (no channels) imply the end of a site …
      4. Q. If you slightly move site, update coordinates but not site code, do you …
      5. Q. Can I add a co-located site?
      6. Q. How can I see the NRL and model associations?
      7. Q. How can I create a new epoch for which the only changes are the …
      8. Q. Is there a way to read the metadata automatically from SIS so that I …
      9. Q. Where is the new location of our network's dataless files at SCEC?
      10. Q. When is the SIS RSS Feed updated?
      11. Q. How do you change a channel orientation in the current epoch?
      12. Q. How do you change a channel name for a multi-site hub logger's sensor?
      13. Q. Where is the Elevation information pulled from, that's on the Site …
      14. Q. How would you suggest approaching sensor template and response …
      15. Q. Do things like "Site logs" end up as comments in published dataless or …
    5. SIS UI - Troubleshooting
      1. Q. I created a Site Epoch and performed a Field Action. I had to undo the …
      2. Q. When i look for wiring templates, none are returned. Are there none in …
      3. Q. I added some State-of-Health (SOH) components/calibrations/epochs, …
      4. Q. When I tried to undo a field action to recalibrate VCO, it failed
      5. Q. I got an Oracle Error while trying to make a datastream template for a …
      6. Q. I'm on a Site summary page, and can't find the "Field Actions on …
      7. Q. I get a SIS error when trying to undo the last field action for my Site
      8. Q. I am trying to swap out an old Windows OS Earthworm (hub logger) for a …
      9. Q. I created a new data logger, but when I tried to publish (with the …
      10. Q. This SIS form I needed to fill out seems oddly arranged.
    6. Historical Updates to UI
      1. Q. Will Historical Forms be usable with metadata imported via extStaXML? …
      2. Q. How do I do a historical install for a device?
      3. Q. Can I do a historical field action at an inactive site?
    7. Naming of Objects in SIS
      1. Q. What is the scope of a template: Organization, Name Space, or global?
      2. Q. Can the NCEDC Name Space have a project named ARRA if the SCEDC …

Work in Progress. If your question isn't answered here, e-mail us at sis-help@gps.caltech.edu

SIS Accounts

Q. How do I get a SIS account?

  1. Ask your network manager to request one for you by sending an e-mail to sis-help@gps.caltech.edu

Q. I need to work with equipment from another network, so I need SIS credentials associated with more than one Operator. Can this be arranged?

  1. If you already have a SIS account, e-mail us (sis-help@gps.caltech.edy) which Operators to add to your profile. If you are just getting your account, have your manager specify which Operators you need.

Equipment

Q. Why don't I see my logger for install?

  1. There are a number of reasons your logger isn't appearing:
    1. After you create the data logger entry in SIS, you must configure your logger. Then it will show in the system as ready for install.
    2. The logger may be installed at another site during the time in question. Follow the instructions at Configure Data Logger to see which loggers are available for install.
    3. Logger may not have a calibration; see Re-calibrate Logger

Q. My network has started using a new equipment model. How can I tell if someone else is using this model in SIS?

  1. Go to the Model summary page for this model, e.g., for Obsidian.
    1. Click the "Filter Current Equipment by" button to open that menu
    2. The operator is automatically set to your own, (in SCSN case, "Southern California....")
    3. Remove that operator, and also set "Is Equipment Template" = "Yes".
    4. Press "Submit" button.
    5. You should now see 1 entry from South Carolina. You can then look at their template.

If you think the template is accurate for you, you can choose "Create Template from this Template" and make one for your operators. If you have any questions about the template itself, post it on the SIS listserv: ANSS-SIS@cisn.org

Q. I want to create some record to track equipment location for some spare parts I've given to a field engineer.

These equipment pieces are not installed yet, but will be with him on the truck until installed.

  1. Fill in the field called "Inventory Location" in the Equipment Epoch Header, which is used to describe the general whereabouts of equipment (applicable when not installed). E.g., see bottom line in the Required Fields box at Edit Equipment Epoch For S/N LA51560699001003.

Q. How can I associate an existing FIR cascade with a new model?

  1. Follow these instructions:
    1. From the SIS Home page click on the "FIR Filter Cascades" link under the "Responses" section
    2. Search for your filter cascade. e.g., you could filter by Namespace = "NRL" and FIR cascade name contains "ROCK"
    3. Select the cascade and clone into your name space
    4. Now under the "Admin" section in the upper right hand corner, there should be "Assign to Logger Model"
    5. When you make your data stream template, the FIR cascade should be available

Q. How does SIS calculate sensitivity/gain?

  1. SIS uses these Formulas to calculate sensitivity and overall gain.

Q. Can I associate the NRL response of a similar episensor, to a new type not yet in NRL?

I want to enter my Obsidian (which has an internal episensor) into SIS. There is an episensor es-deck in the system that looked like the right thing, but when I tried to choose the NRL response, it wasn't there. How can I associate my equipment with something in the NRL that is the same?

  1. You can create such an association at the NRL-SIS Mapping Create form.

Q. How can I track equipment that consist of two parts of a "package"?

Example, a Guralp CMG-5TD which is both a accelerometer and a digitzier in one package, and consists of two pieces of equipment. This means that it is easy to forget to transfer one of them if I sent it back to the depot. If a unit is repaired and passed on to the next network, the sensor half may be given to one operator, and the logger half given to a different operator.

  1. SIS has noted a ticket (#399) on this issue. In the meantime, mention in the notes of each piece of equipment which should be its sibling.

Q. I've noticed that we had swapped a Basalt with internal SM Deck sensor. I am trying to apply this swap now, but getting an error.

  1. The Basalt s/n 654 and Episensor 654 are a package and Basalt 656 and Episensor 656 are a package. When the swap was recorded in the past, only the logger swap was recorded in SIS, not the sensor. To fix this you would have to undo the earlier swap and redo it. Example of actions you might take:
    1. On Site Summary page, go to Site level field actions> Choose date 2014-01-23, Undo latest seismic field action, Submit. That should remove the earlier swap
    2. Then from Site Summary page again, go to Field action on current seismic equipment > Choose date 2014-01-23 , Swap logger and its instruments > On step 1 choose logger > On step 2, choose the new episensor. Use current for the L4 if that did not change. > Submit.

Q. Does recalibrating a seismic instrument automatically change sensitivity values?

I just edited the sensitivity values with numbers provided from a Guralp Cal. Document. How do I tell SIS to recalculate the response information for this epoch using the new sensitivity values? Should I re-publishing the XML and dataless files?

  1. Re-publishing the site should be sufficient. The change is automatically reflected in the overall gain when you recalibrate an instrument.

Q. Must I make separate templates for hardware whose only difference is the gain?

We have a few stations with the same hardware but different gains due to noise reasons. Until now, I've been making separate templates for each gain, but it occurs to me that the gain can likely be tweaked as part of an epoch calibration. Is there a way I can use just one template for each station and tweak the individual gains later?

  1. When you add hardware to the inventory on the equipment model page you have two options:
    • Create equipment, and
    • Create equipment and customize response

When the gain is different, choose the second option and you should be able to reuse whatever is unchanged and edit the response values that are different from the template for that piece of equipment. Make a new template only when you have a new set of responses (nominal), or you have a different set of components (e.g., for sensors earlier only seismic channels were described, and now Mass-positions are to be used, too). Create a new calibration, when you re-calibrate the equipment.

Q. How do I indicate mis-wiring in SIS?

  1. Refer to the entry Mis-wiring, mis-installation, or mis-orientation, notation of in the SIS Glossary

Metadata Loading

Q. What's the best way to move metadata from SIS to AQMS?

  1. Currently there are only dataless loaders into AQMS, and the two known to us are:
  1. The dataless loader developed at the NCEDC http://quake.geo.berkeley.edu/db/Documents/NewSchemas/IR/v1.5.3/IR.1.5.3/index.htm. This will populate the entire AQMS Instrument Response (IR) schema.
    • SCSN and NCEDC use this loader, and SCSN is using SIS generated dataless.
  1. The dataless loader developed at ISTI. This populates a subset of the AQMS IR schema -- generally tables related to the overall response of a channel, but not the individual stages.

Q. When I uploaded, SIS rejected one of my sensor model names. Must I map to existing model names?

  1. The ExtStationXML loader expects the equipment model name to already exist in SIS. Users can create a new model using the UI. Be sure to search SIS before creating a new model, so as to avoid the situation where the same piece of equipment has many variants across RSNs or even within the same RSN, e.g., like STS2, STS-2, Streckheisen STS-2, and Streckeisen STS-2. The SIS developers have attempted to standardize names, using the one that the manufacturer has used, i.e., from the instrument itself or its calibration sheet.

RSNs loading into SIS need to maintain a mapping of equipment model name in their "repo -> model name" in SIS.

Q. How is pre-digital metadata handled in SIS?

I see that for CI.BAR there are epochs that go back to 1932. Is it required to have something for fields such as sample rate?

  1. You are not required to enter a sample rate. Note that the create channel configuration form says sample rate is not required.

Yet even as SIS doesn’t require you to enter a sample rate, it can’t create the StationXML (or dataless) without a sample rate for every epoch. The work-around is putting ‘999’ for the sample rate.

Q. How could I get two "adopted" stations into SIS with the least pain?

I am trying to avoid the many hours of tediously entering responses from scratch, if possible. The stations use like 43 channels per station.

  1. You could try the StationXML to ExtStationXML converter and then upload that extStationXML into SIS.

You could load an adopted site this way and have its epochs ended. Then begin a new site - colocated with the adopted site. This assumes that the adopted site(s) have no hardware info, just dataless/FDSN StationXML, and you are adding this old data to capture its past epochs.

Q. How do we determine how many logger boards are in a Logger when writing to ExtStationXML?

When using the SIS UI, you build the equipment template for a logger and determine the number of boards at that point. But how does this work when importing with ExtSTationXML when we don’t have any logger templates already in SIS?

  1. The number of “LoggerBoard” elements within the “Logger” element in the XML file determines the number of logger boards a logger has. Basically you get to choose how many logger boards each logger has. You don’t have to attempt to match what others have already created in SIS.

It’s good to try and match how many boards are physically in the datalogger. However, sometimes this is hard to determine as the old way of there being actual boards to replace isn’t applicable anymore.

Q. Will my metadata have to change now that the SIS website uses HTTPS?

  1. If you created ExtStationXML to upload into SIS, the schemaLocation attribute on the root element needs to be changed, specifically the second part of that attribute which points to the actual location of the file itself. So

SIS UI - How To

Q. What date format does SIS require?

  1. You can input any of these four forms:
    • YYYY-MM-DD
    • YYYY-M-DD
    • YYYY-M-D
    • YYYY-MM-D

Q. Do you currently have any CI site in SIS that has more than one site epoch?

  1. The following sites have multiple epochs:

Q. Does a break in a station history (no channels) imply the end of a site epoch/new epoch?

If there is a break in the station history, i.e. no channels were recorded for a while; does that imply the end of a site epoch and the start of a new one or can you still have one site epoch overlapping the time where there were no channels?

  1. The site epoch does not need to be ended when there are no active channels as per SIS. The following guidance is from a former field tech:
  • The only times we would end a site epoch is if we were terminating a station or changing the lat/lon. Sometimes we even kept a site epoch active after many years of no sensors being at the station.

Q. If you slightly move site, update coordinates but not site code, do you need new channel epochs?

If you barely move a site and update its coordinates but not its site code, you have to create a new site epoch, but do you also have to create new channel epochs? Can site epochs and channel epochs be completely independent from each others (assuming that no channel epoch starts/ends before/after a site epoch)?

  1. You have to close and reopen channels epochs when you create a new site epoch. The channels epochs should be contained in the site epoch in SIS.

Q. Can I add a co-located site?

  1. Yes, see Co-Located Sites for how to associate a co-located site with another site, how to change an existing co-located site, and how to delete a co-located site. You can also filter your Network Summary page to only show co-located sites.

Q. How can I see the NRL and model associations?

  1. If you want to see what models are associated with NRL responses go to the Equipment Index at http://anss-sis.scsn.org/sis/equipment/

There you will see links for NRL-sensor and logger associations under "Master Table Views" (example, IRIS-NRL Response Lookups for Dataloggers - requires login to SIS).

Q. How can I create a new epoch for which the only changes are the location codes?

The new loccodes would change from "--" to "01" for three channels, ENE, ENN, ENZ.

  1. You have to use a different Data Stream template that has the new location codes. You should be able to clone your template to a new one and give it the new location codes.

Then,

  • Assuming the logger is still installed, do the field action "Change Data Stream configuration only."

Go to Site Summary Page > Select Seismic Equipment Field Action > under "Wired Equipment," check "Change Data Stream configuration only"

OR

Q. Is there a way to read the metadata automatically from SIS so that I can update the AQMS metadata?

The ones that are of concern now (for producing V0 files) are the max g (or clip level), sensitivity, and full scale volts for the sensor.

  1. The 3 formats that SIS produces are FDSN StationXML, ExtStationXML, and dataless SEED -- which is produced from the FDSN StationXML. They can be found at XML and SEED Files
  • There are network subdirectories underneath. When you finish making changes to a site, hit the "Publish" link and these files are produced.
  • The ExtStationXML format is an extension of the FDSN StationXML and developed to explicitly describe the hardware connections to the response.

Q. Where is the new location of our network's dataless files at SCEC?

  1. http://files.anss-sis.scsn.org/production/dataless/{netcode}/ . In other words, for network CI, http://files.anss-sis.scsn.org/production/dataless/CI/

Q. When is the SIS RSS Feed updated?

  1. The RSS feed is now updated whenever a user successfully publishes a file. Previously the feed was updated once a day. This change should allow users to be informed of new metadata changes immediately.

Q. How do you change a channel orientation in the current epoch?

Say you discovered a mis-oriented sensor, then re-oriented it, how do you then change the current epoch?

  1. Under "Field Actions on Current Seismic Equipment," select the field action "Update sensor location/orientation" and record a new epoch. Use the Epoch On Date as the date for the action (it should just change the active epoch), select the radio button "Update sensor location/orientation" and Continue to reach the page where you can change the orientation.

Q. How do you change a channel name for a multi-site hub logger's sensor?

  1. That depends on whether you are changing a channel name that is active or whether you are making a historical change.
    • If this is a current action, you must make the change at the sensor site. See Change Channel Name
    • If this is a historical action, you make the change at the hub logger site. You can follow the instructions directly above, but you must start at the hub logger site.

Q. Where is the Elevation information pulled from, that's on the Site Summary pages?

In each Site Summary, an Elevation is provided when one inputs the latitude and longitude. Where does that value come from?

  1. It comes from the USGS National Map Elevation Point Query webservice that returns NAD 1983 (North American Datum 1983) elevation info for a specified lat and lon. Here's information about the North American Datum 1983 and the difference between it and WGS84:
    • The initial definition of NAD83(1986) was intended to match GRS80 and WGS84, and many older publications indicate no difference. Subsequent more accurate measurements found a difference typically on the order of a meter over much of the US. Each datum has undergone refinements with more accurate and later measurements.
    • One fundamental difference is that NAD83 is defined to remain essentially constant over time for points on the North American Plate, whereas WGS84 is defined with respect to the average of stations all over the world. Thus there is a change over time as to the difference between the systems. For much of the U.S., the relative rate is on the order of 1 to 2 cm per year.

Q. How would you suggest approaching sensor template and response representation creation in the case where poles and zeros are customized for each individual sensor within a particular model?

Would I create a "template" for each individual sensor that has a different "default" response representation? Or is there a way to customize response representations later on?

  1. You can customize response representations without having to create a new template. Use the "Create equipment and customize response" on the equipment model page. Template creation guidelines:
    • You have to create a new template if the component names are different. This is not common, but possible when the first time around the full description was not used. For example, mass position components not used/tracked initially but later on the RSN decides to track it.
    • You can choose to create a new template if there is a new default representation that they want to use for more than one equipment. Then it is quicker to add those identical pieces of equipment using "Create equipment" link on the equipment model page.

Q. Do things like "Site logs" end up as comments in published dataless or StationXML?

Because it would be really nice to be able to record things like site visits that do not result in any change to the station/response, but are useful in keeping up with maintenance.

  1. Channel Logs, Site Logs, Equipment Logs, Problem Reports, Installation Epoch Notes are written into ExtStationXML. Channel Logs are written into FDSN StationXML

SIS UI - Troubleshooting

Q. I created a Site Epoch and performed a Field Action. I had to undo the Field Action, and it also deleted the Site Epoch. Help!

  1. If you create a Site Epoch and then perform a Field Action the same day, and both are dated exactly the same (perhaps you accepted the default time of midnight UTC), if you undo something, it will undo everything that happened with that timestamp.

The solution is, slightly change the timestamp of the Field Action.

  1. Undo the delete of the Field Action (which will undo the Site Epoch delete): From Site Summary page, click "Site Level Field Actions" and choose "Undo Latest Seismic Field Action"
  2. Go back to the Site Summary page, and under Site History Links, click Field Actions
  3. Click the "Action Date" link for the Field Action you wanted to eventually undo
  4. Next screen, modify the Action Date (make it later than the Site Epoch timestamp or whatever it was that disappeared when you undid the Field Action), and click Submit
  5. Now you can go to "Site Level Field Actions" from the Site Summary page, and use "Undo Latest Seismic Field Action" to get rid of the Field Action, but not disturb the Site Epoch

Q. When i look for wiring templates, none are returned. Are there none in the sistest database?

  1. The wiring templates list page (like many other pages) is prefiltered to show only the items for your organization. Click the blue "Select filters" option and clear the selected operator, then press Submit to see the templates created by other networks.

Q. I added some State-of-Health (SOH) components/calibrations/epochs, then later added some more, all on the same day.

Then I noticed one was duplicated. When I deleted that SOH component, all my SOH components/calibrations/epochs of that day were deleted!

  1. If you created SOH components and in the process, created epochs or calibrations that are all time-stamped for the same day, if you delete one, you will undo the others carrying that timestamp.

The workaround to this is to add a brand-new SOH calibration epoch or calibration with a slightly different date (e.g., one day later or earlier). Make sure the new calibration/epoch has all the components you wish to keep, then delete the earlier calibration/epoch which contained the component(s) you didn't want.

Q. When I tried to undo a field action to recalibrate VCO, it failed

  1. The undo field action does not remove the new calibration that is created by the recalibrate process. It does not delete/reactivate calibrations. There is no definite way to tell that the calibration was a part of the field action or was an independent action that was done at the same time in certain instances.

There's a workaround for how to undo the 'Re-Calibrate' field action (as always, this has to be the field action for the latest epoch)

  1. At the Site Summary page, click Site level field action > Historical - Make a Gap for historical corrections > Choose start date matching the date the recalibrate was done
  2. Make the end date the next date after the start date (e.g., end date = startdate+1)
  3. Now go back to the Site Summary page. Click Site level field action > Undo field action > Choose the above gap end date
  4. For this date, use the date after your recalibration date (e.g., recalibrate date+1)
  5. Go to Equipment detail page for the equipment whose calibration needs to be removed. Choose Calibration > Delete Calibration
  6. Go back to Site Summary page. Go to Site level field action > Undo field action > Choose the date the recalibrate was done
  7. Now it will accept the end date for the channel epoch.

All the channels and equip installations should get reactivated and no traces of the recalibrate field action should remain.

Q. I got an Oracle Error while trying to make a datastream template for a QEP logger.

  1. This is a bug that is slated to be fixed. The QEP is the first logger in the NRL that does not have any FIR filters, which will be addressed. As a workaround for now, do not use the NRL options, rather on the step 2 screen, provide the sample rate. That is all you are getting from the NRL resp file at this point.

Q. I'm on a Site summary page, and can't find the "Field Actions on Current Seismic Equipment" link that's supposed to be under "User Actions."

  1. The site likely does not have any equipment, so the link will not appear.
    • If you install some seismic equipment at the site, then the "Field Actions on Current Seismic Equipment" link will appear, and you will be able to go in there and make modifications.
    • In a number of cases, links are hidden if there is nothing to offer the user on that page.

Q. I get a SIS error when trying to undo the last field action for my Site

  1. One thing to check is if the previous equipment (that would then become "Active" after the undo), has been reconfigured or installed since that action. If for example your undo makes a logger your Active equipment, and it has since been reconfigured, you need to delete that configuration before your "Undo" action can succeed.

When in doubt of what an error message means, or if you have other difficulty, don't hesitate to e-mail sis-help@gps.caltech.edu for assistance.

Q. I am trying to swap out an old Windows OS Earthworm (hub logger) for a Basalt, and got an Oracle error.

I "bootstrapped" the older unit then tried to swap in the Basalt and got an error that "the logger wiring template has changed from previous value for site."

  1. When swapping a hub logger, the wiring templates on the old and new loggers have to match (the data stream templates can be different). In your case, I see that the Earthworm’s reverse engineered templates have an Amplifier in the wiring sequence, but the Basalt’s wiring templates do not.
    • If the amplifier has been removed from the sites,
      1. Go to the hub site XFortScottyHub > Select Hub logger field action> Uninstall Logger and All of Its Wired Instruments.
      2. Install the basalt as a hub logger
      3. Go to each sensing site and reinstall the sensor/VCO and discriminator.
    • If no, delete the Basalt’s configuration and create a new one using the same wiring template as the Earthworm. Again, the data stream template can be different.

Q. I created a new data logger, but when I tried to publish (with the ExtStationXML generator), it failed with errors.

  1. Check to make sure you have entered all 3 COSMOS station parameters when recording the field install. If you only entered one or two, the publish will fail. If you cannot provide all 3 then you must enter none. These three parameters go as a set, so all 3 of Geologic Site Class, Physical Condition, and Station Housing should be present or all 3 must be null. You either need to clear the value for Station Housing or set values for the other two. To edit the channels, go to the channel editor:
    • Go to site page for Your Station
    • Click Channel Epochs (under Site History links)
    • Edit or delete Channel Configuration

Q. This SIS form I needed to fill out seems oddly arranged.

  1. After upgrading our web framework software in late 2016, we noticed the default order of form fields became reversed. We typically keep required fields at the top of forms and order the rest logically. Because of this new behavior, forms may look unorganized. Email sis-help@gps.caltech.edu if you spot an oddly organized form or have a suggestion for improving form field ordering.

Historical Updates to UI

Q. Will Historical Forms be usable with metadata imported via extStaXML? If not, what functionalities are available for such metadata?

Specifically, what operations are available in SIS depending on the different metadata levels?

  1. Here's the breakdown:
  • For level 1 data (channel response only), users can
    1. Make a gap
    2. Edit any property of channel configurations, add/delete any channel configurations.
    3. Edit (move) any on/offdates that were created by the make a gap procedure
  • For level 2 data (hardware and associated) channel response not entered via SIS UI users can
    1. Make a gap
    2. Add any channel configuration
    3. Delete channel configurations that are not associated with hardware (such as ones from 2 or batch loaded)
    4. Edit channel configuration properties that are not in conflict with the hardware (for example, pin number cannot be edited, but azimuth/dip can)
    5. Edit (move) any on/offdates that were created by the make a gap procedure.
  • For level 3 data (information entered via SIS UI after yesterday's change) users can
    1. Make a gap
    2. Add any channel configuration
    3. Delete channel configurations that are not associated with hardware (such as ones from 2 or batch loaded)
    4. Edit channel configuration properties that are not in conflict with the hardware (for example, pin number cannot be edited, but azimuth/dip can)
    5. Edit (move) any on/offdates that were created by the make a gap procedure.
    6. Edit (move) any action dates that were created by any field actions entered in SIS UI (this is usually the ondate but for terminating a site it is the offdate).

For all levels of metadata, you can do historical installs if they do not overlap with existing epochs. People can also edit/add/delete calibrations of equipment provided they do not overlap with installation epochs.

See Tutorial 5: Making Edits to Existing Metadata for step-by-step instructions on performing the above actions.

Q. How do I do a historical install for a device?

  1. There is no specific form for installing a device (like a battery) in the past. You simply install the device as if it were a current device, then once installed, edit the equipment installation epoch and add an Off Date.

Q. Can I do a historical field action at an inactive site?

  1. Yes.

Naming of Objects in SIS

Q. What is the scope of a template: Organization, Name Space, or global?

  1. An equipment template is stored in the database as a piece of equipment. So its serial number (essentially used as its name) must be unique for that equipment model. Since the operatorship can be changed for general equipment and can change over epochs, its Operator is not a part of the unique constraint. Although the operatorship cannot be changed for templates, it has to follow the same rules as other equipment. So if an RSN codes the serial number as DEFAULT, for example, no one else could create a template named DEFAULT for that same model.

For this reason, an RSN prefix/suffix is recommended for equipment template names. When the templates are listed they are pre-filtered by operator, so you would not see the templates made by other RSNs unless you uncheck the filter by operator.

Q. Can the NCEDC Name Space have a project named ARRA if the SCEDC namespace already has a project named ARRA?

  1. Projects, datastream templates, wiring templates, and responses have 'namespace' and the unique constraint is a combination of the name and the namespace. So you can have a project named ARRA in NCEDC, and SCEDC can also have one named the same. It was to support this requirement (each RSN to be able to independently name these things without worrying if someone else has used that name) that the 'namespace' concept was added in.



If your question isn't answered here, e-mail us at sis-help@gps.caltech.edu