Help

Contents

Simple Search
Advanced Search
Other
Using the GLOS Metadata Form

Simple Search

• Title
• Abstract
• Keywords
• Location
• Free text (any metadata field)

1. string (e.g., temperature -- all records that mention temperature)
2. string1 string2 (e.g., water temperature -- similar to putting an 'and' between the words, all records that mention both water and temperature anywhere in the record)
3. "string1 string2" with quotes around the phrase (e.g., "water temperature" -- all records with the exact phrase 'water temperature')

• Map: Use the map to zoom in out or add your own boundaries.
• Region: Choose from a text dropdown list for a specific named region (e.g., Lake Erie)

• Options:
  • Sort by: Change the way your results sort (e.g., title). Default is 'relevance'.
  • Hits per page: Change the number of results that display on a page. Default is 10, max is 100.
  • Output: Change whether you want to see the full metadata record including images/maps or just the text. Default is 'full'.
• Narrow your search to a specific category (e.g., water quality) by selecting one of the items in the bulleted list.

Advanced Search

Advanced search allows you to enter searches in separate boxes as defined below. You can enter terms in multiple boxes.

• Any
• Any - with one of these words > enter one or more words and GN will find records that have either/any of them (e.g., water temperature ... will find records that only have water, records that only have temperature, and records that have both terms.
• Any - with this exact phrase > enter a series of words but works the same as quotes in a simple search (e.g., "water temperature" ... will find records that only have the word water followed immediately by the word temperature).
• Any - with all of these words > enter words in any order, works the same as an implied "and" between the words (e.g., temperature water ... will find records that have both water and temperature somewhere in the record but does not need to be next to each other or in that order.
• Any - without these words > used as a not operator, enter words you do not want in the search. Can be used in combination with text in another field or with other of the 'any' commands (e.g., enter water in 'Any with one of these words' box and temperature in the without box and GN will find all records with water but that do not have the word temperature anywhere.
• Title
• Abstract
• Keywords

1. string (e.g., temperature -- all records that mention temperature)
2. string1 string2 (e.g., water temperature -- similar to putting an 'and' between the words, all records that mention both water and temperature anywhere in the record.)
3. "string1 string2" with quotes around the phrase (e.g., "water temperature" -- all records with the exact phrase 'water temperature')

• Map Type: select records that are digital, hardcopy, interactive, or downloadable
• Search Accuracy: select the precision with which you want the search to perform from precise to imprecise. Imprecise searches will employ an algorithm that truncates words to a greater detail (e.g., Imprecise: searching for temperature will also give you temperatures (plural); Precise: you would only get records with the singular version of the word).

• Lat/Lon bounding box and map: Use this section to enter coordinates that match records. You can also use the map to zoom in out or add your own boundaries.
• Type: Relates to the map whether you want the search to overlap, enclose, be an exact point, or be fully outside of the boundary or location you entered
• Region: Choose from a text dropdown list for a specific named region (e.g., Lake Erie)

• Various options to search for records that fit a specific date parameter for either the metadata record itself or the temporal extent of the data. The default is 'anytime'.

Reset: will clear the search parameters back to the default values
Search: (or pressing enter) will execute your search

• Restrict to:
  • Catalog: choose the sub-catalog to narrow your search to (e.g., harvested)
  • Category: narrow your search to a specific category (e.g., water quality). This is the same as selecting from the bullets on a simple search
  • Status: search for records that fit a specific publish status (e.g., approved)
• Options:
  • Sort by: Change the way your results sort (e.g., title). Default is 'relevance'.
  • Hits per page: Change the number of results that display on a page. Default is 10, max is 100.
  • Output: Change whether you want to see the full metadata record including images/maps or just the text. Default is 'full'.

Other

• In remote search the user can select multiple servers from the list; as an alternative, the user can select a profile; this automatically selects all servers defined for that profile. For instance, the GeoNetwork profile selects all GeoNetwork servers providing remote search capabilities.
  Since remote Z39.50 transactions can be very slow, the user can define a timeout for the transaction of 10, 20 and 30 seconds.

• To search for content using your browser, use the following syntax:
• by Category: "http://data.glos.us/metadata/srv/eng/main.search?category=observationsBuoys"
• all records, 500 hits per page: "http://data.glos.us/metadata/srv/eng/main.search?hitsPerPage=500&any="
• a specific record: "http://data.glos.us/metadata/srv/eng/metadata.show?id=439"
• by a specific id: "http://data.glos.us/metadata/srv/eng/metadata.show?uuid=4674d03f-3ee4-4414-973d-2d424dd8b8e1"
• a list of titles with a term: "http://data.glos.us/metadata/srv/eng/main.search.suggest?field=title&q=GLERL"

• For detailed assistance on how to use GeoNetwork, see the GeoNetwork User Manual v.2.10.4

GLOS Metadata Form and Support Documentation

GLOS requires submission of a form (GLOS Metadata Registration Form) for all hosted data (e.g., buoys, stations, datasets).

Form help - use the following definitions to assist in filling out your form. If you are unsure about any value, you can always contact the GLOS Data Curator at metadata@glos.us. Items in bold are required.

• Type of Dataset: Choose from the dropdown whether you are submitting metadata for a buoy, a station, a tower or you may enter in your own term.


• Data needs to be available in: Check whether you are asking for data to appear in the GLOS Data Portal, the GLOS GLBuoys site, whether you are just submitting metadata to display in our GeoNetwork repository. You may also fill in an 'other' option if none of those fit your circumstances.


• How will GLOS obtain your data? Choose from the dropdown whether you plan on submitting data to us on a routine basis via ftp. If you are, indicate in the next dropdown whether you are a new user and need an ftp account for GLOS or if you already have an account/access. Other options for this field are that you need us to work with you on accessing the data from your site or if you need us to direct users to your site and we will not have data appearing in GLOS tools.

• Full title or name of dataset: Enter the name of your dataset (required). The name or title should be fairly short but descriptive. Generally this is the exact name that will appear in GLOS products such as the Data Portal, however the Data Curator may decide to enhance, shorten or change it in order to clarify to the public what the dataset covers.
  Example: "Lake Erie Evaporation and Meteorological Data from Long Point"


• Alternate title or abbreviated name of dataset: If you have a shortened title that someone may search for in GeoNetwork. This field is not searchable in the GLOS Data Portal but the Data Curator may decide to append it to or incorporate it in the full title.
  Example: "Long Point station LNPQ6"


• Existing station ID(s): If your station has alternate identification numbers such as NWS, COOP, etc. enter all that apply here


• Latitude/Longitude/Elevation: If your data comes from a single geographic location, enter the lat/lon here in decimal format. You do not need to go more than 5 significant decimal places. If it is an entire region, enter the bounding coordinates in the 'Other details' box.
  Example: "latitude 42.566667; longitude -80.05". If your station is at a particular elevation, fill in the elevation box. Use the "other location details" as needed.


• Sensors: If you are submitting metadata for a buoy or station, enter a list of all the sensors/parameters you wish displayed in the GLOS tool(s). Please see our Data Enrollment Guide for a list of sample parameters. Be sure to include any units such as feet vs. meters
  Example: wdir1 (wind direction), wvhght (wave height) @ 5m


• Dates: There are three dates which can be used for your metadata - Date created (required), Date published, Date revised. Date created would be the date your dataset was first created regardless if it was published on that date. If you published it at a different date, fill in the publish date and/or the revised date. It is perfectly acceptable to only have a date created value.
  Example: "Created: 2016-01-20; Published: 2016-10-10; Revised: 2017-01-13"


• Edition or version: If you do have a revised version of your dataset or if it is a beta version. Otherwise, leave blank.
  Example: "Rev. 1"


• Abstract: Provide a descriptive abstract (required) detailing what your dataset is about. This field would also be searchable if we provide access through the GLOS Data Portal. A good size abstract will be around 100 words.
  Example: "The Long Point eddy covariance and meteorological station is maintained by Environment Canada and located 30 miles north of Erie, Pennsylvania on Lake Erie. The station is part of the Great Lakes Evaporation Network (GLEN), which was established to improve observations of over-lake meteorology and evaporation, to use these observations to provide more accurate projections of Great Lakes water levels, and to support a variety of stakeholders, including the National Weather Service (NWS), U.S. and Canadian Coast Guard, recreational boaters and commercial shipping, emergency management officials, and the Great Lakes research community."


• Purpose: If applicable, provide a short comment on the purpose of this dataset. This would be a good place to enter sponsorship for the project or other information related to why this project data has been collected.
  Example: "To provide Lake Erie evaporation and meteorological measurements from Long Point."


• Status: Choose from the dropdown which value best fits the status of your project. Options: on-going (in progress); completed; historical archive; obsolete; planned; under development. Generally most GLOS projects will be "on-going", however there may be some that fit better in the other categories.


• Presentation format: Note whether your data is electronic (digital) or hardcopy or both in the left column, then indicate which of the types fit your data (image, map, model, table, video or other). Most of the time for GLOS purposes data is electronic and table.
  Example: "Digital / table, map"


• Contacts: This section should be fairly self-explanatory, but enter in your primary contact or contacts here. Required components are name, role, address and email. Since the form only allows for a single person and since often projects have more than one PI or contact, use the 'Additional Contacts' box to fill in any additional names. The Individual Role dropdown options are: point of contact; principal investigator; owner; resource provider, other (and you can fill in a different role).
  Example: "Joe Smith; Point of Contact; 123 West Ln, Ann Arbor, MI 48104; joes@me.com"


• Resource maintenance: Choose the appropriate timeframe from the dropdown (required) for 'Maintenance and update frequency'. Options: as needed; annually; biannually; continual; daily; fortnightly (two weeks); irregular. If appropriate you can also add in the date of the next update. Fill in the note box if your schedule is other than what is available in the dropdown or if it needs further explanation.
  Example: "As needed; typically done at beginning and end of buoy season."


• Descriptive keywords: Fill in any keywords you think would assist users in searching for your dataset. While this will be enhanced by the Data Curator, it always helps to know how you believe users would look for your information. We do not require that you use a controlled vocabulary (one that relies on a thesaurus or keyword list), but if you do use one, indicate so in the Thesaurus box. Use the top box for subject-type keywords and the bottom for location-based.
  Example: "Subject - eddy covariance system, latent heat, GLEN, climate indicators; Location - Lake Erie; Long Point; Great Lakes"


• Constraints: If your data has any constraints on how it is accessed or used. An access restriction would be something like only accessible by login or only available to government employees. Please note that GLOS will not publish any data that is not publicly available although it is acceptable to require users to login. A usage constraint might be something along the lines of requiring the user to acknowledge the data source in publications. Other constraints along the lines of security and licensing should also be noted. Options: none; restricted; other. If you indicate any type of constraint it is required that you also fill in the clarification field.
  Example: "Access Constraints detailed in Open Data Licence. https://xxx.yyy.com/access.html "


• Language: Check the language (required) that the dataset and/or host website is in. If it is other than English or French, fill in the 'other' box.


• Topic category code: Choose from the dropdown the appropriate ISO topic category code (required). The ones most commonly used for GLOS are: inland waters; climatology, meteorology, atmosphere; environment; oceans. However, you may choose any of the others as well.


• Supplemental information: Fill in anything additional that you feel will provide more information for your dataset such as height of sensor or data only available during buoy season which is typically spring. Also fill in other details about your dataset such as that you plan on ftp'ing the data to us.
  Example: "Site elevation: 175 m above mean sea level; Instrument height: 32.0m "


• URL: If applicable, provide us with the URL to your data. If you are planning on ftp'ing the data to GLOS, indicate that in the above supplemental information box.


• Service type: Provide us with details on what we would need if we are accessing your data from a service such as the above web address (URL), WFS-web feature service, Catalogue service for the web, OpenDAP URL, ncWMS, SOS, etc...


• Offline resource availability: If your dataset is something the user actually has to request from the designated point of contact or website, indicate specifics on how they are to obtain the data.
  Example: Available upon request from the Dept of XYZ at the above contact information.

• Data Quality Section: this section is the hardest part of the form and is required for any dataset that will be published on the GLOS Data Portal or made available in any of our tools. Generally the easiest way to submit this data is in a table instead of using the form fields since most will have more than one quality test they are performing. If you are submitting a separate table, check the box to indicate that and email the table along with your form.


• Type of data: Choose from the dropdown whether your QA/QC is quantitative (measured) or qualitative (characterized or approximated) data.


• Type of quality test performed: Choose from the dropdown one of the following. The most commonly used ones for our purposes are bolded below. >
• absolute external positional accuracy: reporting closeness of the coordinate value to values that are accepted as being true. (example: wind direction values to their positions to a known or accepted-as-true source)
• accuracy of time measurement: reporting errors in time measurement
• completeness commission or completeness omission: reporting presence or absence of features (e.g., whether certain data is being tested for being there (example: testing for satellite coverage and setting a percent of acceptability on missing values due to cloud cover)
• conceptual consistency: count of items that follow the rules set for the dataset or schema (example: data overlaps within a certain acceptable range)
• domain consistency: count of items that follow the set of permissible values for the dataset (example: if you have a list of features that correspond to a number 1, 2, 3 - count of items that are coded appropriately)
• format consistency: count of items that are in the appropriate format such as date or time (example: if you require date in yyyy-mm-dd)
• gridded data positional accuracy: closeness of gridded data position values to those that are accepted as true
• non-quantitative attribute accuracy: accuracy of non-quantitative values (example: text items from a list of acceptable values)
• quantitative attribute accuracy: accuracy of quantitative (measurable) values (example: testing relative humidity values against manufacturer's accepted values, or testing whether temperatures fall within an accepted range)
• relative internal positional accuracy: closeness of the position of a value or coordinate in relation to another (example: a point in relation to a fixed station or known lat/lon)
• temporal consistency: correctness of events or items that require a time sequence
• temporal validity: test of the data with respect to time (example: items with the appropriate date range such as dates on maps or legends)
• thematic classification correctness: how correct is the spectral information contained in an image (example: use of a spectral signature for color in a satellite image)
• topological consistency: reports on the validity of topological characteristics of a dataset (example: polygons too small on a map, lines to close, etc.)


• Name of test: Describe the test you are performing (example: "Test min/max values of wind direction")


• Code: Provide the identifier code that will accompany your test (example: WDIR1)


• Description: A very brief text description for the test (example: "wind direction")


• Evaluation method: Choose from the following options >
  • direct external: method of evaluating the quality of a dataset based on inspection of items within the dataset, where reference data is external to the dataset being evaluated (example: comparing air temperature values with known valid temperatures for the region for that time period, or comparing valid measures with manufacturer specifications for the instrument)
  • direct internal: method of evaluating the quality of a dataset based on inspection of items within the dataset, where all data required is internal to the dataset being evaluated (example: comparing wave height measurements to other wave data being collected)
  • indirect: method of evaluating the quality of a dataset based on external knowledge (example: knowing that a water temperature of 120 deg. F would be an invalid measure)
  
  
• Evaluation method description: a more in-depth description of how the measurement is being done, typically including instrumentation manufacturer, model, etc. (example: Young Wind Monitor SE Model 09101)


• Compliance description: describe in as much detail as possible the steps you will take to resolve quality issues with your data (example: "will report issues within x period of time to GLOS, data will be revised and resubmitted"; or "data will be flagged in the data as being suspect")


• Additional details: add anything here that will clarify or expand upon your QA/QC

• Metadata information: check whether your metadata could be scraped (programmatically incorporated) into our GeoNetwork instance and provide a link. Also provide other metadata contact information or other information if appropriate.

siteID: 699cf735-fabd-4b7f-b7d4-2a1a4e0531ee