Update instructions.md

instructions.md

@@ -6,7 +6,7 @@ ESS-DIVE has been testing use of IGSN for the U.S. Department of Energy’s Envi
 
 Here are instructions on how to register your ESS samples for IGSNs through SESAR, and submit your sample metadata and data to ESS-DIVE. 
 
-1. Register and login to [SESAR's geopass](http://geopass.iedadata.org/josso/), and select a user code. The user code should generally be specific to an individual or project. You should use the same user code for all current and future samples. This is important to a.) effectively manage your sample metadata over time (e.g. add links to related publications), and b.) avoid the proliferation of user codes.   
+1. Register and login to [SESAR's geopass system](http://geopass.iedadata.org/josso/), and select a user code. The user code should generally be specific to an individual or project. You should use the same user code for all current and future samples. This is important to a.) effectively manage your sample metadata over time (e.g. add links to related publications), and b.) avoid the proliferation of user codes.   
 
 2. Plan the allocation of identifiers for your samples and sample relationships. Within the SESAR IGSN metadata template, sample relationships are captured by specifying the “Parent IGSN” for each IGSN registered. Therefore, parent samples must be registered before the child samples. For ESS-DIVE, we are also now using location IDs, sampling event IDs, and/or sample collection IDs (which should be project-specific and unique IDs). These project-specific IDs can be described in separate files and submitted along with your ESS-DIVE data packages associated with the samples. An example sample “journey map” (documenting sample transport, analyses, and relationships) may help you map out your general sample relationships and decide on the allocation of IDs. 
 
@@ -16,7 +16,7 @@ Many projects involved in our testing have expressed a preference to use identif
 
 Some projects may choose to register samples that have already been collected and analyzed. We are developing R scripts to help facilitate standardization of existing metadata, and will provide these when completed. 
 
-4. To pre-register samples before sample collection, you can batch upload basic registration metadata (i.e. Object type); this enables the ability to print IGSNs and QR code labels directly from [MySESAR](https://www.geosamples.org/mysesar). Required metadata to register a sample include the Object type (e.g. individual sample), and project-specific sample names. If the sample was derived from a parent sample, then you also must provide the IGSN for the parent sample. Note that most metadata is not known until sample collection, and would be uploaded later (step 7). If registering samples after collection, you can upload all metadata together, and skip steps 5-6.
+4. To pre-register samples before sample collection, you can batch upload basic registration metadata (i.e. Object type); this enables the ability to print IGSNs and QR code labels directly from [MySESAR](https://geopass.iedadata.org/josso/). Required metadata to register a sample include the Object type (e.g. individual sample), and project-specific sample names. If the sample was derived from a parent sample, then you also must provide the IGSN for the parent sample. Note that most metadata is not known until sample collection, and would be uploaded later (step 7). If registering samples after collection, you can upload all metadata together, and skip steps 5-6.
 
 5. If desired, print labels from MySESAR by selecting registered samples, note that samples can include a project-specific sample name in addition to the IGSN, as shown in the [example label here](http://www.geosamples.org/help/labelprinting).