Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
saeon_odp_standard_operating_procedures [2022/05/27 09:54] – created lindsay | saeon_odp_standard_operating_procedures [2022/10/21 12:30] (current) – [Data Provisioning] lindsay | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Standard Operating Procedures for the SAEON Open Data Platform | + | ===== Standard Operating Procedures for the SAEON Open Data Platform ===== |
+ | The SAEON Open Data Platform (ODP) standard operating procedures (SOPs) document covers practical measures that fall outside the content covered by the [[SAEON Data Policy|SAEON Data Policy]] and [[SAEON Preservation Policy|SAEON Preservation Policy]]. | ||
- | ===== Service Level Agreements and Data agreements | + | ==== Service Level Agreements and Data agreements ==== |
- | + | The conditions of publishing in the SAEON ODP are laid out in the [[saeon_data_policy|SAEON Data Policy]]. All projects and data agreements will be filtered through either the SAEON Managing Director, the Data Management Committee or the uLwazi Node Manager. Small data submissions, | |
- | The conditions of publishing in the SAEON ODP are laid out in the SAEON Data Policy. All projects and data agreements will be filtered through either the SAEON Managing Director, the Data Management Committee or the uLwazi Node Manager. Small data submissions, | + | |
==== Data Provisioning ==== | ==== Data Provisioning ==== | ||
+ | Prior to data being submitted, data provisioning will be organised based off of the project specifications in the data agreement or from [[data_management_planning|data management plans]] submitted to the Curation team and sent to the Infrastructure team if additional provisioning is needed. | ||
+ | |||
+ | ==== Curation ==== | ||
- | Prior to data being submitted, data provisioning will be organised based off of the project specifications in the data agreement or from data management plans submitted | + | The steps for making |
- | === Curation === | + | A curator will work with the data provider to receive the Submission Information Package (SIP), either over email or via FTP if the submission is too large to send via email, they will then assess the SIP and ensure that the data is in the correct format, can be opened and is formatted according |
- | + | ||
- | The steps for making data available in the SAEON ODP are currently executed by members of the data curation team because user registration has not been fully implemented. In future, the system | + | |
- | A curator will work with the data producer to receive the Submission Information Package (SIP), either over email or via FTP if the submission is too large to send via email, they will then assess | + | The curator will then make any necessary edits on the metadata, such as adding a DOI if one was requested, adding administrative metadata and small edits such as making |
- | The curator will then make any necessary edits on the metadata, such as adding a DOI if one was requested, adding administrative metadata | + | When the metadata is complete the curator will then convert |
- | When the metadata | + | Once the record |
- | Once the record is published the first curator will then send the data producer the DOI, or link to the metadata record if no DOI was requested. | ||
- | == Changes to existing metadata records or archived datasets == | + | ==== Changes to existing metadata records or archived datasets |
+ | Minor changes to an existing metadata record, such as adjusting a bounding box or fixing a spelling error can be done in the ODP by a curator if a data provider requests it. Major changes, such as adding an additional creator or changing the lineage statement which would affect how users of the data would either cite or process the data, would require a new version of the metadata record. | ||
- | Minor changes to an existing metadata record, such as adjusting a bounding box or fixing a spelling error can be done in the ODP by a curator if a data producer requests it. Major changes, such as adding an additional creator or changing the lineage statement which would affect how users of the data would either cite or process the data, would require a new version of the metadata record. | + | Any changes to the data itself will require a new version of that data to be archived and a new metadata record |
- | Any changes to the data itself will require a new version | + | We discourage |
- | We discourage the removal of archived and published datasets but if a data producer needs to remove a dataset then the metadata record will be updated to indicate that that has happened. | ||