Please send questions and comments to firstname.lastname@example.org.
- 1.1 How do I register a username and choose a namespace?
- 1.2 How do I register my samples?
- 1.3 How are IGSNs assigned?
- 1.4 How do I set private vs public settings on my samples?
- 1.5 What are the metadata fields built in to SESAR?
- 1.6 What metadata fields are mandatory?
- 3.1 When and how do I cite samples that I use from SESAR?
- 3.2 What is the difference between material and object?
- 3.3 How are parent and sibling relationships defined?
- Link to more user submitted questions
- 4.1 I submitted a batch upload template but have not heard anything. What happened?
- 4.2 How do I submit a comment or bug notification?
At the homepage http://www.geosamples.org, click on the new user? button on the right hand side. You will be redirected to the GeoPass page, where you can register for an account that will give you access to SESAR as well as other Geoinformatics for Geochemistry applications.
Your username is the email address with which you register. The first time that you log into SESAR, you will be prompted to choose your three-character namespace. The name space can include letters and numbers, and is not case sensitive. Common namespaces are initials or abbreviations of a large project.
From the SESAR homepage, click the right-most option in the headerbar, LOGIN TO MYSESAR. You will see your personal SESAR page, mySESAR. Along the top of the page, you will see several tabs for navigating in your SESAR space. Click on the tab for Sample Registration.
From the Sample Registration Page, you can choose to register an individual sample or to create a batch file template. Click here for more information on Sample Registration.
After choosing to register an individual sample, you will be able to choose from two options: letting SESAR assign the IGSN, or assigning the IGSN yourself. If you choose the first option, SESAR will generate the 6-character code after your namespace (counting up in order, alphanumerically), if you choose the second option, you can type in your own 6-character code.
In a batch upload, you have the option to type in your own IGSNs into the template, or leave the column blank to have them assigned by SESAR.
When you register your sample(s), you have two options for Sample Availability: (1) Only to me - your samples will be private and only searchable by yourself (IGSN and metadata?) (2) To all users - your sample IGSNs and metadata will be searchable and viewable to all users of SESAR.
Please see the metadata list here.
The only mandatory metadata fields are Object Type and Sample name. We recommend filling in more metadata to take advantage of search and organization capabilities of SESAR. We recommend filling in at least Collection Method and Geolocation (Lat/Lon), as these are commonly searched fields.
The search page is accessible from the SESAR home page and from MySESAR.
If the search window is slightly shaded, it means that suggestive-search occurs for that field: Start typing and a drop-down list of possibilities will appear.
IGSNs can be used in publications as a unique identifier for a sample. Readers of the publication can then use SESAR to find out more information about the sample, and find related samples.
The suggested format for citing SESAR samples is .... "IGSN: XXXXXXXXX"
A parent sample is a sample from which subsequent smaller samples are derived. Examples of children samples are: splits, rock powders, thin sections. Multiple parent-child relationships are allowed: (Grandchildren, Great-grandchildren.)
The parent-child relationship is NOT automatically encoded in the IGSN number because the number follows strict length rules. However, if you choose your own IGSN, you can select the 6 alphanumeric characters in a way that has meaning to you.
Sibling samples are defined as samples with the same parent.
If you uploaded a batch registration template but do not receive an email from SESAR confirming the registration after a few days, please contact email@example.com with your name and namespace.
Please submit all comments or bug notifications to firstname.lastname@example.org.