diff --git a/aio.html b/aio.html index e702bcc..c8fbf51 100644 --- a/aio.html +++ b/aio.html @@ -646,7 +646,7 @@

To be Findable

-
+

The first step before reusing the data is to be able to find them. The metadata and data should be easy to find for both humans and @@ -668,7 +668,7 @@

To be Accessible

-
+

Once the data can be found, the user needs to know how to access them. That could include authentification and authorisation. The @@ -696,7 +696,7 @@

To be Interoperable

-
+

Those data can then be combined with different datasets, and interoperate with other applications or workflows for analysis, storage, @@ -716,7 +716,7 @@

To be Reusable

-
+

The ultimate goal of FAIR is to optimise the reuse of data. To achieve this, metadata and data should be well-described, including a @@ -934,7 +934,7 @@

Give me a hint

-
+

Look for these objects in Simbad.

Can you find them?

@@ -949,7 +949,7 @@

Why is it improper?

-
+

I1) Insufficient precision in RA and DEC causes confusion. In this case, it could correspond to many objects and different surveys.

@@ -978,7 +978,7 @@

Recommended usage

-
+

R1) LAMOST J221750.59+210437.1 and SDSS J221746.82+210424.1 are potential matches for this incomplete name

@@ -1290,7 +1290,7 @@

Why is it improper?

-
+

The quality of the measurement is indicated using a superscript. Providing this information using an extra column will make the table @@ -1306,7 +1306,7 @@

Recommended usage

-
+
@@ -1524,7 +1524,7 @@

List of solutions

-
+
@@ -2732,7 +2732,7 @@

A. ‘Title of the paper’, ‘Authors’, ‘Reference’

-
+
  • @@ -2755,7 +2755,7 @@

    B. ‘Abstract’ and ‘Description’

    -
    +
    • @@ -2786,7 +2786,7 @@

      C. ‘Byte-by-byte Description of file’

      -
      +

      This section describes the structure of each data files (files with the .dat extension). This description is made in a tabular form, each diff --git a/index.html b/index.html index e9836f6..6e570e7 100644 --- a/index.html +++ b/index.html @@ -155,6 +155,7 @@

    • Type of course
    • Version
    • License
    • +
    • Supporting organisation
    • Contact
    @@ -410,9 +411,9 @@

    Checklist

    Version

    -

    Training version: 0.5.0

    +

    Training version: 0.6.0

    Publication date: 10 July 2023

    -

    Last modified: 11 September 2023

    +

    Last modified: 15 September 2023

    License

    @@ -422,6 +423,12 @@

    ChecklistCC-BY 4.0 License using The Carpentries training format and The Carpentries Incubator lesson infrastructure.

    + +

    Supporting organisation +

    +

    This work has been supported by the EOSC (European Open Science +Cloud) Future project.

    +

    Contact


    If you have got any questions, feel free to contact directly the diff --git a/instructor/aio.html b/instructor/aio.html index 381d138..f534c76 100644 --- a/instructor/aio.html +++ b/instructor/aio.html @@ -646,7 +646,7 @@

    To be Findable

    -
    +

    The first step before reusing the data is to be able to find them. The metadata and data should be easy to find for both humans and @@ -668,7 +668,7 @@

    To be Accessible

    -
    +

    Once the data can be found, the user needs to know how to access them. That could include authentification and authorisation. The @@ -696,7 +696,7 @@

    To be Interoperable

    -
    +

    Those data can then be combined with different datasets, and interoperate with other applications or workflows for analysis, storage, @@ -716,7 +716,7 @@

    To be Reusable

    -
    +

    The ultimate goal of FAIR is to optimise the reuse of data. To achieve this, metadata and data should be well-described, including a @@ -913,7 +913,7 @@

    Instructor Note

    -
    +

    Modified version of Table 1 from Chen et al. 2022:

    Show some examples of improper astronomical designations in @@ -950,7 +950,7 @@

    Give me a hint

    -
    +

    Look for these objects in Simbad.

    Can you find them?

    @@ -965,7 +965,7 @@

    Why is it improper?

    -
    +

    I1) Insufficient precision in RA and DEC causes confusion. In this case, it could correspond to many objects and different surveys.

    @@ -994,7 +994,7 @@

    Recommended usage

    -
    +

    R1) LAMOST J221750.59+210437.1 and SDSS J221746.82+210424.1 are potential matches for this incomplete name

    @@ -1260,7 +1260,7 @@

    Instructor Note

    -
    +

    Modified version from Table 2 from Chen et al. 2022:

    Show that using LaTeX markups or footnotes in tables affect their @@ -1322,7 +1322,7 @@

    Why is it improper?

    -
    +

    The quality of the measurement is indicated using a superscript. Providing this information using an extra column will make the table @@ -1338,7 +1338,7 @@

    Recommended usage

    -
    +

@@ -1540,7 +1540,7 @@

Instructor Note

-
+

Table 3 from Chen et al. 2022:

Give some examples of ambiguous facility/ telescope/instrument names @@ -1572,7 +1572,7 @@

List of solutions

-
+
@@ -2797,7 +2797,7 @@

A. ‘Title of the paper’, ‘Authors’, ‘Reference’

-
+
  • @@ -2820,7 +2820,7 @@

    B. ‘Abstract’ and ‘Description’

    -
    +
    • @@ -2851,7 +2851,7 @@

      C. ‘Byte-by-byte Description of file’

      -
      +

      This section describes the structure of each data files (files with the .dat extension). This description is made in a tabular form, each diff --git a/instructor/index.html b/instructor/index.html index 3786c83..c4574b9 100644 --- a/instructor/index.html +++ b/instructor/index.html @@ -485,9 +485,9 @@

      Checklist

      Version

      -

      Training version: 0.5.0

      +

      Training version: 0.6.0

      Publication date: 10 July 2023

      -

      Last modified: 11 September 2023

      +

      Last modified: 15 September 2023

      License

      @@ -497,6 +497,12 @@

      ChecklistCC-BY 4.0 License using The Carpentries training format and The Carpentries Incubator lesson infrastructure.

      + +

      Supporting organisation +

      +

      This work has been supported by the EOSC (European Open Science +Cloud) Future project.

      +

      Contact


      If you have got any questions, feel free to contact directly the diff --git a/instructor/section_fair_astro.html b/instructor/section_fair_astro.html index 0c25892..f0927c6 100644 --- a/instructor/section_fair_astro.html +++ b/instructor/section_fair_astro.html @@ -388,7 +388,7 @@

      To be Findable

      -
      +

      The first step before reusing the data is to be able to find them. The metadata and data should be easy to find for both humans and @@ -410,7 +410,7 @@

      To be Accessible

      -
      +

      Once the data can be found, the user needs to know how to access them. That could include authentification and authorisation. The @@ -436,7 +436,7 @@

      To be Interoperable

      -
      +

      Those data can then be combined with different datasets, and interoperate with other applications or workflows for analysis, storage, @@ -456,7 +456,7 @@

      To be Reusable

      -
      +

      The ultimate goal of FAIR is to optimise the reuse of data. To achieve this, metadata and data should be well-described, including a @@ -636,7 +636,7 @@

      Instructor Note

      -
      +

      Modified version of Table 1 from Chen et al. 2022:

      Show some examples of improper astronomical designations in @@ -673,7 +673,7 @@

      Give me a hint

      -
      +

      Look for these objects in Simbad.

      Can you find them?

      @@ -688,7 +688,7 @@

      Why is it improper?

      -
      +

      I1) Insufficient precision in RA and DEC causes confusion. In this case, it could correspond to many objects and different surveys.

      @@ -717,7 +717,7 @@

      Recommended usage

      -
      +

      R1) LAMOST J221750.59+210437.1 and SDSS J221746.82+210424.1 are potential matches for this incomplete name

      @@ -947,7 +947,7 @@

      Instructor Note

      -
      +

      Modified version from Table 2 from Chen et al. 2022:

      Show that using LaTeX markups or footnotes in tables affect their @@ -988,7 +988,7 @@

      Why is it improper?

      -
      +

      The quality of the measurement is indicated using a superscript. Providing this information using an extra column will make the table @@ -1004,7 +1004,7 @@

      Recommended usage

      -
      +

@@ -1169,7 +1169,7 @@

Instructor Note

-
+

Table 3 from Chen et al. 2022:

Give some examples of ambiguous facility/ telescope/instrument names @@ -1201,7 +1201,7 @@

List of solutions

-
+
Object Redshift
diff --git a/instructor/section_submit_data.html b/instructor/section_submit_data.html index daa85d1..b40163c 100644 --- a/instructor/section_submit_data.html +++ b/instructor/section_submit_data.html @@ -517,7 +517,7 @@

A. ‘Title of the paper’, ‘Authors’, ‘Reference’

-
+
  • Title of the paper: Title as written in paper
  • @@ -538,7 +538,7 @@

    B. ‘Abstract’ and ‘Description’

    -
    +
    • Abstract: Describes the scientific results @@ -563,7 +563,7 @@

      C. ‘Byte-by-byte Description of file’

      -
      +

      This section describes the structure of each data files (files with the .dat extension). This description is made in a tabular form, each diff --git a/md5sum.txt b/md5sum.txt index ac0d0b2..91e003e 100644 --- a/md5sum.txt +++ b/md5sum.txt @@ -12,6 +12,6 @@ "episodes/section_data_curation.md" "7762c4a4bfadb80226d6d18f283c0804" "site/built/section_data_curation.md" "2023-09-11" "episodes/section_eosc.md" "602f27426f3498b4beeb9b8b0ee4a4b1" "site/built/section_eosc.md" "2023-09-07" "instructors/instructor-notes.md" "60b93493cf1da06dfd63255d73854461" "site/built/instructor-notes.md" "2022-04-22" -"learners/setup.md" "e63e9843113f9293c141a9889d3204fc" "site/built/setup.md" "2023-09-11" +"learners/setup.md" "e854fbac077d091ec9060d00e07ac3c2" "site/built/setup.md" "2023-09-15" "learners/reference.md" "bfa491f8cf0002c2efaeb527354f5b14" "site/built/reference.md" "2023-08-30" "profiles/learner-profiles.md" "60b93493cf1da06dfd63255d73854461" "site/built/learner-profiles.md" "2022-04-22" diff --git a/pkgdown.yml b/pkgdown.yml index e0e60e3..300fc1f 100644 --- a/pkgdown.yml +++ b/pkgdown.yml @@ -2,5 +2,5 @@ pandoc: 2.19.2 pkgdown: 2.0.7 pkgdown_sha: ~ articles: {} -last_built: 2023-09-15T11:13Z +last_built: 2023-09-15T11:28Z diff --git a/section_fair_astro.html b/section_fair_astro.html index 3244f15..0e9a74c 100644 --- a/section_fair_astro.html +++ b/section_fair_astro.html @@ -387,7 +387,7 @@

      To be Findable

      -
      +

      The first step before reusing the data is to be able to find them. The metadata and data should be easy to find for both humans and @@ -409,7 +409,7 @@

      To be Accessible

      -
      +

      Once the data can be found, the user needs to know how to access them. That could include authentification and authorisation. The @@ -435,7 +435,7 @@

      To be Interoperable

      -
      +

      Those data can then be combined with different datasets, and interoperate with other applications or workflows for analysis, storage, @@ -455,7 +455,7 @@

      To be Reusable

      -
      +

      The ultimate goal of FAIR is to optimise the reuse of data. To achieve this, metadata and data should be well-described, including a @@ -656,7 +656,7 @@

      Give me a hint

      -
      +

      Look for these objects in Simbad.

      Can you find them?

      @@ -671,7 +671,7 @@

      Why is it improper?

      -
      +

      I1) Insufficient precision in RA and DEC causes confusion. In this case, it could correspond to many objects and different surveys.

      @@ -700,7 +700,7 @@

      Recommended usage

      -
      +

      R1) LAMOST J221750.59+210437.1 and SDSS J221746.82+210424.1 are potential matches for this incomplete name

      @@ -955,7 +955,7 @@

      Why is it improper?

      -
      +

      The quality of the measurement is indicated using a superscript. Providing this information using an extra column will make the table @@ -971,7 +971,7 @@

      Recommended usage

      -
      +
Names as published Possible interpretation
@@ -1152,7 +1152,7 @@

List of solutions

-
+
Object Redshift
diff --git a/section_submit_data.html b/section_submit_data.html index 44dfb53..ff00251 100644 --- a/section_submit_data.html +++ b/section_submit_data.html @@ -516,7 +516,7 @@

A. ‘Title of the paper’, ‘Authors’, ‘Reference’

-
+
  • Title of the paper: Title as written in paper
  • @@ -537,7 +537,7 @@

    B. ‘Abstract’ and ‘Description’

    -
    +
    • Abstract: Describes the scientific results @@ -562,7 +562,7 @@

      C. ‘Byte-by-byte Description of file’

      -
      +

      This section describes the structure of each data files (files with the .dat extension). This description is made in a tabular form, each

Names as published Possible interpretation