id stringlengths 21 21 | kind stringclasses 3
values | options listlengths 2 6 | target listlengths 2 6 | state stringlengths 160 239 | question stringclasses 7
values | domain stringclasses 1
value | family stringclasses 1
value | source stringclasses 1
value |
|---|---|---|---|---|---|---|---|---|
v3_75e49d97008d3ac9_c | choice | [
"institutional",
"domain_specific",
"general",
"restricted"
] | [
0.08,
0,
0.04,
0.88
] | A code repository includes participant identifiers without a DUA; additionally is stored with a 3-2-1 backup strategy. Context: before the personnel departure, during the system migration. Reported by the review queue. | Repository choice for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_5080ab9300d65f90_c | choice | [
"compliant",
"fixable",
"non_compliant",
"violation"
] | [
0,
0.01,
0.14,
0.85
] | A collaboration archive has 3 undocumented transformations; additionally includes participant identifiers without a DUA. Context: before the personnel departure, under an active deadline. Reported by the supervisor. | Compliance status for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_d21707b56c38149a_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.06,
0.79,
0.15
] | A lab notebook has an embargo expiring next month; additionally contains PHI on an open share. Context: before the personnel departure, shortly after a software update. Reported by the monitoring system. | Rate privacy risk for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_ba42ee58f4765043_c | choice | [
"compliant",
"fixable",
"non_compliant",
"violation"
] | [
0,
0,
0.07,
0.93
] | A collaboration archive contains PHI on an open share; additionally follows the FAIR principles assessment. Context: before the personnel departure, immediately after go-live. Reported by the on-call engineer. | Compliance status for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_1ec9887e823e00d5_n | noul | [
"false",
"true"
] | [
0.13,
0.87
] | A collaboration archive uses community-standard file formats; additionally has versioned metadata and checksums. Context: for the journal submission, during normal operations. Reported by the automated check. | Is this scenario one where: the dataset is fit for sharing? | research_data_mgmt | science | yuri_v3 |
v3_b76efeaeb2f0c874_c | choice | [
"compliant",
"fixable",
"non_compliant",
"violation"
] | [
0,
0.04,
0.16,
0.8
] | A collaboration archive follows the FAIR principles assessment; additionally includes participant identifiers without a DUA. Context: before the personnel departure, while legacy systems are still active. Reported by the automated check. | Compliance status for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_99dd37a676791e5f_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.06,
0.7,
0.23
] | A lab notebook has versioned metadata and checksums; additionally contains PHI on an open share. Context: for the journal submission, following a recent audit. Reported by the on-call engineer. | Rate privacy risk for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_e29dabe0453ee0ea_c | choice | [
"compliant",
"fixable",
"non_compliant",
"violation"
] | [
0,
0,
0.06,
0.94
] | A dataset has versioned metadata and checksums; additionally contains PHI on an open share. Context: before the personnel departure, during the quarterly review. Reported by the supervisor. | Compliance status for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_a8ce9d25ca1508f0_c | choice | [
"compliant",
"fixable",
"non_compliant",
"violation"
] | [
0,
0.17,
0.68,
0.15
] | A code repository lacks a data dictionary; additionally follows the FAIR principles assessment. Context: before the personnel departure, under an active deadline. Reported by the automated check. | Compliance status for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_d26c80d9df7b3ce7_c | choice | [
"institutional",
"domain_specific",
"general",
"restricted"
] | [
0.34,
0.2,
0.45,
0.01
] | A code repository follows the FAIR principles assessment; additionally has versioned metadata and checksums. Context: for the journal submission, with staffing at reduced levels. Reported by the monitoring system. | Repository choice for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_65422b5e777435fd_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.09,
0.12,
0.18,
0.44,
0.15,
0.02
] | A dataset has versioned metadata and checksums; additionally has an embargo expiring next month. Context: under the funder mandate, mid-incident. Reported by the operator. | Rate reusability for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_8c7cff0ecd25711e_c | choice | [
"institutional",
"domain_specific",
"general",
"restricted"
] | [
0.95,
0,
0,
0.05
] | A lab notebook has an embargo expiring next month; additionally uses community-standard file formats. Context: in the institutional repository, with a new vendor onboarded. Reported by the on-call engineer. | Repository choice for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_58f6875383165bae_c | choice | [
"compliant",
"fixable",
"non_compliant",
"violation"
] | [
0.01,
0.12,
0.55,
0.32
] | A collaboration archive lacks provenance for the derived columns; additionally has versioned metadata and checksums. Context: for the journal submission, mid-incident. Reported by the on-call engineer. | Compliance status for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_a92ceb0855601c82_n | noul | [
"false",
"true"
] | [
0.93,
0.07
] | A collaboration archive includes participant identifiers without a DUA; additionally lacks a data dictionary. Context: under the funder mandate, under reduced staffing. Reported by the operator. | Is this scenario one where: the dataset is fit for sharing? | research_data_mgmt | science | yuri_v3 |
v3_f9a00c77ff750561_c | choice | [
"institutional",
"domain_specific",
"general",
"restricted"
] | [
0.03,
0.01,
0.02,
0.94
] | A dataset has an embargo expiring next month; additionally has 3 undocumented transformations. Context: under the funder mandate, during normal operations. Reported by the review queue. | Repository choice for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_222ab128d4655531_n | noul | [
"false",
"true"
] | [
0.68,
0.32
] | A collaboration archive has an embargo expiring next month; additionally has versioned metadata and checksums. Context: for the journal submission, during the system migration. Reported by the monitoring system. | Is this scenario one where: a privacy review is required? | research_data_mgmt | science | yuri_v3 |
v3_f8cb30964a7abf25_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.02,
0.03,
0.22,
0.56,
0.16,
0.01
] | A lab notebook has 3 undocumented transformations; additionally is stored with a 3-2-1 backup strategy. Context: in the institutional repository, with a new vendor onboarded. Reported by the supervisor. | Rate reusability for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_843fdc8e318d8e2c_c | choice | [
"compliant",
"fixable",
"non_compliant",
"violation"
] | [
0.02,
0.28,
0.49,
0.21
] | A code repository has 3 undocumented transformations; additionally has versioned metadata and checksums. Context: in the institutional repository, under reduced staffing. Reported by the operator. | Compliance status for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_77a5610fc9d1f441_c | choice | [
"compliant",
"fixable",
"non_compliant",
"violation"
] | [
0,
0.18,
0.49,
0.33
] | A collaboration archive includes participant identifiers without a DUA; additionally has an embargo expiring next month. Context: in the institutional repository, as part of a compliance sweep. Reported by the supervisor. | Compliance status for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_f3302e7a85babafc_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0,
0.22,
0.78
] | A dataset lacks a data dictionary; additionally contains PHI on an open share. Context: in the institutional repository, during the holiday freeze. Reported by the monitoring system. | Rate privacy risk for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_b523b38b6b15c2a9_n | noul | [
"false",
"true"
] | [
0.07,
0.93
] | A dataset is stored with a 3-2-1 backup strategy; additionally contains PHI on an open share. Context: for the journal submission, while legacy systems are still active. Reported by the on-call engineer. | Is this scenario one where: a privacy review is required? | research_data_mgmt | science | yuri_v3 |
v3_73b5563b59b9fc58_c | choice | [
"institutional",
"domain_specific",
"general",
"restricted"
] | [
0.31,
0.04,
0.04,
0.61
] | A lab notebook has an embargo expiring next month; additionally uses community-standard file formats. Context: before the personnel departure, while legacy systems are still active. Reported by the automated check. | Repository choice for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_3278aaa91a9199a8_n | noul | [
"false",
"true"
] | [
0.5,
0.5
] | A dataset follows the FAIR principles assessment; additionally uses community-standard file formats. Context: before the personnel departure, with a new vendor onboarded. Reported by the operator. | Is this scenario one where: a privacy review is required? | research_data_mgmt | science | yuri_v3 |
v3_e4b699930cd90405_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.1,
0.28,
0.4,
0.21,
0.01,
0
] | A code repository is stored with a 3-2-1 backup strategy; additionally lacks provenance for the derived columns. Context: in the institutional repository, while legacy systems are still active. Reported by the review queue. | Rate privacy risk for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_d996ae89a1c2d228_n | noul | [
"false",
"true"
] | [
0.89,
0.11
] | A lab notebook is stored with a 3-2-1 backup strategy; additionally lacks provenance for the derived columns. Context: under the funder mandate, during normal operations. Reported by the monitoring system. | Is this scenario one where: the documentation is sufficient? | research_data_mgmt | science | yuri_v3 |
v3_31ed960cbbacee74_c | choice | [
"institutional",
"domain_specific",
"general",
"restricted"
] | [
0.29,
0.16,
0.06,
0.49
] | A lab notebook has 3 undocumented transformations; additionally lacks a data dictionary. Context: before the personnel departure, while legacy systems are still active. Reported by the supervisor. | Repository choice for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_d6d5474eaf01ef0f_c | choice | [
"institutional",
"domain_specific",
"general",
"restricted"
] | [
0.96,
0.02,
0.01,
0.01
] | A dataset lacks a data dictionary; additionally uses community-standard file formats. Context: in the institutional repository, immediately after go-live. Reported by the supervisor. | Repository choice for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_e1ea71809dc4e99c_n | noul | [
"false",
"true"
] | [
0.94,
0.06
] | A lab notebook lacks provenance for the derived columns; additionally follows the FAIR principles assessment. Context: in the institutional repository, following a recent audit. Reported by the on-call engineer. | Is this scenario one where: the documentation is sufficient? | research_data_mgmt | science | yuri_v3 |
v3_36f54ae51e9439f3_c | choice | [
"compliant",
"fixable",
"non_compliant",
"violation"
] | [
0,
0.02,
0.09,
0.89
] | A code repository follows the FAIR principles assessment; additionally includes participant identifiers without a DUA. Context: for the journal submission, with staffing at reduced levels. Reported by the supervisor. | Compliance status for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_1db34a792eca79e3_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.49,
0.37,
0.09,
0.05,
0,
0
] | A code repository is stored with a 3-2-1 backup strategy; additionally has versioned metadata and checksums. Context: under the funder mandate, while legacy systems are still active. Reported by the supervisor. | Rate privacy risk for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_7d4a8a3b4429ac65_n | noul | [
"false",
"true"
] | [
0.97,
0.03
] | A dataset has an embargo expiring next month; additionally contains PHI on an open share. Context: under the funder mandate, while on-call rotation changed. Reported by the on-call engineer. | Is this scenario one where: the dataset is fit for sharing? | research_data_mgmt | science | yuri_v3 |
v3_90851e30d5cdd6f9_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.05,
0.84,
0.11
] | A dataset has 3 undocumented transformations; additionally includes participant identifiers without a DUA. Context: in the institutional repository, during the system migration. Reported by the review queue. | Rate privacy risk for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_0cb8cb1760009f0b_n | noul | [
"false",
"true"
] | [
0.22,
0.78
] | A lab notebook uses community-standard file formats; additionally has versioned metadata and checksums. Context: under the funder mandate, during the morning shift. Reported by the review queue. | Is this scenario one where: the dataset is fit for sharing? | research_data_mgmt | science | yuri_v3 |
v3_0f240dfe2969e9a9_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0,
0.02,
0.09,
0.68,
0.2
] | A code repository has versioned metadata and checksums; additionally contains PHI on an open share. Context: before the personnel departure, mid-incident. Reported by the operator. | Rate reusability for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_eb4d507e19384563_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.0101,
0,
0,
0.0303,
0.6869,
0.2727
] | A lab notebook lacks provenance for the derived columns; additionally contains PHI on an open share. Context: for the journal submission, during an external partner integration. Reported by the automated check. | Rate reusability for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_67a285e863ee6b6f_n | noul | [
"false",
"true"
] | [
0.59,
0.41
] | A lab notebook follows the FAIR principles assessment; additionally lacks a data dictionary. Context: under the funder mandate, mid-incident. Reported by the supervisor. | Is this scenario one where: a privacy review is required? | research_data_mgmt | science | yuri_v3 |
v3_f5030f64803bd943_n | noul | [
"false",
"true"
] | [
0.93,
0.07
] | A lab notebook lacks provenance for the derived columns; additionally follows the FAIR principles assessment. Context: in the institutional repository, immediately after go-live. Reported by the automated check. | Is this scenario one where: the documentation is sufficient? | research_data_mgmt | science | yuri_v3 |
v3_f61ac6f4ef33a724_c | choice | [
"compliant",
"fixable",
"non_compliant",
"violation"
] | [
0,
0.07,
0.75,
0.18
] | A code repository lacks provenance for the derived columns; additionally lacks a data dictionary. Context: for the journal submission, at the end of the fiscal period. Reported by the supervisor. | Compliance status for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_75c049062bece37e_n | noul | [
"false",
"true"
] | [
0.12,
0.88
] | A collaboration archive has versioned metadata and checksums; additionally includes participant identifiers without a DUA. Context: before the personnel departure, with a new vendor onboarded. Reported by the operator. | Is this scenario one where: a privacy review is required? | research_data_mgmt | science | yuri_v3 |
v3_d8ce8f6af16e330c_n | noul | [
"false",
"true"
] | [
0.65,
0.35
] | A code repository is stored with a 3-2-1 backup strategy; additionally uses community-standard file formats. Context: for the journal submission, with a new vendor onboarded. Reported by the on-call engineer. | Is this scenario one where: the documentation is sufficient? | research_data_mgmt | science | yuri_v3 |
v3_a40233546405a1bd_c | choice | [
"institutional",
"domain_specific",
"general",
"restricted"
] | [
0.97,
0,
0,
0.03
] | A collaboration archive has versioned metadata and checksums; additionally has 3 undocumented transformations. Context: in the institutional repository, immediately after go-live. Reported by the review queue. | Repository choice for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_f79a6ed090c7159f_n | noul | [
"false",
"true"
] | [
0.05,
0.95
] | A lab notebook is stored with a 3-2-1 backup strategy; additionally includes participant identifiers without a DUA. Context: before the personnel departure, following a recent audit. Reported by the automated check. | Is this scenario one where: a privacy review is required? | research_data_mgmt | science | yuri_v3 |
v3_4eceac99529c034e_n | noul | [
"false",
"true"
] | [
0.82,
0.18
] | A collaboration archive lacks a data dictionary; additionally is stored with a 3-2-1 backup strategy. Context: for the journal submission, during peak load. Reported by the automated check. | Is this scenario one where: the dataset is fit for sharing? | research_data_mgmt | science | yuri_v3 |
v3_99fb7fca6a9c97f2_n | noul | [
"false",
"true"
] | [
0.93,
0.07
] | A dataset has 3 undocumented transformations; additionally is stored with a 3-2-1 backup strategy. Context: in the institutional repository, with a new vendor onboarded. Reported by the operator. | Is this scenario one where: the documentation is sufficient? | research_data_mgmt | science | yuri_v3 |
v3_757a65158d8df771_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.02,
0.4,
0.34,
0.23,
0.01
] | A dataset includes participant identifiers without a DUA; additionally uses community-standard file formats. Context: under the funder mandate, while on-call rotation changed. Reported by the monitoring system. | Rate privacy risk for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_9e9bfc40dbe5fbdb_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.02,
0.1,
0.71,
0.17
] | A lab notebook contains PHI on an open share; additionally uses community-standard file formats. Context: before the personnel departure, while on-call rotation changed. Reported by the on-call engineer. | Rate privacy risk for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_d0c96647fb62b5c4_c | choice | [
"compliant",
"fixable",
"non_compliant",
"violation"
] | [
0.04,
0.32,
0.56,
0.08
] | A collaboration archive follows the FAIR principles assessment; additionally lacks a data dictionary. Context: before the personnel departure, under an active deadline. Reported by the supervisor. | Compliance status for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_5dde2f0df5a28b18_c | choice | [
"institutional",
"domain_specific",
"general",
"restricted"
] | [
0.04,
0.02,
0,
0.94
] | A collaboration archive contains PHI on an open share; additionally has versioned metadata and checksums. Context: under the funder mandate, under an active deadline. Reported by the operator. | Repository choice for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_c6203c9b143fa91d_n | noul | [
"false",
"true"
] | [
0.67,
0.33
] | A code repository has versioned metadata and checksums; additionally uses community-standard file formats. Context: for the journal submission, under an active deadline. Reported by the on-call engineer. | Is this scenario one where: the documentation is sufficient? | research_data_mgmt | science | yuri_v3 |
v3_0f43b0a9992fd03e_n | noul | [
"false",
"true"
] | [
0.67,
0.33
] | A collaboration archive follows the FAIR principles assessment; additionally has versioned metadata and checksums. Context: for the journal submission, under reduced staffing. Reported by the supervisor. | Is this scenario one where: a privacy review is required? | research_data_mgmt | science | yuri_v3 |
v3_c02bc7e4c52af7f1_n | noul | [
"false",
"true"
] | [
0.98,
0.02
] | A collaboration archive lacks a data dictionary; additionally has 3 undocumented transformations. Context: in the institutional repository, with staffing at reduced levels. Reported by the automated check. | Is this scenario one where: the documentation is sufficient? | research_data_mgmt | science | yuri_v3 |
v3_c53804d3bc791b2d_c | choice | [
"institutional",
"domain_specific",
"general",
"restricted"
] | [
0.03,
0.01,
0.01,
0.95
] | A code repository has an embargo expiring next month; additionally lacks provenance for the derived columns. Context: before the personnel departure, under reduced staffing. Reported by the monitoring system. | Repository choice for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_51e733f8e03c7236_c | choice | [
"compliant",
"fixable",
"non_compliant",
"violation"
] | [
0,
0.01,
0.15,
0.84
] | A code repository contains PHI on an open share; additionally has an embargo expiring next month. Context: under the funder mandate, with staffing at reduced levels. Reported by the review queue. | Compliance status for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_545d07b0549dc47f_c | choice | [
"institutional",
"domain_specific",
"general",
"restricted"
] | [
0.04,
0,
0.01,
0.95
] | A dataset has 3 undocumented transformations; additionally includes participant identifiers without a DUA. Context: under the funder mandate, during normal operations. Reported by the review queue. | Repository choice for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_253e388a73788b41_n | noul | [
"false",
"true"
] | [
0.04,
0.96
] | A lab notebook contains PHI on an open share; additionally has versioned metadata and checksums. Context: in the institutional repository, during an external partner integration. Reported by the review queue. | Is this scenario one where: a privacy review is required? | research_data_mgmt | science | yuri_v3 |
v3_ab9a3ff7ab14dd02_n | noul | [
"false",
"true"
] | [
0.08,
0.92
] | A code repository includes participant identifiers without a DUA; additionally is stored with a 3-2-1 backup strategy. Context: before the personnel departure, following a recent audit. Reported by the automated check. | Is this scenario one where: a privacy review is required? | research_data_mgmt | science | yuri_v3 |
v3_d1c9a725b84f9a6a_n | noul | [
"false",
"true"
] | [
0.88,
0.12
] | A lab notebook has an embargo expiring next month; additionally contains PHI on an open share. Context: for the journal submission, immediately after go-live. Reported by the monitoring system. | Is this scenario one where: the documentation is sufficient? | research_data_mgmt | science | yuri_v3 |
v3_3d42547ed596e2a5_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.53,
0.4,
0.05,
0.02,
0,
0
] | A collaboration archive has versioned metadata and checksums; additionally follows the FAIR principles assessment. Context: under the funder mandate, during normal operations. Reported by the operator. | Rate privacy risk for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_b781f00135ee6dd3_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0,
0.01,
0.07,
0.76,
0.15
] | A code repository has an embargo expiring next month; additionally contains PHI on an open share. Context: before the personnel departure, with staffing at reduced levels. Reported by the on-call engineer. | Rate reusability for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_342b24bfd1a8aa3e_c | choice | [
"compliant",
"fixable",
"non_compliant",
"violation"
] | [
0,
0.01,
0.1,
0.89
] | A collaboration archive follows the FAIR principles assessment; additionally includes participant identifiers without a DUA. Context: in the institutional repository, during peak load. Reported by the operator. | Compliance status for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_fc0b68127763f0a1_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0,
0.35,
0.65
] | A lab notebook includes participant identifiers without a DUA; additionally contains PHI on an open share. Context: under the funder mandate, during an external partner integration. Reported by the monitoring system. | Rate privacy risk for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_0d60d8c803c6eba4_n | noul | [
"false",
"true"
] | [
0.85,
0.15
] | A lab notebook is stored with a 3-2-1 backup strategy; additionally lacks a data dictionary. Context: before the personnel departure, with staffing at reduced levels. Reported by the monitoring system. | Is this scenario one where: the documentation is sufficient? | research_data_mgmt | science | yuri_v3 |
v3_e8b8fcc64c8088d1_n | noul | [
"false",
"true"
] | [
0.9,
0.1
] | A dataset contains PHI on an open share; additionally uses community-standard file formats. Context: before the personnel departure, during an external partner integration. Reported by the review queue. | Is this scenario one where: the documentation is sufficient? | research_data_mgmt | science | yuri_v3 |
v3_7b5a4f59eb5b330a_c | choice | [
"compliant",
"fixable",
"non_compliant",
"violation"
] | [
0,
0.17,
0.68,
0.15
] | A code repository lacks provenance for the derived columns; additionally has an embargo expiring next month. Context: before the personnel departure, as part of a compliance sweep. Reported by the supervisor. | Compliance status for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_b06dac4dd45e37ab_n | noul | [
"false",
"true"
] | [
0.95,
0.05
] | A collaboration archive includes participant identifiers without a DUA; additionally lacks provenance for the derived columns. Context: under the funder mandate, during the quarterly review. Reported by the operator. | Is this scenario one where: the dataset is fit for sharing? | research_data_mgmt | science | yuri_v3 |
v3_7c9e2cbb9bdf2301_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.24,
0.43,
0.31,
0.01
] | A code repository has versioned metadata and checksums; additionally includes participant identifiers without a DUA. Context: under the funder mandate, at the end of the fiscal period. Reported by the automated check. | Rate privacy risk for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_a20538f0719adbfb_c | choice | [
"institutional",
"domain_specific",
"general",
"restricted"
] | [
0.46,
0,
0,
0.54
] | A code repository contains PHI on an open share; additionally follows the FAIR principles assessment. Context: in the institutional repository, during normal operations. Reported by the review queue. | Repository choice for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_30a3f74e8de80b2b_c | choice | [
"institutional",
"domain_specific",
"general",
"restricted"
] | [
0.49,
0.07,
0.15,
0.29
] | A code repository lacks provenance for the derived columns; additionally has 3 undocumented transformations. Context: under the funder mandate, during the system migration. Reported by the automated check. | Repository choice for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_1e8ade503fc009e3_n | noul | [
"false",
"true"
] | [
0.94,
0.06
] | A lab notebook has 3 undocumented transformations; additionally is stored with a 3-2-1 backup strategy. Context: under the funder mandate, under an active deadline. Reported by the supervisor. | Is this scenario one where: the documentation is sufficient? | research_data_mgmt | science | yuri_v3 |
v3_e2780a48f1ea0393_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.14,
0.37,
0.18,
0.27,
0.03,
0.01
] | A collaboration archive has versioned metadata and checksums; additionally is stored with a 3-2-1 backup strategy. Context: before the personnel departure, during a scheduled maintenance window. Reported by the operator. | Rate reusability for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_14035da46ce6333b_c | choice | [
"institutional",
"domain_specific",
"general",
"restricted"
] | [
0.06,
0.02,
0.01,
0.91
] | A collaboration archive is stored with a 3-2-1 backup strategy; additionally has an embargo expiring next month. Context: under the funder mandate, during a scheduled maintenance window. Reported by the monitoring system. | Repository choice for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_45bb4b420bb90e0e_c | choice | [
"institutional",
"domain_specific",
"general",
"restricted"
] | [
0.03,
0.01,
0,
0.96
] | A collaboration archive has an embargo expiring next month; additionally contains PHI on an open share. Context: before the personnel departure, with a new vendor onboarded. Reported by the on-call engineer. | Repository choice for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_4397520cc2998f02_n | noul | [
"false",
"true"
] | [
0.6,
0.4
] | A code repository has an embargo expiring next month; additionally has versioned metadata and checksums. Context: for the journal submission, during a scheduled maintenance window. Reported by the automated check. | Is this scenario one where: the documentation is sufficient? | research_data_mgmt | science | yuri_v3 |
v3_6be8347a4269db0b_c | choice | [
"institutional",
"domain_specific",
"general",
"restricted"
] | [
0.19,
0.35,
0.33,
0.13
] | A code repository has versioned metadata and checksums; additionally lacks provenance for the derived columns. Context: for the journal submission, under an active deadline. Reported by the on-call engineer. | Repository choice for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_214f19d717d588cf_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.23,
0.36,
0.27,
0.13,
0.01,
0
] | A lab notebook is stored with a 3-2-1 backup strategy; additionally lacks provenance for the derived columns. Context: for the journal submission, during peak load. Reported by the supervisor. | Rate privacy risk for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_ef63cd19669486d3_c | choice | [
"compliant",
"fixable",
"non_compliant",
"violation"
] | [
0.02,
0.19,
0.32,
0.47
] | A code repository has versioned metadata and checksums; additionally has 3 undocumented transformations. Context: in the institutional repository, under an active deadline. Reported by the monitoring system. | Compliance status for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_f8f8e7f0f255f4aa_c | choice | [
"compliant",
"fixable",
"non_compliant",
"violation"
] | [
0.81,
0.06,
0.09,
0.04
] | A dataset uses community-standard file formats; additionally follows the FAIR principles assessment. Context: for the journal submission, during a scheduled maintenance window. Reported by the monitoring system. | Compliance status for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_5cbfbf41331eb6b7_n | noul | [
"false",
"true"
] | [
0.06,
0.94
] | A collaboration archive has an embargo expiring next month; additionally contains PHI on an open share. Context: under the funder mandate, while on-call rotation changed. Reported by the operator. | Is this scenario one where: a privacy review is required? | research_data_mgmt | science | yuri_v3 |
v3_6071c323fc25d569_n | noul | [
"false",
"true"
] | [
0.96,
0.04
] | A code repository has 3 undocumented transformations; additionally follows the FAIR principles assessment. Context: under the funder mandate, with a new vendor onboarded. Reported by the monitoring system. | Is this scenario one where: the documentation is sufficient? | research_data_mgmt | science | yuri_v3 |
v3_566f7d027e2ed835_n | noul | [
"false",
"true"
] | [
0.06,
0.94
] | A collaboration archive is stored with a 3-2-1 backup strategy; additionally contains PHI on an open share. Context: before the personnel departure, mid-incident. Reported by the automated check. | Is this scenario one where: a privacy review is required? | research_data_mgmt | science | yuri_v3 |
v3_dbf652a25f346be0_c | choice | [
"institutional",
"domain_specific",
"general",
"restricted"
] | [
0.12,
0.02,
0.01,
0.85
] | A collaboration archive has 3 undocumented transformations; additionally has an embargo expiring next month. Context: under the funder mandate, at the end of the fiscal period. Reported by the monitoring system. | Repository choice for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_78348db5c412bc39_c | choice | [
"compliant",
"fixable",
"non_compliant",
"violation"
] | [
0,
0.04,
0.19,
0.77
] | A lab notebook has an embargo expiring next month; additionally includes participant identifiers without a DUA. Context: in the institutional repository, during an external partner integration. Reported by the on-call engineer. | Compliance status for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_a3b77c6d061f8769_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.03,
0.8,
0.17
] | A lab notebook has 3 undocumented transformations; additionally contains PHI on an open share. Context: for the journal submission, while on-call rotation changed. Reported by the monitoring system. | Rate privacy risk for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_6ca319eb7fe70836_c | choice | [
"compliant",
"fixable",
"non_compliant",
"violation"
] | [
0.02,
0.29,
0.38,
0.31
] | A lab notebook has 3 undocumented transformations; additionally follows the FAIR principles assessment. Context: before the personnel departure, under reduced staffing. Reported by the review queue. | Compliance status for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_0d749e9d81591239_n | noul | [
"false",
"true"
] | [
0.98,
0.02
] | A lab notebook contains PHI on an open share; additionally includes participant identifiers without a DUA. Context: before the personnel departure, during an external partner integration. Reported by the operator. | Is this scenario one where: the dataset is fit for sharing? | research_data_mgmt | science | yuri_v3 |
v3_a38287a0185d3293_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.16,
0.34,
0.28,
0.21,
0.01,
0
] | A code repository follows the FAIR principles assessment; additionally has 3 undocumented transformations. Context: under the funder mandate, during a scheduled maintenance window. Reported by the operator. | Rate privacy risk for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_920244500e371475_n | noul | [
"false",
"true"
] | [
0.75,
0.25
] | A dataset is stored with a 3-2-1 backup strategy; additionally uses community-standard file formats. Context: for the journal submission, during normal operations. Reported by the review queue. | Is this scenario one where: a privacy review is required? | research_data_mgmt | science | yuri_v3 |
v3_96d7529f21e49533_n | noul | [
"false",
"true"
] | [
0.84,
0.16
] | A collaboration archive uses community-standard file formats; additionally includes participant identifiers without a DUA. Context: before the personnel departure, during a scheduled maintenance window. Reported by the on-call engineer. | Is this scenario one where: the dataset is fit for sharing? | research_data_mgmt | science | yuri_v3 |
v3_29312decbeaf402d_c | choice | [
"institutional",
"domain_specific",
"general",
"restricted"
] | [
0.06,
0.09,
0.72,
0.13
] | A code repository uses community-standard file formats; additionally lacks provenance for the derived columns. Context: before the personnel departure, shortly after a software update. Reported by the on-call engineer. | Repository choice for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_61c5646b8870fd50_n | noul | [
"false",
"true"
] | [
0.64,
0.36
] | A collaboration archive lacks a data dictionary; additionally is stored with a 3-2-1 backup strategy. Context: in the institutional repository, during peak load. Reported by the review queue. | Is this scenario one where: a privacy review is required? | research_data_mgmt | science | yuri_v3 |
v3_4f3c152e5f99bfbf_n | noul | [
"false",
"true"
] | [
0.6,
0.4
] | A collaboration archive follows the FAIR principles assessment; additionally has an embargo expiring next month. Context: for the journal submission, under reduced staffing. Reported by the monitoring system. | Is this scenario one where: a privacy review is required? | research_data_mgmt | science | yuri_v3 |
v3_b39e905d17d09041_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.02,
0.09,
0.34,
0.48,
0.07,
0
] | A collaboration archive has 3 undocumented transformations; additionally is stored with a 3-2-1 backup strategy. Context: for the journal submission, as part of a compliance sweep. Reported by the review queue. | Rate privacy risk for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_389067745d5709aa_c | choice | [
"compliant",
"fixable",
"non_compliant",
"violation"
] | [
0.04,
0.51,
0.35,
0.1
] | A dataset has versioned metadata and checksums; additionally lacks a data dictionary. Context: in the institutional repository, at the end of the fiscal period. Reported by the on-call engineer. | Compliance status for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_85cc854bcea61e3e_c | choice | [
"institutional",
"domain_specific",
"general",
"restricted"
] | [
0.19,
0.16,
0.25,
0.4
] | A dataset has versioned metadata and checksums; additionally lacks provenance for the derived columns. Context: before the personnel departure, with a new vendor onboarded. Reported by the on-call engineer. | Repository choice for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_1e7bae1bf2da8041_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0,
0.11,
0.89
] | A code repository contains PHI on an open share; additionally follows the FAIR principles assessment. Context: in the institutional repository, immediately after go-live. Reported by the review queue. | Rate privacy risk for this scenario on a 0-5 scale. | research_data_mgmt | science | yuri_v3 |
v3_dc8049374ede3fe1_c | choice | [
"institutional",
"domain_specific",
"general",
"restricted"
] | [
0.65,
0.17,
0.16,
0.02
] | A collaboration archive has versioned metadata and checksums; additionally is stored with a 3-2-1 backup strategy. Context: under the funder mandate, with staffing at reduced levels. Reported by the automated check. | Repository choice for this scenario. | research_data_mgmt | science | yuri_v3 |
v3_0c67267a335f50ce_n | noul | [
"false",
"true"
] | [
0.86,
0.14
] | A code repository contains PHI on an open share; additionally has versioned metadata and checksums. Context: for the journal submission, following a recent audit. Reported by the operator. | Is this scenario one where: the documentation is sufficient? | research_data_mgmt | science | yuri_v3 |
v3_cbb65cdcfc61090f_n | noul | [
"false",
"true"
] | [
0.05,
0.95
] | A dataset contains PHI on an open share; additionally has versioned metadata and checksums. Context: under the funder mandate, during the system migration. Reported by the on-call engineer. | Is this scenario one where: a privacy review is required? | research_data_mgmt | science | yuri_v3 |
v3_82236c80115e221b_n | noul | [
"false",
"true"
] | [
0.85,
0.15
] | A code repository has an embargo expiring next month; additionally is stored with a 3-2-1 backup strategy. Context: in the institutional repository, immediately after go-live. Reported by the automated check. | Is this scenario one where: the dataset is fit for sharing? | research_data_mgmt | science | yuri_v3 |
v3_45d5c9ff8c5213ca_n | noul | [
"false",
"true"
] | [
0.91,
0.09
] | A code repository has versioned metadata and checksums; additionally lacks a data dictionary. Context: in the institutional repository, during the holiday freeze. Reported by the operator. | Is this scenario one where: the documentation is sufficient? | research_data_mgmt | science | yuri_v3 |
End of preview. Expand in Data Studio
JEV corpus - research_data_mgmt
7,859 typed calibrated decision rows from the jev-distill-corpus-v3 corpus (domain: research_data_mgmt).
Each row is one typed decision: kind (noul / choice / score), a state, a question, options, and a target probability distribution over the options.
Part of the per-domain split of SargeDev/jev-distill-corpus-v3 - the full corpus in one repo.
Domains:
- Downloads last month
- -