Closed floradanna closed 3 years ago
About point 2, beware that data privacy is not restricted to human data. There are other sources of sensitive data, such as observations/locations of endangered species, protocols for synthesis of explosives and other dangerous chemicals, and a few others. We probably will not need to address these explicitly, but it may bear at least devoting one "problem" subsection to why data may be sensitive, that points to the human data domain page for more detail on that most common case.
About point 4, I'm not sure what is the best approach.
I agree with everything else :)
Same for industrial biotechnology and intellectual property
Carole
From: Daniel Faria [mailto:notifications@github.com] Sent: 14 October 2020 15:33 To: elixir-europe/rdm-toolkit Cc: Subscribed Subject: Re: [elixir-europe/rdm-toolkit] Suggestion on the "Your problem" section (#127)
About point 2, beware that data privacy is not restricted to human data. There are other sources of sensitive data, such as observations/locations of endangered species, protocols for synthesis of explosives and other dangerous chemicals, and a few others. We probably will not need to address these explicitly, but it may bear at least devoting one "problem" subsection to why data may be sensitive, that points to the human data domain page for more detail on that most common case.
About point 4, I'm not sure what is the best approach.
I agree with everything else :)
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/elixir-europe/rdm-toolkit/issues/127#issuecomment-708443365, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABXWMLYCAZTRUR3BHLIIDQLSKWZAXANCNFSM4SQJGBMQ.
Do some of the topics repeat the topics of the life cycle diagram, though? Data processing, analysis, and sharing are in the diagram, for example, so does that mean there will be two pages about the same thing?
@martin-nc Well, the idea was that life cycle stage pages provide a broad overview of the stage, and problem pages get into concrete problems and solutions, so there shouldn't be overlap in scope. You are right that having the exact same title for a problem page and a life cycle stage page will be confusing and should be avoided. But for now, I think it is OK to give these as broad categories for which we want contentathon participants to detail concrete problems, and figure out the naming issue later.
dear @floradanna
Hi @pinarpink This is also a good option. I will also add the link to the tools inventory in the agenda.
Maybe point 4 can be considered under a "computational reproducibility" topic in the "your problem" section ? Or is it opening a Pandora's box ?
Description @DanFaria and I propose to add new pages to be shown under "Your problem" section, in the sidebar of the website. These pages should refer to broad topics, so that more specific problems can be added later as subpages. Showing additional "broad topic pages" could help contributors better identify the needed guideline and content. The proposed page titles below are based on the questions listed in "Your role" pages.
(Already there) Data storage: estimate data volume, storage during the project, storage after the project, computational storage, costs, ... (Already there) Metadata management: ontology, data documentation (README), ... (Already there) Security & privacy: data access control, personal and sensitive data, ... (Already there) Data sustainability: data preservation, data archiving, file format, identifier, archiving, ... (Already there) Compliance monitoring and measurement: ... (Already there) Data transfer: from provider to compute resource, ...
I would also suggest to: 1) Explain somewhere the sub-topics expected under each "broad topic page" in Your problem section. 2) Keep only "Data security" (data access control) and address "Privacy" in Human Data domain to avoid repetition. 3) Rename "Data sustainability" with a more clear term (is it the same of data preservation or archiving?) 4) Think about guideline for management of software (metadata, licence, repositories, versioning, etc): it could go in "Your domain", or could be treated as any other data type, or could have a dedicated page under "Your problem".