Move OEP_Upload_Process tutorials to legacy #223

Remove links to them Provide alternative links
OpenEnergyPlatform · Jul 4, 2024 · d97d733 · d97d733
1 parent 5a674c3
commit d97d733
Show file tree

Hide file tree

Showing 5 changed files with 3 additions and 3 deletions.
diff --git a/docs/courses/07_metadata.md b/docs/courses/07_metadata.md
@@ -49,8 +49,8 @@ Metadata plays a crucial role in organizing, managing, and understanding informa
 ## What other tools to work with OEMetadata are there?
 
 - A tool for [metadata conversion and integration is `OMI`](https://github.com/OpenEnergyPlatform/omi)
-- An additional helpful tool for publishing a set of data with associated metadata is `oem2orm`. It can translate table descriptions from metadata into a database structure via an object relational mapper. That way it can take a valid pair of data and metadata and upload it directly to the OEP. The structures of both need to be valid. :oep-icon-code: [A tutorial on the use of oem2orm](../tutorials/99_other/OEP_Upload_Process_Data_and_Metadata_oem2orm.ipynb) explains the upload process
-- The `oep client` is a tool that can create, upload, download and delete tables. It also downloads and updates metadata. It's more versatile than oem2orm but less focussed on metadata. There is a :oep-icon-code: [tutorial using oem2orm and oepclient](../tutorials/99_other/OEP_Upload_Process_Data_and_Metadata_oep-client.ipynb) to upload some data and metadata
+- An additional helpful tool for publishing a set of data with associated metadata is [oem2orm](https://github.com/OpenEnergyPlatform/oem2orm). It can translate table descriptions from metadata into a database structure via an object relational mapper. That way it can take a valid pair of data and metadata and upload it directly to the OEP. The structures of both need to be valid.
+- The `oep client` is a tool that can create, upload, download and delete tables. It also downloads and updates metadata. It's more versatile than oem2orm but less focussed on metadata. There is a :oep-icon-code: [tutorial using the oep-client](../../tutorials/02_oep_client/02_client_python_upload/) to upload some data and metadata
 - How to :oep-icon-code: [Validate that your metadata is a datapackage](../tutorials/99_other/getting_started_with_OEMetadata.ipynb)
 
 ## Supplementary material and further readings

diff --git a/...d_Process_Data_and_Metadata_oem2orm.ipynb → ...d_Process_Data_and_Metadata_oem2orm.ipynb b/...d_Process_Data_and_Metadata_oem2orm.ipynb → ...d_Process_Data_and_Metadata_oem2orm.ipynb
diff --git a/...ad_Process_Data_and_Metadata_oem2orm.json → ...ad_Process_Data_and_Metadata_oem2orm.json b/...ad_Process_Data_and_Metadata_oem2orm.json → ...ad_Process_Data_and_Metadata_oem2orm.json
diff --git a/...rocess_Data_and_Metadata_oep-client.ipynb → ...rocess_Data_and_Metadata_oep-client.ipynb b/...rocess_Data_and_Metadata_oep-client.ipynb → ...rocess_Data_and_Metadata_oep-client.ipynb
diff --git a/docs/tutorials/99_other/getting_started_with_OEMetadata.ipynb b/docs/tutorials/99_other/getting_started_with_OEMetadata.ipynb
@@ -35,7 +35,7 @@
         "\n",
         "### Introduction\n",
         "\n",
-        "OpenenEnergyMetadata(OEM) is a standardised metadata format. OEM are used to provide relevant information about a dataset on the OEP \"It´s data explaining the data :)\". OEM are mandatory for oficially publishing data on the OEP, because this will clarify any licensing issues in advance and also provide context for the review that is part of every publishing process. You can find more information about publishing your data in the [publishing guidebook](https://openenergyplatform.github.io/academy/tutorials/99_other/OEP_Research_Data_Publishing_Guidebook/). There are descriptions on how to upload OEM on the Open Energy Platform itself with a [wizard](https://openenergyplatform.org/dataedit/wizard/) and a more [technical description](https://github.com/OpenEnergyPlatform/tutorial/blob/develop/upload/OEP_Upload_Process_Data_and_Metadata_oem2orm.ipynb)) for using the API in scrips. If a dataset has already been uploaded to the OEP, then the metadata can be viewed via the [detailed view](https://openenergyplatform.org/dataedit/view/climate/szenariendb_gwp#MetaInformation) of a table. You just scroll down to the \"Meta Information\" section and there they are. The OEP also offers functions for creating, editing and downloading metadata. These functions can also be found on the detail view. Make sure to [sign in](https://openenergyplatform.org/user/login/?next=/) to the OEP in advance to get writing access.\n",
+        "OpenenEnergyMetadata(OEM) is a standardised metadata format. OEM are used to provide relevant information about a dataset on the OEP \"It´s data explaining the data :)\". OEM are mandatory for oficially publishing data on the OEP, because this will clarify any licensing issues in advance and also provide context for the review that is part of every publishing process. You can find more information about publishing your data in the [publishing guidebook](https://openenergyplatform.github.io/academy/tutorials/99_other/OEP_Research_Data_Publishing_Guidebook/). There are descriptions on how to upload OEM on the Open Energy Platform itself with a [wizard](https://openenergyplatform.org/dataedit/wizard/) and a more [technical description](https://openenergyplatform.github.io/academy/tutorials/02_oep_client/02_client_python_upload/)) for using the API in scrips. If a dataset has already been uploaded to the OEP, then the metadata can be viewed via the [detailed view](https://openenergyplatform.org/dataedit/view/climate/szenariendb_gwp#MetaInformation) of a table. You just scroll down to the \"Meta Information\" section and there they are. The OEP also offers functions for creating, editing and downloading metadata. These functions can also be found on the detail view. Make sure to [sign in](https://openenergyplatform.org/user/login/?next=/) to the OEP in advance to get writing access.\n",
         "\n",
         "### Compatible with frictionless data\n",
         "\n",