Merge pull request #81 from cds-astro/comments_aug23

Comments aug23

episodes/section1_intro.md

@@ -184,3 +184,13 @@ In the next chapters, you will learn what type of data can be submitted, how to
 <!-- 		Link references			-->
 <!--	==> See links.md file			-->
 <!--  ----------------------------------------- -->
+
+
+<!--  ----------------------------------------- -->
+<!-- Transform link a/href with target="_blank" -->
+<!-- Open them in a new window			-->
+<!--  ----------------------------------------- -->
+<script>
+document.querySelectorAll('#main-content a:not([target])').forEach(link => link.setAttribute('target', '_blank'))
+</script>
+

episodes/section_data_curation.md

@@ -248,3 +248,12 @@ In the next chapters, you will learn what happen to your fully ingested data whe
 <!--	==> See links.md file			-->
 <!--  ----------------------------------------- -->
 
+
+<!--  ----------------------------------------- -->
+<!-- Transform link a/href with target="_blank" -->
+<!-- Open them in a new window			-->
+<!--  ----------------------------------------- -->
+<script>
+document.querySelectorAll('#main-content a:not([target])').forEach(link => link.setAttribute('target', '_blank'))
+</script>
+

episodes/section_eosc.md

@@ -14,8 +14,8 @@ exercises: 1
 
 ::::::::::::::::::::::::::::::::::::: objectives
 
-- Describe the integration of astronomy data services in the VO and EOSC.
-- Naviguate through the EOSC portal. 
+- Describe the integration of astronomy data services in the VO and EOSC
+- Naviguate through the EOSC portal
 
 ::::::::::::::::::::::::::::::::::::::::::::::::
 
@@ -41,7 +41,6 @@ The first stop for your data after VizieR is the [International Virtual Observat
 Then the datasets reach a broader audience when [EUDAT/B2Find][b2find] and the EOSC registries gather information (harvest) about everything emitted by the IVOA registry. In this way the familiar processes of publishing data become part of the wider EOSC system. 
 
 
-
 <!--  ----------------------------------------- -->
 <!--            EOSC	                        -->
 <!--  ----------------------------------------- -->
@@ -235,17 +234,24 @@ Browse through EOSC Portal to find some datasets and publications, and answer th
 ## Can you answer the following questions?
 
 
-```
 Q1) What is the publication date for 'Brightest cluster galaxies in Abell clusters'?
+
 Q2) Which CDS service is listed in the 'Services' type of results?
+
 Q3) Can you list some 'cds-astro' Softwares available?
+
 Q4) Advanced question: can you find the dataset associated with the word 'Astronomy'
 and published by the 'National Radio Astronomy Observatory'? 
+
 Q5) If you published a paper or a dataset, type your name in the Search bar. 
 What do you get as an output?
-```
 
-Hint: Browse through [EOSC Portal][eosc-portal] to answer the previous questions.
+:::::::::::::::::::::::: hint
+
+Browse through [EOSC Portal][eosc-portal] to answer the previous questions.
+
+:::::::::::::::::::::::::::::::::
+
 
 :::::::::::::::::::::::: solution
 
@@ -305,4 +311,11 @@ The search result Data should look like: [search-result][eosc-question4-dataset]
 This concludes this training on how to make your published astronomical data (table, images, spectra, …) FAIR and openly accessible to the community, and discoverable in Virtual Observatory tools such as EOSC.
 
 
+<!--  ----------------------------------------- -->
+<!-- Transform link a/href with target="_blank" -->
+<!-- Open them in a new window			-->
+<!--  ----------------------------------------- -->
+<script>
+document.querySelectorAll('#main-content a:not([target])').forEach(link => link.setAttribute('target', '_blank'))
+</script>
 

episodes/section_fair_astro.md

@@ -204,8 +204,8 @@ b) The period of a periodic phenomenon should be given as
 c) Present a measurement as 0.123±0.002, 
 not 0.12345±0.002 or 0.123±0.00234.
 d) Present source color “(B-V) = 0.45 mag” instead of “(B-V) = 0.45”
-e) State your preferred solution in the text and have a dedicated column for the adopted solution in your Table, 
-as shown in <a href="https://vizier.cds.unistra.fr/viz-bin/VizieR-3?-source=J/ApJS/261/19/table8" target="_blank">Table 8 from VizieR catalogue J/ApJS/261/19</a>
+e) State your preferred solution in the text and have a dedicated column 
+for the adopted solution in your Table, as shown in <a href="https://vizier.cds.unistra.fr/viz-bin/VizieR-3?-source=J/ApJS/261/19/table8" target="_blank">Table 8 from VizieR catalogue J/ApJS/261/19</a>
 </pre></big>
 
 ![Figure: Extract of Table 8 from VizieR catalogue J/ApJS/261/19](https://raw.githubusercontent.com/cds-astro/a-FAIR-journey-for-astronomical-data/main//episodes/images/vizier_adopted_value_example.png){alt="Small extract of Table 8 from VizieR catalogue J/ApJS/261/19, displaying 4 columns for the effective temperature: TeffR, TeffS, TeffP and Teff, the latter one corresponding to their adopted temperature"}
@@ -280,63 +280,89 @@ and explain how to correct them.
 
 ## Quiz: Why are these astronomical designations improper?
 
-
-```
 Q1) SDSS J1441+0948
+
 Q2) SN 5J 
+
 Q3) HESS J232+202
+
 Q4) BR 0529-3526
+
 Q5) B0008+006
+
 Q6) DEM45
+
 Q7) Gaia 2448177130188111232 
+
 Q8) Gaia DR 2 2.7904e18
+
 Q9) mu cep
-```
 
-Hint: Look for these objects in [Simbad][simbad-home].
+:::::::::::::::::::::::: hint
+
+## Hint
+
+Look for these objects in [Simbad][simbad-home].
+
 Can you find them?
 
-:::::::::::::::::::::::: hint
+:::::::::::::::::::::::::::::::::
+
+
+:::::::::::::::::::::::: solution
 
 ## Why is it improper?
 
-```
 I1) Insufficient precision in RA and DEC causes confusion.
 In this case, it could correspond to many objects in the different SDSS releases.
+
 I2) Incomplete name can be interpreted into different objects.
+
 I3) Leading zero in RA is missing and can cause misinterpretation 
 of the RA at 23 hours instead of 02 hour. 
+
 I4) Missing letter J to specify J2000 equatorial coordinates.
+
 I5) Name prefix is needed to distinguish between different objects.
+
 I6) H II regions in LMC or SMC should be indicated with 
 “L” or “S” to avoid ambiguity.
+
 I7) Database objectID number is used without specifying release 
 number. The same running number may refer to a different source 
 in a different release.
+
 I8) ID is written in scientific notation, making it impossible 
 to retrieve the actual object (which is a 19-integer number).
+
 I9) Ambiguous name can be interpreted into different objects.
-```
+
 :::::::::::::::::::::::::::::::::
 
 :::::::::::::::::::::::: solution
 
 ## Recommended usage
 
-```
 R1) SDSS J144157.24+094859.1, or SDSS J144156.97+094856.5, 
 or SDSS J144157.26+094853.7
+
 R2) SN 2005J or SN 2015J are different targets
+
 R3) HESS J0232+202
+
 R4) BR J0529-3526
+
 R5) QSO B0008+006 (Redshift z = 2.3) and
 IVS B0008+006 (Redshift z = 1.5) are different targets
+
 R6) DEM L 045, or DEM S 045
+
 R7) Gaia DR3 2448177130188111232
+
 R8) Gaia DR2 2790494815860044544
-R9) *mu. Cep (21h43m30.46s, +58d46m48.2s, J2000), or
-V* MU Cep (22h23m38.63s, +57d40m50.8s, J2000)
-```
+
+R9) \*mu. Cep (21h43m30.46s, +58d46m48.2s, J2000), or
+V\* MU Cep (22h23m38.63s, +57d40m50.8s, J2000)
 
 :::::::::::::::::::::::::::::::::
 ::::::::::::::::::::::::::::::::::::::::::::::::
@@ -522,7 +548,7 @@ Stick to one value!
 e) Authors should include a human-readable description of the data,
 with at least the column descriptions, units, and references (on the 
 origin of the measurements or instruments for observations when relevant) 
-in a ReadMe file. More help on the ReadMe is given in a <a href="section_submit_data.html">forthcoming Chapter</a>.
+in a ReadMe file. More help on the ReadMe is given in the <a href="section_submit_data.html" target="_blank">Chapter "Submitting astronomical data"</a>.
 </pre></big>
 
 <!--  ----------------- -->
@@ -719,12 +745,13 @@ Give some examples of ambiguous facility/ telescope/instrument names from the li
 
 ## Quiz: Can you guess the names of these facilities?
 
-```
 Q1) ARO
+
 Q2) DDO
+
 Q3) EMIR
+
 Q4) OSIRIS
-```
 
 :::::::::::::::::::::::: solution
 
@@ -826,3 +853,10 @@ of data contained in the article.
 In the next chapters, you will learn what are the different submission routes (depending on your journal) and then how to prepare and submit your data to VizieR. Ultimately you will see how to search your data using the EOSC tools.
 
 
+<!--  ----------------------------------------- -->
+<!-- Transform link a/href with target="_blank" -->
+<!-- Open them in a new window			-->
+<!--  ----------------------------------------- -->
+<script>
+document.querySelectorAll('#main-content a:not([target])').forEach(link => link.setAttribute('target', '_blank'))
+</script>

episodes/section_prepare_data.md

@@ -118,7 +118,7 @@ Files containing different numbers of columns per rows.
 
 :::::::::::::::::::::::::::::::::::::::::::::::::::
 
-More details on how to create FAIR tables can be found in the previous Chapter <a href="section_fair_astro.html#general_rules" target="_blank">FAIR principles for astronomical data</a>.
+More details on how to create FAIR tables can be found in the previous Chapter <a href="section_fair_astro.html#general_rules" target="_blank">"FAIR principles for astronomical data"</a>.
 
 Following this checklist will help improving the efficiency of the ingestion in VizieR and also the visibility and reusability of your data :).
 
@@ -226,16 +226,19 @@ Show some good and bad examples of filenames.
 
 ## Quiz: Are these filenames correct or not?
 
-
-```
 Q1) 'TABLE998.dat'
+
 Q2) 'table.4.long.version.dat'
+
 Q3) 'table.dat'
+
 Q4) 'test+table.dat'
+
 Q5) 'my_table.data'
+
 Q6) 'table&data.dat'
+
 Q7) 'myfile.jpg'
-```
 
 :::::::::::::::::::::::: solution
 
@@ -317,3 +320,11 @@ In the next chapters, you will learn how to submit your data to VizieR, and fina
 <!--	==> See links.md file			-->
 <!--  ----------------------------------------- -->
 
+
+<!--  ----------------------------------------- -->
+<!-- Transform link a/href with target="_blank" -->
+<!-- Open them in a new window			-->
+<!--  ----------------------------------------- -->
+<script>
+document.querySelectorAll('#main-content a:not([target])').forEach(link => link.setAttribute('target', '_blank'))
+</script>

episodes/section_submission_per_journals.md

@@ -255,3 +255,13 @@ In the next chapters, you will learn how to prepare and submit your data to Vizi
 <!-- 		Link references			-->
 <!--	==> See links.md file			-->
 <!--  ----------------------------------------- -->
+
+
+<!--  ----------------------------------------- -->
+<!-- Transform link a/href with target="_blank" -->
+<!-- Open them in a new window			-->
+<!--  ----------------------------------------- -->
+<script>
+document.querySelectorAll('#main-content a:not([target])').forEach(link => link.setAttribute('target', '_blank'))
+</script>
+

episodes/section_submit_data.md

@@ -16,7 +16,7 @@ exercises: 0
 ::::::::::::::::::::::::::::::::::::: objectives
 
 - Fill a *ReadMe* file
-- Submit your data in the existing and new Open Science systems,  keeping in mind the Virtual Observatory (VO) standards.
+- Submit your data in the existing and new Open Science systems,  keeping in mind the Virtual Observatory (VO) standards
 
 ::::::::::::::::::::::::::::::::::::::::::::::::
 
@@ -59,7 +59,7 @@ Two routes are possible to submit your data to VizieR:
 		- They will be then available via our [dedicated interface Saada/VizieR][vizier-assoc-data].
 - Option 2: Use the [**File Transfer Protocol (FTP)**][vizier-ftp-login]
 	- You can use the [**Python cdspyreadme library**][vizier-cdspyreadme] to create the required *ReadMe* file.
-	- Tables and other data (not necessarily FITS) can be uploaded. More information on the data types accepted are available in the previous Chapter <a href="section_prepare_data.html" target="_blank">Preparing your data</a>.
+	- Tables and other data (not necessarily FITS) can be uploaded. More information on the data types accepted are available in the previous Chapter <a href="section_prepare_data.html" target="_blank">"Preparing your data"</a>.
 
 
 <!-- #### Special case: large volumetry -->
@@ -275,7 +275,7 @@ allowfullscreen="" allow="autoplay" data-external="1"></iframe>
 
 The VizieR submit service detects automatically the input format.
 Please, upload here only the regular tabular data (tables).
-More information on the accepted formats can be found in the Chapter [Preparing your data](../section_prepare_data.md).
+More information on the accepted formats can be found in the Chapter <a href="section_prepare_data.html" target="_blank">"Preparing your data"</a>.
 
 
 The upload will generate:
@@ -324,7 +324,7 @@ Then you submit the updated *ReadMe* with the "upload" button:
 ### Upload FITS Spectra / Time series
 
 Once the tables and the *ReadMe* are uploaded, you can upload your associated data: spectra and time series.
-More information on the accepted formats can be found in the Chapter [Preparing your data](../section_prepare_data.md).
+More information on the accepted formats can be found in the Chapter <a href="section_prepare_data.html" target="_blank">"Preparing your data"</a>.
 
 The FITS upload generates a mapping between the spectra FITS header and ObsCore keywords. We strongly encourage you to modify the mapping to better describe your data.
 
@@ -352,7 +352,7 @@ For each upload, a report is available. **It is recommended to verify the mappin
 
 FITS images can also be uploaded in a similar way as the FITS Spectra (see above).
 
-More information on the accepted formats can be found in the Chapter [Preparing your data](../section_prepare_data.md).
+More information on the accepted formats can be found in the Chapter <a href="section_prepare_data.html" target="_blank">"Preparing your data"</a>.
 
 
 ![Figure: VizieR catalogue upload page - step FITS images (Screenshot)](https://raw.githubusercontent.com/cds-astro/a-FAIR-journey-for-astronomical-data/main/episodes/images/vizier_submit_online_interface_july23/step4_fits_images.png){alt="Screenshot: VizieR Catalogue upload page, upload associated data: FITS Images after initiating a session, uploading your tables, filling the ReadMe file and uploading FITS Spectra and Time Series, from June 2023"} 
@@ -429,7 +429,7 @@ On success, a mail is sent to your email address with the FTP login and some ins
 Your freshly created account is ready and available for **3** days.
 You can put your files directly under the repository  (the root ftp directory being dedicated per login).
 
-More information on the accepted data and formats can be found in the Chapter [Preparing your data](../section_prepare_data.md).
+More information on the accepted data and formats can be found in the Chapter <a href="section_prepare_data.html" target="_blank">"Preparing your data"</a>.
 
 Type the following command in a terminal to access the FTP server: `ftp ftp.cds.unistra.fr`.
 
@@ -544,3 +544,13 @@ In the next chapters, you will learn what happen to your submitted data before t
 <!--	==> See links.md file			-->
 <!--  ----------------------------------------- -->
 
+
+
+<!--  ----------------------------------------- -->
+<!-- Transform link a/href with target="_blank" -->
+<!-- Open them in a new window			-->
+<!--  ----------------------------------------- -->
+<script>
+document.querySelectorAll('#main-content a:not([target])').forEach(link => link.setAttribute('target', '_blank'))
+</script>
+

learners/setup.md

@@ -94,8 +94,16 @@ If you have got any questions, feel free to contact directly the VizieR team at:
 
 
 <!--  ----------------------------------------- -->
-<!--            Link references                 -->
+<!--            Link references  ==> links.md   -->
 <!--  ----------------------------------------- -->
-[vizier-publi-data-home]: https://vizier.cds.unistra.fr/vizier/submit.htx
+
+
+<!--  ----------------------------------------- -->
+<!-- Transform link a/href with target="_blank" -->
+<!-- Open them in a new window			-->
+<!--  ----------------------------------------- -->
+<script>
+document.querySelectorAll('#main-content a:not([target])').forEach(link => link.setAttribute('target', '_blank'))
+</script>
 
 

links.md

@@ -33,6 +33,7 @@ any links that you are not going to use.
 [vizier-fits-validator]: https://cdsarc.cds.unistra.fr/vizier.submit/fitsvalidator.html
 [vizier-submit-login]: https://cdsarc.cds.unistra.fr/vizier.submit/index.html
 [vizier-submit-data-help]: https://cdsarc.cds.unistra.fr/vizier.submit/help.html
+[vizier-publi-data-home]: https://vizier.cds.unistra.fr/vizier/submit.htx
 <!-- VizieR FTP -->
 [vizier-ftp-login]: https://cds.unistra.fr/ftp/token/
 [vizier-ftp]: https://cdsarc.cds.unistra.fr/ftp/